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.
What’s not covered?
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-B) Standard upgrade (in-place)||2-C) Advanced upgrade (migration)|
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.