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.
Always plan for a catastrophic disaster, in the event of errors when testing:
Once you are ready to start you need to make sure that no one can access the existing TFS 2008 server while you do the migration.
TFS2008:
===========================================
Files
1 28052
2 335168
-- Compressed file size:
11837952896
-- Uncompressed file sizes:
24868196032
-- Areas & Iterations:
1096
Example: Dog Food Stats on TFS2008 Make sure that you save the numbers so you can compare it to TFS 2010 later...
Run your daily backups to provide a safety net should things go wrong.
Since we recommend doing a "move based upgrade", we don’t like the "in place upgrade" option, these are the steps:
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]
![]() | 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 |
All of the hard work has been done, now you need to do a quick test.
Running the "Dog Food" stats on your new TFS 2010 server is a good way to see if the upgrade was successful. You should check the new values against the stats you noted down from your TFS 2008 server.
Getting someone else to test the migration is the best way to make sure that you have not missed anything.