In this post you will learn how to install the director servers in our Lync Server 2013 High Availability environment.
The Director role is an optional server in Lync Server 2013, which means that it is not an requirement to have it in an environment like the one I’m building in this series.
But I like the director in an environment where I have enterprise voice enabled, as an extra protection for the frontend servers, to protect them from Denial of Servcie attacks from the Internet.
In case of a DoS attack it will be the director that is affected and not the frontend and thereby my enterprise voice will continue to run.
In post 6 (http://exchangepro.dk/2013/09/21/creating-the-lync-server-2013-ha-topology-part-6/) I defined the Director servers in the topology builder as this:
- Director Pool: DIRPOOL01.exchangepro.local
- Director Server 1: DIR01.exchangepro.local
- Director Server 2: DIR02.exchangepro.local
- External Name: cswebdir.exchangepro.dk
The Director servers, will be placed on the internal network, between my Access edge servers and the frontend pool, so that communication from the access edge will be delivered to the director servers, which then again delivers it to the frontend.
The specification for the servers is:
- 2 x vCPU
- 8 GB RAM
- 100 Gb Diskspace
- Windows Server 2012
Before installing Lync you will need to install the roles and features which is required – I’m doing it the easy way with powershell:
Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Windows-Identity-Foundation,Web-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, BITS,MSMQ-Server,MSMQ-Directory –restart
Mount the Lync CD, on the server and start setup.exe
Read the license agreement if you have the time, and accept it.
Active Directory is already updated with the attributes needed, so click on Install or Update Lync Server System.
Start on step 1 and continue with step 2 (see my other posts if you want the details about these steps (http://exchangepro.dk/2013/09/30/install-the-first-frontend-server-part-7/)).
The bootstrapper (the “lync name” for the setup) reads the configuration from the Central Management Store, and because the server names is defined in the topology everything is taking care of, and the right components is installed on the server.
In step 3 you should follow the guide to request a certificate for the director servers.
A tip: When the guide ask for additional names, add the second directory servers FQDN name. You can then export this certificate and install it on the second director server, and we can use it for our reverse proxy (in a later post).
When the certificates has been installed, you can start the services.
When the services has been started you should as always make sure to update to the latest update – Follow the same procedure as for the frontend server – http://exchangepro.dk/2013/10/06/update-the-frontend-server-part-8/
When that’s is done continue to install the second director server. When that is fixed as well, we will add some records in the DNS.
You should have these records in DNS:
These record will make use of DNS load balancing, but in my case I will use hardware load balancing so when I’m going to set this up in a later post, I will remove the two DIRPOOL01 records, and create a new one which point to my load balancere.
You could also go for a solution where it’s only the Web Traffic for the directors that is load balanced – in that case you will need to overwrite the internal web url for the director pool in topology builder.
We are now ready to continue with the Access Edge Servers – in the next post J
Lync 2013 High Availability