Migration Exchange 2016 (CU22) to 2019 (CU12) problem autodiscover

Question

hello,

I configured an Exchange 2019 server (CU12) and migrated all balls to the server. Everything works except the Autodiscover service. When Server 2016 is off I get different errors depending on how I try to access Autodiscover. and this does not affect all workstations.
First of all I want to say that if I manually navigate to our xml at https://srv-exch2019.domain.local/autodiscover/autodiscover.xml and put in my credentials I get the error 600 expected and I have to report that autodiscover is functional. (It works internally for a few customers so I know that's not a problem.)
When running the test-outlookwebservices command in PowerShell (using my email address for -Identity and my credentials), I get the following:

from the outlook I have a connection to my 2016 while the BAL is migrated
he also offers me the certificate of 2016 and not of 2019

connection status is:

and if srv-exch16 is shutdown :

Answer 1

Hi @marielaurechaume-3814 ,
Please have a check that the "serviceBindingInformation" attribute of the SCP points to the new server . And is it in the form of having a fully a fully qualified domain name?
For example , https://EX19.contoso.com/Autodiscover/Autodiscover.xml.
Then please have a check that the DNS is pointing to the correct Exchange IP address.

---

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our [documentation][1] to enable e-mail notifications if you want to receive the related email notification for this thread.

[1]: https://learn.microsoft.com/en-us/answers/articles/67444/email-notifications.html

Answer 2

problem fixed. I think there was latency on the sites we had to wait for everything to replicate