Troubleshooting EWS issues in LYNC 2013

The EWS not implemented error in LYNC – can be a pain to troubleshoot, because it can be caused by many different factors.
I will try to give you my experience on troubleshooting this issue.

First of it is important to understand how the EWS integration works in LYNC.
Lync uses the following DNS-based discovery method
http://<smtpdomain>/autodiscover/autodiscover.xml https://<smtpdomain>/autodiscover/autodiscover.xml
SRV: _autodiscover._tcp.<smtpdomain>

So wery often I see customers having a perfectly good working autodiscover setup, seen from Outlook because it utilizes SCP in AD – and when LYNC is deployed integration fails.

So which features are serviced by EWS:
Conversation History
Missed Conversations
Missed Calls
Voice Mail Playback
High-Resolution Photos on contacts
Meeting tab – with meetings from calendar
Contact Information Presence based on Calendar Information
And Unified Contact Store

So EWS is extremely important for LYNC to work correctly
And therefor DNS based autodiscover needs to be setup corrently.
Please note that if EWS fails LYNC will failback to MAPI for some features

Also internal URL for EWS needs to be configured on Exchange – more info:

When all the above is set correct , and EWS integration still fails – well.. start diggin 🙂

First off, lets get an idea of what LYNC actually tries to do.

Sign in to local pc as the failing user, and with LYNC client running, find the LYNC icon in systray – press CTRL and rightclick icon and select “configuration information”

Check to EWS URL lines, and EWS status.

IF EWS not deployed shows up then first thing to check is this reg key:

Start regedit.exe
Go to HKLMsoftwareMicrosoftofficeoutlookaddinsUCAddin.LyncAddin.1
Make sure that value of “LoadBehavior” is = 3, if not then change it to 3

Note: It might be under HKLMsoftwareWow6432NodeMicrosoftofficeoutlookaddinsUCAddin.LyncAddin.1

Restart LYNC client and wait a couple of minutes.
If still “not deployed” Then try
On the Edit menu, point to New, and then click DWORD Value.
Type OverrideDirectHttpConnection, and then press Enter.
Right-click OverrideDirectHttpConnection, and then click Modify.
In the Value data box, type 1, and then click OK.
Exit Registry Editor.
At one particular customer this issue was resolved by adding to Local intranet sites in explorer, where we found that otherwise LYNC would not go from autodiscover method one and move on to metohd 2, 3 and so on.
This article is a work in progress – more troubleshooting tips to come
To be continued…


Leave a Reply

Your email address will not be published. Required fields are marked *