Exchange 2010 Outlook Certificate Error

I recently migrated to Exchange 2010 from Exchange 2003, following all of the needed migration steps and finally cleanly removing Exchange 2003 per the following article:

I realized I made one mistake on the way and that is my Exchange 2003 server operates off of the domain When doing the installation wizard for Exchange 2010, the step which asks what domain to use for the Client Access Server, I put instead of

So after the installation I had to go in and change the internal and external URLs for Outlook Web App, Active Sync, Exchange Control Panel, OAB, Outlook Anywhere and even did autodiscover internal and external via powershell.

However, even after fully removing Exchange 2003 and correcting the domain on all of the URLs, I'm still getting an Outlook certificate error that there's a name mismatch. Specifically "The name on the security certificate is invalid or does not match the name of the site."

I have created a self signed certificate that has the domain and a subject alternative of All DNS for mail and autodiscover is pointing to the correct server. The server's internal name is

See attached images of Outlook Autoconfiguration Test, all domains point to "".

I don't know what next step to take to fix this Certificate Error.

I read somewhere about an Active Directory Service Connection Point for Autodiscover but I'm not sure where to find that or if that will fix the issue or not.

Outlook Cert Error
Outlook AutoConfig test first 1/2
Outlook AutoConfig second 1/2
Who is Participating?
Gareth GudgerCommented:
If the certificate matches, have you checked to verify all your external and internal URLs? Make sure all internal and external URLs are

Also, does your self signed cert have on it? Or are you doing SRV records for autodiscover? Otherwise you will need on your cert.
Manoj BojewarCommented:
This is known issue with outlook 2007. Please check outlook 2010 and 2013 and let me know the status.
Check autodiscoveruri by running get-clientaccessserver | fl

Set-ClientAccessServer -Identity "server" -AutoDiscoverServiceInternalUri

Set-WebServicesVirtualDirectory -Identity "server\EWS (Default Web Site)" -InternalUrl -ExternalUrl
Configure all the virtual directories internal/external with
Configure outlook anywhere using
Create a DNS forward lookup zone in internal DNS as
Create host A record named and point it to Exchange server IP.
Also check if the third party certificate is configured on IIS default web site. If it is self-signed certificate then install it on all workstation.
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

RFVDBAuthor Commented:
Thanks. All that's already been done.

All internal and external URLs for everything are

Outlook anywhere is configured with

There is an internal DNS forward lookup zone for and "mail" is pointed at internal exchange IP.

self signed certificate is bound to 443 on IIS website. I have a GPO that installs this certificate on all client workstations. Initially I was getting the first error on the Outlook error that the certificate is not from a trusted source but now that is gone. Just get the third error about an SSL certificate mismatch.

Also ran test-outlookwebservices -identity username. All came out well (see attached). There is a section in the output that is an error and it mentions the certificate for EX2.OFFICE.DOMAIN.COM/Autodiscover is incorrect. However I checked this output at another client with the same setup and they also had this error on this same command, however they don't have the constant Outlook certificate error mismatch.

I'm lost. Please let me know if you need any powershell outputs or screen shots in case I'm reading things wrong.
RFVDBAuthor Commented:
Also this happens with Outlook 2007 and 2010 which is what the client has in the environment.
RFVDBAuthor Commented:
If only the error would tell you which hostname its wanting an SSL Cert for that is not listed on the the SAN Cert. Thank you microsoft for being so specific...

I even tried creating the _autodiscover SVR record and deleting the local A record for autodiscover and the error still comes up.

I'm wondering if its either stuck on the domain I entered when I ran the Exchange 2010 install wizard as "" instead of "" or if it thinks it needs the hostname of the server as part of the SSL Cert -

Something is awry... and its not telling me what it is.
RFVDBAuthor Commented:
I'm lost on this. I went ahead and created a new self sign cert and added the server name, and the actual domain name "" as subject alternatives. Still had the same problem.

I used the command:

New-ExchangeCertificate -FriendlyName "SelfSigned Cert" -SubjectName "c=US, o=company," -DomainName,, -PrivateKeyExportable $True

I just can't figure out what domain it is looking for!

This has got to be something other's have run into.
Gareth GudgerCommented:
I really would recommend staying away from self-signed certificates for Exchange and only using a certificate from a trusted 3rd-party CA. Its going to save you a lot of time and headaches. So its worth the cost of the cert.

Check out my article here on how to configure split-dns, certificates and all the URLs with a 3rd party cert.
RFVDBAuthor Commented:
Hi Gareth,

Thanks for the and answer link.

I've successfully set it up with a third party cert many a time. Just wondering how to get it to properly work with a self signed cert without getting into setting up a whole CA and all.

This is the link I followed in creating the cert:

I then setup a GPO to import the Cert into all workstations.

Another interesting datum is when going to it comes up with a certificate error on in viewing the certificate error in Internet Explorer: "Mismatched Address" "The security certificate presented by this website was issued for a different website's address".

That's weird, the certificate does match the domain in "". So what am I doing wrong here?
RFVDBAuthor Commented:
Yes, all internal and external URLs have been checked.

It does have on it as a subject alternative name. This wasn't working so I then tried to use SRV records. This also didn't work.

What's strange is if you look at my post above when opening up owa in Internet Explorer, IE is complaining of a "mismatched address". It says "The security certificate presented by this website was issued for a different website's address."

However the address I typed into the web browser is EXACTLY what's on the certificate when viewing the property of the certificate. SO IE IS COMPLAINING OF A MISMATCHED ADDRESS EVEN WHEN THE CERTIFICATE MATCHES THE ADDRESS TYPED INTO IE!!!

Weird. This seems more like a weird certificate issue than the URLs in Exchange being correct.....
Gareth GudgerCommented:
Can you go to and do the autodiscover test and post the results here. Sounds like it is picking up another cert. Possibly your public websites cert.
RFVDBAuthor Commented:
OK, I'll do this shortly and post the results.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.