Forum Discussion
"The name on the security certificate is invalid..." After changing to trusted CA and updating VDs
Hello, This is with Exchange 2019. after changing the virtual directories to mail.domain.com (from mail.domain.local) and applying the appropriate certificate, when starting Outlook, the followi...
Sometimes there will be connections made using the server's hostname. Review your internal DNS MX records if you have any.
I'm not sure why the Autodiscover FQDN did that. I only know there is generally no need to change those settings. When the Outlook client is connected to the domain it will get the autodiscover URI via the SCP record (use Get-ClientService to view the URI details), not anything in the autodiscover virtual directory
I'm not sure why the Autodiscover FQDN did that. I only know there is generally no need to change those settings. When the Outlook client is connected to the domain it will get the autodiscover URI via the SCP record (use Get-ClientService to view the URI details), not anything in the autodiscover virtual directory
We do have split DNS setup. The reason I changed the Autodiscover URI is because I had the idea that maybe Autodiscover is causing the name mismatch since the SCP record is domain.local, which is not on the new cert anymore.
I have opened a case with Microsoft now and hopefully they can help out.
I have opened a case with Microsoft now and hopefully they can help out.