?
Solved

exhange 2010 certificate error message on outlook clients

Posted on 2014-03-26
7
Medium Priority
?
197 Views
Last Modified: 2014-07-02
hi everyone I recently had and expired certificate, updated it, and now internal mail clients are seeing "The name on the security certificate is invalid or does not match the name of the site"

 The untrusted site on external OWA is now resolved but now clients are seeing that error.

Ive seen a few command line fixes but hesitant to make it worse.
0
Comment
Question by:WAMSINC
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
7 Comments
 
LVL 3

Expert Comment

by:Winsoup
ID: 39957029
Are the "Subject Alternative Names" all the same as the last certificate?
Seems to me that an autodiscover.domain.com or something is not set correctly on the new certificate.

Did you import the new cert in the Exchange Management Console as well?
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 39957649
Was this a new self signed or trusted certificate?
If it was a trusted certificate, it probably did not contain your internal server names.
If it was a self signed certificate - well those are not supported for production use.

You may well have to change the Exchange configuration to use your external host name internally. That is easy to do and doesn't take long.

http://semb.ee/hostnames2010

Simon.
0
 
LVL 12

Expert Comment

by:Md. Mojahid
ID: 39958424
Hope you dont have SAN certificate that why comping or may you got certificate with invalid name.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 

Author Comment

by:WAMSINC
ID: 39999839
ok so what happened is the previous IT manager had a ton of other "legacy" sites that were in use. For example the host name of the server was being used on the inside, and there was an OWA site on another mail server, etc. I got a cert to cover other sites but not those. So now people on the inside go to the host name instead of the public address and get the cert error. Im wondering if I can point DNS to the correct address instead of re-keying a cert ?
thanks
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40000253
You can point the DNS to the correct hosts if you like, but that will not deal with the SSL certificate issue if users are entering https://legacyhostname ...

To cover that you either need to include the additional names in your main certificate or get another certificate to cover those and put them on to another server that simply redirects to the right place.

Use the same host name inside and outside, configure Exchange in that way and encourage users to use the one URL.

You could also simply delete the other host names that are being used so that they don't go anywhere (presuming the server doesn't exist any longer).

Simon.
0
 

Author Comment

by:WAMSINC
ID: 40000519
the server exists and host the same site. If youre outside its
https://subdomain.domain.com
if youre inside its
https://servername
so when you go to servername you get the cert error. I was thinking you could DNS forward servername to https://subdomain.domain.com and dodge the alert

Just trying to avoid doing the cert nightmare again, because we have tomcat servers in addition to exchange
0
 
LVL 63

Accepted Solution

by:
Simon Butler (Sembee) earned 2000 total points
ID: 40001339
You are talking about a split DNS system.
That is easy to do, something I do as standard.

http://semb.ee/splitdns

You will need to change the internal URLs within Exchange to use the external host name as well. Then tell all users to use just the external URL everywhere.

http://semb.ee/hostnames2010

Simon.
0

Featured Post

Threat Trends for MSPs to Watch

See the findings.
Despite its humble beginnings, phishing has come a long way since those first crudely constructed emails. Today, phishing sites can appear and disappear in the length of a coffee break, and it takes more than a little know-how to keep your clients secure.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Check out the latest tech news, community articles, and expert highlights in August's newsletter.
What we learned in Webroot's webinar on multi-vector protection.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question