// // Leave a Comment

Step By Step Guide How To Configure IIS ARR (Application Routing Request) as Reverse Proxy for Lync 2013

IIS (ARR) Application Request Routing enables Web server administrators, hosting providers, and Content Delivery Networks (CDNs) to increase Web application scalability and reliability through rule-based routing, client and host name affinity, load balancing of HTTP server requests, and distributed disk caching.
Now TMG now being discontinued by Microsoft. Now most of the users are using IIS ARR or Apache as reverse proxy for Lync 2013. Here I am planning to IIS ARR (Application Request Routing) as a reverse proxy for my Lync 2013. As per Microsoft TechNet 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. Please check below TechNet article
IIS (ARR) Application Request Routing requirements,
Windows Server 2008
Windows 2008 R2
Windows Server 2012 OR Windows Server 2012 R2
You will need two NIC cards for IIS ARR, one is for external traffic with default gateway to get traffic from internet and second one for communicate with Lync 2013 front end server.
Note - Do not join reverse proxy server (IIS ARR) to your domain.

Install IIS on your ARR server. After installing IIS import Public certificate in your IIS ARR server
To do the same open IIS & click on “Server certificates”

Click on Import,

Provide certificate fie path, provide key & certificate store to import certificate.

Next we will install the Web Platform Components for downloading and installing IIS ARR.
Open below URL to install Web Platform Components http://www.microsoft.com/web/downloads/platform.aspx
Click on free download to Download and Install the Web Platform Installer 4.6.

In Web Platform Installer 4.6 window, search for “KB2589179" which will display the Application Request Routing 2.5. Select and click Add then Install to install IIS ARR.

Once installation gets completed. Close & re-open IIS manager. Now you will see new “Server farm” option in IIS.
Now right click “Server Farms”  & click on “Create Server Farsm”

Assign name to server farm & click next. Here I am using FQDN of my Lync webservices.

In Server Address tab enter your FQDN of your Enterprise Pool or Standard Edition Lync Server. Also in “Advance Settings” change http port to 8080 & https to 4443 as shown below and click Finish

Now you will be prompted to create Rewrite Rules, click Yes to continue.

Now your server farm is ready as shown below.
Now go to Caching and disable the disk cache.

Go to Proxy and change the time-out to 200 seconds.

Go to Routing Rules and disable the SSL offloading option.

Now go to URL Rewrite,

Double click on the ARR_Name_loadbalance_SSL Rule.

Now change the following options,
Pattern to (.*)
Using -> Regular Expression
Action Properties Scheme from http:// to https://

Now configure your firewall & publish meet, dialin & Lync web services & test it.
Repeat these steps for each simple URL you have. The goal here is to retain the simple URLs as they pass through ARR, so the Lync Front End URL rewriting rules recognize each simple URL as it comes in from ARR.