Upgrading/Migrating.. the story continues!
Together with a colleague of mine we are trying to upgrade a large Sharepoint 2003 environment to 2007. And ofcourse, as always, this is not a typical straightforward configuration. This environment uses the Shared Services feature (aka the SSP of 2003) and the thing why I'm blogging is the use of user profiles. Now we (or at least I) didn't knew the exact details until yesterday when we found a document about this subject. So if you see the image below you are seeing the difference between a MySite and a Public Profile site, I always thought that these two pages were linked to each other therefore implying that an user who has a public profile page always had a MySite as well. But this is not true, so when migrating you've to migrate the user profiles and the MySite.
Apparently in the huge migration document (Perform a gradual upgrade with shared services) that guides you through the upgrade process, it only states the following about upgrading/migrating the userprofiles :
- Configure profiles and audiences to be synchronized between SharePoint Portal Server 2003 and Office SharePoint Server 2007
So piece of cake huh? We just configure the profiles and audiences to be synchronized.. easy! ;) Luckily there is another document (Upgrade large SharePoint Portal Server 2003 intranet portals to SharePoint Server 2007) that describes this process, although it's not referenced anywhere in the upgrade guide, it clearly explains how to upgrade/migrate the existing user profiles and personal sites. In short you've got to do the following :
- Install Sharepoint 2007
- Assign services to the server
- Create two webapplications to host the SSP Admin site and the SSP MySites (so don't create a SSP first(!!))
- Use STSADM with the restoressp command using the 'old' Sharepoint2003_PROF database
- Migrate the parent portal that hosted the personal sites
- Migrate the personal sites
- You're done! (migrating the profiles and personal sites)
8 comments:
Some additional comments: make sure search services are configured and started before you run the restoressp command. Else, the message 'the new indexer must be enabled and installed' appears.
Second, make sure that when you create a web application, it is an extended web application. Just creating them the 'old' way through IIS Admin is not advisable. Just go to Central Admin -> Application management -> create web application. It's easier that way. ;-)
Robin, really helpful blog! You might want to check out the 6 articles by Jennifer Neumann on The Final Candidate. She's been testing and analyzing MOSS 2007 in depth and has published her findings here: http://www.finalcandidate.com/en/tandp/Pages/default.aspx
Thank you for pointing that out. There's another good document on this topic. You are probably talking about this document, but nonetheless, the MySites Migration Strategy paragraph there is very interesting.
Your blog is fabulous - you have saved me. Thank You!!!
Sara Porter
Thanks Sara :)
Link Update to the Upgrade Whitepaper
http://technet.microsoft.com/en-us/library/cc263270.aspx
Frank
I've been using Infopath for years and feel it is a valuable tool. I'm curious to see what the path forward for the product is though. Great article
Helloo nice blog
Post a Comment