Reassigned/Reissued SSL now getting error in Outlook

Hello,

I had to reassign/reissue the SSL in Exchange 2010.  Now Outlook is getting the error:

Information you exchange with this site cannot be viewed or changed by others.  However, there is a problem with the site's security certificate.

The security certificate is from a trusted certifying authority.

The security certificate date is valid.

The name on the security certificate is invalid or does not match the name of this site.

I have done view certificate and install, but it keeps popping up when I re-open Outlook.

Any advice is greatly appreciated.

Have a great day,

Don
GEMCCAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

George KhairallahCTOCommented:
I had an issue similar to this a couple days ago... and I initially looked through this article (https://social.technet.microsoft.com/wiki/contents/articles/13916.how-to-use-a-self-signed-certificate-in-exchange-2010.aspx) to figure out the solution.  (granted this was through a Self-Signed CA)....)

And in doing this and following the exact instructions in the article, I got the exact message you were getting.

I'm not sure if you create the CSR from the Exchange interface or from the Certificates MMC, but for Exchange, you will need: Digital Signature, Key Encipherment, and Server Authentication, and it needs to be 2048 bit and an Exchange Key (as opposed to Signature)  -- Here's a screencast that shows how to create the CSR correctly:  http://www.netometer.com/video/misc/SAN-request/ (not needed if you're using the Exchange console to create it though .. but is good for reference anyway)

When you download the cert, try to download it as a WebCertificate, and DER encoded instead of Base 64. (the article above states Base 64, but what worked for me was getting the DER Encoded. Give that a shot and see if it works for you.
GEMCCAuthor Commented:
Hi and thanks for your response,

I received the cert from GoDaddy using a CSR.  This issue is only occurring on systems that has been using Outlook/Exchange prior to the reassign/reissue.  If I make a new connection from a new PC, I do not get the error.

Please advise.

Have a great day,

Don
SreRajCommented:
Hi,

This error could occur if the host name used for connections is not added as a Subject Alternate Name in the certificate. For example, if you organization is using the host name webmail.companyname.com for accessing Outlook Web App and this name is not added to the certificate as a SAN then this error can get triggered. Please check if there has been any changes of host names used for connection and if it is not updated in the certificate.

Please refer the following articles for more information.

http://autodiscover.wordpress.com/2010/07/03/exchange-server-what-are-the-names-required-for-my-certificate/

http://exchangeserverpro.com/configure-an-ssl-certificate-for-exchange-server-2010/
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

Simon Butler (Sembee)ConsultantCommented:
Pretty standard error.
You probably don't have one of the URLs in the certificate that Exchange wants to use. If it is coming up immediately then it is probably the Autodiscover URL.

get-clientaccessserver | select identity, autodiscoverserviceinternaluri

If your previous SSL certificate had the server's real name on it, then it has probably been removed by the SSL provider because they are no longer allowed. That can cause you problems.

You will need to setup a split DNS and then use the external name internally.

http://semb.ee/hostnames

Simon.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
GEMCCAuthor Commented:
The issue is that when I reissued the SSL, I did not include .local SANS because GoDaddy says they are not longer supported.
GEMCCAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for GEMCC's comment #a39837920

for the following reason:

Issue resolved
Simon Butler (Sembee)ConsultantCommented:
I am objecting to the question being closed in the manner requested.

In my last post I stated:

"If your previous SSL certificate had the server's real name on it, then it has probably been removed by the SSL provider because they are no longer allowed."

That is the reason that is being asked for the question to be closed.
GEMCCAuthor Commented:
Because he wants the points.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.