Exchange 2010 certificate issue after CA no longer support internal names

Hi,

I have an Exchange 2010 environment where until yesterday was working fine but now the CA no longer supports internalname.local

I have re-issued the certificate which work fine externally for www.mail.domainname.com but local Outlook clients complaining that the mailservername.local isn't trusted which it isn't anymore

My AD is configured as domain.local and not companyname.com

Could do with this help resolving this. Any ideas?

Thanks
htsitguyAsked:
Who is Participating?

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

x
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.

Nadav SolomonCommented:
MASEE Solution Guide - Technical Dept HeadCommented:
Please post a screenshot of the error.
Please check this article as well
http://www.experts-exchange.com/articles/13676/Out-Of-office-not-working.html

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
jerseysamCommented:
There is a great tool here you can use to help you:

https://www.digicert.com/internal-domain-name-tool.htm
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Get Your eBook
ET SupportCommented:
Hi,

you can solve this by changing the OWA, ECP, EWS, outlookanywhere urls to a FQDN of your valid domain name ( mail.domainname.com) .
IvanSystem EngineerCommented:
Hi,

you should create new DNS zone on your internal DNS, make it domainname.com (public name).
In it then create CNAME that will point mail.domainname.com --> to you exchange
Change all services internal URL to match mail.domainname.com in stead of mail.domainname.local.

That means OWA, ECP, ActiveSync, EWS, etc...all of what people already wrote in post's before.
Server Configuration --> Client Access --> select and edit service

Regards,
htsitguyAuthor Commented:
Thanks for your comments, I had to create a sub domain I.e mail.companyname.com on my internal DNS and point to local Exchange servers as internally PC's couldn't ping the external autodiscover address.

Happy to share point regardless
MASEE Solution Guide - Technical Dept HeadCommented:
Thanks for sharing.
I explained the same in my article which is posted above.
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.