First off...THANK YOU FOR YOUR HELP THUS FAR - YOU ARE ALL AMAZING! :D
I'm in the final stage of my new Exchange, load balanced and clustered environment. I was doing a "testexchangeconnectivity.
com" check and found my new Exchange setup was failing on "Testing SSL mutual authentication with the RPC proxy server." It was attempting to use the cert for my production Exchange environment (EMAIL.domain.com) instead of the new cert (MAIL.domain.com). The actual error was:
The certificate common name email.domain.com doesn't validate against the mutual authentication string that was provided: msstd:mail.domain.com
I did some digging and found I needed to run a quick command to fix this:
set-outlookprovider EXPR -CertPrincipalName msstd:mail.domain.com
And, at moment, everything within my new Exchange environment began to work beautifully! But, my joy was short lived...
I found that after switching the outlook provider cert to mail.domain.com (from email.domain.com), my clients in the production environment started getting a nasty error:
There is a problem with the proxy server’s security certificate. The name on the security certificate is invalid or does not match the name of the target site mail.domain.com. Outlook is unable to conned to the proxy server. (Error Code 0)
I immediately switched the outlook provider cert back. I need to know... Can I simply get a wildcard certificate and use that for both my mail.domain.com and email.domain.com? For example, running this command:
set-outlookprovider EXPR -CertPrincipalName msstd:*.domain.com
How would I do this?