Exchange 2013, FQDN for UCC SSL

I have a Exchange 2013 coexisting with exchange 2010, I purchased a UCC SSl cert from Godaddy. to find out you will not be able to use .local on the cert. If I do the cert will expire in November, Wasting 2 years and three months of a valid cert.
I was told there is a workaround for exchange 2013, But can not find one specifically for exchange 2013 running on windows 2012. anyone?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

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.

Cliff GaliherCommented:
Not a workaround. A fully supported scenario. Exchange has powershell commands to change the various URLs that exchange uses and has had since exchange 2007. Simply change the URLs for EWS, OA, autodiscover, etc. The specifics depend on your topology choices, but there is plenty of documentation out there.

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

From novice to tech pro — start learning today.