D(one) IT

IT Tips, Tricks & Such

Monthly Archives: July 2013

Lync Connectivity Analyzer fails to open

I came across an issue where a fresh install of the Lync Connectivity Analyzer (http://technet.microsoft.com/en-us/library/jj907302.aspx) on Server 2012 wouldn’t launch. Looking in the Event Viewer I found the following errors.

Event: ID 1026
Source .Net Runtime
Application: LyncConnectivityAnalyzer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidOperationException

Event: ID 1000
Source: Application Error
Faulting application name: LyncConnectivityAnalyzer.exe, version: 5.0.8308.289, time stamp: 0x5113842c
Faulting module name: KERNELBASE.dll, version: 6.2.9200.16451, time stamp: 0x50988aa6
Exception code: 0xe0434352

I tried the Lync Connectivity Analyzer on my Windows 8 desktop (known to be working) and had the same issue.

System Requirements for the Lync Connectivity Analyzer
•Windows 7 Service Pack 1, Windows 8, Windows Server 2008 R2 SP1, Windows Server 2008 Service Pack 2, Windows Server 2012, Windows Vista Service Pack 2
•Microsoft .NET Framework 4.5

This led me to believe a patch for .NET 4.5 might be the cause. After removing the July patches KB2840632 & KB2833958, I was able to launch the Analyzer again. Another user reported that just removing KB2840632 will resolve the issue.

Details of the KB2840632 Security Update: http://support.microsoft.com/kb/2840632

Updated Lync Connectivity Analyzer: http://blogs.technet.com/b/nexthop/archive/2014/01/21/announcing-the-release-of-the-updated-lync-connectivity-analyzer.aspx


Limit access to Office Web Apps Server (OWAS)

When deploying an Office Web Apps Server (WAC/OWAS) the default allow list contains no domains, meaning OWAS will allow file requests to hosts in any domain.


This could allow unauthorized use of your server/farm if the Office Web Apps Server is accessible from the Internet (deployed in DMZ or Reverse Proxy to Internal). An external party could define the Office Web Apps Server pointing to your OWAS URL and start using your server for their workloads.


To lock down Office Web Apps Server, use the “new-officewebappshost” Cmdlet (http://technet.microsoft.com/en-us/library/jj219459.aspx) and set the domain parameter.


Any external party trying to leverage your Office Web Apps Server will get a server connectivity issue error.

Call Via Phone app Advanced review

With SNOM’s Enhanced Better Together being demonstrated at WPC 2013: http://www.snom.com/en/news/archive/article/2013/en/snom-to-demonstrate-pc-pairing-%E2%80%9Cbetter-together%E2%80%9D-features-on-its-microsoft-lync-qualified-desktop-phones-at-wpc-2013/ and availability being most likely end of 2013. I figured it would be a good time to post my review of the Call Via Phone Advanced. A 3rd party Better Together type application for Lync and SNOM phones which is currently available.

The Call Via Phone application comes in two editions (free and paid) and works with Lync 2010 and 2013.

After installing the Call Via Phone application from the MSI, the Lync client will now have a new item in the Tools drop down.

To configure the application enter the SNOM phone IP address, the Username/Ext, Password/Pin and Save. Note: Username/Password should be the account that can administer the SNOM phone’s web interface.


The freeware version is pretty straight forward which gives the ability to right click a contact and click “Call Via Phone”, this will establish the call on your SNOM phone.

The Advanced version will show an options menu after clicking “Call Via Phone”.

After clicking the number to contact, the call is answered on the SNOM phone and a popup menu with Phone Call commands for the active call will be displayed.

You can type in a number and click “Add Call”, this will establish a call to the added number and display additional commands like Transfer and Conference.

Originally the Call Via Phone application was just for outgoing calls. I reached out to Gianluca the author of the application and made some suggestions. A few emails later I had an updated version 1.5.6, that could handle incoming calls! Note: Account on the SNOM phone should be the same account signed into Lync to allow for incoming functionality.

In the “Call Via Phone” Configurator there is an option to “Activate” the Incoming Call via Phone service.

This creates a system tray icon that catches incoming call events and appears next to the Lync toast.

After clicking “Answer By Phone”, the call is answered on the SNOM phone and a popup option menu with available Phone Call commands for the active call will be displayed.

Benefits of Call Via Phone vs Enhanced Better together:

  • Can be made to work with other IP Phone vendors (Cisco, Polycom, Grandstream, 3CX, Yealink)
  • Doesn’t not require Lync user to have Enterprise voice for Outgoing call functionality
  • No windows driver protocol limitations, allows for future customization (Programming Phone keys, full interaction with any functionality available on the Phone)

For more info reach out to sales@callviaphoneapp.com