Bagikan melalui

Service Accounts and Dependencies in Team Foundation Server

  • Artikel

You can better manage Visual Studio Team Foundation Server if you understand the services and several service accounts that every deployment of Team Foundation Server includes and on which every deployment depends. Depending on how you have installed and configured Team Foundation Server, these services and service accounts might all be running on one computer, or they might be running on many computers.

Team Foundation Server has services and service accounts that run on the following computers in a deployment:

  • any server that hosts one or more databases for Team Foundation Server

  • any server that hosts components of the application tier for Team Foundation

  • any computer that is running Team Foundation Server Proxy

  • any build computer

  • any test machine

  • any computer that is running one or more components of Visual Studio Lab Management

You can install and deploy different features of Team Foundation in various ways. The distribution of features in your deployment determines what services and service accounts run on which physical computers. In addition, you might need to manage the service accounts for software programs that are configured to work with Team Foundation Server, such as the service accounts for SharePoint Products and SQL Server.

In this topic

  • Service Accounts for Team Foundation Server

  • Service Account Interaction Between Team Foundation Server and Microsoft Office SharePoint Server 2007

  • Services That Run Under Service Accounts

Service Accounts for Team Foundation Server

Although Team Foundation Server uses several service accounts, you can use the same domain or workgroup account for most or all of them. For example, you can use the same domain account "Contoso\Example" as both the service account for Team Foundation Server (TFSService) and the data sources account for SQL Server Reporting Services (TFSReports). However, different service accounts can require different permission levels. For example, TFSService must have the Log on as a service permission, and TFSReports must have the Allow log on locally permission. If you use the same account "Contoso\Example" for both, you must grant both of these permissions to it. In addition, TFSService requires significantly more permissions to operate correctly than those that TFSReports requires, as the table later in this topic shows. For security purposes, you should consider using separate accounts for these two service accounts.

Important

You must not use the account that was used to install Team Foundation Server as the account for either of these service accounts.

If you have deployed Team Foundation Server in an Active Directory domain, you should set the Account is sensitive and cannot be delegated option for service accounts. For example, in the following table, you should set that option for TFSService. For more information about required service accounts and placeholder names used in documentation for Team Foundation Server, see the topic "Accounts Required for Installation of Team Foundation Components" in the installation guide for Team Foundation. For more information about how to restrict account delegation in Active Directory, see the following page on the Microsoft Web site: Enabling Delegated Authentication.

Because you must manage several service accounts, each service account is referred to by a placeholder name that identifies its function, as listed in the table later in this topic. The placeholder name is not the actual name of the account that you use for each service account. The actual name of the account varies depending on your deployment. In the previous example, the account used for both TFSService and TFSReports was "Contoso\Example." In your own deployment, you might create domain accounts with the specific names of "TFSService" and "TFSReports," or you might use the system account Network Service as the service account for Team Foundation Server.

Important

Unless specifically stated otherwise, no groups or accounts in the following table should be members of the Administrators group on any of the servers in your deployment of Team Foundation Server.

The following table shows all the service accounts that you might use in a deployment of Team Foundation Server:

Service Account

Placeholder name and usable account type

Required Permission and Group Membership

Notes

Service account for Team Foundation Server

TFSService, which can be a local account, a domain account, Local Service in a workgroup, or Network Service in a domain

  • Log on as a service on the application-tier server

  • Farm Administrators group for any SharePoint Web applications that Team Foundation Server uses1 

  • TFSExecRole, or if this role does not exist for the database, a combination of the following roles for any databases that Team Foundation Server uses:

    • db_owner

    • db_create

This service account is used for all of the Web services for Team Foundation Server. If you use a domain account for this account, it must be a member of a domain that all computers throughout the deployment fully trust.

Data sources account for SQL Server Reporting Services

TFSReports, which can be a local account, a domain account, or Local Service in a workgroup

  • Allow log on locally on the application-tier server and on the server that is running SQL Server Reporting Services

  • TFSWareHouseDataReader on the report server

This service account retrieves data for reports from Reporting Services.

Service account for Team Foundation Build

TFSBuild, which can be a local account, a domain account, or Local Service in a workgroup

Log on as a service

This service account is used when builds are configured and when build status information is communicated between the build controller and the build agents.

Service account for Lab Management

TFSLab, which can be a local account, a domain account, Local Service in a workgroup, or Network Service in a domain

Log on as a service

This service account is used when information about Lab Management is communicated between Team Foundation Server and the lab agent that is running on a virtual machine.

Service account for Team Foundation Server Proxy

TFSProxy, which can be a local account, a domain account, Local Service in a workgroup, or Network Service in a domain

Log on as a service

This service account is used for all of the proxy services. If you use a domain account for this account, it must be a member of a domain that all computers throughout the deployment fully trust.

Service account for Test Agent and Test Agent Controller

TFSTest, which can be a local account, a domain account, or Network Service in a domain.

Log on as a service

This service account is used when information about tests is communicated between the test agent controller and the test agent.

Service accounts for SharePoint Web applications

WebAppService

Allow log on locally

You must add at least one service account for each SharePoint Web application that you configure for use with Team Foundation Server. This service account is used to create team project portals and to enable dashboard functionality.

1 You can integrate your deployment with SharePoint Products without this permission, but you must perform additional steps if the service account is not a member of the Farm Administrators group. For more information, see Integrate Team Foundation Server with SharePoint Products Without Administrative Permissions.

Service Account Interaction Between Team Foundation Server and Microsoft Office SharePoint Server 2007

If your deployment of Team Foundation Server uses Microsoft Office SharePoint Server 2007, you must also configure the service accounts and user groups in the following table, or a farm administrator must configure them for you. The farm administrator will also require information about the service accounts for Team Foundation Server. For more information, see Configure Settings for Dashboard Compatibility. At a minimum, the farm administrator will need three accounts to use as service accounts, each with different permissions. For more information about the permissions and other requirements for service accounts in SharePoint Products, see the following topic on the Microsoft Web site: Plan for administrative and service accounts. For an example of how you can configure these accounts in a deployment, see "Example Deployment of Team Foundation Server with Microsoft Office SharePoint Server 2007" in Interactions Between SharePoint Products and Team Foundation Server.

Note

If you want to configure single sign-on for the first time as part of integrating Microsoft Office SharePoint Server 2007 with Team Foundation Server, the account with which you log on to set up single sign-on requires specific permissions. For more information, see the "Configure Single Sign-On" section of Configure Settings for Dashboard Compatibility.

Description

Requirements

You can also use this account for the following purposes:

Farm administrator account (also known as the database access account)

  • must be a domain account

  • must be a member of the Administrators group on the server that is running SharePoint Products

You should not use this account for any other purpose.

Web and Search Services account

  • must be a domain account

  • Office SharePoint Server Search Service Account

  • Web Application Pool – port 80

  • Windows SharePoint Services Search Service Account

  • Windows SharePoint Services Search content access account

Single Sign-On account

  • must be a domain account

  • must be a member of the Administrators group on the server that is running SharePoint Products

  • must have db_creator on the instance of SQL Server that hosts the databases for SharePoint Products

  • must have Allow log on locally on the server that is running SharePoint Products

  • must be a member of TFSWareHouseDataReader on the report server

  • Single Sign-On Service Account

  • Single Sign-On Administrator Account

Enterprise Application Definition Administrator Account

  • must be a domain account or domain group

This account can also be a member of the Farm Administrators group.

Enterprise Application Definition Group (for the definition that you will create for Team Foundation Server)

  • must be a domain group

You should use the same group that you configure for PortalUsers, as listed later in this table.

Enterprise Application Definition Account Information (stored credentials for the definition that you will create for Team Foundation Server)

  • Allow log on locally on the application-tier server and on the report server

  • TFSWareHouseDataReader on the report server

You should use the same account that you configured for TFSReports.

One or more groups for all users of Team Foundation Server who will require access to the team portal (PortalUsers)

  • A domain group in an Active Directory domain or a local group in a single-server deployment

You use this group (or series of groups) to manage the permissions for users in Team Foundation Server, Reporting Services, and SharePoint Products. For more information, see the following page on the Microsoft Web site: How to: Add Users to Team Projects.

Services That Run Under Service Accounts

The following services run under service accounts in a deployment of Team Foundation Server:

Service name

Service account

Logical Tier

Code Coverage Service

TFSService

application tier

Team Foundation Server Web Services

TFSService

application tier

SQL Server Reporting Services (MSSQLSERVER or InstanceName if using a named instance)

Local System or a domain account

application tier

Report Web Service

Local System, Network Service, or a domain account

application tier

Windows SharePoint Services Administration (if SharePoint Products is installed and configured for use with Team Foundation Server)

Local System, Network Service, or a domain account

application tier

Windows SharePoint Services Timer (if SharePoint Products is installed and configured for use with Team Foundation Server)

Domain account

application tier

Visual Studio Team Foundation Build Service Host (if Team Foundation Build is installed)

TFSBuild

build computer

Visual Studio Team Foundation Background Job Agent

TFSService

application tier

Visual Studio Test Controller

TFSTest

any computer

Visual Studio Test Agent

TFSTest

test computer

Analysis Server (MSSQLSERVER or InstanceName if you are using a named instance)

Local System or a domain account

data tier

SQL Server Browser

Local System or a domain account

data tier

SQL Server (MSSQLSERVER or InstanceName if using a named instance)

Local System or a domain account

data tier

For more information about service accounts for SQL Server, see the following page on the Microsoft Web site: SQL Server Books Online. For the most recent information about service accounts in Team Foundation, download the installation guide for Team Foundation from the following page on the Microsoft Web site: Installation Guide for Team Foundation.

Note

If you change the service account for Team Foundation Build, you must make sure that the new service account is a member of the Build Services group. You must also make sure that the account has read/write permissions to the temporary folders and the ASP.NET temporary folder. Similarly, if you change the service account for the Team Foundation Server Proxy service, you must make sure that the account is a member of the appropriate groups. For more information, see Configure Your Build System.

See Also

Tasks

Change the Service Account or Password for SQL Server Reporting Services

Change the Service Account or Password for Team Foundation Server

Other Resources

Managing Server Configuration with TFSConfig