My ManageEngine Exchange Reporter application uses the 'Test-WebServicesConnectiv
ity' command to test my Exchange 2013 server for Client Connectivity Status.. They use the command noted here: https://technet.microsoft.com/en-us/library/aa998328(v=exchg.160).aspx
. The problem is that it's using the internal / local host name instead of the public DNS host name I have noted in the cert.. This results in TLS / SSL issues.. So.. Not only is Exchange 2013 expecting my external host name but the cert bound to it is also using the external host name. When using the command with external host name is works.. But... By default the 'Test-WebServicesConnectiv
ity' command used the internal name. How can I fix this?