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.local.
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'.
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.