Exchange 2013 Cert warning when connecting to CAS server

I am currently migrating from exchange 2010 to 2013 I have all the servers set up 2 mailbox and 2 CAS along with my 2010 2 mailbox and 2 CAS.  There is a load balancer in-front of the 2013 server but when I switch the autodiscover DNS entry to the load balancer when a user opens outlook I am getting a cert warning the server is coming up servername.domain.local instead of which is the certs primary domain.  All the 2013 virtual directories as well as the load balancer is in the form what am I missing I understood you didnt need to and shouldnt have the local servers name on the SSL cert.  Any Ideas?

Also the only thing I can find different all the 2013 components OWA, OAB, ECP etc point to but the autodiscover  there seems to be two for the 2010 server and for the 2013.  I have been changing the to point to the load balancer which outlook then throws the error.  It the below correct?EX2013
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.

timgreen7077Exchange EngineerCommented:
I believe you may have to also add the cert to the load balancer if you haven't done so already.
Kissel-BAuthor Commented:
I have added the cert to the load balancer
timgreen7077Exchange EngineerCommented:
are the certs also added to your 2013 exchange servers and services assigned
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.

Kissel-BAuthor Commented:
Yes but they do not include local server name just, autodiscover, mx etc
Kissel-BAuthor Commented:
IS this correct?EXCASAuto
timgreen7077Exchange EngineerCommented:
yes that is fine, but I would have made the autodiscover SCP match the 2010 also, but it really doesnt matter. you should have your internal DNS pointing to the new autodiscover record and that record should be pointing to the virtual IP of your load balancer.
Kissel-BAuthor Commented:
I was just pointing to the IP of the load balancer did I miss a step?
timgreen7077Exchange EngineerCommented:
you need to point the autodiscover record for your 2013 servers to the load balancer, not the 2010 autodiscover.

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
Kissel-BAuthor Commented:
After pointing autodiscover to error went away
timgreen7077Exchange EngineerCommented:
Great happy it worked.
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

From novice to tech pro — start learning today.