Migrating Sites from WSS 3.0 to SharePoint Foundation 2010 : CloudBlue Technical Support

Additional Information

Starting from Odin Automation 6.0, new installations of WSS 3.0 are not supported. Starting from Odin Automation 7.0, WSS 3.0 is not supported. Existing WSS 3.0 sites must be migrated to SharePoint Foundation 2010 before upgrading to Odin Automation 7.0. This article describes how to manually migrate sites from WSS 3.0 to SharePoint Foundation 2010.

Note: The detailed description of the migration from WSS 3.0 to SharePoint Foundation 2010 is provided in the http://technet.microsoft.com/en-us/library/cc303311 article.

Before Migration

Deploy a new SharePoint Foundation 2010 farm using the instructions provided in the OA Windows Shared Hosting Deployment Guide > Deploying Windows SharePoint Hosting > Installing Microsoft SharePoint Foundation 2010. There are the following deployment requirements:
- The SharePoint Foundation 2010 farm must be deployed in the AD domain with installed WSS 3.0.
- The SharePoint Foundation 2010 farm must contain the same Language Packs and Site Templates as the WSS 3.0 farm contains.
In PCP, reconfigure WSS 3.0 Resource Types, Service Templates, and Service Plans to switch provisioning from WSS 3.0 to SharePoint Foundation 2010. It will affect all existing WSS 3.0 subscriptions: existing WSS 3.0 sites will continue working; new sites will be provisioned in the SharePoint Foundation 2010 farm.

Migration

Perform the following actions for each WSS 3.0 site:

Obtain and write down the properties of the WSS 3.0 site, which is being migrated. The following properties must be prepared:

Name of the site administrator
Storage quota limit and warning limit
Site language

These properties can be obtained from the OA system database:

plesk=> select d.domain_id, d.name as domain_name, su.hsu_id as admin_user_id, ss.notify_limit as warn_limit, ss.hard_limit as quota_limit, ss.root_site_lang as lang_id from domains d join subdomain_services sd on sd.zone_id=d.domain_id join iis_addons a on a.addon_id=sd.subds_id join iis_sps_sites ss on ss.sps_site_id=a.sps_site_id join iis_sps_users su on su.sps_site_id=ss.sps_site_id and su.type=4 where d.domain_id=<DOMAIN_ID>;

Also, these properties can be obtained from CCP.

If the WSS 3.0 site has an exclusive IP address assigned, log in to CCP and switch the WSS 3.0 site to a shared IP address. If it is required, keep the corresponding SSL certificate and private key.
In CCP, create a temporary SharePoint Foundation 2010 site. This site will be used to keep Service Users during the migration. There are the following recommendations and requirements:
- Create this site on a subdomain. The DNS registration of the subdomain is not required.
- This site must be created in an exclusive web application.
- The Service User prepared at the step 1 must be specified as the site administrator.
- If it is required, increase resource limits of the subscription in PCP.
- Make sure all SharePoint Foundation 2010 provisioning tasks are executed.
On the front-end server of the WSS 3.0 farm, switch the WSS 3.0 site to the read-only mode. For example, this can be done in the following way:
```
stsadm -o setsitelock -url <SITE_URL> -lock readonly
```
On the front-end server of the WSS 3.0 farm, create a backup of the content of the WSS 3.0 site (as a precaution). For example, this can be done in the following way:
```
stsadm -o backup -url <SITE_URL> -filename <FILE_NAME>
```
On the front-end server of the WSS 3.0 farm, run the pre-upgrade checker for the WSS 3.0 site. See the http://technet.microsoft.com/en-au/library/cc287628.aspx article for details.
On the database server of the WSS 3.0 farm, create a backup of the Content Database of the WSS 3.0 site. See the http://technet.microsoft.com/en-au/library/cc287634.aspx article for details.
In CCP, remove the WSS 3.0 hosting service from the corresponding domain.There are the following requirements and recommendations:
- Do not remove the domain.
- Make sure the Content Database of the WSS 3.0 site is in the read-write mode.
- Make sure all WSS 3.0 tasks are processed.
In CCP, add the SharePoint Foundation 2010 hosting service to the corresponding domain. There are the following requirements and recommendations:
- Use the values prepared at the step 1.
- This SharePoint Foundation 2010 site must be created in an exclusive web application.
- Make sure all SharePoint Foundation 2010 tasks are processed.
On the front-end server of the SharePoint Foundation 2010 farm, switch the just created SharePoint Foundation 2010 site to the read-only mode. For example, this can be done in the following way:
```
stsadm -o setsitelock -url <SITE_URL> -lock readonly
```
On the database server of the SharePoint Foundation 2010 farm, create a backup of the Content Database of the SharePoint Foundation 2010 site (as a precaution).
On the front-end server of the SharePoint Foundation 2010 farm, remove the Content Database from the SharePoint Foundation 2010 site. For example, this can be done in the following way:
```
stsadm.exe -o deletecontentdb -url <SITE_URL> -databasename <CONTENT_DATABASE_NAME>
```
The name of the Content Database can be obtained from the OA system database:
```
select * from iis_sps_app_dbs where sps_app_id = (select sps_app_id from iis_sps_sites  where url = '<DOMAIN_NAME>');
```
Perform the upgrade of the Content Database:
- On the database server of the SharePoint Foundation 2010 farm, restore the Content Database from the backup created at the step 7 into the Content Database removed at the step 12. During restoring, the first Content Database must overwrite the second Content Database.
- On the front-end server of the SharePoint Foundation 2010 farm, add the just restored Content Database to the SharePoint Foundation 2010 site. For example, this can be done in the following way: stsadm.exe -o addcontentdb -url -databasename
- Review the upgrade logs.
See the http://technet.microsoft.com/en-au/library/cc287634.aspx article for details.
If the removed WSS 3.0 site had an exclusive IP address assigned, log in to CCP and switch the SharePoint Foundation 2010 site to an exclusive IP address. See the step 2 for details. Note, it is not guaranteed that the same exclusive IP address will be assigned to the site. If it is required, add the corresponding SSL certificate and private key to the SharePoint Foundation 2010 site.
Make sure the SharePoint Foundation 2010 site works.
On the front-end server of the SharePoint Foundation 2010 farm, switch the SharePoint Foundation 2010 site to the read-write mode. For example, this can be done in the following way:
```
stsadm -o setsitelock -url <SITE_URL> -lock none
```
In CCP, remove the temporary SharePoint Foundation 2010 site created at the step 3.
In PCP, adjust resource limits of the subscription. See the step 3 for details.

After Migration

Start crawling and indexing to update the SharePoint Foundation 2010 search database for the migrated sites. This can be done in the following way:
- Open the SharePoint Foundation 2010 Central Administration web site.
- Go to Central Administration > Monitoring > Timer Jobs > **Review Job Definitions.
- Start the SharePoint Foundation Search Refresh job.
Uninstall the WSS3.0 (type: other) package from the WSS 3.0 host.
Remove the WSS 3.0 front-end and database hosts from OA, if it is applicable.

Known Issues

Uninstallation of WSS3.0-ServerAdminTemplates/WSS3.0-SiteAdminTemplates Package Might Fail

The uninstallation of either WSS3.0-ServerAdminTemplates or WSS3.0-SiteAdminTemplates package might fail with the error 'WSS3TemplatesTool.exe' is not recognized as an internal or external command, operable program or batch file. To resolve this problem, perform the following actions:

Upload the WSS3TemplatesTool.zip file to the host where the package is installed.
Extract the content of the file.
Place the content of the file to the C:\Program Files\SWsoft\PEM\ directory.
Start the uninstallatoin of the package again.

CloudBlue Technical Support