Hello,
I've recently did the .local to .com transition for my Exchange 2010 server and put in a new certificate. All my local network computers have been connecting just fine until last weeks install of SP3 Rollup11. Now some(not all) Outlook clients are throwing up a certificate name mismatch error. They are using the default servername of the self signed certificate *.contoso.local and not the newer certificate of mail.contoso.com. Anyone know why?
The original self signed certificate is still installed, should I kill it? All of our Outlook clients show the servername of that old original name and even deleting the profile and recreating it still uses that instead of the new mail.contoso.com one. I've had nothing but odd issues since SP3 Rollup11 and I'm so frustrated, examples: OWA users are now exceeding thresholds\OWA sessions are dropping, ugh please help if you can as I'm about to use a sledge hammer on this server :)
Thanks,
Larry