Setting up reverse proxy servers for Lync Server 2013
Topic Last Modified: 2014-05-08
For Microsoft Lync Server 2013 Edge Server deployments, an HTTPS reverse proxy in the perimeter network is required for external clients to access the Lync Server 2013 Web Services (called Web Components in Office Communications Server) on the Director and the user’s home pool. Some of the features that require external access through a reverse proxy include the following:
Enabling external users to download meeting content for your meetings.
Enabling external users to expand distribution groups.
Enabling remote users to download files from the Address Book service.
Accessing the Lync Web App client.
Accessing the Dial-in Conferencing Settings webpage.
Enabling external devices to connect to Device Update web service and obtain updates.
Enabling mobile applications to automatically discover and use the mobility (Mcx) URLs from the Internet.
Enabling the Lync 2013 client, Lync Windows Store app and Lync 2013 Mobile client to locate the Lync Discover (autodiscover) URLs and use Unified Communications Web API (UCWA).
We recommend that you configure your HTTP reverse proxy to publish all Web Services in all pools. Publishing https:// ExternalFQDN/* publishes all IIS virtual directories for a pool. You need one publishing rule for each Standard Edition server, Front End pool, or Director or Director pool in your organization.
In addition, you need to publish the simple URLs. If the organization has a Director or Director pool, the HTTP reverse proxy listens for HTTP/HTTPS requests to the simple URLs and proxies them to the external Web Services virtual directory on the Director or Director pool. If you have not deployed a Director, you need to designate one pool to handle requests to the simple URLs. (If this is not the user’s home pool, it will redirect them onward to the Web Services on the user’s home pool). The simple URLs can be handled by a dedicated web publishing rule, or you can add it to the public names of the web publishing rule for the Director. You also need to publish the external Autodiscover Service URL.
You can use Microsoft Forefront Threat Management Gateway 2010, Microsoft Internet Security and Acceleration (ISA) Server 2006 SP1, or Internet Information Server 7.0, 7.5 or 8.0 with Application Request Routing (IIS ARR) as a reverse proxy. The detailed steps in this section describe how to configure Forefront Threat Management Gateway 2010, and the steps for configuring ISA Server 2006 are almost identical. Guidance is also provided for IIS ARR. If you are using a different reverse proxy, consult the documentation for that product and map the requirements defined here to the associated features in other reverse proxies.
Internet Information Server Application Request Routing (IIS ARR) is a fully tested and supported option for implementing a reverse proxy for Lync Server 2010 and Lync Server 2013. In November, 2012, Microsoft ceased license sales of ForeFront Threat Management Gateway 2010, or TMG. TMG is still a fully supported product, and is still available for sale on appliances sold by third parties. Also, many third party hardware load balancers and firewalls provide reverse proxy support. For hardware load balancers and firewalls that provide reverse proxy features, check with your vendor for specific instructions on how to configure their product to provide reverse proxy support for Lync Server. You can also view third parties that have submitted documentation for their product to Microsoft. Support is provided by the third party for their solution. To see third parties that are active in providing solutions, see Infrastructure qualified for Microsoft Lync.
The following topics and procedures use Forefront Threat Management Gateway 2010 and IIS ARR as the basis for the deployment and configuration procedures.
Before You Begin
To successfully deploy Forefront Threat Management Gateway 2010 as your reverse proxy, you need to setup and configure a server, using the prerequisites and hardware requirements defined in the Forefront Threat Management Gateway 2010 documentation. See the following topic set to properly configure the hardware and to install Forefront Threat Management Gateway 2010 on the server before proceeding.
To successfully deploy IIS ARR as your reverse proxy, review the following topics to configure the hardware and the prerequisite software.
To install IIS on Windows Server 2008 or Windows Server 2008 R2, see Installing IIS 7 on Windows Server 2008 or Windows Server 2008 R2
To install IIS on Windows Server 2012, see Installing IIS 8 on Windows Server 2012
To install IIS on Windows Server 2012 R2, see Installing IIS 8.5 on Windows Server 2012 R2
To download the Application Request Routing extension for IIS, follow the instructions at Application Request Routing v2.5 Download
To install ARR, for the instructions at Install Application Request Routing Version 2
The instructions currently posted are for ARR 2.0. For installation of the extension, there is no difference between the two versions.