Exchange 2010 UCC Certificate - Can't get internal domain name listed in cert so we have issues.
Posted on 2013-12-12
I have a customer with a new Exchange 2010 install. They were ready to turn up OutlookAnywhere and we purchased the appropriate UCC cert for them. We added in owa.domain.com as well as any other FQDNs we thought appropriate. All was well, remote devices could connect.
But now internal users are complaining that every time they launch Outlook they get a security alert. The name on the cert doesn't match the name of the server they are connecting to.
I went to modify the UCC cert to add the internal FQDN of the Exchange server and I can't because the internal FQDN is something they don't own, but is a real domain name: Exchange.RealDomainName.com
There is no way for me to add this FQDN to the cert. How do I get the internal Outlook users to either accept this, or to go back to using the self signed cert they were using before?