Lync 2013: EWS has not fully initialized

Recently I had to troubleshoot an issue regarding EWS and Lync 2013 Client integration.

In the Lync 2013 Client Configuration Information window, EWS URLs were empty and the status message was EWS has not fully initialized and MAPI Status OK.


Lync 2013 Client was internal, therefore the conversations were stored in the Outlook Conversation History folder. However, there are some features that depend directly on EWS, such as voice mail integration in the Voice tab. In the next print we can see that the Voice Mail feature is missing:


One important information is that SIP and SMTP Domains were different, and there wasn’t any issue connecting to Lync or Exchange.

Using Microsoft Remote Connection Analyzer (, Exchange Autodiscover passed the test with some irrelevant warnings.

In Lync 2010 Client, users were asked to trust the autodiscover certificate:


This happens because Lync Client will trust certificates from the same domain as our SIP domain, even though it asks for confirmation when the domain of the certificate is changed:

SIP domain SMTP domain Trust
lync2013.uclobby lync2013.uclobby Yes
lync2013.uclobby exchange2013.uclobby No

Just for fun I removed the Lync 2013 Client updates and returned to 15.0.4517.1504 (August 2013 CU). After signing in, the following popup message was displayed:


In this case, the solution was to tell Lync to trust the other domain, by adding the following key to the registry:

reg add HKLMSoftwarePoliciesMicrosoftOffice15.0Lync /v TrustModelData /t REG_EXPAND_SZ /d exchange2013.uclobby /f

For more information check this:

After adding the registry key, just restart Lync Client and the EWS status will change to EWS Status OK. Since Lync 2013 Client can connect now to EWS in the voice tab, it will list our voice mails:



7 thoughts on “Lync 2013: EWS has not fully initialized

  1. Thanks for writing this up! I had this exact problem and this got me working. However, what threw me off was I was not getting the pop up to trust the external autodiscover domain because I updated to the latest version of the client before testing. If it is up to date (as of Dec 2013) you wont get the pop up but the EWS still doesn’t populate and stays at “not fully initialized”. Adding the registry entry to trust my external domain name fixed the problem. Thanks!

    1. This was EXACTLY my problem and not having the certificate warning completely sent me off down the wrong track… Not a single log file reported this behaviour either!

      1. Lync Client 2010 was the key to solve this. Even if in future updates the Lync Client 2013 starts to request users to confirm that the certificate is trusted, adding that value to the register avoids the popup message/confirmation.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.