Configuration Quick Reference

Before you can synchronize data between Visual Studio Team Foundation Server 2010 and Office Project Server 2007 with Service Pack 2 (SP2) or Project Server 2010 with Service Pack 1 (SP1), you must first install and configure the integration software. You can use this topic as a quick reference to install software, assign permissions, configure integration, and verify data synchronization. To perform more customized configurations or for more detailed procedures, see Configuring the Integration of Team Foundation Server and Project Server.

Note

To ask a question of the community, see the following forum post on the Microsoft website: Team Foundation Server and Project Server Integration.

In this topic

• Install and Configure Prerequisite Software

• Install Software

• Assign Permissions

• Configure Integration

• Verify Data Synchronization

Required Permissions

To perform the procedures in this topic, you must belong to the following groups or have the following permissions:

• To register an instance of Project Web Access or Project Web App (PWA), you must belong to the Team Foundation Administrators group and to the Administrators group for each instance of PWA that you will register.

• To grant Team Foundation permissions: you must belong to the Team Foundation Administrators group or your View instance-level information and Edit instance-level information permissions must be set to Allow. You must also have access to the Team Foundation Administration Console or the Group Membership dialog box for a team project collection by using Team Explorer.

• To grant Project Server permissions: you must have Manage users and groups global permission for an instance of PWA. You must also have access to Project Server through PWA.

• To grant SSP permissions: you must belong to the Farm Administrators group, the SharePoint Administration group, or the administrators group for the Web application that supports Project Server. Group membership will depend on the security architecture of your deployment.

• To use stsadm.exe: you must be an administrator on the local computer.

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

Install and Configure Prerequisite Software

The following table summarizes the prerequisite software that you must install and configure before you install Service Pack 1 (SP1) for Visual Studio 2010, Team Foundation Server, and the Feature Pack for Team Foundation Server and Project Server Integration:

Step	Task	Machine	Notes
	Install Team Foundation Server 2010.	Each application-tier server for Team Foundation Server that will participate in data synchronization with Project Server.	You must install Team Foundation Server 2010 before you install Service Pack 1 (SP1) for that product.
	Install Office Project Server 2007 with SP2 and the cumulative update that the following page on the Microsoft website describes: Description of the Project Server 2007 hotfix package: August 25, 2009. or Install Project Server 2010 with the updates that the following pages on the Microsoft website describe: Description of Project Server 2010 SP1, Description of the SharePoint Server 2010 and Project Server 2010 Cumulative Update Server Hotfix Package (MOSS server-package, Project server-package): June 28, 2011. Announcing The Release Of Service Pack 1 (SP1) for Microsoft Project and Project Server 2010.	On each application-tier server that hosts Project Server 2007 with SP2 and that will participate in data synchronization or each web-tier and application-tier server that hosts Project Server 2010 and that will participate in data synchronization.	Project Server 2007 must be supported by SQL Server 2005 or SQL Server 2008. Important The SharePoint web application for the instance of PWA must be set to Classic Mode Authentication. You will not be able to register the instance of PWA if it is set to Claims Based Authentication. For more information, see the following page on the Microsoft website: Updates for Project Server 2010.
	Project Server 2010 Only. Run the SharePoint Configuration Wizard. For more information, see Deploy cumulative updates (Project Server 2010).	On each application-tier server that is running Project Server 2010 in the server farm.	After you install the cumulative updates for Project Server 2010, you must run the SharePoint Configuration Wizard to integrate Project Server with SharePoint Server 2010.
	Install Visual Studio 2010 or Team Explorer 2010. You can download Team Explorer from the following page on the Microsoft website: Microsoft Visual Studio Team Explorer 2010 - ISO.	Each client machine or server that you will use to configure and administer the integration of the two products.	You must install SP1 for Visual Studio 2010 on each client machine to get the command-line tool that supports Team Foundation Server and Project Server integration.
	Install Visual Studio 2010 or Team Explorer 2010 and one of the following versions of Office Project: Project Professional 2007 with SP2 and the update that you can download from the following page on the Microsoft website: Description of the Office Project 2007 hotfix package (Project-x-none.msp): February 23, 2010. Project Professional 2010 and the update that you can download from the following pages on the Microsoft website: Description of Project 2010 SP1. Description of the Project 2010 hotfix package (project-x-none.msp): June 28, 2011.	Each client machine on which Project Professional will be used to synchronize data between enterprise project plans and team projects.	You must install SP1 for Visual Studio 2010 on each client machine to get the plug-in that supports integration between Team Foundation Server and Project Server.

Note

You do not need to deploy Active Directory, but it is highly recommended so that you can more easily synchronize the accounts of users, groups, and services that are valid within Team Foundation Server and Project Server.

Back to top

Install Software

The following table summarizes the installation steps that you must perform. To install software, you must have administrative permissions on the machine where the software is installed.

Step	Task	Machine	Notes
	Install Service Pack 1 for Visual Studio Team Foundation Server 2010.	Each application-tier server for Team Foundation Server 2010 that will participate in data synchronization with Project Server.	The software that supports data synchronization is automatically installed with Service Pack 1. You can download the service pack from the following page on the Microsoft website: Service Pack 1 of Visual Studio Team Foundation Server 2010.
	Install the Feature Pack for Team Foundation Server and Project Server Integration.	On each App tier server that hosts Project Server 2007 with SP2 and that will participate in data synchronization or each Web tier and App tier server that hosts Project Server 2010 and that will participate in data synchronization.	Only those machines that have the feature pack installed can participate in data synchronization between the two products. To access the feature pack, you must have an MSDN subscription for Visual Studio Ultimate. You can download the feature pack from the following page on the Microsoft website: Feature Pack for Visual Studio Team Foundation Server and Project Server Integration Important For Project Server 2010 deployments, you must install the 64-bit version of the feature pack.
	Install SP1 for Visual Studio 2010.	Each client machine on which Project Professional will be used to synchronize data between enterprise project plans and team projects. Each client machine or server that you will use to configure and administer the integration of the two products. Important You must install SP1 for Visual Studio 2010 to obtain the add-in for Project Professional, but you do not require a client access license (CAL) to interface with the integration of Team Foundation Server and Project Server.	Each project manager who will manage enterprise project plans that will participate in data synchronization with Team Foundation must install the add-in to Project Professional. Also, each administrator who will configure the integration of the two server products requires the software that is installed with Service Pack 1 for Visual Studio 2010. This software configures the add-in to Project for the integration. The service pack also adds the TFSAdmin command-line tool, which is required for configuring the integration. You can download the service pack from the following page on the Microsoft website: Service Pack 1 of Visual Studio 2010. You must install this software on a machine on which Visual Studio 2010 or Team Explorer 2010 is already installed.

Back to top

Assign Permissions

To assign permissions, you must have administrative permissions for the software elements that you are configuring. You must assign administrative permissions for Team Foundation Server and an instance of Project Web Access or Project Web App (PWA) to the user who will configure the integration of these products. The following table summarizes the permissions that you must assign. You should make these assignments after you have installed the service packs and feature pack that were described earlier in this topic. You assign most permissions through the Team Foundation administration console for a project collection, the Project Security dialog box for a team project, or through the Manage Users or Manage Groups web pages for an instance of PWA.

Note

To assign the minimum set of permissions to service and user accounts, see Assigning Permissions to Support Integration of Project Server and Team Foundation Server. The following table outlines permissions that you can assign quickly by adding accounts to default security groups.

Step	Permissions	User accounts	Notes
	Add to the Team Foundation Administrators group.	Account of user who will configure the integration of Team Foundation Server and Project Server.	This user will use the TFSAdmin command-line tool, which is installed on the same client machine as Visual Studio 2010. Note You must have administrative permissions to register each instance of PWA that will participate in data synchronization. For all other mappings, only the Administer Project Server integration permission is required.
	Set the Administer Project Server integration permission to Allow.	Accounts of project managers or other users who will manage the mappings of enterprise project plans to team projects and manage the configuration of the two server products.	These users will configure the integration of the two server products by using the TFSAdmin command-line tool.
	Assign administrative permissions for the instances of PWA that will participate in data synchronization.	Account of user who will configure the integration of Team Foundation Server and Project Server and, more specifically, register the instances of PWA with Team Foundation Server. Service account for Team Foundation Server.	This user will use the TFSAdmin command-line tool. The TFSAdmin command performs its functions through the service account for Team Foundation Server. This account also runs the Team Foundation Background Job Agent Service. This agent manages data synchronization processes. This account requires permissions to access each instance of PWA that is mapped. All service accounts for Project Server and SharePoint Products must be granted interactive logon permissions for the computer on which the service is running.
	For Project Server 2007: Access to the Shared Services Provider (SSP).	Service account for Team Foundation Server.	For every Shared Services Provider that serves a SharePoint web application that hosts a PWA that will be mapped, you must open a Command Prompt window, and change directories to Drive:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\bin\. For 64-bit machines, the directory is Drive:\Program Files (x86)\Common Files\Microsoft Shared\Web Server Extensions\12\bin\. Type the following command, where TFSServiceAccount is the service account for Team Foundation Server: stsadm.exe -o editssp -title SharedServices -setaccounts "ExistingProcess Accounts,TFSServiceAccount" You can use the following command as an example: stsadm.exe -o editssp -title SharedServices -setaccounts "MyDomain\Account1,MyDomain\TFSServiceAccount" For more information, see the following page on the Microsoft website: Stsadm command-line tool (Office SharePoint Server).
	For Project Server 2010: Full Control permissions to invoke the Project Server Service Application.	Service account for Team Foundation Server.	To add a service account to a service application by using SharePoint Central Administration (2010) Open the SharePoint Central Administration page for Project Server. Under Application Management, click Manage service applications. On the Manage Service Applications page, highlight the row for Project Server Service Application by clicking within the row but not the name of the application. The ribbon becomes available. In the ribbon, click Permissions. In the Connection Permissions for Project Server Service Application dialog box, type the name of the service account, and then click Add. In the middle pane, make sure that the name of the service account that you just added is highlighted. In the bottom pane, select the Full Control check box, and then click OK.
	For Project Server 2010: SQL Server database permissions.	Service account for the web application pool for Project Server 2010.	Grant the service account for the Project Server web application pool the following SQL Server permissions for the PWA Reporting database: Alter any Schema, Create Table, Delete , Execute, Insert, Select, and Update. For the PWA Publish database, grant the Select permission. For more information, see Grant Permissions to PWA Databases to the Service Account for the Web Application Pool for Project Server 2010.
	Add to the Team Members group of PWA.	Team Foundation team members who will submit status updates to Project Server from a client of Team Foundation.	You must add team members to the Team Members group for the PWA, or you must grant them the following minimum set of Project permissions: Open Project and View Project Site.
	Grant permissions to contribute to the team project in Team Foundation Server.	Users of Project Professional who will publish plans to Team Foundation.	Grant View Project-level information permissions in Team Foundation, or assign them as members of the Reader group for the team project.

Back to top

Configure Integration

The following table summarizes the minimum set of steps that you must take to configure integration of the two products. Each step uses the TfsAdmin command-line tool, which you can find in Drive:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE on a computer that is running Service Pack 1 for Visual Studio 2010. For 64-bit machines, the tool is in Drive:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE. To perform more customized configurations, see Configuring the Integration of Team Foundation Server and Project Server.

Note

Even if you log on with administrative permissions, you must open an elevated Command Prompt window to run the TfsAdmin command-line tool on a server that is running Windows Server 2008. To open an elevated Command Prompt window, click Start, right-click Command Prompt, and then click Run as Administrator. For more information, see the following page on the Microsoft website: User Access Control.

Step	Task
	Register an instance of PWA. You must register each instance of PWA that supports the enterprise project plans with the application-tier server that hosts the team projects that will participate in data synchronization. You should register all instances of PWA that are used by enterprise project plans that must synchronize their data with a team project. TfsAdmin ProjectServer /RegisterPWA /pwa:pwaUrl /tfs:tfsUrl Replace pwaUrl with the Uniform Resource Locator (URL) of the instance of PWA and tfsUrl with the URL of the application-tier server. The following example registers PWAInstance to AdventureWorksServer: TfsAdmin ProjectServer /RegisterPWA /pwa:http://PWAServerName/PWAInstance /tfs:http://AdventureWorksServer:8080/tfs/ Note The default port for Team Foundation Server is 8080. For more information, see How to: Verify or Correct Port Assignments.
	Map the PWA instance with a team project collection. You must map each instance of PWA that supports an enterprise project plan. You should map all instances of PWA that are used by enterprise project plans that must synchronize data with team projects. TfsAdmin ProjectServer /MapPWAtoCollection /pwa:pwaUrl /collection:tpcUrl Replace tpcUrl with the URL of the team project collection. The following example maps Collection0 to PWAInstance, which is defined on AdventureWorksServer: TfsAdmin ProjectServer /MapPWAToCollection /pwa:http://PWAServerName/PWAInstance /collection:http://AdventureWorksServer:8080/tfs/Collection0
	Upload default field mappings. You must define the field mappings for each project collection that you have mapped to an instance of PWA. You can use the default field mappings as a starting place and customize them only if necessary. TfsAdmin ProjectServer /UploadFieldMappings /collection:tpcUrl /useDefaultFieldMappings The following example uploads the default field mappings to Collection0 on the AdventureWorksServer: TfsAdmin ProjectServer /UploadFieldMappings /collection:http://AdventureWorksServer:8080/tfs/Collection0 /useDefaultFieldMappings For more information, see Customizing the Field Mapping Between Project Server and Team Foundation Server.
	Associate an enterprise project plan with a team project. Before you can map a project plan, you must first publish it to Project Server, and the team project must be defined in the collection. You must map each enterprise project plan to the team project that contains data that you want to synchronize. You also must indicate which types of work items you want to participate in synchronization. TfsAdmin ProjectServer /MapPlanToTeamProject /collection:tpcUrl /enterpriseproject:PlanName /teamproject:ProjectName /workitemtypes:ListOfTypes Replace PlanName with the name of the enterprise project plan, ProjectName with the name of the team project, and ListOfTypes with the names of the types of work items. For example, you can specify the following types of work items to support an agile process as "User Story,Task" or "User Story",Task. If your project is based on a formal (CMMI) process template, you can specify "Requirement,Task". Do not include a space after the comma. The following example maps MyEnterpriseProjA to MyTeamProjB in Collection0 on AdventureWorksServer and specifies that user stories and tasks will participate in synchronization: TfsAdmin ProjectServer /MapPlanToTeamProject /collection:http://AdventureWorksServer:8080/tfs/Collection0/ enterpriseproject:MyEnterpriseProjA /teamproject:MyTeamProjB /workitemtypes:"User Story,Task" Note The /nofixedwork flag is optional. Specify this flag only if you want Project Server tasks that are mapped to work items in Team Foundation not to be assigned to the Fixed Work task type. If you mapped your project plan while it was open, you should close and re-open it for the changes to register. When you open the plan, you should verify whether the Publish to Team Project and Work Item Type (Text30) columns appear. The presence of these columns indicates that the project plan has been mapped to a team project.
	Add team members to the resources for a project plan. For each task that is published to the team project, you must assign a valid contributor of the team project as a resource. You must also identify as a valid contributor any team member who submits work items that are synchronized with Project Server. To identify valid contributors, you must add team members from the enterprise resource pool to the resources for the enterprise project plan. Each time that you add team members to the resources for a project plan, you must publish the project plan so that the synchronization engine will register the changes. For more information, see Add resources to the enterprise resource pool.

Back to top

Verify Data Synchronization

You can verify that data is being synchronized by performing the steps that the following table summarizes. Perform these steps by using the enterprise project plan and the team project that you mapped when you configured the integration.

Step	Task	Procedure
	Program Manager: Add a task, and set it to synchronize with Team Foundation Server.	Important Make sure that you close the project plan after it was mapped and then re-open it. In a mapped enterprise project plan, define a user story, task, or requirement. Make sure that you assign the following fields: Resource Names, Publish to Team Project, and Work Item Type (TFS). Save the plan, and then publish it to Project Server. You can verify that the plan has been published if you check the status bar in your project plan.
	Team Lead: Verify that the tasks that were added in step 1 appear as work items in Team Foundation.	In Team Explorer, run the Product Backlog or Work Breakdown team query. The new work items should appear within a few minutes of the plan being published to Project Server. Open the work item, and verify that the Project Server Sync message has been added to the history field.
	Team Lead: Change one of the work items that was replicated in Team Foundation. Add a work item, and set it to publish to Project Server.	Open the replicated work item, click the Project Server tab, and modify a field. For example, you can modify the Remaining Work field. Create a work item, set the Submit to Project Server field to Yes, and save the work item. Note You can submit only those work items that are types that were configured to participate in data synchronization.
	Program Manager: Review and approve the updated status for the submitted work items.	From a web browser, open your Approval Center, and verify that a status update appears for the updated work item and the newly created work item. You should expect the status update to appear after a few minutes. Accept the status updates, and add a comment. Note If your integration is with Project Server 2010, you can verify whether the comments that you add to a status update appear in the History field of the work item. To update your enterprise project plan with the changes that were submitted from Team Foundation, you must accept the updates.
	Program Manager: Verify that the approved work items appear in the enterprise project plan.	Open the enterprise project plan, and confirm that the approved work items appear. You may have to close the project plan and reopen it to view the updates.
	Team Lead: Review the Project Server Sync messages and the status of the submitted work items.	In Team Explorer, refresh your team project. Open the work items that were submitted to Project Server, and review the message that was added to the History field. Click the Project Server tab, and review the values that were assigned to the status fields for Project Server. You should expect the updates to appear after a few minutes.

Back to top

See Also

Tasks

Configuring the Integration of Team Foundation Server and Project Server

Concepts

System and Setup Requirements to Support Integration of Team Foundation Server and Project Server

Managing Project Server Integration with TFSAdmin ProjectServer

Overview of the Synchronization Process for Team Foundation Server and Project Server Integration

Change History

Date	History	Reason
September 2011	Added links to information about SP1 and the cumulative updates for Project 2010 and Project Server 2010. Clarified the need to publish the project plan after you add team members to its resource pool.	Information enhancement.
June 2011	Corrected the procedure for adding a service account to a service application by using SharePoint Central Administration (2010). Added a note that the SharePoint web application for the instance of PWA must be set to Classic Mode Authentication.	Content bug fix.
April 2011	Revised the prerequisite software section to and provide more information and to emphasize the steps that are necessary to support integration with Project Server 2010. Corrected the name of the task for step 2 under the software-installation section.	Content bug fix.