I know this question has been asked a ton of times, but I haven't found any instance of this question asked for exchange 2013. Yes, I've seen Exchange 2010, Exchange 2007, but not Exchange 2013. The symptoms are all similar. Here is a description:
1 Exchange 2013 server, all roles installed.
External domain name: associates.com
Internal AD domain name: associates.local
Client installed a third party SSL certificate, but did not purchase a SAN or UC certificate, so there is one namespace on the SSL cert, and that represents the external OWA name: mail.associates.com
Now, when internal OUtlook 2010 clients start, they get the "The name of the security certificate is invalid or does not match the name of the site."
I'm just wondering if http://support.microsoft.com/kb/940726 still applies to Exchange 2013 to fix this issue. Does this article apply to Exchange 2013? If so, I will follow the above article. If not, please direct me to any articles for Exchange 2013 that addresses this.
the autodiscoverserviceuri points to: https://netbiosnameofmailserver.associates.local/Autodiscover/Autodiscover.xml