For source control, we do support a proxy feature and following are some details on TFS proxy.

TFS Proxy provides better support for distributed teams using Team Foundation Server for source control. The proxy would cache copies of source control files in the location of the distributed team, thus significantly reducing the bandwidth-intensive operation of downloading files into a user?? workspace.

The Proxy is installed at remote office and is configured to point to Team Foundation Server at Main office.TFS clients at the remote office are configured to use TFS proxy.

Please refer to TFS Installation guide for instructions on how to install and configure Team foundation Server Proxy.

http://www.microsoft.com/downloads/details.aspx?familyid=e54bf6ff-026b-43a4-ade4-a690388f310e&displaylang=en

Regarding Bandwidth utilization,our general recommendation is to have DSL Speeds. With a TFS proxy Server, anything in the hundreds of Kbps will perform adequately.

Also, refer to the following blog on Accessing Team Foundation Server Remotely

http://blogs.msdn.com/robcaron/archive/2006/02/22/537485.aspx

Rajesh

Our testing has shown that VSTS is faster than VSS. For more details refer to Chris's response in the following forum post.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=253360&SiteID=1

As i said before our general recommendation is to have DSL speeds.

Downloading files to an user?? workspace is one of the very common and bandwidth intensive operation. TFS Proxy is basically used to improve download experience over low bandwidth/high latency networks. All Version Control Operations that involves file download will go through proxy. Following are some examples : Get, Unshelve, Compare,Undo, View, Branch

Here is a sample Proxy Performance Results (Get performed from command line)

Scenario Diference between using Proxy
and without using proxy

3500 files (2000 10 kb files, 6X
1000 50 kb files and 500 100kb files)

10 10 MB files 25X

1 Large File (1.9 GB file) 28X

The above results are based on the following test environment.

*client and proxy deployed on the same LAN
*client and proxy connect to AT over a 3 mbps connection

Hope that helps !!

Rajesh

The following settings are required inorder for proxy to be in a different domain than the Application Tier.

• Establish a one way trust between Application Tier and Proxy (basically, Application Tier trusts Proxy)
• Run proxy as an account which resides in the same domain as the proxy. (for example DomainB\userA)
• For authorization purpose, proxy service account needs to be a member of the TFS Valid Users group.

As i said before, All Version Control Operations that involves file download will go through TFSProxy. Following are some examples : Get, Unshelve, Compare,Undo, View, Branch

At a high level, this is how TFS Proxy works

Proxy caches only the files and does not store any metadata (say which version of a file exists in a workspace) about the files. All the metadata exchange takes place between the client(s) and Application Tier. For instance a "get" request has 3 parts

• Client sends a GetRequest to Application Tier and retrieves GetResponse (metadata about the files that needs to be downloaded)
• Client loops through the results of GetResponse and downloads files from Proxy (if proxy is enabled)
• After downloading files, client sends an acknowledgment to Application Tier indicating that a specific version of a file was successfully downloaded to the client workspace

TFS Proxy Security

The TFS Proxy uses a pre-authenticated ticket schema for determining whether a requesting user is authorized to view the contents of the requested file. In the scheme, the user's client contacts the TFS Server and if the user is authorized, the client is provided a digitally signed ticket containing the details of the file being requested. The client then presents the tickets to TFS Proxy. This use of public and private key signatures allows the proxy to be certain that the ticket came from the TFS server and that the user is therefore authorized to view the file. The proxy then looks in the cache to see if it can service the request , and if not, requests the file from the server and adds it to the cache.

After you are done with installing and configuring TFS Proxy,

Perform a ??orce??get on a file from source control explorer. Errors (if any) from proxy will be displayed in the output window. If there are no errors then you should see some new folders and files under ??program Files%\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\VersionControlProxy\Data\<guid>??on the proxy machine.
Also you can navigate to http://localhost:8081/VersionControlProxy/v1.0/ProxyStatistics.asmx using IE on the proxy server and see whether non-zero values are displayed for the performance counters

Hope this helps , Let me know if you have any questions

Rajesh

Typically this will happen if the repositoryGUID sent by the client to proxy is incorrect (or) when the requested TFS is not added to Proxy.Config file.

In this specific case, Proxy received a download request for an AT whose repositoryID is 959fe0e4-f9b5-45ad-88d8-33023d07a378. But none of the AT?? configured in Proxy.Config (<Servers> section) corresponds to this repositoryGUID

Can you try the following options

• Check whether the repositoryGuid in "VersionControl.config" file under %HOMEPATH%\Local Settings\Application Data\ (in your client machine) matches the id value returned by http://YourTFSServerName:8080/VersionControl/v1.0/Repository.asmx (you can execute this from IE on your AT server). Call GetRepositoryProperties after invoking Repository.asmx.

If they don't match then update repositoryGuid value in VersionControl.config file with the id value returned by repository.asmx.

• If the repositoryGUID in VersionControl.Config file has correct value, then make sure that the corresponding TFS URL is configured (under <Servers> section) in Proxy.Config
  Open Windows Explorer and navigate to the Proxy Install directory
  (For example, C:\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services\VersionControlProxy).
  Using Notepad, open proxy.config.
  Locate the following token and make the appropriate substitution, save and close the file.
  Replace @H_TFSSERVER@/VersionControl with http://YourTFSServerName:8080/VersionControl

After updating, your server section should look like this

<Servers>
<Server>
<Uri>http://YourTFSServerName:8080/VersionControl</Uri>
</Server>
</Servers>

Hope this helps and let me know if you still run in to problems.

Rajesh

Basically this exception is thrown when either the TFS server is down or the Server Uri specified on the proxy.config is not valid.

Are you able to browse to http://YourTFSServerName:8080/VersionControl/v1.0/Repository.asmx from your proxy machine ? Can you check whether the URI specified on the proxy.config file is correct?

Can you also reconfirm that you have performed the following.(Not sure which version you are using, If you are using TFSServer RC version then use RC version of Proxy.)

• Establish a one way trust between Application Tier and Proxy (It is enough if Application Tier trusts Proxy)
• For authorization purpose, proxy service account needs to be a member of the TFS Valid Users group.
• Update proxy.config with the correct URI (on the proxy machine)

After updating the proxy.config file, your server section should look like this

<Servers>
<Server>
<Uri>http://YourTFSServerName:8080/VersionControl</Uri>
</Server>
</Servers>

• Direct Client to Proxy

Perform the following steps on the client machine

1. Open VS
2. Go to Tools -> Options -> Source Control -> Visual Studio Team Foundation Server
3. Check ??se proxy server??
4. Server name is <ProxyTierMachine>
5. Port is 8081
6. Click OK

Hope this helps.

Rajesh

Good to hear that you were able to install TFS Proxy successfully.

I would like to clarify few things...

The following settings are required inorder for proxy to be in a different domain than the Application Tier.

• Establish a one way trust between AT and proxy (It is enough if AT trusts proxy)
• Run proxy as an account which resides in the same domain as the proxy (say proxydomain\userA)
• Add proxy service account to ??FS Valid Users??group.
• It is enough if the setup account is added to the local Administrators group on the proxy machine and this account need NOT be the Team Foundation Server Setup account.

Upgrading from Beta3Refresh->RC involves many steps that include backing up data, running utilities to update your installation and performing some manual steps to complete the process.

For complete details on Upgrading to Team Foundation Server RC, refer to

http://blogs.msdn.com/robcaron/archive/2006/02/07/526353.aspx

For B3R to RC Upgrade Troubleshooting guide, refer to

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=240877&SiteID=1

Rajesh

if you dont have any important projects for backing up, you can just un install Beta3Refresh and do a fresh RC installation.

The installation guide is available @

http://www.microsoft.com/downloads/details.aspx?FamilyId=E54BF6FF-026B-43A4-ADE4-A690388F310E&displaylang=en

Rajesh

Hi there,

I am also interesting in knowing if it is possible to have multiple team server installation and have a synchronization among them. This feature is provided by Rational clearcase tool as a multi-site option.

thanks,

-Rekha