Monthly Archives: February 2014

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.

Lync Virtualization White Papers… Finallllyyyy

It’s here, it’s here!!!  We’ve been waiting for these for a long time.  We feel that we’re pretty good at scaling, sizing, and implementing best practices when it comes to Lync for virtualization, but it’s very welcome to have a document you can reference.  For those of you have your Lync infrastructure virtualized (that means you), it’s a must read.  Look for common mistakes you may have seen such as avoiding dynamic memory and thin provisioned disks.

Find it here:

Multiple CDR Database Errors

If you’re looking at this, you probably have seen the LS Data Collection 56208 events all over your logs.  These can be numerous and ugly.

Insertion of an error report was throttled to prevent flooding of the Call Detail Recording (CDR) database.


Component: CDR Adaptor

Cause: This is an expected condition if too many error reports of the same type were reported at the same time.


No action is needed. A large enough number of error reports of this type have already been inserted into the database and can be used for troubleshooting and reporting. Additional errors are not inserted to avoid flooding of the database with redundant information.

You’re also wondering what to do about them.  Right now, there’s not much for you to do.  Fortunately it’s nothing to be concerned about.  It has been confirmed as a known issue.  We have heard that it may be escalated to make it into the an upcoming CU but until then, consider it a “noise event” and ignore it.

New Key Health Indicators Poster!

Microsoft has release a poster highlighting some of the key health indicators (KHI) to be used in conjunction with the script inside of the Lync Server Networking guide.  Of course, it has to be said that this isn’t the sum total of everything you’ll need to monitor, and remember that there are a lot of components outside of Microsoft Lync that you’ll need to monitor as well (heavy networking and SBC monitoring is a must).  However, this is extremely handy and I urge everyone to take a look!

Link to the KHI poster:

Link to the Lync Server Networking Guide: