Home Library Learn Downloads Support Community
Sign in | United States - English | |
11 out of 23 rated this helpful - Rate this topic

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

Visual Studio 2008

You can move an instance of Visual Studio Team System Team Foundation Server from one hardware configuration to another by performing a restoration-based move. This type of move is not only the most common but also one of the most complex types of move for Team Foundation Server. Before you start a restoration-based move, you should ensure that this type of move best suits your organizational objectives. For more information, see Team Foundation Server Move Types. For a restoration-based move, you must also ensure that the software update levels for the version of Team Foundation Server and SQL Server that you are moving from and to match exactly. Otherwise, your restored deployment might not operate correctly.

Important noteImportant Note:

As you plan to move a deployment, you should verify the scope and purpose of the changes that you expect to make and compare them to the scenarios for each type of move. By choosing the correct move type, you not only minimize confusion and disruption of team productivity but also help ensure the long-term efficiency of your deployment.

To help prepare for a restoration-based move, you should read through all the required steps and consider printing this topic. You should also review the information that it provides through links and determine which steps will vary based on your specific configuration. For example, your deployment might have SQL Server Analysis Services on a different server from the SQL Server databases. In this situation, you must configure those servers separately.

NoteNote:

You can migrate reporting databases from SQL Server 2005 to SQL Server 2008, but this change adds complexity to the move process. You should consider moving or upgrading these databases before you move the deployment. For more information, see the following page on the Microsoft Web site: Upgrading a Report Server Database.

To perform a restoration-based move, you must complete the procedures in the following sections:

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. If you are creating security groups in an Active Directory domain, you must have appropriate permissions in that 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.

Before you can move your deployment of Team Foundation Server, you must back up its databases. As part of the move, you will restore these databases to the new data-tier server.

To prepare the old deployment for a restoration-based move

  1. Back up all the databases for Team Foundation Server.

    For more information, see How to: Back Up Team Foundation Server.

    Note Note:

    You must also back up any custom site definitions, custom site templates, or custom Web parts for SharePoint Products and Technologies that you want to keep. For more information, see these pages on the Microsoft Web site: Backup and Restore Options for Windows SharePoint Services 2.0 or Recommendations for data protection and recovery for Windows SharePoint Services 3.0.

  2. Back up the encryption key for Reporting Services, and store it in a secure location on a different computer from the server that is running Team Foundation Server. Make sure that the new deployment can access the key, and store the password with which the key is encrypted.

    For more information, see How to: Back Up the Reporting Services Encryption Key.

After you back up the databases, you must install Team Foundation Server on the computer to which you want to move your deployment.

To prepare the new server for a restoration-based move

  1. Install Team Foundation Server on the new hardware, and make sure that the server is operational.

    For detailed instructions and information about prerequisites, see the installation guide for Team Foundation on the Microsoft Web site.

    Important note Important Note:

    Before you install Team Foundation Server, you must first install SQL Server on the computer to which you want to restore the data for your deployment. The version of SQL Server that you install must exactly match the version that was running on the old data-tier server, including service pack level, collation settings, and language edition. If the match is not exact, you might not be able to restore the data.

  2. On the server that is running SQL Server Reporting Services, retrieve and save a list of the installation IDs for Reporting Services.

    1. Open the Command Prompt window, and change directories to the following directory:

      %ProgramFiles%\Microsoft SQL Server\90\Tools\bin\

      Note Note:

      For SQL Server 2008, this directory will vary based on the edition. For x86-based systems, the default directory is %ProgramFiles%\Microsoft SQL Server\100\Tools\bin. For x64-based systems, the default directory is Program Files(x86)\Microsoft SQL Server\100\Tools\bin.

    2. Run RSKeyMgmt -l.

    3. Note the installation IDs, and either print the list or save it in a safe location.

  3. Log on to the appropriate server, open Computer Manager, and stop the services and application pools in the following table in the order specified:

    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 (SQL Server 2005 users only. You do not need to complete this step if you are using SQL Server 2008.)

    • Default Web Site or Report Manager Web site
    Important note Important Note:

    To move user accounts and service accounts in a restoration-based move, the new deployment of Team Foundation Server must be in a stopped state. If you restart Team Foundation Server after you restore data but before you move user accounts and service accounts, you could cause users who are targeted for migration to be marked as deleted in the TFSIntegration database. This problem occurs when the group security service cannot find the user’s system identification (SID) during synchronization with Active Directory.

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

Before you restore data to the new databases for Team Foundation Server, you should back up the configuration database for SharePoint Products and Technologies (WSS_Config) on the new server. If you try to restore the database from the old server to the new server, the database might be overwritten or corrupted during the restoration process. 

To back up the WSS_Config database

After you stop the services, you can restore the data for Team Foundation Server by using the tools that SQL Server provides.

Caution note Caution:

You must restore all the databases to the same point in time. Otherwise, they might become corrupted.

To open the Restore Database dialog box

  1. On the new data-tier server, click Start, point to All Programs, point to Microsoft SQL Server, and then click SQL Server Management Studio.

    Note Note:

    For more information about how to restore databases, see "Implementing Restore Scenarios for SQL Server Databases" on the Microsoft Web site.

  2. In the Server type list, click Database Engine.

  3. In the Server name list, click or type the appropriate server.

  4. In the Authentication list, click the appropriate scheme.

  5. In User name, type the user name of a valid account.

  6. In Password, type the password of the account if SQL Server requires it, and then click Connect.

  7. Expand the Databases node to show the list of databases that make up the data tier for Team Foundation.

Important note Important Note:

For restoration-based moves, do not restore the configuration database for SharePoint Products and Technologies (WSS_Config) from the old server to the new server.

Complete the "To restore each database" procedure for each of the following databases:

  • ReportServer

    Note Note:

    If you used a named instance, this database will be named ReportServer$InstanceName.

  • ReportServerTempDB

    Note Note:

    If you used a named instance, this database will be named ReportServerTempDB$InstanceName.

  • The content database for SharePoint Products and Technologies (STS_Content_TFS or WSS_Content)

    Note Note:

    The name of the database that contains data for SharePoint Products and Technologies will vary depending on the version of SharePoint Products and Technologies that is installed and whether the person who installed it customized the name. Additionally, if SharePoint Products and Technologies is installed on a separate server from Team Foundation Server, these databases might not be present on the data-tier server. If they are not present, you must manage the backup, restoration, and configuration of SharePoint Products and Technologies and its databases separately from Team Foundation Server. However, you should synchronize the maintenance of the databases to avoid synchronization errors.

  • TfsBuild

  • TfsIntegration

  • TfsVersionControl

  • TfsWarehouse

  • TfsWorkItemTracking

  • TfsWorkItemTrackingAttachments

  • TfsActivityLogging (optional)

    Note Note:

    As part of the restore process, you must upload any custom site templates or Web parts created for custom process templates to databases for SharePoint Products and Technologies.

To restore each database

  1. Right-click the database that you want to restore, point to Tasks, point to Restore, and then click Database.

    The Restore Database dialog box opens.

  2. Under Source for restore, click From Device, and then click the ellipsis button (…).

  3. In the Specify Backup dialog box, specify the location of the backup file, and then click OK.

    The first backup that you apply must be a full backup, followed by the transaction log backups, in the order in which they were created.

  4. Under Select the backup sets to restore, specify the backup sets to restore.

  5. In the Select a page pane, click Options, and then select the Overwrite the existing database check box.

  6. In the Restore the database files as list, verify that the paths match your current database paths.

    This step is important if you are restoring the database to a different drive.

  7. Under Recovery state, click the appropriate state.

  8. Perform one of the following steps:

    • If you are not applying additional transaction logs, click Leave the database ready to use.

    • If you are applying additional transaction logs, click Leave the database non-operational.

  9. Click OK to close the Restore Database dialog box and restore the database.

  10. If you are applying additional transaction logs, follow this procedure for each set of log backups in the order in which they were created. Start with the one made after the full backup.

    For more information, see "Applying Transaction Log Backups" on the Microsoft Web site.

You must redirect SharePoint Products and Technologies to the new content database.

To restore Web sites for team projects

After you restore project Web sites, you must restore SQL Server Reporting Services to the new application-tier server.

To restore and verify Reporting Services in SQL Server

  1. On the server that is running Reporting Services, open Computer Manager, and start the ReportServer or ReportServer$InstanceName application pool.

    Note Note:

    You do not need to complete this step if you are using SQL Server 2008.

  2. Click Start, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click Reporting Services Configuration.

  3. In the Explorer pane, click Database Setup.

  4. The Database Connection pane opens.

  5. In Server Name, verify that the name of the data-tier server is correct, and then click Connect.

  6. In the SQL Server Connection Dialog dialog box, click OK.

  7. In the Database Connection pane, click Apply.

  8. If you have a dual-server deployment, perform the following steps:

    1. In the Explorer pane, click Windows Service Identity.

      The Windows Service Identity page opens.

    2. In the Built-in Service Account list, click Local Service.

      The Apply button becomes available. Do not click it.

    3. In the Built-in Service Account list, click Network Service, and then click Apply.

    4. In the SQL Server Connection Dialog dialog box, click OK.

  9. Open Computer Manager, and start Reporting Services.

    Note Note:

    If you are using a named instance, this service name will be SQL Server Reporting Services (InstanceName).

  10. Close the Reporting Services Configuration tool.

  11. Open a Command Prompt window, and change directories to the tools directory for your version of SQL Server. For SQL Server 2005, the default directory is %ProgramFiles%\Microsoft SQL Server\90\Tools\bin. For SQL Server 2008, this directory will vary based on the edition. For x86-based systems, the default directory is %ProgramFiles%\Microsoft SQL Server\100\Tools\bin. For x64-based systems, the default directory is Program Files(x86)\Microsoft SQL Server\100\Tools\bin.

  12. Type the following command to list installation IDs of Reporting Services:

    RSKeyMgmt -l

  13. In the list, find the installation ID that corresponds to the new data-tier server.

  14. Type the following command to remove that installation ID, where DTInstanceID corresponds to the old data-tier server:

    RSKeyMgmt –r DTInstanceID

    Note Note:

    Do not remove the installation ID that corresponds to the new data-tier server.

  15. On the server that is running Reporting Services, click Start, point to All Programs, point to Microsoft SQL Server, point to Configuration Tools, and then click Reporting Services Configuration.

  16. In the Explorer pane, click Encryption Key.

  17. On the Encryption Key page, click Restore.

    The Encryption Key Information page opens.

  18. In Password, type the password for the encryption key file.

  19. In Key File, type or click the location of the backup encryption key (.snk file), and then click OK.

After you restore Reporting Services, you must use the TfsAdminUtil command to configure connections and rename the data-tier server.

To rename the data-tier server and update the integration database with the name of the new application-tier server

  1. Log on to the appropriate server, open Computer Manager, and start the application pools and programs in the following table:

    Log on to the server that hosts this program

    Start this component

    Application tier

    • Microsoft Team Foundation Server Application Pool

    Reporting Services

    • ReportServer or ReportServer$InstanceName (application pool)

      NoteNote:
      You do not need to complete this step if you are using SQL Server 2008.

    • SQL Server Reporting Services (TFSINSTANCE)

  2. Open the Command Prompt window, change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools, and type the following command:

    TfsAdminUtil ConfigureConnections /view

  3. Review the settings for /ReportsURI and /ReportServerUri. If the server for Reporting Services has changed from the information shown, you must reconfigure those connections by typing the following command:

    TfsAdminUtil ConfigureConnections /ReportsUri: NewReports /ReportServerUri:NewReportServer

    Note Note:

    If you are using a named instance, you must specify the named instance as part of the values for Reports and ReportServer. Do not eliminate or change the name of the named instance.

    For example, if Reporting Services were running on the old application-tier server and had been moved to the new application-tier server, you would need to provide the new uniform resource indicator (URI) for /ReportsUri and /ReportServerUri. For more information, see ConfigureConnections Command.

  4. (Optional) After you reconfigure the connections, type the following command to review the changes and ensure that they have taken effect:

    TfsAdminUtil ConfigureConnections /view

  5. In the services web.config file, replace the name of the new data-tier server with the name of the old data-tier server as follows:

    1. On the new application-tier server, open a Command Prompt window, and change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services.

    2. In Notepad or any text-based editor, open the web.config file in this directory.

    3. Under the appSettings node, find the connection string element, and change the value of the Source parameter to the name of the old data-tier server. For example, you must modify the following element:

      Application Name=TeamFoundation;Data Source=NewTeamFoundationDataTierServerName;Initial Catalog=TfsIntegration;Integrated Security=True;Persist Security Info=False

      After your changes, the element should resemble the following string:

      Application Name=TeamFoundation;Data Source=OldTeamFoundationDataTierServerName;Initial Catalog=TfsIntegration;Integrated Security=True;Persist Security Info=False

    4. Save the web.config file, and close Notepad.

      Note Note:

      For the TfsAdminUtil RenameDT command to run correctly, the connection string in the services web.config file must refer to the name of the old data-tier server.

  6. Open the Command Prompt window, change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools, and type the following command:

    TfsAdminUtil RenameDT NewTeamFoundationDataTierServerName

    Important note Important Note:

    For the RenameDT command to succeed, the application pools and programs in the previous step must be running. This requirement is new in Visual Studio Team System 2008 Team Foundation Server.

  7. After the command finishes, stop the following application pools and programs:

    • Microsoft Team Foundation Server Application Pool

    • ReportServer or ReportServer$InstanceName

    Note Note:

    You do not need to complete this step if you are using SQL Server 2008.

    • SQL Server Reporting Services (TFSINSTANCE)

    Note Note:

    After you run the RenameDT command, you must stop the services that it requires before you continue with the next steps.

  8. If the new application-tier server has a different name from the old application-tier server, update the TFSIntegration database with the name of the new server. Then update the registration entries in the service interface for the application tier to point to the new server.

    1. On the new application-tier server, open a Command Prompt window.

    2. Change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools.

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

      TfsAdminUtil ActivateAT NewTeamFoundationApplicationTierServerName

After you configure connections and rename the data-tier server, you must rebuild the Team System cube for Team Foundation. The Team System cube supports SQL Server Reporting Services and contains data from the relational database of the data warehouse for Team System. For more information, see Understanding the Data Warehouse Architecture.

To rebuild the Team System cube in the new deployment

After you rebuild the Team System cube, you must delete the version control cache on the application-tier server (and any proxy servers) to force synchronization with the new data-tier server.

To delete the version control cache

  1. On the application-tier server, open the %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\VersionControl directory.

  2. Delete the contents of the Data subdirectory, but do not delete the Data subdirectory itself.

    For more information, see How to: Delete the Version Control Cache on the Application-tier Server.

  3. Repeat this procedure on any server in your deployment that is running Team Foundation Server Proxy.

You must re-create service accounts, user accounts, and any local accounts if you are moving your deployment from one workgroup to another. You must also re-create these accounts if you are moving your deployment to a domain that does not trust the domain to which the old deployment belonged.

Note Note:

The account names that you create in the new deployment must match the names of the accounts from the old deployment. 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.

To move user accounts and service accounts

  1. On the server that is running Reporting Services, open Computer Manager, and start the following components:

    • ReportServer or ReportServer$InstanceName (application pool)

    Note Note:

    You do not need to complete this step if you are using SQL Server 2008.

    • SQL Server Reporting Services (TFSINSTANCE)

  2. On the new application-tier server, open a Command Prompt window, and change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools.

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

    TfsAdminUtil ChangeAccount OldDomainOrComputerName\OldTFSServiceAccount NewDomainOrComputerName\NewTFSServiceAccount NewPassword

    Note Note:

    Ignore any warning that says that the service account does not exist or that the account is not a member of the data warehouse role.

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

    TfsAdminUtil ChangeAccount /ra OldDomainOrComputerName\OldTFSReportingServiceAccount NewDomainOrComputerName\NewTFSReportingServiceAccount NewPassword

    Note Note:

    Ignore any warning that says that the service account is not a member of the data warehouse role or that prompts you to add the account to the service accounts group.

  5. On the old application-tier server, open a Command Prompt window, and change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools.

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

    TfsAdminUtil Sid

  7. Note or print the list of users that appears.

    You might have to re-create this list of users on the new application-tier server, either as local accounts or domain accounts.

  8. On the new application-tier server, create any local accounts that are required to correspond with the local accounts on the old application-tier server. If the old application-tier server was on a domain that the new application-tier server's domain does not trust, open Active Directory, and create domain accounts that correspond to the domain accounts on the old application-tier server.

    For more information, see "Creating user and group accounts" on the Microsoft Web site.

  9. On the new application-tier server, open a Command Prompt window, and change directories to %ProgramFiles%\Microsoft Visual Studio 2008 Team Foundation Server\Tools.

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

    TfsAdminUtil Sid /Change OldDomainOrComputerName NewDomainOrComputerName

    This command updates all user accounts on the application-tier server that uses SIDs for the new domain or workgroup. If you must update user accounts by using information from more than one source (for example, from another domain and from local accounts), you will have to specify additional parameters. You can run TfsAdminUtil SID multiple times to change the SIDs of user accounts from different source domains that the new domain does not trust. For more information, see Sid Command.

    Important note Important Note:

    When you restart Team Foundation Server, 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 the new application-tier server into production before this information is synchronized.

To resume operations, you must restart the services on which Team Foundation depends.

To restart services

  • Log on to the appropriate server, open Computer Manager, and start the components in the following table, 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

To refresh the data cache on client computers

  • Use the ClientService Web service to force clients to update the cache for tracking work items the next time that they connect to the application-tier server. To update the version control cache, each user must update the client computer by using the tf workspaces command.

    For more information, see How to: Refresh the Data Caches on Client Computers.

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 in SharePoint Products and Technologies and Reporting Services to the new application-tier server. Finally, you must re-create any query-bound reports or documents because you will not be able to connect to your new deployment by using queries from the old deployment.

To update build computers with new domain settings

  1. If you want to use an existing computer that is running Team Foundation Build in your new deployment, open the TeamBuild.proj file on that computer, and update the settings for the new computer and a new drop location.

    For more information, see Administering Team Foundation Build.

  2. After you update the build computers with the new settings, start a test build to verify the new configuration.

To migrate users and groups in SharePoint Products and Technologies and Reporting Services

  • After you move your deployment, you might need to manually migrate user accounts, groups, and role memberships in SharePoint Products and Technologies and Reporting Services across domains to the new deployment. The Active Directory trust relationship with the old deployment determines how much information you must migrate. Both SharePoint Products and Technologies and Reporting Services will show the users, groups, and their role memberships for each site or report folder. For more information, see Managing Permissions and Trusts and Forests Considerations for Team Foundation Server.

To create reports in Microsoft Project or Microsoft Excel reports

  • After you move your deployment, re-create any Microsoft Project or Microsoft Excel files that connect to Team Foundation Server. For more information, see Team Foundation Server Reporting.

Did you find this helpful?
(1500 characters remaining)
Community Content Add
Annotations FAQ
Remapping SID's may require a Hotfix after SP1 is applied

After moving a domain account configuration to a workgroup configuration, you may receive the error message "Error: Could not access database". Microsoft has released a hotfix for this issue. The knowledge base article that references this hotfix is incorrect according to Microsoft. The hotfix file name is VS80sp1-KB933848-X86-ENU.exe. You have to call support and request the hotfix. I applied it to my migration and it worked like a charm.

History
In the Explorer pane, click Database Setup
In "Restore and Test SQL Report Server, Reporting Services, and Default Reports" section under "To restore and verify Report Server in the new deployment of Team Foundation Server", the step "3. In the Explorer pane, click Database Setup." should have been "In Reporting Services Configuration (from SQL Server configuration tools), click Database Setup."
History
No docs for Reporting Services for SQL Server 2008
The section "Restore and Test SQL Server Reporting Services and Default Reports" only mentions SQL Server 2005, but not what (if anything) to do for SQL Server 2008.
History
Could not rebuild the cube before moving service accounts
I was moving TFS 2008 from one server to the other in the same domain. I was also changing TFS service and reports accounts. When executing steps in the order they appear in the article, I was failing to perform "Rebuild the Team System Cube" step. http://localhost:8080/Warehouse/v1.0/warehousecontroller.asmx service was not available. Accessing it generated "TF53002: Unable to obtain registration data for application VersionControl." error in event log. Error details contained exception "TF50309: The following account does not have sufficient permissions to complete the operation: MYDOMAIN\NewTfsServiceAccount." Eventually I performed "Move User and Service Accounts" step during which TFS service and reports accounts were changed to the new ones. After that "Rebuild the Team System Cube" step went successfully.
History
TF50309 Error Message For TFS Service Account TfsService no permission
After completing all steps above, my TFS services wouldn't start. I was getting a TF50309 error in the logs relating to my tfsservice account not having permission to access the tfs webservices. Had to run this command for it to work $0$0 $0 $0TfsSecurity /g+ “Service Accounts” Domain\TfsService /server:servername$0
History
TF53007 error when restoring DT to a different server name
IMHO When moving TFS deployments between two differently named SQL servers, this whole article misses some critical details:

1. The TFS service pack levels must be identical between the TFS Aplication Tiers, in addition to the SQL Server service pack and collation settings. The TFS version is recorded in the TfsIntegration database Properties under Extended Properties under the TFS_PRODUCT_VERSION field. TFS2008 SP1 should be 9.0.30729.1. You can also find out the SQL Server collation settings here as well.

2. Simply restoring the TFS Data Tier databases to a differently named servers creates Error TF53007 when one tries to connect with Team Explorer or TSWA: "The application tier name <SERVER1> recorded in the database does not match the local machine name <SERVER2>".

The tfsadminutil renamedt and activateat commands do not apply here to resolve this issue as others bloggers have speculated.

I found that it is necessary to open the TfsIntegration database in SQL Management Studio, drill down to the following tables:

tbl_database
tbl_registration_extended_attributes
tbl_service_interface
tbl_subscription
tbl_tmp_security_acls tables

and **manually update** all references to the old server name with the new server name (right-click on the table and select "Open Table")

> If just one entry is not updated the TF53007 error occurs and also make sure there are no stray spaces, especially padding the end of the field, which is impossible to see but can send you to the insane asylum to troubleshoot. Same goes for editing the Registry! <

(The TfsIntegration database contains other TFS AT configuration settings like service account names so it is helpful to note to the contents of the other tables and entries as an aid to troubleshooting.)

Once all old server name references are updated, the TFS AT connects to the new DT correctly.

AFAIK there is no automated utility to update the TfsIntegration tables following a restoration based server move - somebody let me know if there is!

When moving Windows Share Point Services 3.0 databases it is only necessary to restore the WSS_Content database when doing a restoration based server move and not the others.

It may also not necessary to backup and restore the Reporting Services databases as then you get the headache of migrating GUIDs and the symmetric encryption key.

Just re-create the Reporting Services Project folder and import the Analysis functions corresponding to the Development model using the Process Template Manager in Team Explorer.

Anthony Maw, B.Sc., MCSE
Vancouver, Canada
tel/sms +1 604 318 9994
anthony@maw.bc.ca
www.anthonymaw.com
History
Domain and Hardware migration completed successfully (Dual Server deployment)

Completed TFS2008 SP1 restoration successfully after few issues.


1) Rebuild the Team System Cube failed. I continued with the remaining steps then attempted this step. Rebuild the Team System Cube was completed successfully
2) Workitems were showing with a red cross mark.

the following 2 blogs and MS suport url helped me to resolve this issue.
http://blogs.msdn.com/emmamou/archive/2009/03/13/a-case-study-on-tfs-identity-replication.aspx
http://blogs.msdn.com/dstfs/archive/2009/03/03/red-x-on-work-items-folder-in-team-explorer.aspx
http://support.microsoft.com/kb/958433


3) WSS_AdminContent restoration is not required. Which is not discussed in the document. May be irrelevant here.

History
Include information for changing the SQL instance
Could you please include information on moving from one SQL instance (possibly the default) to another instance? Especially confusing is the handling of the reporting services databases and the reporting services encryption keys. I don't know of a document that describes this.
History
You do not need to recreate your excel (office) documents

The documentation indicates to recreate your excel and ms-project.

Instead you can use the team foundation power tool command: tfpt changedocurl filespec /server:serverurl

Explanation of feature:
Update the server information. TFS server information is stored as metadata in TFS bound Excel or Project files. But there might be cases where server is renamed, port number is changed, or the protocol is changed (i.e. https instead of http). This command updates the server information on existing files

History
-mturl is required for setupwarehouse.exe
History
Additional revision to this topic

It has come to our attention that the words "new" and "old" were inadvertantly swapped when using the rskeymgmt -r option. The steps should read:

11.Open a Command Prompt window, and change directories to %ProgramFiles%\Microsoft SQL Server\90\Tools\binn.

12.Type the following command to list installation IDs of Reporting Services:

RSKeyMgmt -l

13.In the list, find the installation ID that corresponds to the new data-tier server.

14.Type the following command to remove that installation ID, where DTInstanceID corresponds to the new data-tier server:

RSKeyMgmt –r DTInstanceID

NoteDo not remove the installation ID that corresponds to the old data-tier server.

This change will appear in the next revision of the topic (note: the "Last Updated" date functionality in this topic is not working at this time). The change is also available on the VSTS UE team blog here: http://blogs.msdn.com/vstsue/archive/2008/04/25/draft-documentation-update-for-moving-team-foundation-server-from-one-hardware-configuration-to-another.aspx.
History
Rename the Data-Tier Server and Activate the Application-Tier Server
In step 5 under Rename the Data-Tier Server and Activate the Application-Tier Server, when you run RenameDT command, you may get “ERROR: TF55030: Rename Data Tier failed. Please verify that the supplied Data Tier name is a valid Team Foundation Data Tier name, that the Data Tier can be accessed on the network and that you have administrative rights.”

For this to work, default web site on new server has to be running. It is stopped as per instructions in preceding steps
History
Extra steps when "Copy" a TFS instance
This document is just for Moving a TFS instance. If you want to Copy an existing TFS instance to a new one, please re-stamp the new TFS instance as described in Buck Hodges blog:http://blogs.msdn.com/buckh/archive/2006/10/17/creating-a-new-server-from-an-old-one-beware-of-the-instanceid.aspx.
History
Moving between servers on the same domain
After completing the move based on the steps provided above, we experienced some issues that made it appear that we were connectied to the NewServer while in fact data was being populated in the OldServer.

It appears that if you move your TFS instance between two computers that are on the same domain, you might need to run a few more steps that are not listed in the documentation above.

(note: this was a single-server deployment)

“%TFSInstallDir%\Tools\InstanceInfo.exe" stamp /setup /install /rollback /d TFSWorkItemTracking,TFSBuild,TFSVersionControl,TFSIntegration,TfsWarehouse /s <<your new data tier>>

"% TFSInstallDir %\Tools\InstanceInfo.exe" stamp /d TFSWorkItemTracking,TFSBuild,TFSVersionControl,TFSIntegration,TfsWarehouse /s <<your new data tier>>

Close Visual Studio/Team Explorer(if already open). Clear the TFS Client side cache after you perform the above steps.
History
Draft update to this topic available on the VSTSUE blog

A change in the behavior of the renameDT command invalidates the order of the steps as seen here.

A draft update to this topic with revised steps for the changed behavior of renameDT is available on the VSTS UE team blog here:

http://blogs.msdn.com/vstsue/archive/2008/04/25/draft-documentation-update-for-moving-team-foundation-server-from-one-hardware-configuration-to-another.aspx.

History
TfsAdminUtil ConfigureConnections Bug in TFS2008SP1
On the section "Rename the Data-Tier Server and Activate the Application-Tier Server" in step 3 is the correct syntax

TfsAdminUtil ConfigureConnections /ReportsUri:http://<Server>:80/Reports /ReportServerUri:http://<Server>:80/ReportServer/ReportService.asmx

and not

TfsAdminUtil ConfigureConnections /ReportsUri:http://<Server>:80/Reports /ReportServerUri:http://<Server>:80/ReportServer

for more infos
http://blogs.msdn.com/dstfs/archive/2008/09/26/tfsadminutil-exe-from-tfs-2008-sp1-configureconnections-fails.aspx
History
Appropriate server
Into many places there are terms like "On the server that is running Reporting Services", or "Log on to the appropriate server", and it is not clear on which server operation should be performed. Suggest is to use more clear terms like "new server", "old server", or "new data-tier server", "old application-tier server", etc.
History
  • 8/31/2008
  • IAF
Team Foundation System - Configuration, Backup, Restore and Move Manager

Team Foundation System is a combination of all kind of services and (web)applications.

Moving a Team Foundation System is at this moment a complicated and time consuming procedure.

It would be very helpfull to have a "Team Foundation System - Configuration, Backup, Restore and Move Manager" which can do this for some common configurations.

I expect that more Team Foundation System users will be happy with such a tool.

History
Reboot before section -- Rebuild the Team System Cube
I had to perform a reboot before I could get this section to work.
History
Warehouse updating
Before Warehouse update (command: SetupWarehouse.exe -o -snewDataTierServerName-dnewTeamFoundationDataWarehouseName -c warehouseschema.xml -raTFSReportServiceAccount-a TFSServiceAccount -mturl http://ApplicationTierServerName:Port) make sure that IIS has been restarted and all Application Pools are running
History
Change the connectionstring in web.config before running TfsAdminUtil RenameDT

Before you run the command TfsAdminUtil RenameDT <newmachine> you must make sure that connectionstring points to the old machine:

  1. On the new machine, open the web.config located in the folder: \Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\Services.
  2. Locate the key "ConnectionString".
  3. Make sure that the Data Source property in the connectionstring is set to the name of the old machine.
  4. Save the web.config
  5. Run the command TfsAdminUtil RenameDT <newmachine>.
History
Do not delete the \VersionControl\Data\ folder

In the section To delete the version control cache it is said to delete the folder \program files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services\VersionControl\Data\ but if you delete the folder you get permission denied errors in the VersionControl service because the \data\ could not be found and the TFSSERVICE account does not have the permissions normally to recreate it. Therefore after deleting the \Data\ folder recreate it under the TFSSETUP account.

History
Adding the WSSSERVICE account to the WSS_Content SQL Server database

If you are performing a restoration-based move and you have used the TFSSERVICE account for the Sharepoint Services but on the new machine you have used a dedicated WSSSERVICE account, than it is possible that step 6 fails of the section To restore project sites in Windows SharePoint Services 3.0 on the new application-tier server for Team Foundation Server.

When you create a new content database through the Sharepoint Central Administration web site, you will get an "Unknown Error" and the reason is because the WSSSERVICE account does not have permissions to the restored WSS_Content database. Therefore give the WSSERVICE account the db_owner database role membership and try again.

History
Removing Reporting Service instances
In step 13 and substep e) for SQL Report Server Standard Edition, section To restore and verify Report Server on the new Team Foundation Server it is mentioned that you need to call RsKeyMgmt -r passing the name of the instance to remove but you need to pass the instance ID being the GUID not the name.
History
Correct name of Windows Service
In the document there are references to the Timer Service of Sharepoint as SharePoint Timer Service, please note that the correct name of this service is Windows SharePoint Services Timer.
History
Important note
Please move the note "For restoration-based moves, do not restore the configuration database for SharePoint Products and Technologies." to the line where it says that you need to restore the WSS_Content databases because you can easily miss this important piece of information.
History