The Lync applications can be published manually like this – note the port 4443 on the Backend server URL: Even though we are not using Preauthentication, WAP cannot be setup without being configured as an ADFS Proxy. Note that there is a dependency on a Windows 2012 R2 Preview ADFS farm. Install the certificate and run the configuration wizard to setup the server as an ADFS proxy. Setup the Web Application Proxy by installing the Remote Access Web Application Proxy role service as mentioned in the previous post. Lync applications cannot use Preauthentication and have to use Pass-through which lets the backend server provide authentication. Office Web Apps Server for PowerPoint sharing.Lync External Web Services (which includes the Lync Web App and Lync Scheduler).Lync has a few different namespaces that need to be published: the solution to a problem I had testing this on Azure IaaS Virtual Machines.fix to make Lync mobile work ( updated 19 July 2013 with information about Windows Phone 8 SNI support).why the Office Web Apps Server published URLs must be the same.
#LYNC WEB APP 2013 HOW TO#
how to publish (reverse proxy) Lync 2013 and Office Web Apps Server 2013 (OWAS) using the Web Application Proxy.I showed how to publish Exchange 2013 (except for Outlook Anywhere which isn’t working) and a claims based application. I discussed the new Windows 2012 R2 Preview Web Application Proxy (WAP) remote access role in a previous post Windows 2012 R2 Preview Web Application Proxy – Exchange 2013 Publishing Tests.
0 kommentar(er)
