Aracılığıyla paylaş

Changing the Configuration of Your Deployment

  • Makale

After you have configured Visual Studio Team Foundation Server 2010 and Project Server to support data synchronization, you may need to perform additional administrative tasks when you change your deployment. For example, you may need to remove, re-register, or re-map a component before or after you move or delete a team project, a team project collection, or an application-tier server. Before you change your deployment or perform maintenance operations, you should consider the impact that these operations have on the synchronization process.

Review the following notes and resources before you change a deployment that has the feature pack for Team Foundation Server and Project Server integration installed:

  • Delete a team project. After you delete a mapped team project, the synchronization engine updates the metadata for the instance of Project Web Access or Project Web App (PWA) during the next synchronization update. You do not need to take additional steps.

  • Delete a collection. Before you delete a mapped collection, you should unmap it by following the procedure in Remove a Team Project Collection from Participating in Synchronization.

  • Move or split a collection. To move a mapped collection to another instance of Team Foundation Server and continue synchronizing data on the new application-tier server, you must perform the following steps:

    1. Use the /UnmapPwaFromCollection command option with the /force switch to unmap each collection that you are not moving and that is mapped to the instance of PWA.

      Uyarı

      By using the /force switch, you break all associations between enterprise project plans and team projects that are defined for the collection. A recommended practice is to move or split all collections that are mapped to the same instance of PWA at the same time.

    2. Move or split the collection. For more information, see the following topics:

    3. Register the instance of PWA with the new application-tier server by using the /RegisterPWA command option with the /force switch.

    4. Wait until the synchronization engine runs through one cycle of updates and updates the instance of PWA.

    5. Unregister the instance of PWA from the old application-tier server by using the /UnRegisterPWA command option.

  • Move Team Foundation Server to another machine or environment. You will need to re-register each instance of PWA that is registered with the current machine. To re-register an instance of PWA, use the TFSAdmin ProjectServer /RegisterPWA command option with the /force switch.

  • Upgrade from Project Server 2007 to Project Server 2010. If you have an instance of Project Web Access that is registered to Team Foundation Server and the synchronization process is running for a collection, you must perform the following procedures before you upgrade the instance from Project Server 2007 to Project Server 2010:

    1. Perform the steps on the following page of the Microsoft website: Database-attach full upgrade to Project Server 2010

    2. To enable the synchronization after the upgrade, open a Command Prompt window, and change to the following directory: Drive:\%Program Files%\Microsoft Visual Studio 10.0\Common7\IDE.

    3. Type the following command:

      TfsAdmin ProjectServer /tfs:TfsURL /previousPWA:URLFor2007 /PWA:URLFor2010

      For more information, see Registering an Instance of PWA to Team Foundation Server.

For more information, see the following topics:

See Also

Concepts

Removing a Component from Participating in Data Synchronization

Administering the Integration of Team Foundation Server and Project Server