Actually there is no direct path to upgrade/migrate from SPS 2003 to SPS 2010. Unfortunately you must go via the WSSv3/MOSS 2007 stage!
For customers running prior versions of SharePoint, including Windows SharePoint Services 2.0 and SharePoint Portal Server 2003, this means that you must first upgrade to Windows SharePoint Services 3.0 SP2 or Microsoft Office SharePoint Server 2007 SP2 prior to upgrading to 2010 versions.
Please find the full description and how-to approach on our SharePoint Team Blog for this topic:
http://blogs.msdn.com/sharepoint/archive/2010/01/04/planning-for-upgrade-from-sharepoint-portal-server-2003-to-sharepoint-server-2010.aspx
Upgrade/Migration from SharePoint 2010 BETA to RTM:
This is not supported and the BETA bits are only considered for testing and evaluating purposes!
If you have a running BETA setup, you must have to uninstall it and reinstall your farm with the RTM bits.
Even if any upgrade scenario may work, you will not be supported for any issues! Bear that in mind!
Upgrade from WSSv3/MOSS 2007:
As 2010 is only supported on 64bit systems you have to plan your upgrade due to change to from 32bit to 64bit.
Farm insight:
- Pre-upgrade Checker
- Stsadm –o EnumAllWebs
- SPDiag v2
Customizations gathering:
- Stsadm –o ExportIPFSAdminObjects
Upgrade path:
- First of all, you should run the “Pre-Upgrade Checker tool” on your existing WSSv3/MOSS2007 farm!The Pre-Upgrade Checker Command was introduced in SP2, and is being improved in the October 2009 CU to address some shortcomings. The tool identifies farm information and current and potential issues with the farm that you need to know before upgrading. Some of the issues the tool would be looking for are missing site definitions, data orphans and modified content databases.
Modified content databases, specifically, will more than likely cause a problem during upgrade, so you’ve got to back out of those changes before upgrading. The tool will compare the schema of your content databases to an untouched schema. - After the check you have to fix now all logged problems before you really start the upgrade. Otherwise you’ll get into a huge effort to fix certain issues after the upgrade in your new farm. We recommend to fix those problems before the upgrade process by using the output that pre-upgrade checker will provide you.
- Supported is an In-Place or database attach upgrade (Content only). There is no gradual upgrade supported and also no direct upgrade from any earlier version than WSSv3 or MOSS2007. For smaller environments and less or no customizations, the in-place upgrade is a very straight-forward and easy way to upgrade. If you are still on a 32bit system, you need to upgrade first to 64bit systems inside your WSSv3/MOSS 2007 farm prior to start the in-place upgrade!
For all other farms that have customizations, large site counts or big databases, the database attach approach is the best and only one you should use. As mostly, all depends on a solid and robust planning before you consider to upgrade your farm! there is also an upgrade with well documented steps on how to upgrade a standard setup of WSS7MOSS with the windows internal database / SQL express (also known as MSDE database).The prime recommendations are:
– setup a copy of your environment on a 64bit VM
– start an in place upgrade to 2010
– test it, test it, test it…. - On database attach method, you start with an setup of 2010 server from scratch, backup and restore your databases from Moss to 2010 and attaching them to your new 2010 farm. Consider that this will only move your content! The SSP cannot be used here as in 2010 the complete service model has changed and is not compatible with the old SSP model. Also certain custom configurations you may have to have reconfigure them manually again on the new farm.
- After attaching the content DB’S you should check your sites regarding the customizations and custom solutions. For that you’ll have the option to choose “visual upgrade” by sticking on the old MOSS 2007 Layout and view. With this option you can check by using the “preview” to check your customization whether it works on the new layout or not.
The default mode for an upgrade is the Visual Upgrade. Because 2010 ships with all of the 2007 master pages, you can remain in the 2007 UI rather than moving to the 2010 UI. This was Microsoft’s answer to this issue. Farm admins and site admins can preview the new UI without making actual changes to the site itself. There are some incompatibilities with the 2007 UI in 2010, such as the My site host. It requires the new UI due to the social networking enhancements, but all subpages will look just like they do in 2007. - Downtime mitigations:
There is no magic number for the time that an upgrade will take, but Microsoft will be developing documentation to help admins to determine how long a potential upgrade will take. One new feature is the ability to do parallel upgrading of databases, which will run multiple upgrade sessions in parallel. It may take a very long time to upgrade a single database. In my test case, a database with 500MB took almost 12 hours to be finally updated. - The minimum patch level to do an in place or database attach upgrade from WSSv3/MOSS 2007 is at least SP2 but we highly recommend a higher or latest patch level (cumulative updates). Since the august CU and later, there was a whole lot of functionalities included that will help you on the upgrade process such as additional tools to be used prior upgrade to check and/or verify your farm health for the upgrade.
- You’ll have also an dedicated upgrade log per session and its separately error log for each session.
- As always common by handling customizations during an upgrade, you should bear in mind that some things will not work or may have issues which you need to fix afterwards manually.
A detailed example with step-by-step guide on how-to upgrade in-place from MOSS2007 to SPS 2010 will be provided here soon. So please stay tuned and we’ll meet us soon again 😉
greets,
Steve Chen, Support engineer – EMEA GTSC
SharePoint mysteries and more... 