Updating an Existing Installation with Service Pack 1

You should follow the guidelines in this topic when you update a deployment from the beta version of the Feature Pack for Microsoft Visual Studio Team Foundation Server 2010 and Project Server Integration. You can install the release to manufacturing (RTM) version of both that feature pack and Service Pack 1 (SP1) for Team Foundation Server 2010 without losing data. You do not have to uninstall the beta version of SP1 before you install the RTM version.

To locate the most recent version of the software for integrating Team Foundation Server and Project Server, see System and Setup Requirements to Support Integration of Team Foundation Server and Project Server.

In this topic

• Recommended Update Sequence When You Install the RTM Version of the Feature Pack

• Recommended Update Sequence When You Install the Feature Pack on the Application-Tier Server

• Changes Introduced by the RTM Version of the Integration Software

• Updating Mapped Team Project Collections

• Resolving Errors When You Remap Previously Mapped Team Project Collections

Required Permissions

To perform the procedures in this topic, your Administer Project Server integration permission for the team project collection must be set to Allow. Also, the service account for Team Foundation Server must be granted the necessary permissions to interact with the instance of Project Web Access or Project Web App (PWA) that will participate in data synchronization. For more information, see Assigning Permissions to Support Integration of Project Server and Team Foundation Server.

Recommended Update Sequence When You Install the RTM Version of the Feature Pack

You can update Project Server with the RTM version of the feature pack according to one of the following two sequences:

• Recommended. You can uninstall the beta version of the feature pack and then install the RTM version. This sequence will support integration only with Team Foundation Server and other clients of Team Foundation that have been updated with the RTM version of SP1. This sequence is recommended because it blocks connections from sources that are running a beta version of SP1.

• You can install the RTM version of the feature pack on top of the beta version. This sequence will support integration with Team Foundation Server and other clients of Team Foundation that have been updated with either the beta or RTM versions of SP1.

Back to top

Recommended Update Sequence When You Install the Feature Pack on the Application-Tier Server

If you are installing the RTM versions of the service pack and the feature pack on a machine that hosts both Team Foundation Server and Project Server, you should install the feature pack first. If you install the service pack first, the synchronization engine will stop working and report that a method cannot be found. To resolve this error, perform the following actions:

1. Restart the TFSJobAgent.

2. Restart the IIS Admin Service.

For more information, see Stop and Start Services, Application Pools, and Websites.

Back to top

Changes Introduced by the RTM Version of the Integration Software

The RTM release of the Team Foundation Server and Project Server Integration introduces the following changes:

• The switch for specifying the URL for Team Foundation Server was changed for the tfsadmin projectserver commands. The switch was /TFSServerURL and is now /tfs. For example, you now use the following syntax when you register an instance of PWA:

  **TfsAdmin ProjectServer /RegisterPWA /pwa:**pwaUrl **/tfs:**tfsUrl **/previousPwa:**pwaUrl

• You can re-register an instance of PWA by using the /previousPwa and /force switches for the tfsadmin projectserver /RegisterPWA command. For more information, see Registering an Instance of PWA to Team Foundation Server.

• The friendly names of several fields that are used exclusively to manage the synchronization process were renamed. This change has implications if you remap project collections that were previously mapped with the beta version of the feature pack. For more information, see Resolving Errors When Mapping Previously Mapped Team Project Collections later in this topic.

Back to top

Updating Mapped Team Project Collections

Instead of unmapping and then re-mapping a collection, you can avoid errors by running the TfsAdmin ProjectServer /MapPWAtoCollection command. This step will update the collection with field names and global rules that the RTM version of the feature pack introduces. You can find the TfsAdmin command-line tool in Drive:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE on a computer that runs Team Explorer. On 64-bit machines, you can find the tool in Drive:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE.

Run the following command once for each collection that is mapped to an instance of PWA:

TfsAdmin ProjectServer /MapPWAtoCollection /pwa:pwaUrl /collection:tpcUrl

Replace pwaUrl and tpcUrl with the URL of the instance of PWA and the collection, respectively. For more information, see Mapping a Team Project Collection to an Instance of PWA.

Back to top

Resolving Errors When You Map a Non-Updated Collection

An error will appear if you try to remap a collection that was first mapped by using the beta version of the feature pack and then unmapped without first being updated with the current set of global fields and rules. This error appears because several friendly names for fields were updated between the beta version and the RTM release of the feature pack.

To resolve this error, you must change the names of several fields in the collection by using the witadmin changefield command. You can find the witadmin command-line tool in same folder as the TfsAdmin command tool.

Run the following set of witadmin changefield commands, substituting the URL for your collection for MyTPC.

witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.ApprovalWatermark /name:"Project Server Sync Approval Watermark"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.AssignmentData /name:"Project Server Sync Assignment Data"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.IsSummaryInProjSvr /name:"Project Server Sync Is Summary in Project Server"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.LastSubmittedRevision /name:"Project Server Sync Last Submitted Revision"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.LastSyncRevision /name:"Project Server Sync Last Sync Revision"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.LastSyncType /name:"Project Server Sync Last Sync Type"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.ProjGuid /name:"Project Server Sync Project GUID"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.QueueFlags /name:"Project Server Sync Queue Flags"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.RequestedAssnGuid /name:"Project Server Sync Requested Assignment GUID"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.RequestedProjGuid /name:"Project Server Sync Requested Project GUID"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.SubmitTag /name:"Project Server Sync Submit Tag"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.TaskGuid /name:"Project Server Sync Task GUID"
witadmin changefield /noprompt /collection:MyTPC /n:Microsoft.Sync.ProjSrv.TaskModifiedRevCounter /name:"Project Server Sync Task Modified Revision Counter"

Back to top

See Also

Concepts

Administering the Integration of Team Foundation Server and Project Server

Other Resources

Microsoft Team Foundation Server 2010 and Microsoft Project Server Integration Feature Pack

Change History