Hi everybody. 

I have just installed a new domain with Exchange 2013 and Lync Server 2013, my clients are running w8.1 with lync 2013 basic.

When i log in with the clients it is possible to use every function not directly combined with exchange, like chat,video,voice.

The problem is that i get a error saying Lync and Exchange is not making a connection.

EWS internal and external is not filled out on the lync clients

I have checked with the EMC for the internal URL and it lists out only the internalurl, wich is fine since its only a test environment

I can access it from all the domain computers through the web-browser. 

I have also created a auto-discovery on the internal DNS but the client still cant contact the Exchange server.

New host A or AAA 
Host:autodiscover
FQDN: autodiscover.domain.xx
IP: exchangeservers ip

As you probably already know i am quite new to this, it is my first time setting up a lync server.

For the record i used this guide deploying my Lync server.

http://windowspbx.blogspot.no/2012/07/step-by-step-installing-lync-server.html

My question is, how do i make Lync client discover the EWS, and is it working correctly ?

Hi,

Is your Lync sip domain different from primary SMTP domain ? Can you confirm ?

Thanks

Saleesh

Hello!

There are a decent handful of blog entries out there detailing in simple terms the requirements for properly configuring this integration. Doing a Google search for "how to configure lync 2013 for ews" will bring up a very helpful post by Thomas Poett and the various requirements for this, including the proper DNS settings, EWS Virtual directory setup with authentication settings, and SSL requirements. Therefore, I won't repeat what he has already so eloquently constructed.

However, if you feel you have followed these guidelines well, and are still not getting the expected integration, I would take a look at the client logs here: C:\Users\<username>\AppData\Local\Microsoft\Office\15.0\Lync\Tracing\Lync-UccApi-0.UccApilog. Once you open this file with a text editor, like Notepad or Wordpad, search for the term "ExchangeAutoDiscover". That should get you the entry where Exchange Auto Discover is failing, and then you can see what specific error is occuring, and what URLs are being attempted versus what you expect would be attempted. If searching for "ExchangeAutoDiscover" does not return a failure entry, try just searching "Exchange" in that log to see if it brings up something helpful.

If you find the entry, and need further assistance with understanding what is displayed in the log, please feel free to post the pertinent portion of the client log here, and I will do my best to help.

-Regards

Josh B.

Hello!

There are a decent handful of blog entries out there detailing in simple terms the requirements for properly configuring this integration. Doing a Google search for "how to configure lync 2013 for ews" will bring up a very helpful post by Thomas Poett and the various requirements for this, including the proper DNS settings, EWS Virtual directory setup with authentication settings, and SSL requirements. Therefore, I won't repeat what he has already so eloquently constructed.

However, if you feel you have followed these guidelines well, and are still not getting the expected integration, I would take a look at the client logs here: C:\Users\<username>\AppData\Local\Microsoft\Office\15.0\Lync\Tracing\Lync-UccApi-0.UccApilog. Once you open this file with a text editor, like Notepad or Wordpad, search for the term "ExchangeAutoDiscover". That should get you the entry where Exchange Auto Discover is failing, and then you can see what specific error is occuring, and what URLs are being attempted versus what you expect would be attempted. If searching for "ExchangeAutoDiscover" does not return a failure entry, try just searching "Exchange" in that log to see if it brings up something helpful.

If you find the entry, and need further assistance with understanding what is displayed in the log, please feel free to post the pertinent portion of the client log here, and I will do my best to help.

-Regards

Josh B.

• Marked as answer by Eric_YangKMicrosoft contingent staff, Moderator 5 hours 0 minutes ago

Hello!

There are a decent handful of blog entries out there detailing in simple terms the requirements for properly configuring this integration. Doing a Google search for "how to configure lync 2013 for ews" will bring up a very helpful post by Thomas Poett and the various requirements for this, including the proper DNS settings, EWS Virtual directory setup with authentication settings, and SSL requirements. Therefore, I won't repeat what he has already so eloquently constructed.

However, if you feel you have followed these guidelines well, and are still not getting the expected integration, I would take a look at the client logs here: C:\Users\<username>\AppData\Local\Microsoft\Office\15.0\Lync\Tracing\Lync-UccApi-0.UccApilog. Once you open this file with a text editor, like Notepad or Wordpad, search for the term "ExchangeAutoDiscover". That should get you the entry where Exchange Auto Discover is failing, and then you can see what specific error is occuring, and what URLs are being attempted versus what you expect would be attempted. If searching for "ExchangeAutoDiscover" does not return a failure entry, try just searching "Exchange" in that log to see if it brings up something helpful.

If you find the entry, and need further assistance with understanding what is displayed in the log, please feel free to post the pertinent portion of the client log here, and I will do my best to help.

-Regards

Josh B.

• Marked as answer by Eric_YangKMicrosoft contingent staff, Moderator Thursday, March 19, 2015 2:20 AM

Hi Gruber Hist,

Lync will look at your primary SMTP address and attempt to use it to find the EWS URL via Autodiscover after signing in. Its recommend to use the same SIP and SMTP address.

If the sip address is different with SMTP address and the DNS records are not configured correctly, youll have problem. To resolve this issue, you should configure additional SRV record for Autodiscover per SIP domain.

If this is not your problem, please feel free to let me know.

Best regards,

Eric