Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
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
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
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Take a look over here:
http://www.experts-exchang
Sounds like the same problem.
http://www.experts-exchang
Sounds like the same problem.
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
Please check this article as well
http://www.experts-exchange.com/articles/13676/Out-Of-office-not-working.html
There is a great tool here you can use to help you:
https://www.digicert.com/internal-domain-name-tool.htm
https://www.digicert.com/internal-domain-name-tool.htm
Hi,
you can solve this by changing the OWA, ECP, EWS, outlookanywhere urls to a FQDN of your valid domain name ( mail.domainname.com) .
you can solve this by changing the OWA, ECP, EWS, outlookanywhere urls to a FQDN of your valid domain name ( mail.domainname.com) .
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,
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,
Premium Content
You need an Expert Office subscription to comment.Start Free Trial