Windows Server 2012 R2 is soon reaching the GA state, so I decided that I would test how Lync Server 2013 behave on a Windows Server 2012 R2 RTM Server.
So this guide will take you though on how to install Lync Server 2013 on a Windows Server 2012 R2 Server, RTM.
I have created a virtual server in my HyperV lab with these specs:
- 3 vCPU
- 8 GB RAM
- 100 GB Disk space
Login to the server and right click on Windows Powershell and select “Run as administrator”, where we will install the roles and features that a Lync frontend server needs.
Type the below cmdlet or copy-paste it to the powershell window.
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, Telnet-Client, BITS,RSAT-DNS-Server,MSMQ-Server,MSMQ-Directory –restart
When the roles and features has been installed, and the server has rebooted, you should mount the Lync Sever CD.
Navigate to this location on the CD, and double click on setup.exe
Read the License Agreement, and if tyou can accept then make a check in the litle check box. If can’t accept it – wash your car instead J
The Deployment Wizard startes up and the first step is to prepare the Active Directory, in my Lab AD.
Click on “Prepare Active Directory”
Next to Step 1 click Run
If you have multiple domain controllers you should wait for the replication to Finish.
Next to Step 3 click Run
Again wait for replication
Next to Step 5 click Run
Now you should make you administrator account or install acccount member of the new Lync groups.
As minimum the accoung must be member of CSAdministrator and RTCUniversalServerAdmins
Logout of the server and in again.
Start the Lync Server Deployment Wizard Again
Click on the “Prepare first Standard Edition Server”
Now open Explorer and create a new directory called “LyncFileStore”
Right click on the new directory and select properties.
Navigate to Sharing and select Advanced Sharing.
Click to share the folder and call the share LyncFileStore
Click Permission and Everyone full control
Click OK and navigate to the Security fane.
Add RTCUniversalServerAdmins and give this group Full Control.
Next we will create a new topology which we will publish to the Central Management Store that we created before.
Open Lync Topology builder.
Select New Topology
Save the topology
Type the primary sip domain
Give the first site a name and click Next
Type the Site details and click Next
Create a standard pool and give the pool a name, which matches the FQDN name of the frontend server
Select the feature you want to use and click Next
Colocated the Mediation Server, if you are going to use Enterprise Voice and is not using a SIP trunk. (if you are using a sip trunk Microsofts recommends that the mediation server is a separate server)
Type the FQDN name on the Frontend server and the share you created before.
Give the Web service URL a name which can be reached from the internet.
Click on New to create an Office Web Apps Server
Type the name for the Office Web Apps Server and click OK
Click New to create a new Edge Server Pool
Type the FQDN Name of the Edge Server and select Single computer pool. Click Next
Make the selection below and click Next
Type the FQDN record which is used on the internet.
Type the IP address of the internal Nic and click Next
Type the IP adresses on the public nic. (I will be using NAT so I still have private IP’s on this adapter – from a seperat segment)
Navigate to the Edge server and right click on it an select properties
Click on Next hop
Make a mark in “A/V Edge service is NAT enabled”
Navigate to the button and type the Public IP address that the A/V Service will use:
Click Ok and navigate to the top, right click on Lync Server and select Edit Properties
Change the Simple Url if you want.
Select the frontend server that will hold the Centrale Management Store and click OK.
Navigate to the Site level and right click and select Edit Properties
Navigate to Federation route and make the below selections and click OK.
Right click on the “Lync Server” in the top, and select Publish Topology
The topology has now been published to the Central Management Store, and we are ready to install Lync on the frontend server.
Open (or go back to) Lync Deployment Wizard.
Select “Install or Update Lync System”
On step 1 clikk Run
On Step 2 Click Run
After a while the installation is complete. Click Finish
On Step 3: Click Run
Select the OAuthTokenIssuer abnd click on Request
Select the Certificate authority and click Next
I’m going to use a custom certificate which allows that the certificates can be exported (which is not allowed on the standard web server template.)
So I’m going to find the OID number for the certificate.
This is done from the Certificate Authority toll on the CA server.
Navigate to Certificate Templates
Right click and select manage
Find your custom web server certificate and right click and select Properties
Navigate to Extensions and click on Certicate Template Information
Mark the Number just below “Object identifier” and copy it with CTRL+C
Back on the Lync server paste the OID number
Type a name for the certificate and click Next
Type the organization names and click Next
The the GEO information and click Next
Now do the Same for the Default Certificate – select it and click Request and follow the guide
Click Close when Finish
On Step 4 click Run
Next to Service Status click Run
Verify that all the Lync Services is running
You have now installed Lync Server 2013 on a Windows Server 2012 R2, and is almost ready to start using it, but first you should always remember to update the server to the latest update.
See this post on how to do that: http://exchangepro.dk/2013/10/06/update-the-frontend-server-part-8/