SBS 2003 R2 RWW OWA SSL Certificate Problem

If I install legitimate certificates from Comodo or Equifax or even a self-signed certificate using the Configure Email and Internet Connection Wizard ( CEICW ) the error exists. It trusts nothing! I have been issued two different basic FREE certificates from InstantSSL and RapidSSL & neither of them or the self-signed one are trusted by the server.
dsascAsked:
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.

dfxdeimosCommented:
Look in the Trusted Root Certification Authorities store on your server. That list is all the Certification Authorities that your server will trust. Do you see the companies that issued you those certificates in the list?
0
dsascAuthor Commented:
Yes.
0
dfxdeimosCommented:
Did you get a individual certificate or a certificate chain (p7b) file from the issuer?
0
dsascAuthor Commented:
How about we keep this really simple. Limit conversation to the self-signed certificate. In this case, the Small Business Server is the Certification Authority and it creates a self-signed certificate that is trusted by itself.

When the Small Business Server creates a self-signed certificate, you can access the site locally (on the server) using; https://SERVERNAME/SITENAME and the certificate is indeed trusted. When viewed, the Certification Path shows servername.domain.com as the root path and the Certificate status section shows "This certificate is ok"

In the problem environment, when the Small Business Server creates a self-signed certificate, you can access the site locally (on the server) using; https://SERVERNAME/SITENAME and the certificate is not trusted. When viewed, the Certification Path shows servername.domain.com as the root path and the Certificate status section shows "This CA Root certificate is not trusted because it is not in the Trusted Root Certification Authorities store."

The statement in the Certificate status section is false.
0
dsascAuthor Commented:
Eventually... after several days and countless support hours they "allowed" escalation to someone who repaired and validated the repair in 3 minutes. OMG! Microsoft support fixed this one by running certutil.exe -repairstore with specifics related to the certificate.
0

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
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
SSL / HTTPS

From novice to tech pro — start learning today.

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.