This is Part 2 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
I am going to assume that you have done your backups and updates on the source SBS 2003 server.
If you have enabled full text search on SBS 2003 Companyweb (by migrating the databases to the full version of SQL from MSDE) you will firstly need to disable prior to the migration.
Disabling Full Text Search SBS 2003
The easiest way to tell whether full text indexing has been enabled on WSS v2 is simply to view the WSS v2 site. To do this, simply open a web browser and type http://companyweb into the address. If full text indexing has indeed been enabled you will see the search box in the top right of the window.
Full text indexing on WSS v2 needs to be disabled prior to any migration.
To disable full text indexing on WSS v2 logon to the SBS 2003 server as an administrator and select Start | Administrative Tools | SharePoint Central Administration.
When the Central Administration site appears scroll down to the bottom of the screen.
Under the Component Configuration section select the Configure full-text search link.
You should now see a check box indicating that full-text search is enabled. Simply uncheck this box.
And press the OK button to save the new configuration.
After pressing OK the system will now process you changes and return you to the Central Administration site.
You can now proceed with the WSS v2 migration.
1. Ensure that http://companyweb is operational.
2. Download the prescan.exe utility from:
and copy it to your SBS 2003 server.
3. Open a command prompt on the console and run prescan.exe like so:
At the command prompt type prescan /all and press Enter. The scanning tool will examine the existing SharePoint v2 databases and report if there are any issues that may arise when you attempt to migrate. When the process is successful close the DOS prompt. Note, that running prescan does not in any way affect the existing SharePoint v2 database operations, it does however make a minor change to the databases that is required prior to any migration. Thus, you need to run this prescan tool for the migration to succeed. So beware that a small change is made to the databases but this shouldn’t affect their operation in any way.
If there issues they will need to be addressed and resolved before you continue with the migration.
3. The next step is to stop the SharePoint v2 database service so that the existing databases can be copied to a new location. To do this go Start | Administrative Tools | Services.
Locate the service named MSSQL$SBSSHAREPOINT, right mouse click on the service and select Stop from the list that appears.
When this process is complete you should see nothing in the Status column for that service, this indicates that the service is not running. Close the Services window.
4. You now need to locate the original SharePoint v2 databases. Normally these will be located in <install drive>:\program files\microsoft sql\server\MSSQL$SHAREPOINT. Typically, the files will be named STS_<servername>_1.mdf and STS_<servername>_1.log.LDF (in this case STS_VMSBS2003P_1).
Right mouse click on both of these files and select Copy from the menu that appears.
Move to the location where you wish the new databases to be located (on a WSS v3 server typically) and paste the files into that directory.
Once the databases have been copied they need to be attached to the SQL server associated with your installation of WSS v3. I’ll cover this in the next part of the series.
You can now restart the service named MSSQL$SBSSHAREPOINT on the SBS 2003 server so that Companyweb continues to operate. Remember though, if you make changes to the version of Companyweb on the SBS 2003 server AFTER you have copied the databases you’ll need to re-migrate to incorporate these changes.
This will be the last we’ll need from the SBS 2003 server.