Wednesday, May 25, 2016

Exchange Management Shell and Proxy

HI folks,

Just wanted to share with you another adventure which I have recently had with Exchange 2016. When launching Exchange Management Shell (aka EMS) on the newly installed server. I have got the following error:

New-PSSession : [server01.contoso.com] Connecting to remote server server01.contoso.com failed with the following error message : The WinRM client sent a request to an HTTP server and got a response saying the requested
HTTP URL was not available. This is usually returned by a HTTP server that does not support the WS-Managementprotocol. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1

Internet is full of articles related to this particular error and I'm sure they are valid for a lot of scenarios. However, in my case it was due to misconfigured unauthenticated proxy which you use for CRL retrieving for Exchange certificates.

To make EMS working again all you need to do is to exclude FQDN suffix of your Exchange servers from being proxied. This can be achieved by using netsh utility. Below it the code sample:

netsh winhttp set proxy "proxy01.contoso.com:80" bypass-list="<local>;*.contoso.com;

Enjoy!