This project is read-only.

How to support a remote office

- J.D. Meier, Jason Taylor, Alex Mackman, Prashant Bansode

Client and server communication in TFS uses Hypertext Transfer Protocol (HTTP) and Secure HTTP (HTTPS). To support Internet access, publish your TFS application tier in your extranet and install your TFS database on a separate server, also located on the extranet (a dual-server deployment). Configure your Team Foundation Server for HTTPS access by using a server-side certificate.

At your remote location, install and configure Team Foundation Server Proxy. This improves performance by caching source control files in the remote office’s proxy. To configure and optimizing proxy performance:
  1. Make sure that caching is enabled, and monitor the performance of your cache. Monitor the performance counters (installed by default) and event logs (for errors/warnings) on your proxy server on a periodic basis, to see how your proxy is performing. Note: The TFS proxy saves cache performance statistics to an XML file named ProxyStatistics.xml; you can change the interval for saving these statistics. The ProxyStatistics.xml file is located in the App_Data folder in the proxy installation directory.
  2. Run a scheduled task to retrieve the latest files to the proxy server on a periodic basis. This helps to ensure that the latest versions of the files are available in the proxy cache, and to ensure that subsequent client requests for these files result in a cache hit.
  3. If you know that large files are going to be downloaded over a low-bandwidth (< 3 megabits per second Mbps) network, set the executionTimeout configuration to an appropriate value in Web.config. The default value is one hour <httpRuntime executionTimeout="3600"/>.

Additional Resources

Last edited Jul 17, 2007 at 11:58 PM by jtaylorsi, version 8


No comments yet.