<div>
The alternative as a temporary measure is to create a spilt DNS.<br />
<br />
I.e create a zone for your external domain name in your internal DNS and then create an A record for mail and point it to your internal Exchange Servers IP address.
</div>


The alternative as a temporary measure is to create a spilt DNS.

I.e create a zone for your external domain name in your internal DNS and then create an A record for mail and point it to your internal Exchange Servers IP address.

<div>
<div class="content wysiwyg-content">
Hi,<br />
<br />
We have just set up a new Exchange 2010 server. I have imported our SSL certificate in for mail.mycompany.com and we can use OWA without any certificate errors.<br />
<br />
When we load Outlook on our lan though, as it loads we get a security error saying that the certificate is for the wrong domain name. Obviously when Outlook connects to Exchange it is connecting to the machine name (eg. exch.domain.local), problem is it is presenting the certificate for mail.mycompany.com thus the error.<br />
<br />
How do I configure Exchange so that when Outlook connects it uses the self signed (or a cert signed by our enterprise CA) instead of the mail.mycompany.com cert?<br />
<br />
If I configure IIS to use the exch.domain.local one, Outlook works fine but obviously OWA doesnt. If I configure IIS to use the mail.mycompany.com one then OWA works fine but Outlook doesn't.
</div>
</div>


Hi,

We have just set up a new Exchange 2010 server. I have imported our SSL certificate in for mail.mycompany.com and we can use OWA without any certificate errors.

When we load Outlook on our lan though, as it loads we get a security error saying that the certificate is for the wrong domain name. Obviously when Outlook connects to Exchange it is connecting to the machine name (eg. exch.domain.local), problem is it is presenting the certificate for mail.mycompany.com thus the error.

How do I configure Exchange so that when Outlook connects it uses the self signed (or a cert signed by our enterprise CA) instead of the mail.mycompany.com cert?

If I configure IIS to use the exch.domain.local one, Outlook works fine but obviously OWA doesnt. If I configure IIS to use the mail.mycompany.com one then OWA works fine but Outlook doesn't.

Exchange 2010 Certificate Problem

Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.

Exchange

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.