We have Exchange 2010 and Lync 2013 servers in our environment.We are in the middle of Exchange migration to 2016 version.I've installed new servers and set the virtual directories on them.All the urls set correctly. On some clients I've added mail.mydomain with new server IP address into hosts file to test the new server client access role.Outlook and owa are working fine.Some users have no problem with lync or SFB client but most of them have "EWS Not Deployed" in their lync configuration information and their conversation won't save in conversation history.I try lots of googled solutions but nothing works.Users who don't have any error in their lync have a log in iis like this:

/autodiscover/autodiscover.xml &CorrelationID=<empty>;&cafeReqId=d8477152-1642-4a6d-bac0-d224361d42f4; 443 domain\user Microsoft+Office/16.0+(Windows+NT+10.0;+Microsoft+Outlook+16.0.4549;+Pro) - 200 0 0 135

Others who encounter error have below log:

/autodiscover/autodiscover.svc &CorrelationID=<empty>;&cafeReqId=14b89ba7-d59a-4c94-8f36-0e8413843a53; 443 domain\username OC/15.0.4997.1000+(Microsoft+Lync) - 302 0 0 27

Update:Users whose mailbox are in mailbox 2016 doesn't have such problem and only mailboxes from 2010 have this problem.


As we known, the Lync / SfB client will not use Active Directory SCP records to retrieve the Autodiscover URL. It will only use the DNS-record method.

Therefore, please ensure point autodiscover record (also other Exchange services, for example EWS, OAB) to new Exchange 2013 server. It will do proxy if mailbox in Exchange 2010.

  • I already have changed virtual directories of exchange services but we are in a large environment with too many users so I prefer to be sure that everything would be okay before cutting the whole name space by changing dns record of forest. – harsini Jan 9 '18 at 6:10
  • All right, however Lync/SFB client only use Autodiscover's DNS record to get EWS service. You can double check it after change this record after everything is fine to migration. – Jianfei Wang Jan 15 '18 at 9:28
  • I correct my question.I add mail and autodiscover address and new server ip address to hosts file . – harsini Jan 15 '18 at 14:37

Some of 2010 mailboxes already has problems with EWS in lync without moving to 2016 servers but some don't.Moving mailboxes to 2016 servers solve the second group problem but not the first group.The first group problem maybe solve by using client side solution here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.