Team Foundation server proxy initial experience

The role of TFS proxy is to provide a proxy for remote access to TFS, cache, and improve the efficiency of remote access.

Two days ago, we had to install TFs proxy for our team. We wanted to use it to access a TFs on the Internet and perform source control. The installation process is very simple. Under the proxy directory of the TFS installation disk.

Because there is also a local TFS, when installing the proxy, you need to enter an account that runs the proxy service, and I have entered the local TFs running domain account. After the installation is complete, modify the proxy. config file to configure proxy. This is an XML file with the following content:

Proxy. config
<? XML version = "1.0" ?>
< Proxyconfiguration
Xmlns: XSD = "Http://www.w3.org/2001/XMLSchema"  
Xmlns: xsi = "Http://www.w3.org/2001/XMLSchema-instance" >
< Servers >
< Server >
< Uri > Http: // z: 8080/versioncontrol </ Uri >
</ Server >
</ Servers >

<! -- Proxy File Cache root folder -->
< Cacheroot > C: \ Program Files \ Microsoft Visual Studio 2005 team Foundation Server \ Web Services \ versioncontrolproxy \ data </ Cacheroot >

< Cachelimitpolicy >
<! -- Cache limit expressed as percentage of disk space -->
< Percentagebasedpolicy > 75 </ Percentagebasedpolicy >

<! -- Cache limit expressed as MB -->
<! -- <Fixedsizebasedpolicy> 10 </fixedsizebasedpolicy> -->
</ Cachelimitpolicy >

<! -- Percentage of cache size that needs to be freed up, on hitting cache limit -->
< Cachedeletionpercent > 10 </ Cachedeletionpercent >

<! -- Indicates how often (number of hours) the proxy statistics information shocould be persisted to a file -->
< Statisticspersisttime > 20 </ Statisticspersisttime >

< Readerchunksize > 1048576 </ Readerchunksize >
< Writerchunksize > 1048576 </ Writerchunksize >
</ Proxyconfiguration >

 

You can modify the URI to the TFS Uri. You can use the default values for other parameters, but some values are limited. You must pay attention to the modification. Statisticspersisttime is limited to 1 ~ 24.

Configure the client:
First of all, the client needs to install vs2005 + Team explorer, vs2005 is better than team edition, and express is definitely not good. I remember professinal, but I tried it. I cannot install team explorer. I don't know why.

In vs2005, in options in the Tools menu, select Current Source Control plug-in selection from source control to team Foundation server and Visual Studio team Foundation server, select User proxy server, Team Foundation server name: Enter the host name for proxy installation, port 8081, protocol HTTP, OK.

Select connet to team Foundation server from the Tools menu, click the servers button to add the server, and enter the TFS name in team Foundation server name, port 8080 in port, and protocol in HTTP. You can connect to TFs. After the connection is successful, the dialog box for entering the user name and password appears. Enter the user password for verification and connect to TFs. In this way, source control uses the proxy to access TFs.

When installing proxy, note that the account for running proxy must be the same as the account for running TFs.
I have no problem using proxy locally. in <cacheroot> C: \ Program Files \ Microsoft Visual Studio 2005 team Foundation Server \ Web Services \ versioncontrolproxy \ data </cacheroot> the directory contains cached files. If the directory is empty, proxy does not play a role.

When I access TFs whose URI is changed to the Internet, an error message is displayed: I forgot to record it, which means that the proxy has no permission to access it.

I think this error occurs because the account running proxy is different from the account running TFs. Because I used the domain account for running TFs locally when installing the proxy, he certainly has no permission to access the Internet TFs. Run the proxy using the remote TFs running account, and add the account to the Administrators group where the proxy host is installed locally. The host itself may also need to be added to the domain of the other party, this involves domain-related issues, such as domain name resolution and network management. In this regard, I am not refined. After the problem is solved, check whether the Internet TFs can be accessed through the proxy, and notify everyone after the problem is solved.