Outlook clients on LAN getting a Certificate error after installing 3rd party SSL cert
Posted on 2012-08-22
New, single server, Exchange 2010 install. This client has numerous users accessing OWA outside the network, so we purchased a cert from a well know provider, and its working, no issues. The problem is that LAN users are now getting a pop-up stating the Certificate is invalid b/c the name doesnt match. It lists the Exchange server's local FQDN (example.mydomain.local), and provides the new SSL cert with the public FQDN (mail.mydomain.com). Users are the LAN are automatically being configured with Outlook Anywhere (which i need enabled for some remote users), and when i attempt to turn this off, it automatically re-enables itself. Im not sure if forcing users on the LAN to NOT use Outlook Anywhere would fix this or not, but i find it odd that it's automatically re-enabling itself.
How do i keep the purchased SSL cert in place for OWA and Outlook Anywhere, and stop the certificate mismatch error in Outlook for users on the LAN?