Configure Team Foundation Server Using the Advanced Configuration

Visual Studio Team Foundation Server 2012 v4

You can set up Team Foundation Server using the advanced configuration, which allows you to customize most settings. Although you can run this configuration on a client or server operating system, if you use a client, you won't be able to add a portal or reporting to your deployment.

To complete this procedure on a client operating system, you don't need any domain accounts. On a server, you must have at least one domain account, which you can use for all of the following identities:

  • The service account for Team Foundation Server (TFSSERVICE).

  • The report reader account for creating reports (TFSREPORTS).

  • The service account for new installations of SharePoint Foundation 2010 (WSSSERVICE).

For more information about accounts, see Accounts Required for Installation of Team Foundation Server.

TipTip

You can access the Team Foundation Server Configuration tool from the Start menu by launching Team Foundation Server Administration Console, choosing Application Tier, and then choosing Configure Installed Features.

Required Permissions

You must be a member of the Administrators security group on the server on which you will install Team Foundation Server. If you plan to configure reporting, you must also be a member of the Administrators security group on the server that is running SQL Server Reporting Services. If you plan to configure SharePoint Products, you must be a member of the Farm Administrators group on the SharePoint Products administration site. If you did not install the Database Engine that will host the configuration database or a database administrator manages the instance of SQL Server that you are using, you must be a member of sysadmin Server role in SQL Server.

TipTip

If you or your database administrator want a better understanding of the required SQL Server permissions, see the following page on the Microsoft website: Database Permissions Required to Configure TFS.

To configure Team Foundation Server using the advanced configuration

  1. In the Team Foundation Server Configuration tool, choose Advanced, and then choose Start Wizard.

    The Advanced Configuration wizard appears.

  2. Read the Welcome screen, and then choose Next.

  3. In SQL Server Instance, type the name of the server that is running SQL Server or the named instance that will host the configuration databases, and choose Next.

    You can also perform any of these optional steps:

    • Select This instance is a SQL AwlaysOn Availability Group to specify that the SQL Server instance is an Availability Group Listener (AGL) and its availability group will host the TFS databases created during set up. See Use SQL Server 2012 Always On Availability Groups with Team Foundation Server.

    • In Server Database Label, type a label string, which is then embedded into all three of the default database names.

      This technique enables you to use a single instance of SQL Server to host multiple configuration databases.

    • Select the Use pre-existing empty database(s) check box, and then specify databases that are hosted on the server that is named in SQL Server Instance.

      You must create names for these databases by using the default naming structure, with or without a label. You can find the default naming structure under Team Foundation Server Databases.

    • Choose Test to test the connectivity to SQL Server.

  4. Under Service Account, choose Use a system account to use a built-in account or Use a user account to use a domain or local account. If you are using a user account, you must type the password. To test the user account and password combination, you can optionally choose Test.

    A built-in account is the default value for this service account (TFSSERVICE).

  5. Under Authentication Method, choose NTLM or Negotiate (Kerberos), and then choose Next.

    • If you choose NTLM, NTLM authentication is used. This option is the default setting.

    • If you choose Negotiate (Kerberos), Kerberos authentication is attempted first. If that attempt fails, NTLM authentication is used.

  6. Under Web Site, type a name in Web Site Name and a port number in Port. This is the name that appears in Internet Information Services (IIS) and the port number used to connect to Team Foundation Server.

    The default values for Web Site are Team Foundation Server and 8080.

  7. Under IIS Virtual Directory, you can use the default value of tfs or optionally type a virtual directory name.

  8. Under Web Site, note the Team Foundation Server site URL, which is dynamically assembled based on your input in Web Site and IIS Virtual Directory. Clients use this URL to connect to Team Foundation Server. Choose Next.

    On a client operating system, you must skip to step 11. You can't add a portal or reporting (steps 9 and 10) on a client operating system.

  9. Use the Configure Reporting for Team Foundation Server page to opt in or out of using reporting. Select the Configure Reporting for use with Team Foundation Server check box to use reporting, or clear the check box to skip reporting, and then choose Next.

    1. Type the name of the server that is running SQL Server Reporting Services in Reporting Services Instance and choose Populate URLs.

      The URLs for the report server and its management site appear in the drop-down lists for Report Server URL and Report Manager URL.

    2. Ensure the values displayed are the URLs that you want to use for Team Foundation Server and choose Next.

    3. Type the name of the server that is running SQL Server Analysis Services in SQL Analysis Services Instance and choose Next.

      To test the connectivity to SQL Server, you can optionally choose Test.

    4. Type the name and password of the report reader account (TFSREPORTS) and choose Next.

      If you specified a user account for the service account of Team Foundation Server in step 4, you must select the Use a different account than the Team Foundation Server service account for the report reader account check box to use a different account.

      To test the user account and password combination, you can optionally choose Test.

  10. Use the Configure SharePoint for Team Foundation Server page to opt in or out of using SharePoint Products. Select the Configure SharePoint Products for use with Team Foundation Server check box to use SharePoint Products, or clear the check box to skip SharePoint Products. Choose Next.

    If you selected the check box to configure SharePoint Products, perform one of the following procedures:

    • Install and configure SharePoint on this machine.

      1. Choose Install and configure SharePoint on this machine and choose Next.

      2. Choose the big Install SharePoint Foundation 2010 button. Once the install completes, choose Next.

      3. Type a user account and password for the service account forSharePoint Foundation 2010 (WSSSERVICE). If you specified a user account for the service account of Team Foundation Server in step 4, you must select the Use a different account than the Team Foundation Server service account for the SharePoint farm check box to use a different account.

      4. Choose Next.

    • Integrate with a remote SharePoint farm.

      1. Choose Integrate with a remote SharePoint farm and choose Next.

      2. In Site URL, type the URL for the SharePoint web app.

      3. In Administration URL, type the URL for the SharePoint Central Administration site. To test connectivity to each of these URLs, choose Test.

      4. Choose Next.

  11. Select the Create a new team project collection check box to create a collection, or clear that check box to skip that step.

    If you create a collection, accept the default values, or type a new name and description. Choose Next.

  12. On the Review page, review the settings, and choose Next.

    The wizard validates your configuration.

  13. Choose Configure.

    The wizard applies configuration settings. This process might take several minutes.

  14. Choose Next. Close, Close.

    The Team Foundation Server Administration Console appears.

See Also