[Webinar] Streamline your web hosting managementRegister Today

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 247
  • Last Modified:

Exchange 2010 Outlook Certificate Warnings

I just installed Exchange 2010 in my organization.  My internal domain is different then the exchange domain.  I purchased a SSL certificate for my public domain and my outlook 2010 keeps coming up with a certificate mismatch warning.  I can not purchase a ssl for my internal domain name because just by chance someone else owns that.  How would I go about stopping these mismatch warnings.

  • 3
  • 3
1 Solution
Can you create a free self signed certificate for internal use. This is normal and proper practice for internal resources for the most part. Use your internal self signed certificate will eliminate this error on any computer on your domain that accesses your local certificate store. (In other words just any computer that is connected to the domain).

Below is a great guide I used in the past:


Hope that gets you going =]
bidgadgetAuthor Commented:
Thank you.   Will there be any issues for the users on the outside?  Also how do I make it that the internal users see the internal cert and outside users see the external?
The outside SSL certificate points to your public IP address. The purchased certificate is hosted by the public third party entity. Whereas the local self signed certificate will be hosted locally on your server and points to only your local IP address.

So from the outside if you type in website.com the certificate translates that to x.x.x.x (your public IP)

From the inside, you will have to make a entry on your DNS server to state website.com...but instead you will translate it to use x.x.x.x (your local server's IP)

So that's how it makes the distinction of what certificate to use, it's actually using different IP addresses (local vs public).
Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

bidgadgetAuthor Commented:
OK.  I followed.  No I am getting a different popup.  I am getting the warning that the certificate is from a company that I have not chosen to trust.  Is there any way to stop that?
bidgadgetAuthor Commented:
Also sorry to be a pain.  Now the outside items are giving me a certificate error for the internal certificate.  Is there any way to stop that?
As explained to you by "Pancake_Effect" on the link (guide) he suggested, you will have to copy/import the self-signed certificate in every single machine you have on your organization... hope you don't have a couple of hundreds!!!

The other way around is to use only 1 SSL for everything.  what you will have to do is rename your internal links to match the external or have a wildcard on the SSL.

The simplest way is to have the same name outside and inside the organization and create the proper DNS record on your organization to point to your internal server.

Now, because this is not done since the beginning you will still get some errors for some names you can't change with the EMC.

When you setup Exchange Server it creates a default self-signed certificate for internal use and the common name on it is usually the machinename.domainname, when you installed the new certificate  you did with your external (internet facing) name which is normal but now you need to replacement he fully qualified domain name (FQDN) of the URL that is stored in the following objects:

The Service Connection Point for the Autodiscover
The InternalUrl of Exchange Web Service (EWS)
The InternalUrl of the OAB Web service

Here is what worked for me: http://support.microsoft.com/kb/940726 

Let me know!!!

Shouldn't the certificate store automatically push/pull the self signed certificate into all the local machines? Shouldn't have to manually do it unless I'm mistaken. It's been a long time, but I think that's what I did for our webmail service.

Internally I just made a dns entry called mail.example.com, and associated a self signed certificate with it and the local IP. Which all the domain computers pull from the certificate store, and fixed the errors.

Externally I used Go daddy to host mail.example.com, which I then pointed to the public address which fixed those issues.

Again it's been a long time, but I thought hat was the general steps I did. Please correct me if I'm wrong, it's always nice to have a refresher course haha.

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now