We recommend using Visual Studio 2017
This documentation is archived and is not being maintained.

How to: Verify Team Foundation Server Fail-Over (services)

After you have completed setup and the primary application-tier server is running correctly, you can simulate failure of the application tier and verify the activation procedures for your organization.

Required Permissions

To perform this procedure, you must be a member of the Administrators security group on both the primary and the standby Team Foundation application-tier servers. For more information, see Team Foundation Server Permissions.

To simulate failure and test activation

  1. On the primary computer, open the Internet Information Services (IIS) Manager by clicking Start, clicking All Programs, clicking Administrative Tools, and then clicking Internet Information Services (IIS) Manager.

  2. In the Internet Information Services manager, locate and select the Application Pools node, right-click each following application pool, and then click Stop.

    • ReportServer

    • StsAdminAppPool

    • TFS AppPool

    • TFSWSS

    • TFSWSSAdim


    To simulate a failure, you can shutdown the primary computer.

  3. Ask the domain administrator to change the static IP address for the virtual server from the IP address used by the primary computer to the IP address used by the standby computer.

  4. Log on to the standby computer and run the ActivateAT command of the TFSAdminUtil command-line utility available in the Tools directory.

    For example,

    C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools>TfsAdminUtil ActivateAt <virtual server name>

    The utility binds the standby application tier to the data tier and restarts the Internet Information Services to make sure that all services have the current registration data. The utility reports that the binding was successful and that all services function. The standby server becomes the primary server and the server that failed can be restored and then act as the new standby server.

  5. Verify that the Reporting Services are running.

    For more information, see How to: Activate a Fail-Over Application-Tier Server.

  6. Notify the client users that they may have to run ipconfig /DNSFlush.

See Also