Install Team Foundation Server

Installing on more than one server

If you intend to have SQL Server and TFS on the same server, then you might be able to use the TFS standard installation wizard, which is designed to streamline the number of decisions you have to make during TFS installation. To use the standard wizard, you have to have SQL Server set up on the default instance (as we did in the SQL Server installation topic) and the reporting features must be installed. We recommend that you have 24 GB of RAM to run SharePoint on the same server as SQL Server. If you’re okay with all these requirements and with the default TFS options¹ (SharePoint Foundation is installed), then use the standard wizard.

If you want more control over installation options, use the advanced configuration.

Tip Tip

¹If you want to see the default options for TFS, use the advanced wizard and don’t change any of the default settings. You’ll get the same TFS installation as if you had used the standard wizard.

Whether you use standard or advanced TFS install wizards, you’ll need at least one domain account for the report reader account. TFS uses this account to generate reports. If you let us install SharePoint, we use this same account for the Farm Admin account in SharePoint.

Tip Tip

The report reader account only needs the Allow log on locally permission, which all domain accounts have by default.

If you want to change the default installation options for Team Foundation Server, use the advanced wizard, which lets you configure Team Foundation Server on multiple servers and change many other options.

Why use advanced? The standard installation might not fit your needs. You might want to customize a single server installation or install Team Foundation Server and its configuration database on different servers. Perhaps you already have SQL Server or SharePoint Products running in your organization and you’d like to use one of these installations to host team projects or the data for Team Foundation Server. If you use the optional features that require prerequisite server software, these installations can also be hosted on different servers. If you use multiple servers, you can distribute the load between Team Foundation Server and the configuration database, or you can ensure that prerequisite server software for features such as reporting or the portal site is running on capable hardware.

Don’t confuse the multiple server installation with the robust scale-out features that Team Foundation Server offers. These scale-out features include the ability to create a Team Foundation Server farm and add a team project collection to an instance of SQL Server that was not part of the original deployment of Team Foundation Server. However, these scale-out features are not part of this scenario. This scenario offers you guidance for an initial deployment of Team Foundation Server that takes advantage of configurable installation options, such as installing TFS on more than one server. For more information about how to add an application-tier server to your deployment of Team Foundation Server, see How to: Create a Team Foundation server farm (high availability).

Tip Tip

A multiple-server installation requires an Active Directory domain and domain accounts or the Network Service account. You cannot use local accounts for service accounts.

Step 1 Verify that the operating system and hardware meet the requirements for Team Foundation Server and all its prerequisites. You must use a 64-bit server if you install TFS on a server operating system. Determine the report reader account you will use for Team Foundation Server.

For more information, see System requirements for Team Foundation Server, Accounts required for installation of Team Foundation Server.

Step 2 Install a supported version of SQL Server. You must install these SQL Server features: Database Engine, Full-Text and Semantic Extractions for Search. To get HTML reports from your TFS team projects, add these features: Analysis Services, and Reporting Services – Native

SQL R2 installation

For more information, see: SQL Server requirements for Team Foundation Server, Manually install SQL Server for Team Foundation Server

Step 3 You have a lot of options for SharePoint. If you have SQL Server and TFS on running on the same server, your best alternative might be to install SharePoint on a different server to minimize competition for resources. If you know you want SharePoint Server, you should install and configure it before you install TFS. Remember that you can always skip SharePoint integration altogether by using the TFS advanced wizard. TFS doesn’t require SharePoint.

Configure SharePoint Server

For more information, see SharePoint Products requirements for Team Foundation Server, Manually Install SharePoint products for Team Foundation Server

Tip Tip

You can also verify and use an existing SharePoint deployment that meets the TFS requirements for SharePoint. If you’re existing SharePoint is not on the same server as where you’ll install TFS, you’ll want to first install the TFS SharePoint extensions on the SharePoint site. See How to: Install Remote SharePoint Products for Team Foundation Server.

Step 4 Run the Team Foundation Server install from the product DVD and then use one of the configuration wizards to configure your installation. Use the standard wizard if you have SQL Server on the default instance, and TFS will install SharePoint Foundation 2013 for you. For everything else, use the advanced wizard. See, “Why use the advanced wizard?” earlier.

Select TFS standard configuration

For more information, see Run Team Foundation Server installation, Configure Team Foundation Server using the advanced configuration, Configure Team Foundation Server using the standard configuration

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft