This is the install guide for Team Foundation Server 2012 with Update 3 (TFS 2012.3). The latest release is Update 3. To apply TFS 2012.3 to an existing installation of TFS, you upgrade. (This is different from applying Visual Studio’s update 3, which works more like a traditional patch.) You can also install TFS 2012.3 the same as you would any other TFS 2012 release.
The only updates to this guide for TFS 2012.3 are the addition of Update 2 to the list of supported releases for upgrade and some changes to the initial build service configuration wizard to support automatic restoration of build server settings. Otherwise, it’s exactly the same installation guidance as in previous versions.
If you want to install Team Foundation Server with the least amount of preliminary work, use the basic configuration, which comes with SQL Server Express, and the installation wizard will configure everything for you.
With the basic configuration of Team Foundation Server, you can track bugs, tasks, and other work items. You can put files under version control, and use Team Web Access to log and resolve bugs. However, you will not be able to configure reporting or SharePoint with the basic configuration.
If you are installing Team Foundation Server on a server operating system, you can always add reporting or SharePoint later. If you want reporting and SharePoint right from the start, use one of the other Team Foundation Server installation options listed below.
Verify that your operating system and hardware meet the requirements for Team Foundation Server. For client operating systems, you can use Windows 7 or Windows 8, 32-bit or 64-bit. For servers, you must use 64-bit.
You can install Team Foundation Server and all its prerequisites on a single server. This scenario focuses on new installations of prerequisite software, but you can use existing installations as long as you install all the software on the same computer.
You can install Team Foundation Server and all its prerequisites across more than one server or by customizing any of the default options. For example, you might want reporting, but not a project portal. This scenario focuses on using your existing infrastructure for prerequisite software and incorporating other server products that offer high-value integration with Team Foundation Server, such as SharePoint Server 2010.
If you don’t want to run a portal on the same computer as Team Foundation Server, you can use Team Foundation Server Extensions for SharePoint Products to add SharePoint Products to Team Foundation Server. New for this version of the product, you can use this application to install SharePoint Foundation 2010 or add SharePoint to your already installed deployment of Team Foundation Server.