EWS Not Deployed reported by Skype for business while Exchange 2010 and 2016 coexistence

exchangeexchange-2016lync-2013

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 172.17.8.202 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 172.17.8.80 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.

Best Answer

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.