This is Part 5 in a series of migrating SharePoint from SBS 2003 to SBS 2011. Series posts are:
Introduction – Overview
Part 1 – Caveats and Considerations
Part 2 – Preparation steps on v2
Part 3 – Upgrading v2 database to WSS v3
Part 4 – Attaching upgraded database to WSS v3
Part 5 – Check WSSv3 for migration to Foundation 2010
Part 6 – Move database to SBS 2011
Part 7 – Post migration steps and considerations
In this part we are going to run a check to ensure that our original SBS 2003 Companyweb site (now in Windows SharePoint Services v3) will migrate to SharePoint Foundation 2010.
Prior to any upgrade from WSS v3 it is recommended that you run the stsadm –preupgradecheck from the command line.
To do this go to the command prompt as an administrator on the WSS v3 server. Change to the directory c:\program files\common files\microsoft shared\web server extensions\12\bin. At this location type the following command and press ENTER.
stsadm –o preupgradecheck
You should now see a number of checks being run on your system like so:
When the process is complete you will then see a HTML summary page displayed like so:
Scroll to the bottom of the page to see any errors like shown here:
It is recommended that you read the report carefully and note any warnings and errors as they may prevent successful migration.
Some errors may not be relevant. For example in screen shot above you will note that the error indicates that the system is not running on a 64 bit operating system. This will not apply in the situation where a migration to new hardware is being undertaken.
The –preupgradecheck option is only available on WSS v3 installations that have WSS v3 Service Pack 2 installed.
If everything looks good then you are ready to forklift the WSS v3 databases onto SBS 2011 and attach them to SharePoint Foundation 2010 which I’ll cover in the next part.
CIAOPS 