Taoffi's blog

As I already said (I should not be the only one to sayJ): TFS is a precious tool for project management. The problem with TFS is the tedious processes to install and troubleshoot specific issues.

This has greatly been changed in TFS 2010 to become much less tedious (thanks to the TFS team and to Brian Harry for all the useful information) but IT IS, still, quite tedious!

For instance: One of the usual tasks we do from time in the real world is to move our stuff from somewhere to somewhere else!

Don't expect this to be as easy as you may think in TFSJ

The context

Let's say we have a whole TFS installation somewhere (configuration / collections databases… etc.) and we want (or need) to move everything to another machine.

At a first glance, that should be straightforward:

• Install TFS (and SQL server) on the new machine;
• Attach (or restore) TFS databases to the new machine;
• Tell the new TFS where to find the databases;
• Done!

Yes, it is a good path… but somewhat tortuous!

The recipe

On the new machine:

SQL configuration and settings

• Install SQL Server (2008 or 2008R2). Note the following elementary observations:
  • During installation, you should select a CI AS (case insensitive / accent sensitive) collation (either Windows or SQL);
  • Prefer a 'default instance' installation
• Attach (or restore) all TFS databases (configuration database, collections and datawarehouse databases.
• Install latest SQL server updates and Service Packs.

TFS configuration and settings

• Install TFS
• DON'T click Configure at the end of the install process
• Launch TFS admin console
  • Click Application Tier node
  • Click Configure Installed Features
  • Select the 'Application-Tier only' Wizard
  • Click List Available Databases.
    • This will display detected TFS configuration databases on the SQL server. If none is detected, then you have to go back to SQL configuration and see what is missing
  • Select the configuration database
  • Select the account service
  • Check and correct errors and warnings. You may need to go back to SQL configuration steps.
  • Click Configure

Problems encountered?

If you encounter problems (this is often the case with TFSJ), you may need to uninstall and restart the Application-Tier configuration:

• Open a command prompt (Run As Administrator)
• Go to TFS tools directory (%program files%\Microsoft Team Foundation Server 2010\Tools)
• Uninstall the Application Tier: Type the following command:

tfsconfig setup /uninstall:ApplicationTier

• Restart the above TFS configuration steps at Launch TFS admin console

Security configuration issues

Original SQL server configuration, TFS and various service accounts may not match the new machine's configuration. This may generate some errors that can be corrected using SQL server management studio and, in case, TF admin console (Administer security option). It is sometimes necessary to go through TFSSecurity command line utility.

Please note: all this should be considered as "useful hints" to solve TFS migration from machine to machine. You should be armed with patience and try find other simple and reliable paths for your specific problems.

Anyway, Hope this may help!