Lync Client 2013 – EWS has not fully initialized

UC Lobby

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.

EWSFully01

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:

EWSFully02

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 (https://testconnectivity.microsoft.com/), Exchange Autodiscover passed the test with some irrelevant warnings.

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

EWSFully03

This happens because Lync Client will trust certificates from the…

View original post 133 more words

Advertisements
Posted in Uncategorized

Leave a Reply

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

WordPress.com Logo

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

Google+ photo

You are commenting using your Google+ 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

%d bloggers like this: