Exchange 2010/Outlook 2007 certificate error mismatch

I have just converted from Exchange 2003 to Exchange 2010. I installed a UCC SSL certificate from go daddy on my exchange 2010 server. The Outlook 2007 clients started getting a certificate mismatch warning because the built in certificate that the Outlook clients were pointing to was the internal name of the server (blgexchserv1.blg.local).
I did some research and came accross this post:
http://exchangeserverpro.com/outlook-2007-clients-display-certificate-mismatch-error-after-mailbox-migration/
I attempted to  change the URL of the Autodiscover services within Exchange 2010. I completed the first entry, but the outlook clients are still getting the certificate error. I did not think I needed to modify the web services url at all. I tested OWA internally and it is resolving fine. What am i doing wrong? what else do I need to do to get rid of the error.
williamstechnologygroupAsked:
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.

MAS (MVE)EE Solution GuideCommented:
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
williamstechnologygroupAuthor Commented:
the auto discover internal is set correctly.... I know that IIS is using the Godaddy cert because active sync and OWA are both working correctly with no certificate errors. I am not sure why the clients are persisting in looking for the internal cert with the .local name....
0
williamstechnologygroupAuthor Commented:
the OAB default website for internal is pointing to the .local name of the server, but would that generate the certificate error in outlook?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Zacharia KurianAdministrator- Data Center & NetworkCommented:
The certificate mismatch occurs because the Autodiscover Service and/or Availability Service use the FQDN of the Exchange 2010 host in their URL (eg https://your server.domain.local/AutoDiscover/AutoDiscover.xml) but the IIS instance has an SSL certificate that does not match that name.

So just follow the links Posted by the expert MAS.
0
SreRajCommented:
Hi,

You could add internal FQDN name of the CAS server as a Subject Alternate Name in UCC. This helps to get rid of certificate warnings internally.

https://www.digicert.com/ssl-support/exchange-2010-san-names.htm

Also, it is good to add EWS URL, because of OOF uses web services. You could run 'Test E-mail Configuration' from a connected machine. This will list all the URLs used by Outlook both thru RPC and using HTTP. You could verify that all these URL names are added as SANs in the UCC.

http://premnair.wordpress.com/2010/07/03/configure-ews-autodiscover-owa-oab-ecp-on-exchange-server-2010/
0
MAS (MVE)EE Solution GuideCommented:
@SreRaj
You wont be able to add internal FQDN in your certificate in the near future.
Almost all CAs stopped adding internal FQDN to the certificate.

And it is not a good practice to add internal FQDN in your exchange certificate.
0
Zacharia KurianAdministrator- Data Center & NetworkCommented:
You wont be able to add internal FQDN in your certificate in the near future.
Almost all CAs stopped adding internal FQDN to the certificate.

And it is not a good practice to add internal FQDN in your exchange certificate.

very true MAS. Adding the internal name to SSL was just tweak but then all started to realize the security issues related to it and I think many SSL providers do not do so now, rather they do issue wild card SSL.
0
williamstechnologygroupAuthor Commented:
Yes, the internal names on a san cert are going away. Godaddy made that clear. I ended up calling Microsoft after I had exhausted all other possibilities. I had performed the correct scripts, but the outlook clients were not responding. THanks to MAS for the tip on the Outlook Test email auto configuration. will reward points based on relativity.... thanks...
0
williamstechnologygroupAuthor Commented:
Contact Microsoft for final resolution
0
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.

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.