A Unified Communication Blog
Get Adobe Flash player

In the seventh part of the series of installing a Lync 2013 HA, we have come to the point where we are ready to install the first frontend server in our Lync Server 2013 High Availability solution.


We are going to have three frontend servers, but for now we have only defined one frontend server in the Enterprise Pool. When Lync is up and run we will later on add the two other frontend servers and hardware load balancing.


When we are installing the Lync servers, the deployment wizard will read information from the central management store and thereby determines what needs to be installed on the server.

Start the Deployment Wizard on the first frontend server.

The wizard will detect at which step we have come to.

Click on the “Install or Update Lync Server System”

Start by click on run for Step 1:

This step will install a SQL 2012 express database on the server, which is going to store the Lync configuration which is received from the Central Management Store.

All Lync servers (Frontend, Edge, Director and Mediation) will have a Local Configuration Store.

Select Next

The installation of the local configuration store takes 5-10 minuttes to install.

Click on finish

Select Run under Step 2:

Click Next

The installation now read the configuration and thereby determend which Lync Components that is going to be installed on this server:

This step takes some time to complete, depending on the speed of your server.

Click Finish

Click Run on Step 3

Select OAuth and the click Request

Select Next

Select Next

Select your CA and click Next

Select Next

If you have a custom Web Server Template for your Lync Servers (I often has that) you will type the OID number for that template here

Give the certificate a name

Fill in the two fields

Fill these fields

Select Next

Select Next

Select Next

Select Next

Select Finish

Select Next

Select Next

Select Finish

Now do the same for the Default Certificate

Click your sip domain

Add the two other frontend server names to the certificate

And complete the certificate request and assignment.

Close the wizard when finished.


We have now install the first frontend server, and before we will go ahead and start the services, we need to create DNS records that is needed by Lync.

So navigate to your domain controller and open DNS Management.

The recommend domain configuration for your sip domains is to use split dns. With split dns you will have your public domain created both on your inside dns servers and on the public dns servers.

This gives a little bit overhead when you create services that needs to be accessed from both inside and the internet, because you need to create the record on both servers. But it’s in real life not a big problem to do that – just remember to create records both places.

The servers which is member of the domain is should register itself to the internal domain name – in my case exchangepro.local.

But we need to create the edge servers dns records in the dns in the internal domain.

In DNS manager right click the internal domain name and select “New Host…)

Create the records for the two edge servers. (edge01 and edge02) – you will use the internal IP addresses

Also create the Edgepool01 record. This record should point to the virtual IP (VIP) of the hardware load balancer (in my case it will be, however because I want to make sure that the basic Lync functionality is working before I deploy HLB’s, I will start to point the record to the first edge server. I will later on change it to the right IP address when I have deployed the HLB.

The frontend pool record (FEPOOOL01.exchangepro.local) is also created for now to point to the first frontend servers IP – this will also be changed later.

Do the same for the Mediation Pool, Director Pool and the Office Web Apps Farm (Pointing the pool name to the first server)

Your records should look like these:

Now switch to the public name on the internal dns zone and create a record called sip.exchangepro.local, which points to the FEPOOL01 IP.

Create Lyncdiscover and Lyncdiscoverinternal

So the DNS will look like this:

Then create meet record – this I will create as a C-Name.

And the Dialin record

If you are going to have Lync Phone Edition on your network you will also need this record, which is used for the Lync phone to find updates.

We then need to create the internal SRV records that is needed by Lync.

Right click on the public name and select “Other New Records”

Select “Service Location (SRV)” and click on Create Record

Create the _sipinternaltls record this way:

Create also these new SRV Records:

You should also have record that points to Exchange Autodiscover and Exchange Web Services.

We have now created al the internal DNS records, that is needed for now.

We will create the External DNS records in a later post, when we deploy the Edge Servers.


We are now ready to start the frontend services

Click Run on Step 4 in the deployment guide or use the command Start-CSwindowsservice in powershell

Click Next

Click Finish

From the Service you can see that Lync Services has started:


We have now installed the first frontend server. In the next post we will test if it works and we can login to Lync from a client, and also how we update the server with the latest update.


Lync 2013 High Availability

Part 1: http://exchangepro.dk/2013/08/28/install-a-sql-2012-mirroring-cluster-for-use-with-lync-2013-part-1/

Part 2: http://exchangepro.dk/2013/08/29/install-a-sql-2012-witness-server-for-use-with-lync-2013-part-2/

Part 3: http://exchangepro.dk/2013/09/01/configure-a-sql-2012-mirroring-cluster-for-use-with-lync-2013-part-3/

Part 4: http://exchangepro.dk/2013/09/14/deploy-a-lync-2013-file-store-part-4/

Part 5: http://exchangepro.dk/2013/09/19/prepare-your-servers-for-lync-server-2013-ha-part-5/

Part 6: http://exchangepro.dk/2013/09/21/creating-the-lync-server-2013-ha-topology-part-6/

Part 8: http://exchangepro.dk/2013/10/06/update-the-frontend-server-part-8/

Part 9: http://exchangepro.dk/2013/10/13/install-the-office-web-servers-part-9/

Part 10: http://exchangepro.dk/2013/10/21/deploy-the-director-servers-in-lync-2013-ha/

Part 11: http://exchangepro.dk/2013/10/25/install-the-access-edge-ha-servers-part-11/

Part 12: http://exchangepro.dk/2013/11/05/deploy-reverse-proxy-using-kemp-hardware-load-balancer-part-12/

Part 13: http://exchangepro.dk/2013/11/14/adding-additional-frontend-servers-to-lync-ha-part-13/

Part 14: http://exchangepro.dk/2013/11/26/setup-load-balancers-for-the-internal-lync-servers-part-14/

Part 15: http://exchangepro.dk/2013/11/26/load-balance-the-office-web-apps-server-part-15/

Part 16: http://exchangepro.dk/2013/11/26/load-balance-the-lync-frontend-web-services-part-16/

Part 17: http://exchangepro.dk/2013/11/28/load-balance-the-lync-frontend-services-part-17/

Part 18: http://exchangepro.dk/2013/12/15/load-balance-the-lync-director-servers-part-18/

Part 19: http://exchangepro.dk/2013/12/15/load-balance-lync-access-edge-internal-nic-part-19/

Part 20: http://exchangepro.dk/2013/12/29/load-balance-lync-access-edge-external-nic-part-20/

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>


Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Join 77 other subscribers

Follow me on Twitter