Exchange 2013 cert with local domain we do not own
Posted on 2013-02-06
I have a unique problem. I'm adding Exchange 2013 to a clients existing environment. Problem is that the domain that was originally setup is: xxx.org, which we do not own and is unavailable.
I have created an external certificate for the correct domain, yyy.org, and it is working fine with OWA.
Problem is that Internal outlook clients are getting a cert error for mail.xxx.org.
I'm guessing you can get around this with an internal cert? I just set one up, but I'm still getting the error when I start outlook.
does anyone know how to get around this? I'm guessing Outlook is only looking at the cert that has the default SMTP service set on it, which is the remote cert.
Any help would be appreciated,