Team Foundation Proxy – Your friend for distributed development teams

Since you can only deploy one master TFS server and replication mechanisms are not supported you might consider using a TFS Proxy server, which caches the downloads from the Team Foudation Version Control.


Functionality / What it does:


Cache downloads from Version Control only. Control Messages and other artifacts like work items are still transferred directly between client (Visual Studio) and server (TFS).

Read more about how the proxy works.


Licensing:


From a licensing perspective the TFS Proxy costs you one (additional) TFS license.

See also: Licensing whitepaper.


Installation


You find the installation files on your TFS CD under Proxy\setup.exe.

After the installation is complete you need to modify the configuration file.

See also: hardware requirements.


More Information (including all links mentioned above):


2 thoughts on “Team Foundation Proxy – Your friend for distributed development teams”

  1. Any product that requires a homogeneous DOMAIN across all servers (including that remote proxy) is not the answer.

    We want the remote users on their own domain, pushing and pulling data across the smallest number of ports possible. Not trying to authenticate to the master domain.

    Sad really – I had real hope for TFS

  2. Jim, my experience does not fit in what you say. Many companies have successfully deployed TFS in their environments – either using domain trusts, or using active directory for their employees only and creating user accounts for the external users directly on the TFS. Wouldn’t that solve your problems?

    N.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>