I notice there’re plenty of published articles available on the Internet when it comes to the basic deployment of Lync Server 2013. However, in my recent attempt to install Lync Server 2013 on Windows Server 2012, I suppose another article to support those deployment maybe useful during the preparation stage.
Preparing the Back-end Server running on SQL Server 2012
As there isn’t much of information when it comes to installing the Back-end Database Server in Lync Server 2013. The installation is basically pretty straight forward – just following the wizard and you’ll get there 🙂 I won’t be covering the details about the installation but I’ll share some of the ‘incidents’ that I’ve encountered during the installation of it.
SQL Server 2012 basically requires .NET Framework 3.5, so if this option has not been selected, the system will indicate that the component is missing and basically terminates the installation – after the running through the entire installation wizard. When attempting to install the .NET Framework 3.5 via the Server Manager, you’ll like received an error if the system that you intend to install is not connected to the Internet:
Therefore, the easiest way to get .NET Framework 3.5 installed is to use mount the Windows Server 2012 installation CD/DVD and execute the following command with PowerShell:
Install-WindowsFeature –name NET-Framework-Core –source D:\sources\sxs
Preparing the Front-End Server
Though TechNet provides a very good guidance on preparing the Lync Server roles at this chapter on Additional Software Requirements. Some of the components are not emphasized for Windows Server 2012 which may be easily missed out. If you’ve encounter the similar error as below:
Make sure you’ve the following components Enabled & Installed from the Server Manager:
- Windows Identity Foundation 3.5
- Media Foundation
- HTTP Activation, this can be located under .NET Framework 4.5 Features > WCF Services
The rest of the components and dependencies will be automatically added upon selecting the components.
I’ll try to add more contents along the way…