The topic you requested is included in another documentation set. For convenience, it's displayed below. Choose Switch to see the topic in its original location.

A Moderate Team Foundation Server Topology

You can choose to configure Team Foundation Server in a number of topology configurations. Generally speaking, the simpler the topology, the easier a Team Foundation Server deployment will be to maintain. Deploy the simplest topology that meets your business needs. This topic describes a moderately complex Team Foundation Server topology, with the logical Team Foundation data tier and application tier installed on separate servers.  Team Foundation Server can be accessed by client computers in multiple domains.

A moderate server topology will use two or more servers to host the logical Team Foundation data and application tier components. The following diagram demonstrates a moderately complex Team Foundation Server topology:

Moderate Server Topology

In this example, the Team Foundation Server services are deployed on one application-tier server. The Team Foundation Server databases are installed on a separate data-tier server. Team Foundation Build and the team's test rig (agents) are deployed to additional servers. In this diagram, the domain represents a child domain located in the same office as the parent domain. The child domain has a 2-way transitive trust relationship with Users in the child domain can access the server. These users are authenticated automatically using Windows integrated authentication. In this configuration, there is no need for Team Foundation Server Proxy and it is not installed. This example is designed for a moderately-sized product development team with under 1,000 users. For more information about choosing a deployment topology that best suits your business needs, see Team Foundation Server Planning Roadmap.

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2014 Microsoft