Partilhar via

Server and Notification URL

  • Artigo

Generally, the Server URL and the Notification URL should not be modified. Both these values are TFS-system-wide. So, if multiple application-tiers exist, modifying either one of these values will impact them on all application-tiers

The Notification URL is the URL used in e-mail alerts. This should only change if

  1. The name of the computer changes
  2. TFS is installed behind a network load balancer. (In which case, the Notification URL should be the front end of the load balancer.)
  3. TFS is only accessible via SSL. (In which case, the Notification URL should be the fully-qualified-domain name)
  4. People external to the Notification URL's default value, https://computername:8080, in which case the Notification URL should be adjusted accordingly.

The Server URL is the URL TFS uses for communicating with itself. This should only be changed if

  1. TFS is only accessible via SSL. (In which case, the Server URL should be the fully-qualified-domain name)
  2. Localhost is disabled on the computer hosting TFS. (In which case, the  Server URL should be https://computername:8080)

Comments

  • Anonymous
    June 19, 2011
    Is valid for both TFS2008 and TFS2010?

  • Anonymous
    March 22, 2012
    The comment has been removed

  • Anonymous
    July 04, 2012
    After updating bindings in IIS site, I have tried setting these up to use tfs.ourdomain.com but can only hit the tfs.ourdomain.com:8080/tfs/web sites on the actual server where tfs is installed. I updated webconfig to include new path to tfsServer also but this didn't help either. I've reversed these changes as I need a working tfs, but I need some advice as I need our tfs implementation to be available to remote workers.