How to: Verify Team Foundation Server Fail-Over (services)
The document is archived and information here might be outdated

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 application-tier servers for Team Foundation. For more information, see Team Foundation Server Permissions.

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 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. Stop all application pools and services that Team Foundation requires.

    For more information about how to start and stop services and application pools, see How to: Stop and Start Services, Application Pools, and Web Sites.

    The service and application pools that you must stop might include the following:

    • ReportServer

      NoteNote:

      You manage ReportServer in IIS for SQL Server 2005 but not for SQL Server 2008.

    • Microsoft Team Foundation Server Application Pool

    • The relevant application pools for SharePoint Products and Technologies, if they are running on the application-tier server. Based on which version and edition of SharePoint Products and Technologies you installed and how you configured it, these application pools might include the following:

    • TFSWSS

    • TFSWSSADMIN

    • SharePoint Central Administration v3

    • SharePoint - 80

    NoteNote:

    As an alternative to the previous steps, you can simulate a failure by shutting down the primary computer.

  3. 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.

    If you are not a domain administrator, you must ask a domain administrator to change the address.

  4. Log on to the standby computer, and activate it.

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

  5. Start all needed application pools and services.

    For more information about how to start and stop services and application pools, see How to: Stop and Start Services, Application Pools, and Web Sites.

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

Show:
© 2016 Microsoft