It is also important to note that there is no way for you to assign a different certificate to the external URL and internal URL as you are forced to use the same certificate which I hope would change in future versions to give us a bit more flexibility when configuring the farm.īegin by creating the the Office Web Apps Server object in the Lync Server 2013 Topology Builder and use the external URL as the FQDN: You could easily use the FQDN of the Office Web Apps server if you put that as a SAN entry into the certificate. This isn’t a requirement but I chose to do so because the public certificate we’ll be using is actually shared with the other Lync services and it only includes the public URL for the Office Web Apps server service. I won’t go into the details for the Office Web Apps server install because my previous post demonstrate this so I’ll begin by explaining the URLs I have chosen for internal and external:Īs shown above, I am using the same URL for both internal and external access.
#Install lync web app how to#
I’m not sure why but writing this follow up post seems to have consistently slipped my mind over the past 2 years so without further delay, this post will demonstrate how to configure the Office Web Apps server to serve PowerPoint presentations for both internal and external Lync conference meetings. … as to why I never included instructions on how to publish this service externally because the configuration only allows for internal access. I’ve been asked on several occasions over the last 2 years since I’ve written the following post demonstrating how to deploy an Office Web Apps Server:ĭeploying Office Web Apps Server on Windows Server 2012 for Lync Server 2013 Enterprise or Standard Pool
0 kommentar(er)
