Recently (about 5 minutes ago) I did an upgrade in production of our Team Foundation 2008 server to Team Foundation 2010. I had a dry run that worked well but of course on the real thing I had a couple of issues. Here are some notes.
- TFS requires sysadmin on the new SQL server, it wants to create/drop databases like crazy
- TFS previous to 2010 required sharepoint to be installed, with 2010 it’s just an option, you can add it later.
- To clean up from an earlier install (failed, test run, etc.) you can run this command (see the gotcha at the end!)
C:Program FilesMicrosoft Team Foundation Server 2010Tools>tfsconfig setup /un
- Install TFS 2010
- Configure TFS 2010 (this creates databases)
- Backup your old TFS databases (all of them)
- Restore your old TFS databases to your new sql instance
- Run the TFS import command from command line. It should look like this:
C:Program FilesMicrosoft Team Foundation Server 2010Tools>Tfsconfig import /s
qlinstance:serverinstance /collectionName:imported /confirmed
- TF30046: The instance information does not match.
- C:ProgramDataMicrosoftTeam FoundationServer ConfigurationLogs
- Visual studio 2005
- Tfs plugin for vs 2005
- Vs 2005 sp1
- Vs 2005 vista compatibility update (run windows update)
- Vs 2005 TFS 2010 update
- Then you enter the full URL in the server name field: http://tfs2010_server:8080/tfs
- If it tells you that you can’t put in the “/” and such, it means you installed in the wrong order.
- Install vs 2008
- Install vs 2008 sp1
- Install vs 2008 TFS compatibility pack
- Enter servername as: http://tfs2010_server:8080/tfs