The WinRM client received an HTTP status code of 403 from the remote WS-Management service. (remote management)

_{Monday, November 18, 2013 11:15 AM}

Hi Experts,

I hope you could me me to solve issue with remote administration of new Exchange 2010 environment. Environment is based on 2008 R2 Servers, and having 3 CAS servers (STD version). In all 3 CAS servers there are separate virtual directories for internal and external OWA users. PowerShell virtual directory is only in internal (Default Web Site)

When I am trying to run EMC or EMS remotely, I got 50% of tryings the message:

"VERBOSE: Connecting to <server name>  Connecting to remote server failed with the following error message : The WinRM client received an HTTP status code of 403 from the remote WS-Management service. For more information, see the about_Remote_Troubleshooting Help topic. "

When running EMC or EMS on Exchange servers, there are no problems.

The only solution for this i have found is the SSL ebnabled for powershell directory in IIS, which I have disabled (http://support.microsoft.com/kb/2276957/fi). I have also recreated the powershell virtual directories with no luck.

Any clues, what to try next?

_{Tuesday, November 19, 2013 6:14 AM ✅Answered | 3 votes}

Hi,

First, please make sure all the prerequisites are installed and check if you specify the right virtual directory when connecting to a remote Exchange 2010 server.

Exchange 2010 Prerequisites
http://technet.microsoft.com/en-in/library/bb691354(v=exchg.141).aspx

Troubleshooting the Exchange Management Shell
http://technet.microsoft.com/en-in/library/dd351136(en-us).aspx

Besides, could you please follow the steps below to check the result?

1. Make sure IIS WinRM extension is installed.
2. Open powershell and run command : WinRM Quickconfig.
3. Open IIS and then go to Powershell virtual directory and check that SSL in disabled and authentification is set only to Anonymous.
4. Open Windows powershell modules.
5. Run Remove-PowershellVirtualDirectory command.
6. Run New-PowershellVirtuallirectory command.
7. IISRESET /noforce.

If the issue persists, I recommend you use the Exchange Management Troubleshooter (or EMTshooter for short) to narrow down the issue.

Related information:

Resolving WinRM errors and Exchange 2010 Management tools startup failures
http://blogs.technet.com/b/exchange/archive/2010/12/07/3411644.aspx

Best regards,
Belinda

Belinda Ma
TechNet Community Support

_{Monday, November 18, 2013 8:19 PM | 1 vote}

You have posted in an Exchange 2013 forum.  The Exchange previous versions forums are here:  http://social.technet.microsoft.com/Forums/en-US/category/exchangeserverlegacy

Have you configured HTTP redirect in IIS?  That can break all sorts of things.

Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

_{Thursday, August 11, 2016 1:13 PM}

Hi, wanted to let you know I experienced these same symptoms for about a year and tried everything I could find online, nothing would fix it.

Finally I poked around in the IIS settings and discovered that after I installed and turned on "Dynamic IP Restrictions", on IIS on my Exchange server, it was dynamically blocking the local client "::1".

I added the local address ::1 to the "Allowed addresses" and that fixed the issue.