Moving Team Foundation Server

Quite a few people sent me e-mail recently asking for documentation that supports a number of scenarios to move Team Foundation Server between domains, hardware, and more. On the Team System User Education Team blog you’ll find some prerelease documentation that covers these scenarios. As Susan notes, your feedback is very welcome and appreciated. Given the variety of environments that exist in the wild, we’re especially interested in learning about complications we didn’t foresee.

Today we have some draft documentation on how you can move your Team Foundation Server deployment. We have one conceptual and three procedural documents on this: Team Foundation Server Move Types, How to: Move from a Single-Server to a Dual-Server Deployment, How to: Move Your Team Foundation Server from One Hardware Configuration to Another, and How to Move Your Team Foundation Server from One Environment to Another. This content is not yet part of the live MSDN content, but all of the other topics referenced within these draft topics are available on MSDN. This is the latest, most up-to-date content for Visual Studio Team Foundation - be sure to check it out!

From: Visual Studio Team System User Education : Moving Your Team Foundation Server Deployment


Comments (7)

  1. Greg Duncan says:

    One simpler move scenario I’m doing is moving the data files from the default C drive to LAS mounted as an E drive.

    I’m going to treat this move as a SQL admin operation (i.e. detach and attach the SQL Db’s), but it would be cool to confirm that I’m taking the right approach and not shooting myself in the foot…

    I’m sure there will be other people who add drive space on an existing TFS server and want to move their TFS files around…?

    Also I want to say thanks for the posting you and the other TFS members have been doing. You guys rock…

    Thanks again…

  2. RobCaron says:

    You’ve made the correct assumption. Something like changing data devices is a SQL Server admin operation. Take a look at SQL Server Books Online for the "how-to". The only caveat is that you should take Team Foundation Server offline while you do it.

  3. Greg Duncan says:

    Rock on. Thanks.

  4. Joshua Blake says:

    Here is a scenario I haven’t seen answered yet.  I have TFS Beta 3 Refresh installed on a nice powerful machine as a single-server deployment.  This machine is also hosting pretty much all of our other services, including Domain Controller, dhcp, and misc file serving.  

    I’ve read that installing TFS on a domain controller was blocked starting in either RC or RTM, so haven’t upgraded.  We’re a small company with limited resources, so decided to get a good deal on a single nicer server than get two less powerful ones.  I can’t figure out how I would upgrade to RTM.  It isn’t as easy as creating a new domain controller on another machine and joining that domain, as I would also have to demote the current machine.  Since AD was the first thing to install, my instincts tell me that that process would break everything.  Would a restore-based approach be better?  

    Also, the documents say that moves aren’t supporting on pre-RC installs.  This is a dilemna because I don’t think that upgrading Beta 3 Refresh -> RC/RTM will work in place on a domain controller!  

    I understand the reasoning for blocking installs on DC, and think I might be able to scrounge up another machine for a new DC, but I am really not sure that this transition will even work.  I just want to make sure my existing data, projects, code, etc. are safe, plus minimize downtime.

    On a slightly different note, given this difficulty and the fact that beta3 refresh seems to be working fine for us, it is tempting to just continue to run with the current install.  Is there a time-bomb or licensing issue?


  5. RobCaron says:

    Joshua –

    I don’t have an immediate answer for anything other than the last part. The Go-Live License associated with the Beta releases only permits their use until 30 days after commercial release, or May 1st, whichever comes first.

    I’ll see what I can find out about the rest.

  6. I just posted a question on vstsue as well regarding this: how about a procedure to move a team project from one TFS to another?

  7.  One of the fun things after being gone for a while is catching up on all the good news you missed…

Skip to main content