Hello,
This has been on several threads and appears to be a common occurrence, however, I'd like some input on this version, if I may:
Exchange 2010 server (Internal hostname: mail.comp.local) and (External:webmail.comp.com)
All email works fine, on the inside Outlook clients, webmail, external mail flows well. The hiccups is with the publicly provided SSL cert that was created with a wildcard for*.comp.com (outside OWA access). This cert is served to all Outlook clients. When setting up a new Outlook client, the Exchange server points tomail.comp.local, yet the SSL cert has *.comp.com, throwing popups of server mismatch. I've changed URL/URI mappings in the shell (per, http://support.microsoft.com/kb/940726?wa=wsignin1.0) and the matter persists.
Do we need to get a new certificate for *.comp.local to remove the popups and create a trust without warnings? Been trying many different variations for a week, and still persists; the more we change with configs, the more other issues start occurring, i.e., Free/Busy errors, Out of Office not working, etc.
Please shed some light on this.
Thank you.
NSI, IT.