Export (0) Print
Expand All

Configure and manage TFS resources

You configure and manage Team Foundation Server (TFS) and additional resources to support your teams. These resources include the application-tier and data-tier server(s), team project collections which host team projects, and optional resources such as report servers, SharePoint products, build servers, lab management, and more.

Example: possible location of collection databases

For additional information on Team Foundation Server (TFS) components and architecture, see Team Foundation Server architecture.

Through the Team Foundation Server Administration Console, you can manage and monitor your server configuration. Tasks you can accomplish through the administration console are indicated with this image: Team Foundation Server Administration Console.

The Team Foundation Server Administration Console

You can add or remove resources to your deployment to better meet the changing needs of your business and the software projects that you support with TFS. You can add or remove reporting and Web resources at any time. You can also use more than one instance of SQL Server to host the databases for your deployment. For example, you can add a server that is running SQL Server Reporting Services to your deployment after you install and initially configure TFS. You can also upgrade the version of SharePoint Products that supports your deployment and add its capabilities of that product to the team projects that already exist in your deployment.

When you create a team project, you automatically gain access to the following functions:

  • Web access: provides a web interface to TFS that grants access to team projects, Agile planning and tracking tools, version control, and builds. For an overview, see Work in Team Web Access (TWA).

  • Source control repository using Team Foundation version control or Git repositories.

  • Work item tracking: teams can create work items and work item queries to track, monitor, and report on the development of a product and its features. A work item is a database record that stores the definition, assignment, priority, and state of work. Your team can create only those types of work items that are defined in the process template that is used to create the team project or types that are added to the team project after it is created.

    Team members can work in TWA, Team Explorer, or Team Explorer/Eclipse. To learn more about these and other clients that connect to TFS, see Choose the Team Foundation client to support your tasks.

The following table indicates the additional servers and functionality that you must configure for your team to have access to the corresponding feature. You can add resources before or after you have created your team project.

Feature area

Required resources

Related topics

Notes

Feedback requests and email alerts

SMTP Server

Configure an SMTP server to support alerts and feedback requests

The SMTP server you configure supports all team projects created under the project collections defined on the application-tier. If the SMTP server isn’t configured, then links may not appear to access the Request feedback and to set Alerts.

Builds Icon Builds

Team Foundation Build

Configure and manage your build system

The Builds Icon Builds page lists the build definitions defined for your team project. This page appears only when your deployment has installed and configured Team Foundation Build. Access to Team Foundation Build Service requires that the team project collection has been configured to use a build controller. Each build controller is dedicated to a single team project collection. The controller accepts build requests from any team project in a specified collection.

Team Foundation Build enables your team to create and manage product builds. For example, a team can run daily builds and post them to a shared server. Team Foundation Build also provides build reports about the status and quality of each build.See Build the application.

Document node Documents (team project portal)

SharePoint Products

Add SharePoint products to your deployment

How to: Configure a Default Location for Team Project Portals

The Document node Documents page appears only when your team project has been configured with SharePoint Products. After the team project is created, you can configure a SharePoint site or another web location as the project portal. See Share information using the project portal.

Excel reports

SharePoint Products

SQL Server Analysis Services

Add SharePoint products to your deployment

Add a report server

Microsoft Excel reports are uploaded to the Document node Documents folder when you configure your team project with a SharePoint site. With these reports you can track your team project’s burnrate, bug backlog, software quality, test progress, and other metrics. Many of these reports display within your project's dashboards. In addition to the SharePoint Products dependency, Excel reports depend on your team project collection that hosts your team project has been configured with both SQL Server Analysis Services.

For an overview of the default Excel reports, see Excel reports or Excel reports (CMMI).

If your team project doesn't have a SharePoint site, you can still use Excel to create status and trend reports. See Create Excel reports from a work item query.

Report Reports

SQL Server Analysis Services

SQL Server Reporting Services

Add reports to a team project

The Report Reports page appears only when the team project collection that hosts your team project has been configured with both SQL Server Reporting Services and SQL Server Analysis Services. This page provides access to Report Manager and the default and custom reports that you upload to the server that hosts SQL Server Reporting Services. Each of the default process templates that Team Foundation Server provides contain a number of default reports.

For an overview of the default reports, see Reports (SQL Server Reporting Services).

Remote-site support

Team Foundation Server Proxy

How to: Install Team Foundation Proxy and set up a remote site

Configure Visual Studio to connect to TFS Proxy

If some team members are located remotely from the main location for version control, you may want to install and configure Team Foundation Server Proxy to support them. Team Foundation Server Proxy manages a cache of downloaded version control files in the location of the distributed team, which significantly reduces the bandwidth that is needed across wide area connections.

If clients are configured to use Team Foundation Server Proxy, management of the files is transparent to the user. Any metadata exchange and file uploads continue to interface directly with TFS.See Connect to team projects in Team Foundation Server.

Virtual environments

Visual Studio Lab Management

Configuring Lab Management for SCVMM Environments

By using Visual Studio Lab Management, your team can create, assign, and track virtual environments to support application development, deployment, and tests. By using Microsoft Test Manager, your test team can test your application by using these virtual environments. Access to these virtual environments from Test Manager requires that the server where your team project is stored is configured to communicate with Lab Management.

Automate deployments

Release Management

Automate deployments with Release Management

You can support a rapid release cadence and manage simultaneous releases using Release Management. Set up release paths that represent your stages from development to production. Run actions to deploy your app to an environment for that stage. Add approvers to sign off that the app has successfully passed each stage.

Synchronize with Project Server

TFS-Project Server Integration

Synchronize Team Foundation Server with Project Server

By installing Team Foundation Server Extensions for Project Server, project managers can use Microsoft Project Server to access up-to-date project status and resource availability across agile and formal software teams who work in Team Foundation. 

This integration enables data to flow from work items in Team Foundation Server (TFS) to tasks in enterprise project plans in Project Server. Project managers and software development teams can use the tools that they prefer, work at the level of precision that supports their needs, and share information transparently.

Capture production incidents

PreEmptive Analytics

PreEmptive Analytics

PreEmptive Analytics for Team Foundation Server allows development teams to capture production incidents (unhandled, caught, and thrown exceptions) and create and update work items within TFS based on custom rules and thresholds.

You configure PreEmptive Analytics through the Team Foundation Administrator Console.

Show:
© 2014 Microsoft