Deploying Office Web Application Server for Lync on Windows 2012 R2

There are a thousand articles on the deployment of Office Web Application Server (WAC or OWAS) for Lync and this one isn’t much different, however I wanted to hit a few extra best practices in terms of staging directories and securing your server.  Skip to the end if you already have OWAS installed and are curious or if you don’t need a full step by step.


  1. From within an Administrative PowerShell window, run:
    Add-WindowsFeature Web-Server,Web-Mgmt-Tools,Web-Mgmt-Console,Web-WebServer,Web-Common-Http,Web-Default-Doc,Web-Static-Content,Web-Performance,Web-Stat-Compression,Web-Dyn-Compression,Web-Security,Web-Filtering,Web-Windows-Auth,Web-App-Dev,Web-Net-Ext45,Web-Asp-Net45,Web-ISAPI-Ext,Web-ISAPI-Filter,Web-Includes,InkandHandwritingServices,NET-Framework-Features,NET-Framework-CoreOWAS_PowerShell_Install
  2. Once complete, you’ll need to reboot.
  3. Download Office Web Apps server (OWAS) from
  4. Download the OWAS update from:
  5. The OWAS link from step 3 will give you a wacserver.img file. Right click it and select Mount.
  6. Find the mounted media in “This PC” (formerly My Computer). Right click setup.exe and choose “Run as administrator”.  You might choose to install it on a separate application partition as I have.
  7. Now, let’s right click the update and Run as Administrator.
  8. Great!  Now we’ve got it installed.  Let’s create our OWAS farm.  From Powershell run: New-OfficeWebAppsFarm -InternalUrl “” -ExternalUrl ” ” -CertificateName “OfficeWebApps Certificate”  Of course, change to the public name you’ll be publishing and use a certificate that contains this name.  If you need it, Digicert has a nice little writeup for requesting a certificate in IIS 8.5: OWAS_new_farm_1
  9. If you notice the arrows in the above picture, you’ll notice that we’re using the C drive for a lot of these locations.  Now that we’ve got our pool, let’s change some of the logging and cache locations to our application partition.  From PowerShell, run:
    Set-OfficeWebAppsFarm -LogLocation E:\ProgramData\Microsoft\OfficeWebApps\Data\Logs\ULS -CacheLocation E:\ProgramData\Microsoft\OfficeWebApps\Working\d -RenderingLocalCacheLocation E:\ProgramData\Microsoft\OfficeWebApps\Working\waccache
  10. Finally, let’s lock it down so other’s can’t use it!  From the following article: Let’s run “New-OfficeWebAppsHost – Domain”.
    This will ensure only users from our domain are using our server.