How to: Configure Team Foundation Server to Use Fully Qualified Domain Names (FQDN)

Article
02/22/2012

You can configure Team Foundation Server 2005, Team Foundation Server 2008, and Team Foundation 2008 SP1 to use fully qualified domain names (FQDN), such as tfsserver.mycompany.com, for Windows SharePoint Services and Reporting Services. These services include the Team Portal Web site, SharePoint Administrator Web site, and Team Foundation Server Web sites.

This topic is based on Buck Hodge's blog entry Configuring Team Foundation Server to use fully qualified domain names.

Note

To complete these procedures, you must be a member of the Team Foundation Administrators group on the Team Foundation application-tier server and a member of the sysadmin group on the SQL Server on the Team Foundation data-tier server. For more information, see Team Foundation Server Permissions.

Team Foundation Server 2005

Use this procedure to update all address rows in the tbl_subcription table of the TFSIntegration database of Team Foundation Server 2005 to use a single FQDN address.

To configure Team Foundation Server 2005 to use a single FQDN

On the application-tier computer, open the Windows command prompt and then open the location where \Microsoft Visual Studio 2005 Team Foundation Server\Tools is installed.

For example, open \Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Tools\.
Type the following text:

tfsadminutil activateat <Fully.Qualified.DomainName>
Open Registry Editor, and then update the value of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\8.0\TeamFoundation\ReportServer to use the <Fully.Qualified.DomainName> value from step 2.
Open Windows Explorer, and then locate where \Microsoft Visual Studio 2005 Team Foundation Server\Web Services is installed.

For example, open \Program Files\Microsoft Visual Studio 2005 Team Foundation Server\Web Services.
Right-click Web.Config and then click Edit. If it is necessary, select an editor with which to modify the file, such as Notepad.

Note

For more information about this file, see Global Web.Config File Settings in Team Foundation Server Components.
Set the value of TFSUrlPublic to http://<Fully.Qualified.DomainName>:8080 to force e-mail notifications to use FQDN references.

Note

If you want to specify that all local communication to the application-tier use FQDN, use the topic How to: Configure Team Foundation Server for HTTPS and SSL Only as a guide.
Add the FQDN to the Intranet Zone or Trusted Sites list in Microsoft Internet Explorer for all clients. For guidance, see Knowledge Base article 303650: Intranet site is identified as an Internet site when you use an FQDN or an IP address.

Team Foundation Server 2008 and Team Foundation Server 2008 SP1

Team Foundation Server 2008 and Team Foundation Server 2008 SP1 with Windows SharePoint Services 3.0 or Microsoft Office SharePoint Services 2007 also supports using fully qualified domain names for SharePoint and Reporting services.

For Team Foundation Server 2008, you must complete the following tasks:

Configure Team foundation Server to use a single FQDN
Update the Alternate access mappings for Windows SharePoint Server 3.0

For Team Foundation Server 2008 SP1, you must complete the following tasks:

Configure Team foundation Server to use a single FQDN
Update the Alternate access mappings for Windows SharePoint Server 3.0
Fix authentication errors, per Knowledge Base article 926642.

To configure Team Foundation Server 2008 to use a single FQDN

On the application-tier computer, open the Windows command prompt and then open the location where \Microsoft Visual Studio 2008 Team Foundation Server\Tools is installed.

For example, \Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Tools\.
Type the following text:

tfsadminutil activateat <Fully.Qualified.DomainName>
Open Registry Editor, and then update the value of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\9.0\TeamFoundation\ReportServer to use the <Fully.Qualified.DomainName> value from step 2.
Open Windows Explorer, and then locate where \Microsoft Visual Studio 2008 Team Foundation Server\Web Services is installed.

For example, \Program Files\Microsoft Visual Studio 2008 Team Foundation Server\Web Services.
Right-click Web.Config and then click Edit. If it is necessary, select an editor with which to modify the file, such as Notepad.

Note

For more information about this file, see Global Web.Config File Settings in Team Foundation Server Components.
Set the value of TFSUrlPublic to http://<Fully.Qualified.DomainName>:8080 to force e-mail notifications to use FQDN references.

Note

If you want to specify that all local communication to the application-tier use FQDN, use the topic How to: Configure Team Foundation Server for HTTPS and SSL Only as a guide.
Add the FQDN to the Intranet Zone or Trusted Sites list in Microsoft Internet Explorer for all clients. For guidance, see Knowledge Base article 303650: Intranet site is identified as an Internet site when you use an FQDN or an IP address.

In order to successfully access the team portal by using the new FQDN URL, you must update the alternate access mappings for Windows SharePoint Server 3.0. If you do not update these mappings, trying to browse http://<Fully.Qualified.DomainName>/sites/TeamProjectName will redirect you to http://NETBIOSNAME/sites/TeamProjectName automatically.

To update the Alternate access mappings for Windows SharePoint Server 3.0

Open the Windows SharePoint Server 3.0 Central Administrator.

Typically, this tool can be found by clicking Start, pointing to All Programs, pointing to Administrative Tools, and then clicking SharePoint 3.0 Central Administration.
Click the Operations tab.
In the Global Configuration section, click Alternate access mappings.
Click the Add Internal URLs button.
In the Alternate Access Mappings Collection drop-down list, select the default Web site that uses port 80.
In the URL protocol, host, and port box, type the <Fully.Qualified.DomainName> value.
In the Zone drop-down list, select Custom.
Click Save.

If you are using Team Foundation Server 2008 SP1 with .NET Framework 3.0 SP1, you must perform additional steps to avoid authentication errors.

To prevent possible authentication errors

Follow the instructions in Knowledge Base article 926642: Error message when you try to access a server locally by using its FQDN or its CNAME alias after you install Windows Server 2003 Service Pack 1: "Access denied" or "No network provider accepted the given network path".