Install TFS on a single server
TFS 2018 | TFS 2017 | TFS 2015
There are three different options for installing Team Foundation Server (TFS):
- Single server install (covered in this guide)
- Dual server install
- Multiple server install
The simplest way to set up TFS is to put everything on a single server. Make sure to review our hardware recommendations to confirm that this configuration seems appropriate for your team. If not, consider a dual server or multiple server configuration instead.
Prepare a single computer that satisfies the system requirements for TFS.
If you do not plan to use SQL Express, set up an appropriate version of SQL Server. When you set SQL Server up for TFS, install at least the database engine and full text search services.
While the configuration wizard will install SQL Server Express for you, we don't recommend using SQL Server Express for anything but personal or evaluation deployments of TFS. Paid copies of TFS come with a license to SQL Server Standard for use with TFS. The Team Foundation Server pricing page explains the details. If you use the license that's included with TFS, you can only use if for the TFS databases.
Ensure that the account you plan to use to configure TFS is a member of the SysAdmin server role in SQL Server.
Installing TFS involves a complex set of operations that require a high degree of privilege - these include creating databases, provisioning logins for service accounts, and more. Technically, all that is required is membership in the ServerAdmin role; ALTER ANY LOGIN, CREATE ANY DATABASE, and VIEW ANY DEFINITION server scoped permissions; and CONTROL permission on the master database. Membership in the SysAdmin server role will confer all of these memberships and permissions, and is therefore the easiest way to ensure that TFS configuration will succeed. If necessary, these memberships and permissions can be revoked after TFS is installed.
You can download TFS from:
Kick off the installation.
The installation process itself simply gets TFS bits onto your machine. At the end of this process, the installer will launch the TFS Configuration Center.
Configure TFS using your selected scenario. The easiest way to set up Team Foundation Server on a single server is to use the Server Configuration Wizard with the New Deployment - Basic scenario.
In previous versions of TFS, you would use the Basic Configuration Wizard.
This scenario is optimized for simplicity, using default options for most inputs. If you want full control over all inputs, use the New Deployment - Advanced scenario instead.
With the New Deployment - Basic scenario, you will need to choose:
- Language: Which language you would like to configure TFS for.
- SQL Server Instance: Whether to install SQL Express or use an existing SQL Server instance.
- Application Tier: Which website settings to use, including whether to use HTTP or HTTPS bindings. See website settings for more information.
- Search: Whether to install and configure Code Search features. See configuring search for more information.
If you select the New Deployment - Advanced scenario, you will additionally need to choose:
- The service account your various TFS deployment processes will run as. The default value used in the Basic scenario is
NT AUTHORITY\NETWORK SERVICEin domain joined scenarios, and
LOCAL SERVICEin workgroup scenarios.
- Whether to enable SSH, along with the port it should listen on. The default value used in the Basic scenario is to configure SSH on port 22.
- The location of the file cache used for frequently accessed TFS resources. The default value used in the Basic scenario is the path
TfsData\ApplicationTier\_fileCacheon the local drive which has the most free space.
- Whether to configure Reporting features and SharePoint integration. The default behavior used in the Basic scenario is to not configure these features. Note that these options are not available on client operating systems.
- Whether to create a team project collection in which to store your projects, along with the name of that collection. The default behavior in the Basic scenario is to create a project collection named DefaultCollection.
In both cases, the wizard will run readiness checks to validate your environment and your setting selections. If all goes well, the wizard will then let you configure your deployment. If there are errors, you will need to fix each of them and re-run the readiness checks before you can continue.