We have two ways to upgrade from MOSS 2007 SP2 (64bit) to SP2010. ( It doesnot talk about customization upgrade, This article primarily talks about what happens to SSP )
- Inplace upgrade
- Database attach and upgrade
Inplace upgrade in detail
- To do inplace upgrade make sure that MOSS 2007 is applied with SP2 and latest CU (preferred Oct 2009 CU). It should also be running on Windows Server 2008/2008 R2 64 bit and using SQL Server 64 bit.
- Run stsadm –o preupgradecheck command before you do an upgrade. Please go through the report which gets generated as it gives very useful information.
- When you do inplace upgrade most of the services and customization will be intact.
- SSP Database will be upgrade into the following :
i. User profile service application
ii. Search service application
iii. Session State service application
iv. Application registry service application & BDC
v. Excel service application
vii. WSS Usage database
After upgrade we need to move the taxonomy. Use the Move- SPProfileManagedMetadataProperty PowerShell cmdlet to upgrade profile taxonomy data to the Taxonomy database and reconnect the data to the Managed Metadata and User Profiles service applications. · The User Profiles service proxy and Managed Metadata service proxy must be in the same proxy group to upgrade and to use the data.
- For Excel services, create unattended service account.
- Need to re-configure BDC in SP2010.
- SSP Admin site will be available which will have BDC profile pages.
Database attach and upgrade in detail
- User Profile Service Application and Managed Metadata service application
i. Before doing a database attach to SP2010, you need to have managed metadata service running in the same proxy group as User Profile SA.
ii. First backup all data in MOSS 2007.
iii. Restore the SSP database and MySite database in SP2010’s SQL Server.
iv. Create a new web application for MySite host in SP2010. Attach the SSP MySite Database to this new web application. (Mount-SPContentDatabase)
v. Create a new User Profile Service Application by using New-SPProfileServiceApplication. In this command, use the SSP database.
vi. Once the command has run successfully, you will see SocialDB and SyncDB also get created.
vii. Now create a new service application proxy using New-SPProfileServiceApplicationProxy. Make use this is in the default group ( or same group as new user profile service appln.)
viii. Go into Central Admin-> manage service application->User profile Service application, click manage in ribbon and add Administration.
ix. Go to the Setup Mysites within the UPSA and give the URL of MySite host.
x. Do an incremental sync ( Just to make sure 🙂 )
2.Search Service Application : Unfortunately we will need to do full crawl of the content if we do database attach and migration.
3. InfoPath Forms : When you upgrade by using the database attach upgrade approach, you must export any administrator-deployed form templates (XSN files) and data connection files (UDCX files) before migrating, then import them to the new farm after migrating by using the Export- SPInfoPathAdministrationFiles Windows PowerShell cmdlet. If the URL of the new server is different from the URL of the previous server, you can run the Update-SPInfoPathAdminFileUrl Windows PowerShell cmdlet to update links that are used in the upgraded form templates.
4.Excel services : Need to reconfigure it
5.BDC : It is not upgraded. Need to reconfigure it.