Team Development with Visual Studio Team Foundation Server

• Your remote users cannot add Microsoft Active Directory® groups to folders in source
control.
• Your remote users will not be able to initiate or manage builds remotely.
• Your remote users cannot create new team projects.
• Your remote users cannot publish test results to your TFS.
Note: Whenever you use Basic authentication, use SSL. Basic authentication transmits
credentials in clear text. Use SSL to protect this information.
Locating TFS in an Extranet (“Hosted Scenario”)
Figure 17.4 shows architecture for hosting TFS in an extranet.
Figure 17.4 TFS Hosted in an Extranet Architecture
With this approach, you install your complete TFS infrastructure―both application tier and data
tier―inside your perimeter network, off of your internal intranet. All connections to your TFS
come over the Internet, whether they are from external or internal users. TFS can work with or
without a domain controller (DC). If your perimeter network does not have access to a DC, the
Active Directory service features of TFS will not work. For example, adding users to TFS
groups, or adding an Active Directory group to folders in source control, will not work without a
DC. This option will not work unless you have TFS SP1 installed.
Advantages
• Your TFS users are cleanly segregated from your internal network.
• Your remote users do not need access to the domain.
Disadvantages
• You cannot use the TFS Proxy at the remote location.
• Your remote users cannot initiate or manage builds.
• Your remote users cannot create new team projects.