* Please take the time to comment or digg this post if this post was helpfull*

In our company we use TFS for internal use, but our developers also work from home. Please note that this tutorial was done using a “Standard Configuration” in TFS (Everything on one box).  Should be very much the same for advanced also. Achieving this is considerably easier than it was in tfs 2008, but there’s still no magic change urls button.

So here’s how to do it:

In our company, we use the following urls which resolves internally and externally:

TFS Main: http://tfs.mydomain.com:8080
Sharepoint: http://sp.tfs.mydomain.com
Reports: http://tfs.mydomain.com/reports

To start off, this is what my config looked like before making any changes, just installing all components: 1. Change the main TFS url:

  • Open the IIS Management Console and click on the Team Foundation Server site.  On the right panel click on “Bindings”.
  • Click on “add” in the “Site Bindings” dialog.
  • In the “host name” field, type your FQDN of your new tfs url.

  • Click ok
  • Click Close
  • Go back to the TFS Administration Console and on the application tier node click on “Change URLs”
  • In the Change URLs dialog, change the Notification URL field to your new fqdn you entered in the IIS manager.

  • Your notification and web access urls should change on the application tier summary screen (refresh if need be)

  • To test, open a browser and browse to your new url, which should bring up the TFS web access site.

2. Add alternate access mapings to Sharepoint:

  • Open Sharepoint Central Administration by going to Control Panel / Administrative Tools / Sharepoint Central Administration
  • Click on the operations tab at the top
  • Click on Alternate access mappings under the Global Configuration section

  • Click on “Edit public URLs”

  • In the edit public urls page, enter your full fqdn into the “Internet”  field in the format “http://tfs.mydomain.com”

  • Click on Save
  • Test that you can get to the site by opening a browser and browsing to your sharepoint tfs site (eg: http://sp.tfs.mydomain.com)

  • Back in the TFS administration console, navigate to /Application Tier/Sharepoint Web Applications
  • Click on the item in the listbox which should still be on the local server url, and click on “Change”

  • In the Sharepoint Web Application Settings dialo box, change the friendly and and web application url to your fqdn sharepoint url and click on “Verify Path”

  • If tfs resolves sharepoint correctly, you should get this dialog box

  • Click on ok, and back in the administration console, the listbox will change with the changes you made.

3. Change the Reporting Services URLs:

  • Open the Reporting services configuration manager by going to Start / Programs / Microsoft SQL Server 2008 / Configuration Tools / Reporting Services Configuration Manager
  • Connect to your reporting services instance
  • Click on Report Manager URL
  • Click on Advanced

  • In the Advanced Multiple Web Site Configuration click on Add
  • Enter the fqdn of your report server you want.  We used tfs.mydomain.com

  • Click ok, and the url should be reserved for you

  • Go to the Web Service URL settings and do the same as the report manager config

  • Go back to the TFS administration console, and navigate to /Application Tier/Reporting
  • To do this configuration, you need to first stop all the jobs on the server, so click on “Stop Jobs”

  • You will get a warning, click ok.

  • Now click on Edit
  • In the reporting dialog, go to the Reports tab, and click on Populate URLs

  • In the URLs for Report Server groupbox, select the urls which you just setup in reporting services configuration manager for both the Web Service and Report Manager

  • Click Ok, the urls should now change on the below screen.  Verify they are correct, and start the jobs again.

That’s it!  TFS should be configured for external access, you can double check all your settings on the application tier main node (refresh the page) and make sure all your urls are now FQDN urls.

That’s all there is to it.  TFS should work fine now internally and externally.  In my next post, I will show how to deploy this via ISA 2006 to the outside world

 

If you found this post helped you significantly… Don’t be cheap and pay me for my knowledge.  Thank you :)

Support My Blog

If you think that this blog post has significantly helped you do your job or helped you get around that niggly problem that hindered you from reaching your target, realize that it took me time to write this post and consider compensating my knowledge with a donation. I have bills to pay just like everyone else, and I'm giving out my knowledge for free here...
$ 12.00 raised.
Choose donation amount: