When installing Lync Server 2010 some roles requires specific Windows Features to be installed. The features are about the same as for OCS 2007 R2.

NOTE: This article will be updated when more information and requirements become available and necessary. Last update 02.12.2010

Part One – Prerequisites required on all server roles

• Open PowerShell as administrator and run the following commands
• Import-Module ServerManager
• Add-WindowsFeature NET-Framework-Core,Telnet-Client
  • This installs the following features
    • [NET-Framework-Core] – .Net Framework 3.5 SP1
    • [Telnet-Client] – Telnet Client (recommended not required)
  • For .Net Framework 3.5 SP1 download the following updates
    • http://go.microsoft.com/fwlink/?linkid=197396, which addresses a set of known application compatibility issues
    • http://go.microsoft.com/fwlink/?linkid=197397, which addresses a file association issue for XPS document
• Install the prerequisites for the specific role as described in Part Three
  • A PowerShell script for installing the prerequisites: SCRIPT: Set-Lync2010Windows2008R2Features.ps1
• Run Windows Update untill everything is updated
• Install the Lync Server 2010 binaries for the role you are installing
• Do post installation tasks as described in Part Two

Part Two – What to install AFTER Lync Server 2010 is installed

I describe it here so it is more accessible rather than in the end of the post

• Download and install the Lync Server 2010 Resource Kit Tools
• Download and install the latest updates for Lync Server 2010 (Link can be found here: https://msunified.net/lyncdownloads/)

Part Three – Commands to install prerequisites for Lync Server 2010 on Windows Server 2008 R2

Front End, Director and Group Chat Server Roles on Windows Server 2008 R2

NOTE: To be able to run schema, forest and domain prep from the Front End Server you need to have the Remote Server Administrative Tools [RSAT-ADDS] installed. It is only required on the first Front End server in you organization. For more information on preparing AD see: http://technet.microsoft.com/en-us/library/gg398607.aspx

• Open PowerShell as administrator and run the following commands
• Import-Module ServerManager
• Add-WindowsFeature RSAT-ADDS,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-Http-Tracing,Web-Windows-Auth,Web-Filtering,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools,Web-Client-Auth,Desktop-Experience

Installs the following components:

• [RSAT-ADDS] – Remote Server Administrative Tools
• [Web-Static-Content] – Static Content
• [Web-Default-Doc] – Default Document
• [Web-Http-Errors] – HTTP Errors
• [Web-Asp-Net] – ASP.NET
• [Web-Net-Ext] – .NET Extensibility
• [Web-ISAPI-Ext] – Internet Server API (ISAPI) Extensions
• [Web-ISAPI-Filter] – ISAPI Filters
• [Web-Http-Logging] – HTTP Logging
• [Web-Log-Libraries] – Logging Tools
• [Web-Http-Tracing] – Tracing
• [Web-Windows-Auth] – Windows Authentication
• [Web-Filtering] – Request Filtering
• [Web-Stat-Compression] – Static Content Compression
• [Web-Mgmt-Console] – IIS Management Console
• [Web-Scripting-Tools] – IIS Management Scripts and Tools
• [Web-Client-Auth] – Client Certificate Mapping Authentication
• Anonymous Authentication (This is installed by default when IIS is installed)
• [Desktop-Experience] – Desktop Experience

NOTE: Installing on Server 2008 R2 SP1, you need to do this step manually. 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. Thats why Desktop Experience is installed. If you only want to install the correct runtime run the command below:

• Run using Command Prompt as administrator
• Requires reboot
• %systemroot%\system32\dism.exe /online /add-package
  /packagepath:%windir%\servicing\Packages\Microsoft-Windows-Media-Format-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.mum
  /ignorecheck
  

Mediation Server Role on Windows Server 2008 R2

• No additional features required for mediation

EDGE Server Role on Windows Server 2008 R2

• Need one aditional hotfix for Lync EDGE Server Role.
  • Note: This hotfix is included in SP1 for Server 2008 R2
  • Windows Server 2008 R2 update available from Microsoft Knowledge Base article 2028827, “The applications that use the TDI driver for network traffic may stop responding in Windows Server 2008 R2 or in Windows 7,” at http://go.microsoft.com/fwlink/?LinkId=205459

Monitoring and Archiving Server Roles on Windows Server 2008 R2

NOTE: If Monitoring og Archiving is deployed in the topology, all server roles must install the below features, including the Monitoring and Archiving Servers

• Open PowerShell as administrator and run the following commands
• Import-Module ServerManager
• Add-WindowsFeature msmq-server,msmq-directory

Installs the following components:

• [MSMQ-Server] – Message Queuing Server
• [MSMQ-Directory] – Directory Service Integration

Software Automatically Installed by Lync Server Setup

References:
For more information see TechNet documentation: http://technet.microsoft.com/en-us/library/gg398686.aspx