Symbolic name does not apply everywhere

TFS can be accessed through a symbolic name like teamsystem.company.com. This is accomplished by creating a dns entry for the name teamsystem.company.com and then running the activatedt command with this name as the argument on the application tier.

We done this on our TFS-server to be able to creating a hot standby later but also to make it easier to move to a different (more powerful) server. But some problems occur.

  1. The links to the builds in the builds report on the reporting site links to the physical machine - not to teamsystem.company.com.
  2. The same applies to the links to the bugs on the Bugs found without corresponding test report.

This applies to the RTM release of TFS. Have we missed some important information or is it a bug

Regards

Christer



Answer this question

Symbolic name does not apply everywhere

  • Jimmy Li

    Hi Christer,

    Try setting the TFSUrlPublic value in the global config located at ..\Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services

    Change to HTTP://<FQDN>:8080

    (Note that you will need to remember to uncomment the portion below.

    <!-- TFS Url for access from internet, used for specifying links in alerts

    <add key="TFSUrlPublic" value="https://www.microsoft.com:8081"/>

    -->

    Thanks,

    Brad



  • Shaby

    This solved the problem! Thanks.

    /Christer


  • Symbolic name does not apply everywhere