In Exchange 2016, you may have come across WinRM errors, today we had a strange one, error 403. This error showed up on the Exchange Management Shell (EMS) as you can see below:

Exchange 2016:- the winrm client received an http status code of 403 from the remote ws-management service.
Exchange 2016:- The WinRM client received an HTTP status code of 403 from the remote WS-Management service. 1

First thing to check is the proxy settings on the server. If you head to IE and check the settings, it should show no proxy. If you go and launch PowerShell (elevated), you can run the following command to verify the proxy:

  • netsh winhttp show proxy

To remove the proxy defined, you can run the following command:

  • netsh winhttp reset proxy
Exchange 2016:- the winrm client received an http status code of 403 from the remote ws-management service.
Exchange 2016:- The WinRM client received an HTTP status code of 403 from the remote WS-Management service. 2

We did an IISReset and when you re-launch the Exchange Management Shell (EMS) it should start without an error:

Exchange 2016:- the winrm client received an http status code of 403 from the remote ws-management service.
Exchange 2016:- The WinRM client received an HTTP status code of 403 from the remote WS-Management service. 3

Hope it helps.

    wpChatIcon

    Discover more from COLLABORATION PRO

    Subscribe now to keep reading and get access to the full archive.

    Continue reading