The script is pretty straight forward, all you have to do is run it form a local folder on your FE server with elevated permissions.
However, this will only give you the FE’s certificates.
Guy was smart enough to create the following additions:
-EdgeCertificates and -OWASCertificates
You can run either or both, and they will give you information about your Office Web Apps Servers’ certificates (-OWASCertificates) and your Edge Servers’ certificates (-EdgeCertificates).
When using the -EdgeCertificates option, you’ll be prompted to enter your Edge Server’s credentials.
That’s all the configuration needed on the Lync side.
Next step is to configure a publishing rule in TMG 2010. Unfortunately, you cannot use your External web url, since Lync traffic is bridged to port TCP 4443, and Office Web Apps Server works HTTPS, meaning TCP 443.#
Since TMG is end of life, You can now use IIS ARR to publish Lync Server 2013.
27.03.2013: Updated to the latest version of Office Web Apps Server.
Lync Server 2013 WAC is a new requirement in the Lync Server 2013 deployment. You’ll have to have this server is you want to be able to share PowerPoint presentations.
The installation and configuration of this server is quite easy, let’s take a look:
First, download the Microsoft Office Web Apps Server from here and the update from here. While it downloads, we can configure the other prerequisites.
If you’re using Windows Server 2008R2, please download Microsoft’s .Net Framework 4.5, download Windows Management Framework 3.0, and download KB2592525, which will allow you to run the applications in a Server 2008R2 environment.
Install all of the above, Then, run this using an elevated PowerShell:
If you’re using Windows Server 2012, it’s even easier; Just run the following from an elevated PowerShell (Server 2012 imports the relevant PS modules automatically, so you don’t have to use the “Import-Module” command) :