As you can see I’ve upgraded the blog to Microsoft SharePoint Foundation Server 2010 Beta 2 which was the result of an interesting upgrade journey and some jiggery pokery.
The original blog resided on a server with MOSS and I was lucky enough to have the opportunity to start from scratch on a new server rather than an in situ upgrade. So I have my standalone server install with Windows Server 2008 R2, critical updated to the hilt and I’m doing a default flavour install of SharePoint 2010 using MSDE pretty simple stuff. Run the Microsoft Baseline Security Analyzer 2.1 and voila ready to restore my backed up site.
Eh naw! The backup came from the old server and even with the xml file SharePoint 2010 will not have anything to do with the backup, it point blank refuses to see it at all. No problem I’ll just download SQL Server Management Studio and connect direct to the MSDE SharePoint database. Waste of time, doesn’t work as the SharePoint install has created an SA account, which I have no password for, and of course Builtin\Users is locked down. Using OSQL was futile as well as I can’t escalate my logged in user account and I can’t log in as SA. Same permission issues trying to use SharePoint 2010 Management Shell. So I have a new install with a backup I can’t restore to.
Faced now with a complete uninstall of SharePoint or changing all the accounts that SharePoint runs under which I really don’t want to do on a Beta version I came up with a cunning plan.
Installed another version of MSDE, restored my database to the new version, used mount-spcontentdatabase to attach my database and changed the SQL Server location for content databases.
Not ideal but it works, all the SharePoint related databases are on the first MSDE instance and my content db is on the second instance.
When I’m done playing with this I’ll blow it away and install it tidier but hey for the time being it works!