asked on Exchange 2010 Cert error
Hi all,
I am looking to see if someone can link me to a workaround for issuing a new cert that includes SAN to resolve my issues on a network I inherited.
Currently - I just resolved the Free/Busy, OOF issues internally by adjusting all my internal URL's. I have a single issue cert. that includes only webmail.domain.ca. It has no SAN.
I know the proper resolution is to issue a multi-cert (can't recall the actual name for that right now) that includes autodiscover.domain.ca and localservername.domain.loc
Is there a workaround to Exchange 2010 that can let me prevent the Outlook pop up with security alert "servername.domain.local" and 'The name on the security certificate is invalid or does not match the name of the site'.
Thanks!
I am looking to see if someone can link me to a workaround for issuing a new cert that includes SAN to resolve my issues on a network I inherited.
Currently - I just resolved the Free/Busy, OOF issues internally by adjusting all my internal URL's. I have a single issue cert. that includes only webmail.domain.ca. It has no SAN.
I know the proper resolution is to issue a multi-cert (can't recall the actual name for that right now) that includes autodiscover.domain.ca and localservername.domain.loc
Is there a workaround to Exchange 2010 that can let me prevent the Outlook pop up with security alert "servername.domain.local" and 'The name on the security certificate is invalid or does not match the name of the site'.
Thanks!
OutlookWindows Server 2008Exchange
Last Comment
Seth Simmons
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Looks like a reasonable solution sembee, I'll hammer that out after hours today and see what happens.
Thanks!
Thanks!
Agreed, the urls mentioned in the article I sent above must be reachable internally and proper DNS configuration will enable that..
ASKER
Simon,
I just flipped all the records for internal URL's back to webmail, and configured the internal DNS server ( hosted on another virtual server internally ) as suggested. I am essentially back at square one. I have an SRV record, and the new zone for webmail.domain.ca pointing to my internal IP for the Exchange server. Doesn't fly. No OOF, no Free/Busy.
I just flipped all the records for internal URL's back to webmail, and configured the internal DNS server ( hosted on another virtual server internally ) as suggested. I am essentially back at square one. I have an SRV record, and the new zone for webmail.domain.ca pointing to my internal IP for the Exchange server. Doesn't fly. No OOF, no Free/Busy.
ASKER
Tentatively, I appear to have resolved it through catching a typo, and making some other network changes. More testing and an update on the matter tomorrow.
As far as my message about DNS testing not working, it could be related to a record I am unable to clear linking to the previous and dead DNS server.
As far as my message about DNS testing not working, it could be related to a record I am unable to clear linking to the previous and dead DNS server.
I've requested that this question be closed as follows:
Accepted answer: 500 points for Simon Butler (Sembee)'s comment #a39669759
for the following reason:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
Accepted answer: 500 points for Simon Butler (Sembee)'s comment #a39669759
for the following reason:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
However, it was set to the webmail.domain.ca previously, and would not resolve/time out looking for it hence my change to the internally resolve-able FQDN.
I am looking over your article now. I can always hit the URL externally on all /ews /autodiscover /owa etc., but internally was the issue and my 'forced hand' at changing all the URL's to reflect FQDN to make sure that my users could hit the OOF buttons and so on to make it work.