Thursday, September 09, 2010
 

Search
Latest entries in the Euricom Team blog
Aug 11

Written by: Euricom
8/11/2009 2:05 PM 


Yesterday I’ve installed a new TFS 2010 Beta 1. Everything was working well from the first time, but we could only access the server with his local name. Our developers work both at the office and at home, so we wanted to enable a (public) fully qualified domain name. The TfsAdminTool seems to be gone so I couldn’t configure the connections like I did with TFS 2008. I couldn’t find either a simple solution but the following procedure did the job. (Without reinstall TFS)

(Temporary) disable the Loop Back Check. Only necessary if you want to test the FQDN on the server. http://support.microsoft.com/kb/926642
Restart
Add your FQDN to the alternate access mapping of SharePoint:  SharePoint 3.0 Central Administration > Operations >Alternate access mappings
Change the RS & WSS locations by editing tbl_LocationMapping table in the TFS Configuration database
IISRESET
Change the WSS connection URLs : Team Foundation Administration Console>[ Your Server] > Application Tier >SharePoint Web Applications>Change SharePoint Web Application>URLs tab>Site Creation URL: http(s)://FQDN
Change the SharePoint/TFS mapping: Team Foundation Administration Console>[ Your Server] >Extensions for SharePoint and Technologies>Modify Mapping>Replace the local name with the FQDN
Clear the TfsRedirect.aspx cache for Team System Web Acces. There is a querystring argument for TfsRedirect.aspx called tf:ClearCache that allows you to clear the cache (if you are a site administrator). So if your site is at http://myserver/sites/Collection0/Project1, you would use the following URL to clear the cache http://myserver/sites/Collection0/Project1/_layouts/TfsRedirect.aspx?tf:Type=WebAccess&tf:ClearCache=1. This will clear the cache and then redirect you to web access. You can use the tf:Test =1 argument without using tf:ClearCache if you want to see the URLs that its going to use, but don't want to forcibly clear the cache.
Clear the TfsRedirect.aspx cache for the Reports: so if your site is at http://myserver/sites/Collection0/Project1, you would use the following URL to clear the cache http://myserver/sites/Collection0/Project1/_layouts/TfsRedirect.aspx?tf:Type=ReportLists&tf:ClearCache=1& tf:Test=1
By Wim Van Hoye, Technology Manager

Tags:

5 comment(s) so far...

Re: Changing the URL of Team Foundation Server (TFS) 2010 Beta 1 to a FQDN

Thanks for this, i did an updated post here, with additional configuraiton. bit.ly/7owSd, almost there!

By Keith Patton on   10/22/2009 10:26 AM

Re: Changing the URL of Team Foundation Server (TFS) 2010 Beta 1 to a FQDN

Well, that makes sense.
www.rapidsharemix.com

By Camryn on   12/19/2009 7:11 PM

Re: Changing the URL of Team Foundation Server (TFS) 2010 Beta 1 to a FQDN

Does this method work for TFS 2010 RC as well?

By Sammy on   2/13/2010 7:46 PM

Re: Changing the URL of Team Foundation Server (TFS) 2010 Beta 1 to a FQDN

Anyone did this with TFS 2010?

By Targan on   3/1/2010 10:28 PM

Re: Changing the URL of Team Foundation Server (TFS) 2010 Beta 1 to a FQDN

To optimize the network hops, I configured my internal DNS to resolve to internal IP addresses instead of public IP addresses. This optimizes the TFS communication traffic at the office.

Lesson Learned:
I had to configure my internal DNS server like this;
Add Foward Lookup Zone with the name tfs.company.com.
A-record WITHOUT a name and with the internal IP address.
If you would add a Foward Lookup Zone with the name company.com this will break all other nslookup's for company.com.

By Tjerk Drouen on   6/11/2010 10:27 AM

Your name:
Your email:
(Optional) Email used only to show Gravatar.
Your website:
Title:
Comment:
Add Comment   Cancel 
Copyright (c) 2010 Euricom ::Terms Of Use::Privacy Statement