Topic Last Modified: 2014-02-17

To successfully complete this procedure, you should be logged on to the server minimally as a local administrator and a domain user.

Before you configure and install the Front End Server for Lync Server 2013, Standard Edition or the first Front End Server in a pool, you install and configure the server role and Web Services for Internet Information Services (IIS).

Important:
If your organization requires that you locate IIS and all Web Services on a drive other than the system drive, you can change the installation location path for the Lync Server 2013 files in the Setup dialog box when you initially install the Lync Server 2013 Administrative tools. You install the Administrative tools before installing IIS. If you install the Setup files to this path, including OCSCore.msi, the rest of the Lync Server 2013 files will be deployed to this drive as well. For dtails, see Install Lync Server Administrative Tools. For details about how to relocate the INETPUB deployed by Windows Server Manager when installing IIS, see http://go.microsoft.com/fwlink/p/?linkId=216888.

The following table indicates the required IIS 7.5 role services.

IIS 7.5 Role Services

Role Heading Role Service

Common HTTP features installed

Static content

Common HTTP features installed

Default document

Common HTTP features installed

HTTP errors

Application development

ASP.NET

Windows Server 2012 also requires ASP.NET4.5

Application development

.NET extensibility

Application development

Internet Server API (ISAPI) extensions

Application development

ISAPI filters

Health and diagnostics

HTTP logging

Health and diagnostics

Logging tools

Health and diagnostics

Tracing

Security

Anonymous authentication (installed and enabled by default)

Security

Windows authentication

Security

Client Certificate Mapping authentication

Security

Request filtering

Performance

Static content compression

Dynamic content compression

Management Tools

IIS Management Console

Management Tools

IIS Management Scripts and Tools

On the Windows Server 2008 R2 SP1 x64 operating system, you can use Windows PowerShell 2.0. You must first import the ServerManager module, and then install the IIS 7.5 role and role services.

Copy Code 
Import-Module ServerManager
Copy Code 
Add-WindowsFeature Web-Server, Web-Static-Content, Web-Default-Doc, Web-Scripting-Tools, Web-Windows-Auth, Web-Asp-Net, Web-Log-Libraries, Web-Http-Tracing, Web-Stat-Compression, Web-Dyn-Compression, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Errors, Web-Http-Logging, Web-Net-Ext, Web-Client-Auth, Web-Filtering, Web-Mgmt-Console
Note:
Anonymous authentication is installed by default with the IIS server role. You can manage anonymous authentication after the installation of IIS. For details, see “Enable Anonymous Authentication (IIS 7)” at http://go.microsoft.com/fwlink/p/?linkId=203935.

The following table indicates the required IIS 8.0 and IIS 8.5 role services for Windows Server 2012 and Windows Server 2012 R2.

Note:
For Windows Server 2012 and Windows Server 2012 R2, the Add-WindowsFeature cmdlet has been replaced by the Install-WindowsFeature cmdlet. For details, see Install-WindowsFeature.

IIS 8.0 and IIS 8.5 Role Services

Role Heading Role Service

Web Server (IIS)

Web Server

Common HTTP Features

Default Document

Common HTTP Features

Directory Browsing

Common HTTP Features

HTTP Errors

Common HTTP Features

Static content

Common HTTP Features

HTTP Redirection

Health and Diagnostics

HTTP Logging

Health and Diagnostics

Logging Tools

Health and Diagnostics

Request Monitor

Health and Diagnostics

Tracing

Security

Request Filtering

Security

Basic Authentication

Security

Client Certificate Mapping Authentication

Security

Windows Authentication

Application Development

.Net Extensibility 3.5

Application Development

.Net Extensibility 4.5

Application Development

ASP.Net 3.5

Application Development

ASP.Net 4.5

Application Development

ISAPI Extensions

Application Development

ISAPI Filters

Application Development

Server Side Includes

Management Tools

IIS Management Console

Management Tools

IIS 6 Metabase compatibility

Management Tools

IIS Management Scripts and Tools

.Net 3.5 Framework Features

.Net 3.5 Framework

.Net 4.5 Framework Features

.Net Framework 4.5

.Net 4.5 Framework Features

ASP.Net 4.5

.Net 4.5 Framework Features

HTTP Activation

.Net 4.5 Framework Features

TCP Port Sharing

Background Intelligent Transfer Service

IIS Server Extensions

Ink and Handwriting Services

Ink and Handwriting Services

Media Foundation

Media Foundation

User Interfaces and Infrastructure

Graphical Management Tools and Infrastructure

User Interfaces and Infrastructure

Desktop Experience

User Interfaces and Infrastructure

Server Graphical Shell

Windows Identity Foundation 3.5

Windows Identity Foundation 3.5

Windows Process Activation Service

Process Model

Windows Process Activation Service

Configuration APIs

In Windows Server 2012 and Windows Server 2012 R2, you can use Windows PowerShell 3.0 to install the IIS Requirements. Using the ServerManager module in Windows PowerShell 3.0, type:

Copy Code 
Import-Module ServerManager
Copy Code 
Add-WindowsFeature 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-Framework-45-Core, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Console, Web-Mgmt-Compat, Windows-Identity-Foundation, Server-Media-Foundation, BITS -Source D:\sources\sxs
Important:
New with Windows Server 2012 is the –Source parameter that defines where the Windows Server 2012 source media can be found. The media can be defined as a DVD drive (for example, D:\Sources\Sxs), or to a network share that the media files have been copied (for example, \\fileserver\windows2012\sources\Sxs).

See Also