A Unified Communication Blog
Get Adobe Flash player

In my Lync Server 2013 High Availability environment series, we have now deployed most of our Lync servers, but we still need to deploy two more frontend servers.

 

The topology that we have deployed so fare consist of an Enterprise Pool with one frontend server.

The minimum recommend number of frontend servers in an Enterprise Pool is three – Have a look at this Microsoft page for guidelines about planning for frontend servers: http://technet.microsoft.com/en-us/library/gg412996(v=ocs.15).aspx

 

At this point I assume that you have installed the two new frontend servers with the same specification has the first server (see part 5: http://exchangepro.dk/2013/09/19/prepare-your-servers-for-lync-server-2013-ha-part-5/).

Before you start I will recommend that you do this in maintenance window, because you will need to reboot the frontend servers, which can cause disruption for the users.

Start by opening the Lync Topology builder and download the current topology.

Navigate to the Enterprise Pool

Right click the Enterprise Pool and Select New Server

Click Yes to the below prompt which tells you that after adding more frontend servers you will need to restart all frontend servers one at a time.

Type the name of the second frontend server and select OK

Add the third Frontend server

Right click Lync Server at the top and select Publish Topology

Click Next

Click Finish (the warning is related to the DFS file store and can be ignored)

After the topology has been deployed, you are now ready to install the additional two frontend servers.

Follow the installation steps as we did in Part 7 – http://exchangepro.dk/2013/09/30/install-the-first-frontend-server-part-7/.

You should also export the frontend server certificate that we created when we installed the first server. In that certificate, we manually added the FE02 and FE03 server names.

Import that certificate on the two new frontend servers.

When you follow the guide for installing the new frontend servers, you assign the certificate, which you have imported. You do not need to create a new Oauth Certificate (that you only do when you add additional sip domains).

When the servers has been installed you should also remember to update Lync with the latest CU – follow the guide in part 8: http://exchangepro.dk/2013/10/06/update-the-frontend-server-part-8/

And get the latest updates here: http://exchangepro.dk/updates/lync/lync-2013-updates/.

At the end also remember to run windows update so that the SQL server instance and windows is patched.

You should only reboot one frontend server at a time, and the first frontend server must also be rebooted.

After a reboot wait for the frontend service is started – I can sometimes take some time. You can follow the progress in Services.msc and in the eventlog.

 

When the three frontend servers has been, installed, updated and rebooted you now have a running frontend pool with three frontend servers. If you want to add more servers, then follow the same rules, and boot one frontend server at a time.

 

In the next post we will continue be setting up the internal hardware load balancer which is a required component in an Enterprise Pool, and also correcting the internal DNS, which right now points to the first frontend server.

 

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 7: http://exchangepro.dk/2013/09/30/install-the-first-frontend-server-part-7/

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 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/

5 Responses to Adding Additional Frontend Servers to Lync HA – Part 13

  • Exchangepro.dk: Adding Additional Frontend Servers to Lync HA – Part 13 http://t.co/tVbn1Kh8k1 #Lync

  • hi after exporting the front end certificates (that contains all my front end server names) how should I import it on the other front end servers? -using mmc > certificates > machine or through the lync certificate wizard and Import it there?
    regards,
    Thiago

    • you can use the one you find easist. The effect will be the same. Properly the deployment wizard because you are already in there when you install the other servers.

      Br. Joachim

  • So once the 3 FE servers are setup, what about the DNS entries for the FE Pool?

    • Hi Ed

      I use a combination of DNS LB and Hardware LB. So you register the pool name three times in the dns (one for each Frontend) – this is DNS LB. The Lync/Skype client is able to use DNS LB.
      You then in the topology builder create an internal Web name (and external) – these are pointed to a Hardware load balancer – which again points (and checks) the backend frontend servers.

      Did that make sense to you :)

      Br. Joachim

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>

Search

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

Join 71 other subscribers

Follow me on Twitter