Austin Agile DevOps

DevOps in the Cloud
posts - 70 , comments - 7 , trackbacks - 0

Integrating Team Foundation Server (TFS) 2010 and SharePoint (SP) Server 2010 when on Separate Server Machines

The purpose of this post is to provide clear and concise steps for a very specific scenario:

  • Integrating TFS 2010 with SP Server (SPS i.e. formerly MOSS) 2010
  • TFS and SPS are on different server boxes
  • SPS is installed on a single sever machine

NOTE: in my particular case, TFS is an multi-machine configuration using separate server computers for the TFS application and data tiers. The integration I'm describing is between the TFS application tier computer and the SPS computer dedicated to TFS integration.

I used many sources of guidance in my attempts to complete the integration. The sources will be refernced later in the posting.

S1 - Integrate SharePoint 2010 with Team Foundation Server 2010 by Martin Hinshelwood

S2 - Integrating Team Foundation Server 2010 with SharePoint 2010 by Pramod Aachi

S3 - Microsoft Team Foundation Server 2010 MOSS Configuration Tool

S4 - Add Integration with SharePoint Products to a Deployment of Team Foundation Server (MSDN Library)

S5 - Interactions Between SharePoint Products and Team Foundation Server (MSDN Library)

S6 - Create a Web application (SharePoint Server 2010)

S7 - Create a site collection (SharePoint Server 2010)

S8 - Configure Settings for Dashboard Compatibility (MSDN Library)

In general, the steps appear to be many and complicated. They also vary depending upon the source and often assume signficant knowledge of SP. Issues include:

  • The sequence of steps is unclear. For example, when do you install the TFS Extensions for SP Products? Before or after "Creating a Web application and site collection?" Some sources specify installing before and some after.
  • Setting up permissions on the SharePoint There are so many typse of permissions: farm, services, site collection administrators, site collection users, etc... There needs to be a permissions validation utility: perhaps built into the Extensions Configuration Wizard.
  • Exactly what does the TFS 2010 MOSS Configuration Tool do and not do?" The documentation that comes with the utility addresses the to some extent, but it is not clear and the referenced MSDN postings do not provide the details in question.

Be sure and read the followign section on "Problems and Things Not to Do" prior to starting your integration.


  1. Installing SPS 2010 using a local administrator account. You must use a domain account per the guidance
  2. Expecting the configuration tool to create or setup the web application and site collection on the SPS computer for TFS. It doesn't do this. You have to do it manually.
  3. Cannot bring up the newly created site collection on the new web application in the browser Because the default web application uses port 80 and the new web application created for TFS integration also uses port 80, you must use a host header. However, on the SPS server the OS security blocks any local sites where a host header (i.e. different from the server name) is used. And you can't do this from a remote computer because the host header you added is not in the DNS. This can be overcome by:
    1. Changing the security setting on the local box
    2. Adding the host header to the host file on the local box using and on remote boxes usuing the IP of the local box (SPS computer)
    3. As a permanent solution, the host header needs to be added to the DNS

    NOTE: the link to items 1 and 2 above is to a post by Charlie Holland titled "Using the HOSTS file for SharePoint Development."

  4. Excel Services were missing on the SPS 2010 server until the Office Web Applications were installed. See the posting "Excel Services" not found in Service Applications in SharePoint 2010 for details.
  5. The MOSS web parts do not show up. The team portal looks no different than before. I found the site features with the following status:
    • Agile Dasboards - Active
    • Agile Dasboards with Basic Reporting - Active
    • Agile Dasboards with Excel Reporting - Not Active

    When I clicked the Activate button, processing takes place (i.e. the blue status bar on the bottom of the browser appears and completes), but nothing changes. The status of each feature remains unchanged. There is no error message displayed and no error in the event log. I tried to activate the feature (TfsDashboardAgileMoss) from the PS console as well. The SharePoint log does not show any relevant errors that I can tell, but does indicate that the feature is being de-activated immediately after being activated. There is no indication of WHY or WHAT is causing this. The problem was that I was using the standard edition of SPS 2010. TFS/SPS 2010 integration requires the SPS Enterprise Edition. See the "Note" in S8 above. Although the "note" states MOSS 2007, it happpens to also be true for SPS 2010. It would be very helpful if the Extensions Configuration Wizard verified that the Enterprise Features were enabled.

    I upgraded to the Enterprise Edition and everything started working. I was able to get the full TFS/SPS integration for my Team Projects. Here's how I performed the upgrade:

    • Obtained a valid SPS 2010 Enterprise product key
    • Login to SP using the SP Setup account
    • Select Enable Enterprise Features from the SP Central Admin, Upgrade and Migration
    • Selected Enterprise features and enter the PK
    • Go on to Enable Features on Existing Sites
    • Reset IIS using IISRESET /NOFORCE
    • Create a new Team Project and all the MOSS web parts should display on the dashboard


  1. Setup permissions using S4 and S5 as a guide. Ensure TfsSetup and TfsService are member of the SPS Farm Account Group.
  2. Create a new web application and site collection using S6 and S7 as guidance. Here's the specs I used:

    Web App

    • Name: TfsWebApp - 80
    • Port: 80
    • Host Header: [host header name]
    • Content DB name: WSS_Content_TfsWebApp

    Site Collection

    • Title: Tfs
    • URL path: select \sites\ and enter tfs (note: verify that sites is specified as wildcard inclusion)
    • Pri Admin: [domain]\SpSetup
    • Sec Admin: [domain]\sptsvc1

    NOTE: Be sure to test the site collection by bringing it up in a local browser and from a browser on a remote computer (see problem #3 above).

  3. Login to the SP server with [domain]\SpSetup and run the TFS 2010 Pre-Configuration Tool for SharePoint 2010 tool. Be sure to read the instruction document located in the application folder.

    NOTE 1: If you attempt to do this with an account other than [domain]\SpSetup, say with [domain]\TfsSetup, TfsSetup must have admin rights on the SQL Server DB.

    NOTE 2: Excel Services must be available. If they are missing, you can correct this by installing the Office Web Application on the SPS 2010 server. See above in the Problems Encountered section. In retrospect, this problem may not arise if you start with an installation of SPS Enterprise Edition (see last problem noted above)

    After correcting the above noted problems, I was able to successfully complete the execution of the configuration tool. Here is the output from the tool, which is used in subsequent integration steps:

    • Application Id (i.e. the Enterprise Application Definition): tfs
    • Application Friendly Name: Team Foundation Server
    • Administration Account: [domain]\SpSetup
    • Group Account: [domain]\TfsUsers
    • Credential UserName: [domain]\TfsReports
    • Email:
  4. Install the Extensions for SharePoint products on the SPS server. See the section "How to: Install Team Foundation Server Extensions for Windows SharePoint Services" of the TFS Installation Guide.
  5. Add the SharePoint Web Application to TFS
    • Open the TFS console on the app tier server
    • Select SharePoint Web Applications
    • Click Add
    • Enter the information requested
      • You can get this from the SP Central Admin Console under Manage Web Applications
      • For a default location, I used sites\tfs where sites is a managed path with wildcard inclusion and tfs is the home site collection in an earlier step
    • Click the Verify Path button to ensure all network, computer and SP permissions are correctly configured
    • Click OK to add the SharePoint Web Application once the path is verified as valid
  6. Update the default SharePoint site location for existing collections
    • Select Team Project Collections on the TFS console
    • For each collection change the default location. For example to: ...sites\tfs\[collection name]
    • Click the Yes button on the SharePoint site dialog to create a SharePoint collection for the TFS collection. This is the SharePoint collection under which the Team Project portals for that TFS collection will be created.
  7. Create new sites on the new SharePoint sever for existing Team Projects
    • Create a new site under the collection site for the Team Project
    • Verify/setup appropriate permissions
  8. Reconfigure existing Team Projects to use the new SharePoint server
    • Right-click the Team Project in Team Explorer
    • Select Team Project Settings>Portal Settings...
    • Click the Configure URL... button
    • Select the new SharePoint Web Application
    • Update/verify the relative site path. For example: ...sites/tfs/[collection name]/[team project name]
    • Click OK
    • Check the checkbox "Reports and dashboards refer to data for this team project."
    • Click OK
  9. Activate the TFS SharePoint Server dashboard features on the new portal site
    • On the new SharePoint server, go to the Team Project site > Site Settings > Features
    • Depending on the TFS Process Template used to create the Team Project, click the Activate button for the [Agile | CMMI] Dashboards with Excel Reports. NOTE: This will automatically result in the other 2 process template features to be activated as well.
  10. See my posting on TFS 2010 - SPS 2010 MOSS Web Part Connection Refresh Failure to help resolve any access/display issues of the web parts on the stie.

Print | posted on Tuesday, September 28, 2010 2:17 PM | Filed Under [ Agile SCM Talk Blog ]


No comments posted yet.
Post A Comment

Powered by: