Following on from PART 1, This post will no go into detail about implementing and installing Lync 2013 onto your Frontend servers.
Firstly lets just confirm again that there are a few pre requisites which are required before the fronted services can be implemented. These pre reqs can be found in the part 1 of the guides.
Lync 2013 Frontend Specs
Microsoft recommend the following frontend infrastructure to support Lync 2013
6Cores
32gb Ram
72gb Disk Space
At the time of writing this will be the minimum requirements and will have the ability to home 6600 users per server
————————————————————————————————————————————————————————————————————————————————————————
Let move onto the installation.
Navigating back to your start menu again select the ‘Lync Deployment Wizard’
If you have followed part 1 when the deployment wizard opens you should see green ticks as per image below.
Now select ‘Install or Update Lync Server System’
The next step is key, and you should check all the PreReqs for the install are met before select Run
For this lab build i added RTCUniversalServerAdmins to my srv_lync account.,
Once your are happy select ‘Run’
Once you pressed run on the next dialog leave the default radio button pressed for Retrieve directly from the central management store
Select the ‘Next’ Button
On clicking next the wizard will then proceed to install the required modules to home the CMS database locally.
Once you get the dialog saying complete move onto step 2
Click Next to move through the wizard
Ensuring the Step 2 has successfully installed its time to move onto the certificate placements.
Select Step 3 Run
On the below certificate dialog if you have an internal CA then leave as default, else select the bottom option to prepare the request for later.
then select Next
Once you’ve requested your certificates from your CA import and enable them for Lync 2013.
Now lets start the services.
NOTE: For my lab I’ve also added a few users for testing purposes within AD. The Lab machines are using Windows 8 with win8lab1 running Lync2010 and winlab2 running Lync 2013.
If we have all our initial DNS entries correct for the front ends, which we set up for using DNS load balancing and automatic configuration using the service record we created in PART 1 of the PreReqs blog no further changes are needed to be made to the Lync 2013 client for logging in as it should be automatic.
Onto Part 3 soon
