26.04.2015 Views

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

Team Development with Visual Studio Team Foundation Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

• Use a VPN connection. You can provide access to TFS over a virtual private<br />

network (VPN).<br />

• Publish your TFS through a reverse proxy. You can provide access to TFS through<br />

a reverse proxy such as Microsoft Internet Security and Acceleration (ISA) <strong>Server</strong>.<br />

• Locate your TFS in the extranet (“hosted scenario”). You can host your TFS<br />

server on an extranet.<br />

If you are supporting remote users <strong>with</strong> VPN access, use the VPN solution. This is the<br />

easiest solution to enable, provides well-understood security, allows remote access to all<br />

TFS features, and allows you to use the TFS Proxy to improve performance. In this<br />

solution Your TFS sits inside the internal network, and external users access it over a<br />

VPN. Internal users access a TFS directly<br />

If you are supporting remote users <strong>with</strong>out VPN access or <strong>with</strong>out access to the domain,<br />

use the reverse proxy scenario. This solution is more difficult to set up, but it enables<br />

remote users to access an internally located TFS <strong>with</strong>out the need for VPN. In this<br />

solution your TFS sits inside the internal network, and one or more reverse proxy<br />

machines, such as ISA <strong>Server</strong>, bring in client requests from the Internet to your TFS.<br />

If you are supporting a set of remote users who will be using a TFS installation dedicated<br />

to their use, such as a community development site, use the extranet scenario. This<br />

solution gives you the most separation between the remote users and your internal<br />

network resources. In this solution only external clients access your TFS, and it is located<br />

outside of the firewall on an extranet<br />

If you are supporting an office <strong>with</strong> multiple clients connecting to a remote <strong>Team</strong><br />

<strong>Foundation</strong> <strong>Server</strong>, you should install and configure <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong> Proxy in<br />

the remote office. This improves performance by caching source control files on the<br />

remote office’s proxy server.<br />

If you are supporting a single client connecting to a remote TFS, configure the client to<br />

connect directly to the TFS.<br />

Additional Resources<br />

• To learn more about TFS remote access scenarios, see “Ch 17 - Providing Internet<br />

Access to <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong>” in this guide<br />

• To learn more about the <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong> Proxy, see “<strong>Team</strong> <strong>Foundation</strong><br />

<strong>Server</strong> Proxy and Source Control” at http://msdn2.microsoft.com/enus/library/ms252490(VS.80).aspx<br />

• For more information about examining TFS proxy performance, see “How to:<br />

Examine Cache Performance for <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong> Proxy” at<br />

http://msdn2.microsoft.com/en-us/library/ms252455(VS.80).aspx<br />

How to optimize TFS Version Control proxy performance<br />

At your remote location, install and configure <strong>Team</strong> <strong>Foundation</strong> <strong>Server</strong> Proxy. This<br />

improves performance by caching source control files in the remote office’s proxy.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!