I am having an issue with a client where when they log in to their Outlook the wrong certificate is showing. The users are using Win7, Office 2010 and Exchange 2010.
When the users log in they should receive the cert for remote.contoso.com.
Instead they receive a cert for *.externallyhostedwebsite.com.
This issue started about 2 weeks ago when they launched a new externally hosted website. The cert is from RapidSSL and doesn't show any information showing its connection to the user's domain contoso.com.
I made a wildcard cert for their exchange, so *.contoso.com so that it would also get rid of those mail.contoso.com cert issues that they were previously receiving. I set this cert in the IIS bindings for 443 to the address of their mail server.
All users can currently bypass the cert error and get their email, but are worried about this cert showing up that isn't from their domain.
I do not see the *.externallyhostedwebsite.com certificate anywhere on their internal server.
My question is, how can i ensure that the wildcard that I made, the *.contoso.com, is the certificate that Outlook prompts for instead of the *.externallyhostedwebsite.com certificate?
No Rockin it