TechPrufer
Get started
Microsoft
Microsoft logoMicrosoft · Feature trail

Team Foundation Server and Project Server Integration

4 posts · Dec 2005 – Aug 2017

What this trail covers

This thread tracks the evolution of Team Foundation Server (TFS) and Project Server integration, focusing on synchronization, reporting, and configuration. Recent updates include manual configuration for MOSS 2010 dashboard compatibility with TFS 2010, including screencasts, and detailed guidance on verifying the synchronization process for TFS and Project Server integration. It also covers manually updating work item type definitions when mapping issues arise and emphasizes the need for Classic. This post announces the deprecation of the TFS Extension for SharePoint and its web parts, moving towards a loosely coupled model using public APIs and extensibility frameworks. Future integration will focus on embedding TFS/VSTS Dashboards on SharePoint pages and leveraging Power BI for reporting. The Team Explorer Documents pane is also being removed, with a recommendation to use OneDrive for Business sync client.

All Microsoft trails
  1. The future of our TFS/SharePoint IntegrationThis post announces the deprecation of the TFS Extension for SharePoint and its associated features: automatic SharePoint site creation with team projects, TFS Web Parts on classic SharePoint sites, and the Team Explorer Documents pane. It outlines the rationale for this change, citing the evolution of both TFS/VSTS and SharePoint towards cloud experiences and the limitations of the existing tightly coupled integration. The post details the future direction, which involves a loosely coupled model using public APIs, embedding TFS/VSTS Dashboards on SharePoint pages, and leveraging Power BI for reporting. It also provides guidance on upgrading from SharePoint 2013 to SharePoint 2016 and disabling SharePoint integration after upgrading to TFS 2018 RC1, including links to documentation and private preview solutions for these scenarios.
  2. Querying Lab Environments Using TFS Lab Management APIsThis post introduces code examples for querying lab environments using TFS Lab Management APIs. It demonstrates how to obtain a reference to the lab service, create a lab environment query specification, run the query to get a list of environments, search for a specific environment by name, and then iterate over the lab systems within that environment to retrieve their computer names.
  3. TFS Lab Management with multiple SCVMM serversThis post clarifies how to configure separate SCVMM servers for different TFS Team Project Collections using the TfsLabConfig command tool. It details the necessity of unique MAC address ranges for each SCVMM server to prevent conflicts and recommends distinct SCVMM host groups and library shares per collection.
  4. Team Foundation Server 2012 and Project Server 2010 IntegrationThis post details the upgrade process from Team Foundation Server (TFS) 2010 SP1 and its Project Server 2010 Feature Pack to TFS 2012 and the TFS Project Server Extension 2012. The procedure involved uninstalling the previous versions, installing SQL 2008 R2 SP2 as a prerequisite, and then installing TFS 2012 with the upgrade option. The integration of Project Server functionality is now handled by a 'Project Server Extensions' folder within the main TFS installer, simplifying the process compared to previous versions.
  5. Creating Team Foundation Server 2012 Lab Management Standard Environments and getting error “Verify that the machines are accessible using the user name and password provided”This post addresses a specific error encountered during the setup of Team Foundation Server 2012 Lab Management standard environments when using non-domain-joined machines. The error, "Verify that the machines are accessible using the user name and password provided," is resolved by disabling "Remote User Access Control" on the standard environment machine. This is achieved by adding and modifying the `LocalAccountTokenFilterPolicy` DWORD value to `1` in the registry at `HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionPoliciesSystem`.
  7. VS ALM Library Updates on MSDN for June 2010This post details updates to the ALM Library for June 2010, specifically focusing on the Team Foundation Server and Project Server Integration Feature Pack. It includes a new topic on verifying the synchronization process and guidance on manually updating work item type definitions. It also emphasizes the requirement for Classic Mode Authentication for SharePoint web applications and provides access to demo videos.
  8. VS ALM Library Updates on MSDN for May 2011This post details rules governing specific field updates in the Team Foundation Server and Project Server integration feature pack. It explains how data type, the OnConflict field mapping attribute, and task hierarchy influence the synchronization engine's update process for specific fields. It also provides links to resources for configuring MOSS 2010 on TFS 2010, troubleshooting the TFS 2010 MOSS Configuration Tool, and understanding SQL Server permissions for TFS installations and service accounts.
  9. VS ALM Library Updates on MSDN for December 2010This post announces the release of Visual Studio 2010 Feature Pack 2, which includes extended testing capabilities and code visualization/modeling capabilities. It also highlights new documentation for these features, including playback tests using Firefox, editing coded UI tests with the Coded UI Test Editor, and creating coded UI tests for Silverlight 4 applications. Additionally, it details updates to the MSDN ALM Library for Eclipse integration with Team Foundation Server, portfolio management through TFS and Project Server integration, and build customization with the build activity reference and build process object model. Finally, it covers Lab Management capabilities and planning for virtual labs.
  10. Manage and Track Your Software Project Portfolio in both Team Foundation and Project ServerIntroduces the Visual Studio Team Foundation Server 2010 and Project Server Integration Feature Pack (Beta), enabling data flow from TFS work items to Project Server enterprise project plans. Details three methods for managing projects, the synchronization process, and configuration options for test and production environments. Also outlines content organization for project management and administration.
  11. Sample Code: Connect to Team Foundation ServerThis post provides sample C# code for programmatically connecting to Team Foundation Server (TFS) and accessing team projects within project collections. It demonstrates how to use TfsConfigurationServerFactory.GetConfigurationServer to establish a connection and then query the catalog to list team project collections and their contained team projects. The post also lists various services accessible via TfsConfigurationServer and TfsTeamProjectCollection classes, such as ITeamFoundationRegistry and VersionControlServer.
  12. Getting Started with Team FoundationThis post introduces Team Foundation as a set of tools and technologies for team collaboration and product development. It details how Team Foundation enhances communication through project portals, Team Explorer, alerts, source control, and builds. It also explains work item tracking, history, queries, and integration with Microsoft Project and Excel, as well as reporting capabilities. The post outlines roles in process, security groups, process enactment via XML customization, and tool integration, particularly within the Visual Studio IDE and through extensibility. It concludes with guidance on where to start for Project Administrators, Project Leads, and Project Members.