Hi
Here's the setup.
1 Exchange 2013 server with two public domains. 1 (normal) public certificate for public domain A installed. Users have for a while been using public domain B as their primary domain (email) with the certificate warnings that comes with it.
I have now installed a wildcard certificate for public domain B, activated it for relevant services (IIS + SMTP) and changed all public addresses on the Exchange server from domain A to domain B. The old certificate for domain A has been removed from the server now.
Also did a few other things in regards to receive and send connectors - bottom line is that everything seems to be working fine, apart from a SSL certificate warning from Outlook after it starts up claiming that "The name on the security certificate is invalid or does not match the name of the site" - headline is autodicover.domainA.com here. If I click "View certificate" I see the wildcard certificate for domain B which is as it should be. I then just press Yes (to continue) and Outlook works and as far as I have tested doesn't prompt me again before I restart Outlook when it prompts me again.
If I configure a new Outlook profile using the email address in domain B, it configures fine and Outlook opens without any prompts and doesn't prompt me.
Also when I run the autodiscover tests everything points at domain B, no mention of domain A anymore and I don't get any certificate warnings running these tests.
I have configured split DNS for domain B, I have not deleted any DNS records for domain B yet.
So my question is, have I missed a vital change to get Outlook to let go of the old name that can be easily fixed, or do I really have to reconfigure all mail profiles for this certificate prompt to go away? All mobile devices had to be reconfigured - which I expected, but I didn't expect Outlook to do this :(
Thanks for your time
Best
Thomas