About: In this type of move, you will not move any part of your TFS systems between machines, but instead will move your machine between environments. Most often this is used for moving from a workgroup to a domain. So, of the four steps described in the introduction (http://blogs.msdn.com/tfsao/archive/2009/02/20/server-change-we-can-believe-in.aspx, backup/install/restore/hookup), the only one we have is hookup.

Introduction: One of the main admin scenarios that customers have problems with is moving Team Foundation Server (TFS) between severs. I have constructed a series of blog postings that present overviews of the most common move scenarios. The introduction to this series can be found here: http://blogs.msdn.com/tfsao/archive/2009/02/20/server-change-we-can-believe-in.aspx, and the index of server moves can be found here: http://blogs.msdn.com/tfsao/archive/2009/02/20/index-of-server-moves.aspx.

 

This type of move has official documentation, which for TFS 2005 can be found here: http://msdn.microsoft.com/en-us/library/ms404879(VS.80).aspx and for TFS 2008 can be found here: http://msdn.microsoft.com/en-us/library/ms404879.aspx. Since you can find all the specifics for this moves in the above documentation, I’m not going to go through them in detail. Instead I’ll give you an overview of the key steps for this move.

 

1.      Hookup the Backups to the New System

a.      Stop any TFS-related service from running to prevent interference, may include Windows SharePoint (WSS) services.

b.      Join the computer to the domain.

c.      Via the ChangeAccount command, change the service accounts to accounts that exist in the new environment.

d.      Via the Sid command, change the user accounts to accounts that exist in the new environment.

e.      Reconnect Reporting Services to TFS in the new domain.

f.       Restart all of the services.

g.      Update Build with new settings.

h.      Migrate SharePoint & Reporting Services groups/users.

i.       Create Project and Excel Reports.