Last time we saw our hero, he was trying to figure out why an existing SharePoint2003 installation that had been upgraded to Microsoft Office SharePoint Server 2007 Beta 2 and finally Microsoft Office SharePoint Server 2007 RTM could not create personal MySites.
After much help from Microsoft Support, it looks like the problem is being caused by a design change between SharePoint 2003 and MOSS 2007. MOSS2007 currently only supports hosting the MySties application at the root of a web application (http://mysites.yourdomain.com and not http://yourdomain.com/mysites).
Microsoft has proposed two solutions to the problem:
- Create a new web application to host the MySites (http://mysites.yourdomain.com). This may be OK for new, vanilla installations but would require a separate SSL certificate as well as more management. Where this will not work well is for an existing installation with tons of existing MySites. This would either cause two locations for MySites or require the migration of existing MySites to the new location.
- Give the application pool account for the existing web application (http://yourdomain.com) farm administrator rights using the Central Administration application. This solution is ok unless your security gurus balk at this. To find this account:
- Open up IIS manager and view the properties of the site in question. Note the application pool that is being used by this site.
- View the properties of the application pool from the first step and look at the identity tab. This is the account that needs Farm Admin rights.
Microsoft is looking at marking this issue as a bug so hopefully it will be changed back to the old way in the near future.
