We currently have Exchange 2010 SP3 CU4 co-existence with Exchange 2013 CU8
We did the cut-over of autodiscover.domain.com and webmail.domain.com from Exchange 2010 to Exchange 2013
Autodiscover, OWA, ECP all work with user on Exchange 2010 and also on Exchange 2013

Now we experience some behavior i cannot explain and don't know how to troubleshoot.
When i have a mailbox on Exchange 2010 and go to https://webmail.rdgg.nl/ews/Exchange.asmx i automatically get on the page https://webmail.rdgg.int:/EWS/Services.wsdl showing a XML

When i have a mailbox on Exchange 2013 and go to https://webmail.rdgg.nl/ews/Exchange.asmx i get a page with "you have created a service" with a link to https://internalfqdn.domain.com:444/EWS/Services.wsdl

Clicking on this link opens the https://internalfqdn.domain.com:444/EWS/Services.wsdl url with a XML but this site has a certificate error , this because this is the BackEnd website of Exchange with a self signed Exchange certificate

1)Is there something different/changed in EWS on Exchange 2013 ?
2)Is this expected behavior that in 2013 we not directly get the XML but instead 'you created a service' ?
3)which log file should i check to see that goes wrong ?
4)what is a good test to verify ews works as should ?

Running "Service Account Access (Developers)" on testexchangeconnectivity.com shows GREEN and all test succesfull

We use EWS to receive mail in a mailbox, get mail from this mailbox and forward this.
We use EWS to synchronize calendar of a roommailbox to a 3rd party application.

Currently both functions dont work anymore and looking for a solution, troubleshoot tips, determine if this is really an Exchange 2013 problem.

Regards,

• Edited by dirkverhagen123 13 hours 47 minutes ago