Home | Requirements | Basic Server Upgrade | Set up Build | Add New Features
Standard / Advanced
Use this guide to upgrade TFS 2010 to Team Foundation Server 2012.
You’ll find step-by-step guidance that covers the most popular upgrade tasks, including in-place upgrades and upgrades that involve moving to new hardware. Direction on what to do with SharePoint, whether it’s running on the same server as TFS or somewhere else. We’ll also walk through upgrade of a build machine, as well as adding new features to your upgraded team projects.
Some upgrade issues are only covered in the install guide on MSDN. For example, upgrades that involve TFS farms, Project Server integrations, or upgrades that start with TFS 2008. But even if you have an installation that’s not covered, this guide might still be useful to you. Many of the high level process are the same—you’ll still want to back up your deployment, for example—but the exact steps might be different. If we don’t cover your task specifically, we’ll offer links to relevant MSDN articles. And we may be able to give you some insight about how to tackle certain tasks, like how to deal with SharePoint or moving the application tier to new hardware.
First, read the upgrade requirements. Team Foundation Server has new 64-bit server OS requirements. Upgrade no longer supports all previous versions of the product.
Next, choose a server upgrade path.
The steps are different based on whether you're using TFS 2010 basic, or if you're planning to use the same hardware (standard upgrade) or move to a new machine (advanced upgrade). Select from one of the paths below:
2-A) I want to upgrade from TFS 2010 Basic (Basic upgrade)
After you upgrade the application tier, you might want to install the new build service. You can't use TFS 2010 build service with Team Foundation Server 2012, but you can install the new build service side-by-side on the same server as the TFS 2010 build service.
You can also use a wizard to add new features to your TFS 2010 team projects.
I have read your ebook regarding the upgrade and it's really great. There's one thing I am trying to figure out but haven't been able to. We want to upgrade TFS 2010 to 2012 on new hardware. We are using WSS and Reporting features. For some time (couple of weeks or so) we want to maintain both 2010 and 2012 environments for testing/validation purposes. There'll be two data migrations, one initial and then the final one after testing is successfully completed.
The question is what to do with sharepoint?
One of the steps in upgrade talks about detaching the content database and then attaching it to the new tfs/sharepoint server. But that will make the existing sites unavailable to users of TFS 2010. How can I make sure that the existing sites remain up and running and also the new TFS 2012 gets the same websites (of course with different URLs)?
Have you considered copying the content database from the previous version of SharePoint before you move it to the new one? I haven't tried this in my lab, but it seems like it ought to work. If you took this route, you'd have to figure out a way to deal with the forked data at some point. If the work you're willing to lose the work you're doing in the test environment, one solution might be to do the upgrade all over again, from scratch, when you're ready to migrate to production. Something to think about.
Thanks for the kind words on the book. If possible you should put future comments on my WordPress blog (http://elhajj.wordpress.com) or the MSDN topic for upgrade (msdn.microsoft.com/.../jj620933.aspx). I no longer use this blog. :)