In the first post we have covered the planning steps and upgrade options you need to consider for your upgrade process , in this post we will perform step by step upgrade from SharePoint portal server 2003 to SharePoint 2010
Upgrade Toolkit for Windows SharePoint Services from 2003 to 2007
Before starting the upgrade from 2003 to 2007 especially for the cases of custom areas and site template of SharePoint portal server 2003, you should be aware of Upgrade Toolkit for Windows SharePoint Services Sites and Templates Guide of which Solution Accelerator Team (SAT) has created a solution accelerator that provides guidance and tools to enable IT Professionals to successfully upgrade their Windows SharePoint Services 2.0 custom sites and templates
When you upgrade from WSS 2.0 to WSS 3.0, your existing SharePoint sites are upgraded to work in the WSS 3.0 environment and the new WSS 3.0 features are applied to them. Also during the upgrade, the default WSS 2.0 site templates are replaced by WSS 3.0 equivalents. This is not true, however, for WSS 2.0 customized sites and site templates―there are no equivalents for them and they do not upgrade correctly.
The Upgrade Toolkit for Windows SharePoint Services Sites and Templates serve two main purposes:
· To provide IT professionals with the guidance and tools that they need to upgrade customized WSS 2.0 sites and site templates to function in a WSS 3.0 environment. The upgraded sites and site templates maintain their customizations and acquire a set of WSS 3.0 features.
· To provide a set of upgraded application templates for Windows SharePoint Services based on those currently published for WSS 2.0 on TechNet and to provide instructions for installing these application templates in a WSS 3.0 environment.
You can download the guide from the following URL
now lets proceed with the upgrade sample
Step 1 In place upgrade for SharePoint 2003 to 2007:
In place upgrade starts by installing SPS2007 at server on which you have already restored a SPS 2003 portal, for the upgrade process no need to install new SQL server, SharePoint 2007 works with both SQL 2005 and SQL 2000 which usually installed for server that runs SPS 2003.
Start by MOSS (Microsoft Office SharePoint) installer, Double click on setup.exe
Enter the product License key then click on ‘Next’
Accept the Microsoft Software License Terms, then click on ‘continue’
On the windows below choose ’Yes, perform a Gradual upgrade. This will allow the existing installation to function and enable you to upgrade web sites in batches. This is best for large installations or where web sites have been extensively customized’ and click on ‘install now’
When the page below is displaying , uncheck ‘ Run the SharePoint Products and Technologies Configuration Wizard now’ then click on ‘close’.
Launch of pre-scan tool
Before proceeding run the pre-scan tools (the pre-scan tools shows errors that may occur during upgrading process such as orphan’s links)
Pre scan tool can be found at SystemDrive:\Programm Files\Common files\Microsoft Shared\web server extensions\12\BIN
Launch DOS console and type cd Drive:\Programm Files\Common files\Microsoft Shared\web server extensions\12\BIN
Type the command prescan /c preupgradescanconfig.xml /all, scan process will take place resulting in two files one of them is XML file and the other is txt file they will be created in current folder.
Click here for more details about the Prescan tool also Here you can find a good article describing prescan in more details
Most probably you will see the screen above, as it’s expected that you will have some errors
Open the log files and search for “error” word and starting fixing them, here you can find helpful steps that help fixing the error such as deleting the orphaned sites.
In our case custom site definitions caused the issue , and those site definition are created to reflect organization look and feel and special branding images, so resetting them to initial state will not cause a big issue as we already planning to recreate the branding.
In our case we need to fix custom site definitions that caused the errors by resetting them to their initial state ,thanks to Upgrade Toolkit for Windows SharePoint Services Sites and Templates Guide that helped us resetting the site definitions to its initial state, also please check this blog How to Upgrade an Area based on a Custom Site Definition.
Lunch configuration wizard as indicated in screen below
Click Next ,You will see a warning for some services that need to restarted, click ‘yes’
Information message getting displayed asking either you have language packs to be installed click ‘OK’
Check ‘No, I want to create a new server farm’, then click on button ‘Next’
Specify Configuration Database Settings
Database server: Server Name
Database name: The name you want to give to the new database
Specify Database Access Account
Password: SPSAdmin password
In Configure SharePoint Central Administration Web Application screen check ‘negotiate (Kerberos)
Click ‘yes’ on the ‘warning windows’ , then click Next
Configuration is in progress, then this screen is shown
now we need to Reset Site Definition
open the portal and from Site settings/Modify all site settings
Click on reset to site definition
Now navigate to SharePoint Central Administration , then Click on ‘Operations’ at the left side of the page, then Click on ‘Site content upgrade statues under ‘upgrade and migration’
On the next windows click on ‘Begin Upgrade’
Fill in the needed information then click ok
Upgrading should be done in stages as maximum of 500 sites can be checked at once.
now after selecting the sites , click on upgrade sites
You will have this page which shows you the status of upgrading process
now proceed with other sites by clicking on continue upgrade
now we should have reached to the middle stage , the site is now upgraded to 2007 version, in the next post we will proceed with next steps for upgrading to SharePoint 2010
Right after running the configuration wizard you mention that "Now is the time to revert the site definitions". The instructions you're outlining are lost on me at the moment. At the moment, we've essentially just introduced the MOSS implementation on
the system with the central admin web app and configuration database. Going "to the portal" would still be going to the WSS 2.0 side where the options for "Site Actions --> Site Settings" doesn't appear to exist.