In an attempt to ease into a TFS 2010 Migration, I set up a 2010 server much too early, hoping that we could continue to use the old 2008 server and just synchronize the changes to the new server. There is a synchronization service available called the Tfs Integration Platform (http://tfsintegration.codeplex.com/) which is provided by the Visual Studio ALM Rangers. I installed this and it worked great on the work items, transferring them from the old to the new server but it seemed to be overwhelmed by the version control. I concluded that the version control was just so markedly different between the two servers and that was why it was having such a rough time. That became the impetus for migrating the data again. Here is the procedure that I wanted to follow.
- Backup the existing 2010 databases. (just in case)
- Copy the SQL backup files from the 2008 server to the new server.
- Delete the new databases on the 2010 server.
- Restore the 2008 databases on the new server. At this point the list of databases should resemble those on the 2008 server.
- Reinstall TFS 2010.
The reinstall did not work, so I tried an uninstall/reinstall. This also did not work. I discovered a trick to get the install to recognize the upgrade in the following article http://rules.ssw.com.au/TFS/RulesToBetterTFS2010Migration/Pages/default.aspx which explained how to select “Upgrade” on the Team Foundation Server Configuration rather than the inviting “Standard Single Server”. Some differences that I chose were to use TFSSERVICE and TFSREPORTS accounts rather than NETWORK SERVICE. Some gotchas that I encountered were
- having to delete the Tfs_Analysis cube by connecting to Analysis Services in Sql Server Management Studio
- having to add the sysadmin role to the TFSSETUP account in the Sql Server 2008 database
- having to add TFSSETUP to the WSS Farm Administrators group
All in all, I got the upgrade to succeed in this way with one minor warning. Now, back to synchronization!