TFS with WSS 3 to SharePoint Foundation 2010 upgrade

During the weekend we successfully upgraded a production server from TFS2010Beta2/WSS3 to TFS 2010 RTM/SharePoint Foundation2010 RTM. The new challenge in this, apart from the usual upgrade of a production server, was to include upgrading WSS3 to SharePoint Foundation 2010.

Migration scenario
In this case we went for the Server Migration/upgrade scenario, which is very good if you need to verify and test our upgrade routines. This was very important as we to include the move from WSS to SharePoint Foundation 2010 in the upgrade and the WSS upgrade procedure hasn't made it into the official installation documentation yet, so we had to find the right way before we went for the big move.

Don't forget the InstanceId
If you migrate your server to a new hardware for testing purposes, or simply keeps the original server on the network, you have to change the instanceid of your server. Buck Hodges has a post on this, including information on how to change instanceid in TFS 2010. http://blogs.msdn.com/buckh/archive/2006/10/17/creating-a-new-server-from-an-old-one-beware-of-the-instanceid.aspx

Installation of SharePoint Foundation 2010
This was really simple, once I got the install of SharePoint Foundation 2010 right. Sadly to say it took me several tries getting a new unwanted separate SQL instance for SharePoint. If you want to use your existing SQL instance you have to select Server Farm installation and then Complete Server Farm. IF you select that path, you can point out your existing SQL Server instance during configuration.

Upgrade from WSS to SharePoint Foundation 2010
Searching for information how to upgrade tfs & wss to SPF 2010 I found this posts http://sharepointgeorge.com/2009/upgrading-content-database-sharepoint-2010-database-attach-method/
During verification of content db it prompted for two non blocking missing components, as expected, as I had not configured TFS and it SharePoint extensions yet.
Attaching the content db using stsadm -o addcontentdb -url -databasename resulted in an attached and upgraded content database up and running according to the Managed content databases pages in SharePoint Central Administration. Browsing to team project portals did howevere not work at this stage.

After configuring TFS and upgrading the team project collection witch installs the TFS add-ons to SharePoint, browsing to the project portals worked fine as far as we could se.

The upgrade process in short steps
Install Server roles according to TFS installation
Install SQL Server according to TFS installation
Install SQL Server SP1 Cumulative update package 2, KB 970315 (http://support.microsoft.com/kb/970315)
Restore Reporting Services

• Stop Reporting services
• Restore backup,
• Start
• Restore encryption keys
• Remove Orginal server from scale out deployment
• Verify

Install SharePoint Foundation 2010 PreReq
Restart
Install SharePoint Foundation

• Select Server Farm,
• Select Complete
• Configure
• Create New Farm
• Use existing SQL server

Install Team Foundation Server
Import wss3 content database

• Verify using SharePoint 2010 Management Shell and run Test-SPContentDatabase –Name -WebApplication
• 2 Missing components
• Attach database stsadm -o addcontentdb -url -databasename

Configure TFS
Upgrade team project collection
Update Instance Id

• iisreset /stop
• tfsconfig changeserverid /sqlinstance: /databasename:Tfs_Configuration
• tfsconfig registerdb /sqlinstance: /databaseName:Tfs_Configuration
• iisreset /start
• net start tfsjobagent

Upgrading TFS 2010 RTM from pre-release versions

Today I upgraded one of our internal pre-release server and moved in to a new machine. What before in the old days with TFS2008 could be a real painful experience taking several hours or even days to perform could now mostly be handled in an hour.

Preparations
This post is simply a brief description of the main steps and what to do and expect. If you want a more detailed information and as preparation always is the key to success I recommend you to read the following

• Microsoft Team Foundation 2010 Install guide
• VS ALM Rangers TFS 2010 Upgrade guide at codeplex
• Bryan Krigers post on TFS 2010 Upgrade
• SSW's Rules To Better TFS 2010 Migration

Backup and In place upgrade
The first step is to backup the current environment, be it databases or taking a snapshot of your existing environment. Once that's done Its time to uninstall the previous installed pre-release versions. You can leave the .Net framework as it will be upgraded, but TFS2010 Beta2/RC must be uninstalled. After removing the Pre release versions simply install TFS2010 RTM, It's a very easy and quite fast but did take me a reboot to finish it.
Once installed its time to configure your server. If your moving from prerelease versions it's important that you select Upgrade in the first page of the configuration wizard. Follow the steps of the wizard and then you finish the upgrade you will have an upgraded Team Project Collection.

Move to new machine = Detach, Move, Attach
If you want to move to a new clean machine (without any previous installed beta software) you simply Detach your newly upgraded team project collection using Team Foundation Administrative Console. Once detached backup the database TFS_MyProjectcollectionName to file using SQL Manager.
Now it's time to move to a new fresh start. Simply Install and configure TFS2010 RTM on a clean machine. After its done, restore the previous backed up database to the new SQL Server using SQL Manager. Once installed its time to attach, simply point out the database and attach it to your server and you now have your upgraded team project collection up and running on your new server.