In my last series of post I’ve looked at how you can rename server which runs TFS components and reconfigure them so that the platform can be operational again. In this new series i’ll explain how to realize an installation using DNS aliases so that future server changes will be simplified by simply changing the alias
Even you start with a single server installation, using DNS aliases for all components will simplify your task if you need to make some evolution later. Here’s the list of components on which we will have an alias:
- SQL Server
- Analysis Services
- Reporting Services
- SharePoint
- Team Foundation Server (Application Tiers)
I’ll look at the specific installation and configuration for this task in 3 parts:
- Part 1 : Data Tiers
- Part 2 : SharePoint
- Part 3 : Team Foundation Server
Let’s start with the Data Tiers part which is comprised of SQL Server, Analysis Services and Reporting Services. Here are the aliases i’ll be using but feel free to use your own
- SQL Server : sql01
- Analysis Services : analysis01
- Reporting Services : reporting01
My domain used for this tutorial is demo.local.
SQL Server
For the SQL Server part (database only), there is no specific configuration as this component doesn’t have any dependency
Analysis Services
As for SQL Server, this component doesn’t have any dependency so there is not specific configuration except in one case : when you install Analysis Services on the same server as another component which depends on it. In this case after the installation you must add a registry key to disable the loopback check. By default you cannot connect to Analysis Services locally using another address than “localhost”. Here’s how to do this:
- Open the registry editor (regedit.exe).
- Go to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa key.
- Add the DisableLoopbackCheck entry of type DWORD with the value 1.
Be careful that this can have some security implications. For more information please read the following Microsoft KB : http://support.microsoft.com/kb/983444
Reporting Services
Installing and configuring Reporting Services is a little bit longer so that you can use DNS aliases:
- Install Reporting Services but do not configure it.
- When the installation is done you must configure Reporting Services manually using the configuration manager.
- Connect to your local SSRS server.
- On the Database tab, click Change Database.
- Select Create a new report server database and click Next.
- In the field Server Name, enter the fully qualified DNS name (FQDN) of the SQL server using it’s DNS alias and click Next.
- Finish the database creation by using the default values.
- On the Web Service URL tab, click Apply.
- On the Report Manager URL tab, click Apply.
- On the Web Service URL tab, click Advanced.
If you ask yourself why we left the Web Service URL tab and come back to it after this is because the UI is not refreshed automatically and we need to change the tab to have the button enable - In the Multiple HTTP Identities section, click Add.
- Click Host Header Name and enter the fully qualified DNS name of the Reporting Services server using the it’s DNS alias and click OK.
- Click OK to close the Advanced Multiple Web Site Configuration window.
- In the Dans l’onglet Report Manager URL, cliquez sur Advanced.
- In the Multiple Identities section, click Add.
- Click Host Header Name and enter the fully qualified DNS name of the Reporting Services server using the it’s DNS alias and click OK.
- Click OK to close the Advanced Multiple Web Site Configuration window.
- Click Exit to close the Reporting Services configuration manager.
Here’s what you must do to install and configure the SQL Server components to work with DNS aliases For the next part we’ll see how to configure SharePoint.
Carpe Diem.