This category has been archived
TFS 2010 has been replaced by TFS 2012 - if you're moving to TFS 2012, see our Rules to Better TFS 2012 Migration.
Update: TFS 2010 has been replaced by TFS 2012 - if you're moving to TFS 2012, see our Rules to Better TFS 2012 Migration.
In this page we will look at upgrading an existing TFS2008 server to TFS2010. We assume you are using a single server configuration and have a DNS entry setup for external access at tfs.yourdomain.com.
Upgrading Team Foundation Server can be a daunting task. Be assured that things have become easier and if you follow this guide, it will minimize your downtime.
If you still need help, visit Application Lifecycle Management and book in a consultant.
There are many options for migrating to TFS 2010 from TFS 2008.
- Prepare a new image. We recommend running Windows 2008 R2 Server x64using Hyper-V Manager. Your options are:
- Manually build a server
- A syspreped image (this will be quicker)
- System Center Virtual Machine Manager (recommended, quickest)
- Add the roles
- Application Server
- IIS
- Install SQL Server 2008 x64 default configuration
- Install SQL Server 2008 SP1
- Run www.ssw.com.au/ssw/Diagnostics/ and get all green ticks
Since we recommend doing a "move based upgrade", we don’t like the "in place upgrade" option, these are the steps:
- Copy the TFS2008 backups to TFS2010 server (e.g. C:\TfsBackups)
- Restore all the databases to TFS2010’s instance of SQL 2008
- Install Team Foundation Server 2010
- After the install has completed the Team Foundation Server Configuration Wizard will open
- Select Upgrade | Start Wizard 
- Click "Next" 
- Click "List Available Databases"
- Select the TfsIntegration database
- Check "By checking this box, I confirm that I have a current backup"
- Click "Next" 
- Select "NT AUTHORITY\NETWORK SERVICE" for the System account
- Click "Next" 
- Click "Next" 
- Click "Next" 
- Click "Next" 
- Click "Next" 
- Specify the TFSService account
- Click "Next" 
- Click "Next" 
- Click "Next" 
- Click "Next" 
- Click "Next" 
- Click "Configure" 
- Have coffee (2 hours)
BTW: A good user interface should have a coffee image
[TODO: Martin to create new rule in "Rules to better UI"]
[TODO: Martin to add suggestion to TFS]
 - Click "Next" 
- Click "Close" 
- Click "Close" 
- Change the DNS entry for tfs.northwind.com to point to TFS2010 on
- Internal DNS
- External DNS
Since you have to deal with your system admins, this job will take the longest. Speed it up by buying a Red Bull for your system admin If you have already done some test migrations on the new server there is no need to start from scratch. Just follow these simple steps and you will be up and running in no time.
- Open the Team Foundation Server Admin Console
- Click Application Tier | Team Project Collections | Detach Team Project Collection  Figure: Remove the old Team Project Collection from the server.
- Delete the Tfs_* databases except Tfs_Configuration from SQL Server Management Studio
- Delete the Tfs_Analysis database from SQL Server Analysis Server.
- Copy the TFS2010 backups to TFS2010 server (e.g. C:\TfsBackups)
- Restore the databases to the TFS2010’s SQL 2008 Server
- In the Team Foundation Server Admin Console
- Click Application Tier | Team Project Collections |Attach Team Project Collection 
- Follow the wizard, rule #8 from step 13.
Most of your reports (built in and custom) will be broken as the database schema has significantly changed.
To be ready for this, do a test migration and update any custom reports against the new database schema. That way, when your live server is up and running, your reports will be ready.
See John Socha-Leialoha's post for a good write up about what has changed and how to get your reports working.