Export (0) Print
Expand All

How to: Move Your Deployment of Team Foundation Server from One Environment to Another

Updated: December 2010

In contrast to restoration-based moves, environment-based moves do not involve moving data for Visual Studio Team System Team Foundation Server from one set of hardware to another. Instead, an environment-based move involves changing the environment of the deployment itself. The most common scenario for an environment-based move is moving a deployment from a workgroup to a domain. The procedures in the following section specifically support this scenario.

NoteNote:

The procedures in this topic are designed specifically to support changing the environment in which your deployment runs from a workgroup to a domain. However, the steps are almost identical for changing a deployment from one domain to another domain. Minor differences are called out in notes. If you want to move your deployment to new hardware, see How to: Move Your Deployment of Team Foundation Server from One Hardware Configuration to Another.

Before you move your deployment of Team Foundation Server, you must plan and prepare for the environment-based move. You must complete many steps in an environment-based move, and some of them are linked to through this topic. Read through and consider whether you want to print all the steps that are required before you start the move. To complete an environment-based move, you must be able to perform steps such as stopping and starting services, re-creating or migrating user accounts and service accounts, and reconfiguring your servers.

To move your deployment of Team Foundation Server from a workgroup to a domain, you must complete the procedures in the following sections in the sequence listed:

  1. Stop Services that Team Foundation Server Uses

  2. Join the Application-Tier and Data-Tier Servers to the Domain

  3. Move User and Service Accounts

  4. Redirect SQL Server Reporting Services to Connect to Team Foundation Server in the New Domain

  5. Restart Services that Team Foundation Server uses

Required Permissions

To complete these procedures, you must be a member of the Administrators group on the old and new servers and a member of the Team Foundation Administrators group, and you must have permissions to join a server to the Active Directory domain. If you are creating new domain security groups, you must have appropriate domain permissions in the Active Directory domain.

In addition to these permissions, you might need to address the following requirements on a computer that is running Windows Server 2008 or Windows Vista:

  • To follow a command-line procedure, you might need to open an elevated Command Prompt by clicking Start, right-clicking Command Prompt, and clicking Run as Administrator.

  • To follow a procedure that requires Internet Explorer, you might need to start it as an administrator by clicking Start, clicking All Programs, right-clicking Internet Explorer, and then clicking Run as administrator.

  • To edit web.config files, you might need to start the text editor as an administrator by clicking Start, clicking All Programs, right-clicking the editor, and then clicking Run as administrator.

  • To access Report Manager, reports, or Web sites for SQL Server Reporting Services, you might need to add these sites to the list of trusted sites in Internet Explorer or start Internet Explorer as an administrator.

For more information, see the Microsoft Web site.

To stop services that Team Foundation Server uses

  • Log on to the appropriate server, open Computer Manager, and stop the following services:

    Log on to the server that hosts this program

    Stop this component

    SharePoint Products and Technologies

    • SharePoint Timer Service or Windows SharePoint Services Timer

    • Default Web Site or Team Web site

    Application tier

    • Visual Studio Team Foundation Server Task Scheduler Service

    • Microsoft Team Foundation Server Application Pool

    SQL Server Reporting Services

    • SQL Server Reporting Services (TFSINSTANCE)

    • ReportServer or ReportServer$InstanceName (application pool)

    • Default Web Site or Report Manager Web site

      NoteNote:
      You manage ReportServer and the Report Manager Web site in Internet Information Services (IIS) for SQL Server 2005 but not for SQL Server 2008.

    For more information, see How to: Stop and Start Services, Application Pools, and Web Sites.

You must join every server in your deployment of Team Foundation Server to the domain to which you want to move as part of changing the environment. If you are moving from a workgroup environment to a domain, both your application tier and your data tier will be on the same physical server. You must join only that server to the domain. You do not have to join each server that hosts a tier of the deployment to the domain separately unless you also moved from a single-server to a dual-server deployment. For more information, see How to: Move Your Deployment of Team Foundation Server from One Hardware Configuration to Another.

To join each application-tier and data-tier server to the domain

  1. On each application-tier and data-tier server, click Start, right-click My Computer or Computer, and then click Properties.

  2. (For Windows Server 2008) Under Computer Name, domain, and workgroup settings, click Change settings. 

  3. In the System Properties dialog box, click the Computer Name tab, and then click Change.

  4. In the Computer Name(/Domain) Changes dialog box, click Domain.

    NoteNote:

    If you are changing from one domain to another, this option will already be clicked.

  5. Type the name of the domain to which you want to join the server, and then click OK.

    If you are prompted to provide the user name and password of an account that has permissions to join this computer to the domain, provide the appropriate credentials, and then click OK.

  6. Click OK.

  7. Restart the computer for the domain change to take effect.

    NoteNote:

    After you restart the computer, a warning might appear that services or drivers could not be started. This error will be resolved when you complete the next procedure. Click OK to ignore this error.

To move user accounts and service accounts

  1. On the Windows taskbar, click Start, point to Administrative Tools, and then click Local Security Policy.

  2. Expand Local Policies in the Explorer pane of the Local Security Settings window.

  3. Click User Rights Assignment.

  4. Double-click Log on as a service on the viewing pane.

  5. Click Add User or Group on the Log on as a service Properties dialog box.

  6. In the Enter the object names to select box, type the name of the new service account, and click OK twice.

  7. On the application-tier server for Team Foundation, open a Command Prompt window, and connect to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools.

    Important noteImportant Note:

    When you move accounts from one environment to another, the account names created on the new and original deployments must match. This requirement includes both user and service accounts. These account names are used to identify and update the database records for Team Foundation Server as part of the move process.

  8. At the command prompt, type the following command, where "OldComputerName\OldTFSServiceAccount" is the name of the service account that was used in the previous workgroup or domain, including the computer or domain name; NewDomain\NewTFSServiceAccount is the name of the service account that you will use in the new environment, including the domain name; and NewPassword is the password for the service account that you will use in the new environment:

    TfsAdminUtil ChangeAccount "OldComputerName\OldTFSServiceAccount" "NewDomain\NewTFSServiceAccount" NewPassword

    NoteNote:

    Ignore any warnings about the service account not existing or being a member of the data warehouse role.

  9. At the command prompt, type the following command:

    TfsAdminUtil ChangeAccount /ra "OldComputerName\OldTFSReportingServiceAccount" "NewDomain\NewTFSReportingServiceAccount" NewPassword

    NoteNote:

    Ignore any warnings about the service account not being a member of the data warehouse role or reminding you to add the account to the service accounts group.

  10. At the command prompt, type the following command:

    TfsAdminUtil Sid

  11. Note or print the list of users generated by the TFSAdminUtil Sid command. This is the list of the users you might need to re-create on the Team Foundation Server in its new domain as domain accounts, if you want to use domain accounts instead of local accounts.

  12. Open Active Directory and create domain accounts to replace the old local computer accounts in the workgroup deployment of Team Foundation Server. For more information about how to create accounts, see the Microsoft Web site.

  13. At the command line, type the following command:

    TfsAdminUtil Sid /Change OldComputerName NewDomain

    NoteNote:

    This command will update all user accounts on the Team Foundation Server that uses SIDs for the new domain. For more information, see Sid Command.

    Important noteImportant Note:

    When Team Foundation Server is restarted, you might have to wait for up to an hour before the Group Security Service will re-synchronize with Active Directory to update user account information in the TFSIntegration database. Do not put Team Foundation Server back into production before this synchronization is finished.

To redirect Reporting Services to connect to Team Foundation Server in the new domain

To restart services that Team Foundation Server uses

  • Log on to the appropriate server, open Computer Manager, and start the following services and application pools, in the order specified:

    Log on to the server that hosts this program

    Start this component

    SharePoint Products and Technologies

    • SharePoint Timer Service or Windows SharePoint Services Timer

    Application tier

    • Visual Studio Team Foundation Server Task Scheduler Service

    • Microsoft Team Foundation Server Application Pool

Depending on your Team Foundation deployment, you might have to update TeamBuild.proj files with the new settings. Additionally, you might have to migrate users and groups for SharePoint Products and Technologies and SQL Server Reporting Services to the corresponding users and groups in the domain for Team Foundation Server. Finally, you will have to re-create any query-bound reports or documents, because queries that were created before the move will not be able to connect to Team Foundation Server in the domain.

To update build computers with the new domain settings

  1. If you want to use an existing Team Foundation Build computer in your new deployment, you must update the settings for the new Team Foundation Build computer and provide a new drop location in the TeamBuild.proj file. For more information, see Administering Team Foundation Build.

  2. After you have updated the build computers to use the new settings, test the build settings by starting a test build.

To migrate Windows SharePoint Services and Reporting Services groups and users

  • No tools are available to automatically change SharePoint Products and Technologies and Reporting Services users and groups and their role memberships from local accounts (used in workgroups) to domain accounts. Although the local accounts will still work as local accounts, you might want to take advantage of the flexibility and management of Active Directory groups. Both SharePoint Products and Technologies and SQL Server Reporting Services will show the users and groups and their role memberships for each site or report folder. You can populate SharePoint Products and Technologies and Reporting Services to use new or existing Active Directory groups depending on your new deployment.

To create Microsoft Project or Microsoft Excel reports

  • As soon as you have finished moving your Team Foundation Server deployment to the domain, you will have to re-create any Microsoft Project or Microsoft Excel files that connect to Team Foundation Server. For more information, see Team Foundation Server Reporting.

Date

History

Reason

December 2010

Clarified the number of servers that you must join to a domain when you move a deployment from a workgroup to a domain environment.

Customer feedback.

June 2010

Clarified the purpose of this document.

Customer feedback.

Community Additions

ADD
Show:
© 2014 Microsoft