Export (0) Print
Expand All

Changing the Configuration of Your Deployment

Updated: March 2012

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.

In this topic

Whenever you delete a mapped component, you should unmap it and review the following guidelines:

Back to top

To move a mapped collection to another instance of Team Foundation Server and continue to synchronize data on the new application-tier server, you must perform several steps, based on the following choices:

  • All collections move to a different instance of Team Foundation Server but remain mapped to the same instance of PWA. A recommended practice is to move or split all collections that are mapped to the same instance of PWA at the same time.

  • Some collections move to a different instance of Team Foundation Server, but some collections remain with the same instance. In this case, you must unmap the collections that are split and remap them to the same or to a different instance of PWA that will then be registered with the second instance of Team Foundation Server. An instance of PWA can be registered to only one instance of Team Foundation Server.

To Move All Mapped Collections to a Different Instance of Team Foundation Server

  1. Move or split the collection.

    For more information, see Move a Team Project Collection or Split a Team Project Collection.

  2. Grant required permissions to the service account for the second instance of Team Foundation Server.

    For more information, see Assigning Permissions to Support Integration of Project Server and Team Foundation Server.

  3. Add the Administer Project Server integration permission to those accounts that will run the TfsAdmin ProjectServer command-line tool for the second project collection.

  4. Add the accounts of users who will configure and register instances of PWA to the Team Foundation Administrators group for the second project collection.

  5. Register the instance of PWA with the second application-tier server by using the /RegisterPWA and /force command options.

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

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

Back to top

To Move Some Collections to a Different Instance of Team Foundation Server and a Different Instance of PWA

  1. Use the /UnmapPwaFromCollection command option with the /force switch to unmap each collection that you are moving.

    Caution noteCaution

    By using the /force switch, you break all associations between enterprise project plans and team projects that are defined for the collection.

  2. Move or split the collection.

    For more information, see Move a Team Project Collection or Split a Team Project Collection.

  3. Assign all required permissions.

    For more information, see Assigning Permissions to Support Integration of Project Server and Team Foundation Server.

  4. Use the /RegisterPWA command option to register the second instance of PWA with the second application-tier server.

  5. Use the /MapPwaToCollection command option to map each collection that you moved to the second instance of PWA.

  6. Use the /MapPlapToTeamProject command option to map each plan to the team project that was moved to a different collection.

For more information, see the following topics:

Back to top

You must re-register each instance of PWA that is registered with the current machine.

To move an instance of Team Foundation Server to which an instance of PWA is mapped

  1. Move the instance of Team Foundation Server.

    For more information, see Team Foundation Server Move Types.

  2. Assign all required permissions.

    For more information, see Assigning Permissions to Support Integration of Project Server and Team Foundation Server.

  3. Use the /RegisterPWA command option to register the instance of PWA with the second application-tier server.

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

  5. Use the /UnRegisterPWA command option to unregister the instance of PWA from the first application-tier server.

NoteNote

You must specify the /force switch when you move the project collection to a different instance of Team Foundation Server. If the instance identifier has not changed, you do not have to specify the /force switch.

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 /RegisterPwa /tfs:TfsURL /previousPWA:URLFor2007 /PWA:URLFor2010
    

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

Back to top

Date

History

Reason

March 2012

Corrected the command for registering a PWA instance.

Content bug fix.

August 2011

Minor corrections to clarify certain procedures.

Content bug fix.

June 2011

Addressed additional deployment change configurations.

Information enhancement.

Community Additions

ADD
Show:
© 2014 Microsoft