Exchange 2010 Self Sign Cert popping up and other issue

I recently migrated from Exchange 2003 to 2010 and am having a couple of strange issues.

1) I did (correctly) install a GoDaddy UCC SSL Cert but when any (internal) Outlook 2007 or 2010 clients connect, I get a Security Alert dialog box that says the name on the security certificate is invalid- and is a self-signed cert for my Exchange server. I did assign the correct services to my UCC public cert, and removed the self-signed cert from my Exchange server. How do I go about resolving this issue?

Additionally, my Outlook clients receive an error while attempting to download the OAB. I did move this over from the old Ex2003 server and when I noticed it still wasnt downloading, I recreated it and made sure to path to the new OAB on the Mailbox Store properties. How do I go about fixing this as well??
TrihimbulusAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
LLMorrissonConnect With a Mentor Commented:
Adding your local computer name to the UCC is a common way, but it is not necessary if you prefer not to. You just need an internally resolvable namepointing to your client acces server and need to change your internal service URLs to match this name, and to the names in your cert. So long as that all matches up, it will still work and you can leave the real internal server names out of the certificate.
0
 
LLMorrissonCommented:
Have you checked your internal service URLs are set correctly as per your cert etc? Check this article which discusses this issue.

http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/A_3704-Troubleshooting-Outlook-Certificate-Errors.html

0
 
LLMorrissonCommented:
With regards to the OAB error received by your clients, what is the actual error?

Have you checked the event log for any specific messages relating to the OAB?

0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
Glen KnightCommented:
doesn't sound like you completed the wizard for the Exchange Certificate with the correct names in it?
0
 
TrihimbulusAuthor Commented:
Yes Dematz - you are correct. For some reasone one of the domain names listed is www.mail.mycompany.com but I went through the certificate import directions to a T and didn't see this listed. By chance, did enableing this for all services (specifically IIS) add this to the cert? How do I fix this?
0
 
Glen KnightCommented:
It will add this automatically if there is a spare SAN/UCC in the 5 domain list.

Does the name you are seeing on the error message appear on the certificate?

You should have at a minimum the following names:

owa.domainname.com (the URL used for Outlook Web Access)
autodiscover.domainname.com (where domainname.com is the part after the @ in your email address)
servername.domainname.local (the internal fully qualified domain name of your server)
0
 
TrihimbulusAuthor Commented:
Ok - so I should have added the internal name of my Exchange Server when setting up the UCC Cert with godaddy? Isn't that bad to let the world know what that name is? Also, we hit OWA via mail.mycompany.com.
0
 
Glen KnightCommented:
You mind if I ask what was in that last solution that i hadn't already offered?
0
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.