#LYNC WEB APP DOWNLOAD 2013 INSTALL#

For each server farm, do the following steps:Ĭlick each server farm and choose “Caching”: Now, a few adjustments to make this work right with Lync. This will come in very handy in just a few more moments.ĭo the same steps for every external address you want to publish.Įventually, you’ll end up with enough farms to publish all your external addresses: Once you click “Finish”, you’ll get a prompt asking if you would like to create a URL rewrite rule:Ĭhoose “Yes”. Now you can see the server in the server farm: *** For the Office Web Apps farm leave the ports 443 and 80, as these are redirected directly to the server’s website. Set the HTTP port to 8080 and the HTTPS port to 4443, then click “Add”: “Advanced settings” is where we set the port bridging rules from 443 to 4443, just like we used to do with TMG 2010. You need to add the server to the farm only after you set the advanced settings for the server. Remember to click “Advanced settings” BEFORE you click “Add”. On the “Add Server” window, type the name of the server you want to publish and then click “Advanced settings”: After you enter the name of the server farm, click “Next”: In “Server Farm Name” enter the external FQDN of the service you want to publish. To build the first Server Farm, right click “Server Farms” and choose “Create Server Farm”: The Internal names of your Lync servers and WAC servers must be resolvable from this server, so don’t forget to add them to your hosts file.The Internal root CA (The one that’s used for signing the internal Lync certificates) must be placed in the “Trusted Root Certification Authorities” container in your IIS ARR machine.We need to create a server farm for each name we’re publishing.This completes the configuration of the web site. In the next window, choose “HTTPS” from the drop down menu, then choose your Lync external certificate, and press “OK”: Navigate to your default website in IIS Manager and click “Bindings”: Import your Lync 2013 external certificate to the server: “Web Platform Installer” in the management node.Open IIS Manager, and you’ll see you have two new features: This is all you need for IIS ARR to work:

#LYNC WEB APP DOWNLOAD 2013 INSTALL#

Install all of the above in respected order.Ĭhecking Windows 2012’s Programs and features will show you these exact 4 items.Download Web Farm Framework 2.2 (Scroll to bottom of page).If your server can’t access the internet for some reason, you’re up for a real treat: When the installation is finished, You’ll see it has installed four components: That’s 4 components all together:Ĭlick “I Accept” and enjoy the commercial content from Microsoft whilst the installation is taking place: Hitting “Install” will show you the features you’re about to install.

You’ll get the first installation screen, telling you it will install 2 features: Whichever platform you choose (ARR 2.5 or ARR 3.0), it’s an identical installation and configuration process: Use Microsoft Web Platform Installer to install IIS ARR 2.5.Download Hotfix for Microsoft Application Request Routing Version 2.5 for IIS7 (KB 2732764) (圆4), we’ll use that later.

Install IIS on Windows Server 2012 with all defaults, nothing too smart.

Use Microsoft Web Platform Installer to install IIS ARR 3.0.

Install IIS on Windows Server 2012R2 with all defaults, nothing too smart.

As Forefront TMG 2010 is becoming end of life, Microsoft’s official and at the moment only supported Reverse Proxy solution for Lync Server 2013 is IIS ARR.įor Skype for Business Server the only supported solution is Server 2012 WAP, but IIS ARR 3.0 will also work for you.ĭoing this is rather simple, and this post will demonstrate the steps to publish Lync 2013 External Web Services using IIS ARR on Windows Server 2012.įirst things first, an installation and two downloads:

Lync web app download 2013