Install Operating Systems and Prerequisite Software on Servers
Topic Last Modified: 2012-10-13
After you have set up the hardware and system infrastructure, you need to install the appropriate Windows operating systems and updates, in addition to all other prerequisite software on each server that you are deploying. This includes each Lync Server 2010 server role and any additional infrastructure servers and SQL Server-based servers required for your deployment.
Note
This section describes installation of operating systems and prerequisite software for internal servers. If you are deploying Edge Servers to support external user access, you will also need to install operating systems and prerequisite software for those servers, including Edge Servers and reverse proxy servers. For details about preparing servers to support external user access, see Preparing for Installation of Servers in the Perimeter Network in the Deploying Edge Servers documentation.
Install Windows Operating Systems on Servers
On each server that you are deploying, install the appropriate Windows operating system:
Servers running Lync Server 2010. For details about the operating system requirements for servers running Lync Server 2010, see Server and Tools Operating System Support in the Supportability documentation.
Database servers. For details about operating system requirements for database servers, including the back-end database, Archiving database, and Monitoring database, see the SQL Server documentation. For SQL Server 2005, see the SQL Server Books Online 2005 at https://go.microsoft.com/fwlink/p/?LinkID=202922. For SQL Server 2008, see the SQL Server 2008 Books Online at https://go.microsoft.com/fwlink/p/?LinkID=202921. For SQL Server 2008 R2, see the SQL Server 2008 R2 Books Online at https://go.microsoft.com/fwlink/p/?LinkId=218015.
Install Windows Update on Servers
Install the Windows Update required by Lync Server 2010 on each server:
Windows Update for servers running Lync Server 2010. For details about the Windows Update required for servers running Lync Server 2010, see Additional Software Requirements in the Planning documentation.
Database servers. For details about the Windows Update required for database servers, including the back-end database, Archiving database, and Monitoring database, see the SQL Server documentation. For SQL Server 2005, see the SQL Server Books Online 2005 at https://go.microsoft.com/fwlink/p/?LinkID=202922. For SQL Server 2008, see the SQL Server 2008 Books Online at https://go.microsoft.com/fwlink/p/?LinkID=202921. For SQL Server 2008 R2, see the SQL Server 2008 R2 Books Online at https://go.microsoft.com/fwlink/p/?LinkId=218015.
Install Other Prerequisite Software on Servers
Lync Server 2010 requires the installation of additional software on servers:
Prerequisite software for servers running Lync Server 2010. The additional software prerequisites for servers running Lync Server depend on the server role being deployed. For details about the specific software requirements for each server, see Additional Software Requirements in the Planning documentation.
Lync Server requires Microsoft .NET Framework 3.5 with SP1. You should apply the update discussed in the Microsoft Knowledge Base article 981575, “A memory leak occurs in a .NET Framework 2.0-based application that uses the AesCryptoServiceProvider class” at https://go.microsoft.com/fwlink/p/?linkid=3052&kbid=981575. You should also apply the update discussed in the Microsoft Knowledge Base article 975954, “FIX: When you run a .NET Framework 2.0-based application, a System.AccessViolationException exception occurs, or a dead-lock occurs on two threads in an application domain” at https://go.microsoft.com/fwlink/p/?linkid=3052&kbid=975954.
Prerequisite software for database servers. For details about the Windows Update required for database servers, including the back-end database, Archiving database, and Monitoring database, see the SQL Server 2008 documentation at https://go.microsoft.com/fwlink/p/?LinkId=202921 and SQL Server 2008 R2 documentation at https://go.microsoft.com/fwlink/p/?LinkId=218015.
Note
Lync Server 2010 automatically installs SQL Server 2008 Express on each Standard Edition server and each Lync Server 2010 server on which the local configuration store is located. After deploying the servers, you can upgrade the RTC database on the Standard Edition server and the RTCLocal databases on other server roles to SQL Server 2008 R2 Express by running the SQL Server 2008 R2 Express setup wizard and selecting the upgrade option. Repeat this process for each RTC and RTCLocal database.
Windows Media Format Runtime All Front End Servers and Standard Edition servers where conferencing will be deployed must have the Windows Media Format Runtime installed. The Windows Media Format Runtime is required to run the Windows Media Audio (.wma) files that the Call Park, Announcement, and Response Group applications play for announcements and music.
We recommend that you install Windows Media Format Runtime before you install Lync Server 2010. If Lync Server 2010 does not find this software on the server, it will prompt you to install it, and then you must restart the server to complete installation.
Important
With the release of Windows Server 2008 R2 SP1, the name of the package that contains the Windows Media Format runtime has changed. The scripted methods in the Deployment Wizard for Lync 2010 Server do not yet reflect the updated package name.
If you are deploying Lync Server to a computer running Windows Server 2008 R2 SP1, you must install the Windows Media Format runtime by using the command line cited below, and then restart the system to apply the change. If you use the Deployment Wizard prior to applying the runtime, the runtime will not install because the Deployment Wizard tries to apply the Windows Server 2008 or Windows Server 2008 R2 runtime, and fails because the package Deployment Wizard expects does not exist. The error may be missed because it is a subtle error. You resolve this issue by either applying the runtime prior to running the Deployment Wizard or after you run the Deployment Wizard. Restart the computer to complete the installation of the runtime.To install the Windows Media Format Runtime on servers running Windows Server 2008, use the following command:
%systemroot%\system32\pkgmgr.exe /quiet /ip /m:%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.0.6001.18000.mum
To install the Windows Media Format Runtime on servers running Windows Server 2008 R2, use the following command:
%systemroot%\system32\dism.exe /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7600.16385.mum /ignorecheck
To install the Windows Media Format Runtime on servers running Windows Server 2008 R2 SP1, use the following command:
%systemroot%\system32\dism.exe /online /add-package /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum /ignorecheck
Message Queuing. Message Queuing (also known as MSMQ) role components and Directory Service Integration should be installed on the Front End Server, and the Archiving Server if you plan to deploy the Lync Server 2010 Archiving Server roles. The Message Queuing components can be found in Server Manager or can be deployed by using servermanagercmd.exe . For details, see "Install Message Queuing" at https://go.microsoft.com/fwlink/p/?LinkId=205338.
To install Message Queuing by using the Add-WindowsFeature Windows PowerShell cmdlet, do the following:
On the Windows Server 2008 R2 x64 operating system, use Windows PowerShell 2.0.
At the Windows PowerShell prompt, type:
Import-Module servermanager
, and then press Enter.Type:
Add-WindowsFeature MSMQ-Server, MSMQ-Directory
, and then press Enter.