Additional Software Requirements
Topic Last Modified: 2012-10-16
In addition to the hardware and operating system requirements for server platforms, Microsoft Lync Server 2010 requires the installation of additional software on the servers you deploy.
Note
For details about the platform requirements for servers running Lync Server 2010, see Server Hardware Platforms and Server and Tools Operating System Support. For details about system requirements for client computers and devices, see Planning for Clients and Devices in Lync Server 2010 in the Planning documentation. For details about software requirements for administrative tools, see Administrative Tools Software Requirements.
Additional Software Necessary for All Server Roles
On all server roles, you must also make sure that Windows PowerShell command-line interface 2.0, Microsoft .NET Framework 3.5 with SP1, and Windows Installer 4.5 are installed.
Additionally, Microsoft .NET Framework 3.5 with SP1 is required on any computer where you will run the Lync Server administrative tools or Microsoft Lync Server 2010, Planning Tool.
Windows PowerShell 2.0
On servers running Windows Server 2008 R2, Windows PowerShell 2.0 is automatically installed with the operating system.
On servers running Windows Server 2008 SP2, you must make sure that Windows PowerShell 2.0 is installed. If not, you must install it. Before doing so, you must remove any previous versions of Windows PowerShell that are installed on the server.
To install Windows PowerShell 2.0 on a server running Windows Server 2008 SP2, see the Microsoft Knowledge Base article 968929, "Windows Management Framework (Windows PowerShell 2.0, WinRM 2.0, and BITS 4.0)," at https://go.microsoft.com/fwlink/p/?linkid=3052&kbid=968929.
Microsoft .NET Framework 3.5 with SP1
The 64-bit edition of Microsoft .NET Framework 3.5 with SP1 is required for Microsoft Lync Server 2010. Setup prompts you to install this prerequisite, and it automatically installs it if it is not already installed on the computer. .NET Framework 4.0 can be installed on the same computer as well, but does not take the place of .NET Framework 3.5 with SP1, which is the required version for Lync Server 2010.
Note
If you install Lync Server 2010 by using the command line, you need to manually install this prerequisite on the server. To manually install it, download the Microsoft .NET 3.5 Service Pack 1 (Full Package) from the Microsoft Download Center at https://go.microsoft.com/fwlink/p/?linkid=197398.
Updates to Microsoft .NET Framework 3.5 with SP1
After installing the .NET Framework 3.5 SP1 package, either manually or using Lync Server setup, you should immediately install the following updates:
Note
-
Microsoft Knowledge Base article 959209, "An update for the .NET Framework 3.5 Service Pack 1 is available," at https://go.microsoft.com/fwlink/p/?linkid=3052&kbid=959209, which addresses a set of known application compatibility issues.
-
Download "Update for .NET Framework 3.5 SP1 (KB967190)" from the Microsoft Download Center at https://go.microsoft.com/fwlink/p/?linkid=197397, which addresses a file association issue for XPS document.
Windows Installer Version 4.5
Microsoft Lync Server 2010 uses Windows Installer technology to install, uninstall, and maintain various server roles. Windows Installer version 4.5 is available as a redistributable component for the Windows Server operating system.
Download Windows Installer 4.5 from the Microsoft Download Center at https://go.microsoft.com/fwlink/p/?linkid=197395.
Additional Software for Front End Servers and Standard Edition Servers
All Front End Servers and Standard Edition servers must also run Internet Information Services (IIS) with certain modules. Additionally, all Front End Server and Standard Edition servers where conferencing is deployed must run Windows Media Format Runtime.
If you are deploying Monitoring Server or Archiving Server, you must also run Message Queuing (also known as MSMQ) on your Front End Servers and Standard Edition servers.
Internet Information Services (IIS)
Front End Servers and Standard Edition servers must run Internet Information Services (IIS), with the following modules:
Static Content
Default Document
HTTP Errors
ASP.NET
.NET Extensibility
Internet Server API (ISAPI) Extensions
ISAPI Filters
HTTP Logging
Logging Tools
Tracing
Windows Authentication
Request Filtering
Static Content Compression
IIS Management Console
IIS Management Scripts and Tools
Anonymous Authentication (This is installed by default when IIS is installed.)
Client Certificate Mapping Authentication
Windows Media Format Runtime Requirements
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 d 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. 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 application 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
If you are deploying Monitoring Server or Archiving Server, your Front End Servers and Standard Edition servers must run Message Queuing. Message Queuing is an optional feature in Windows Server 2008 R2 and Windows Server 2008 SP2.
Additional Software for Edge Servers Running Windows Server 2008 SP2
On Edge Servers that run Windows Server 2008 SP2, to prevent increasing memory usage involving the Web Conferencing Edge service, you should install the update described in the Microsoft Knowledge Base article 979231, "Memory usage keeps increasing if Schannel authentication is used after the update 968389 is installed in Windows Vista or in Windows Server 2008," at https://go.microsoft.com/fwlink/p/?linkid=3052&kbid=979231.
Additional Software for Directors
Directors must run Internet Information Services (IIS), with the following modules:
Static Content
Default Document
HTTP Errors
ASP.NET
.NET Extensibility
Internet Server API (ISAPI) Extensions
ISAPI Filters
HTTP Logging
Logging Tools
Tracing
Windows Authentication
Request Filtering
Static Content Compression
IIS Management Console
IIS Management Scripts and Tools
Anonymous Authentication (This is installed by default when IIS is installed.)
Client Certificate Mapping Authentication
Additional Software for Monitoring Server and Archiving Server
Servers running Monitoring Server or Archiving Server must run Message Queuing. Message Queuing is an optional feature in Windows Server 2008 R2 and Windows Server 2008 SP2.
Do Not Install Layered Socket Providers on Media Servers
Do not install any Microsoft Internet Security and Acceleration (ISA) Server client software, or any other Winsock Layered Service Providers (LSP) software, on any server roles that handle media traffic (for example, audio, video, or application sharing). This includes Mediation Server, A/V Conferencing Server, and Front End Servers that have one of these server roles collocated. Installing this software could cause poor performance.
Software Automatically Installed by Lync Server
When you install Lync Server 2010 on a server, some software that is required by Lync Server is installed automatically (that is, if the required software is not already installed on the server). This includes the following:
Microsoft Visual C++ 2008 Redistributable
Microsoft Visual J# version 2.0 Redistributable
URL Rewrite Module version 2.0 Redistributable
SQL Server 2008 Express SP1
SQL Server 2008 Native Client