Exchange 2013 Security Certificate

I am testing a new deployment of Exchange 2013.  I have a new domain name purchased, and licensed from godaddy, have already made all of the DNS forwarding changes and MX pointers.  I have email working on the server. Our domain is set as l*********p.net . This is our external, public domain.  Our internal, private domain is just set as *example.com.  This was setup before I ever even came on board years ago.

I have purchased a multi domain security certificate for our public domain, but this is where the issue comes into play.  When I enable that certificate, I can access our Exchange server from the web-portal both internally and externally just fine, everything works as it is supposed to, EXCEPT for Outlook. If I try and add the Exchange account to Outlook (2013) it gives error codes that the Security Certificate does not match, as it is looking at the local name of the Exchange Server itself (dc4.example.com).  The issue here is that I cannot purchase the *example.com domain as it is owned by someone else.  This has not been an issue in the past, since we never needed to have a public facing domain before.  Well, since we don't 'technically' own the rights to the public *example.com domain, I cannot get a third party certified certificate with that domain name in it. I can create a self-certified certificate through Exchange, that includes the domain, but then every web browser throws up security warnings every time you try to connect both internally and externally.

What is the best practice here to make both ends meet?
Brendon GaigeIT DirectorAsked:
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.

becraigCommented:
All you need to do here is to set autodiscover internaluri to match your external url.

Here is a really simple step by step on how to get this working (Step 7):
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
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
Brendon GaigeIT DirectorAuthor Commented:
Thank you, actually the step I was missing was step 6, in changing the Outlook Anywhere address, it was still pointed at the servers local domain name, instead of the public address (which I already have SNAMES for in our DNS).  Now it is working like a champ once I reset the certificates.  Thank you very much for that link!
0
Brendon GaigeIT DirectorAuthor Commented:
Actual suggestion was not where the issue was occurring, but provided link did involve the correction necessary to fix the issue.
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.