OK, I have installed on a clean server, a fresh, clean installation of Exchange 2013 (CU8).
The local network is running on a .local
As I've done many times before, once I've done the initial setup of Exchange, there are the powershell commands that I execute to rename the virtual directories.
Set-ClientAccessServer -Identity "DWEX" -AutodiscoverServiceInternalUri "https://owa.domain.com/Autodiscover/Autodiscover.xml"
Set-OABVirtualDirectory -Identity "DWEX\OAB (Default Web Site)" -InternalUrl "https://owa.domain.com/OAB"
Set-WebServicesVirtualDirectory -Identity "DWEX\EWS (Default Web Site)" -InternalUrl "https://owa.domain.com/EWS/Exchange.asmx"
Set-ActiveSyncVirtualDirectory -Identity "DWEX\Microsoft-Server-ActiveSync (Default Web Site)" -InternalUrl "https://owa.domain.com/Microsoft-Server-ActiveSync"
Set-OWAVirtualDirectory -Identity "DWEX\owa (Default Web Site)" -InternalUrl "https://owa.domain.com/owa"
Set-ECPVirtualDirectory -Identity "DWEX\ecp (Default Web Site)" -InternalUrl "https://owa.domain.com/ecp"
These all executed successfully
I've obtained a certificate from a 3rd party and the SAN names featured are owa.domain.com, autodiscover.domain.com etc
OWA both internally and externally works fine (no certificate errors).
Outlook 2013 clients do autodiscover as expected, but the Outlook gives a certificate error when we start Outlook every time.
"There is a problem with the proxy server's security certificate. The name on the security certificate is invalid or does not match the name of the target site dwex.dw.local. Outlook is unable to connect to the proxy server (Error Code 10)".
dwex.dw.local is the Exchange server name.
Clicking OK clears the error and Outlook continues to work fine.
I've done this setup a number of times but never encountered this error.
Running "get" commands on the virtual directories all return the expected directory name (ie https://owa.domain.com... etc)
When clients ping owa.domain.com, it returns the correct LAN IP address.
Thanks in advance!