Winrm http status code 403 from the remote ws-management exchange 2010 EMC won't load

Posted on 2010-01-01
Last Modified: 2012-05-08
after following after running exchange 2010 prerequsites at

[] Connecting to remote server failed with the following err
or message : The WinRM client received an HTTP status code of 403 from the remo
te WS-Management service. For more information, see the about_Remote_Troublesho
oting Help topic.
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:Re
   moteRunspace) [], PSRemotingTransportException
    + FullyQualifiedErrorId : PSSessionOpenFailed

found no way of reinstalling winrm.
followed  tring to fix the problem and that didn't help.
the server was rebooted and no anti-virus program is running.

Question by:Giladn
    LVL 74

    Expert Comment

    by:Glen Knight
    Check in IIS under Default Website check the authentication settigs of the PowerShell virtual directory and the SSL settings what are they set to?
    LVL 11

    Author Comment

    I will try reinstalling powershell to restore directory, I did reinstall IIS7 today..
    LVL 74

    Expert Comment

    by:Glen Knight
    There should be a PowerShell virtual director.

    Remove and re-install PowerShell.

    Sorry didn't realise it was you Giladn.
    LVL 11

    Author Comment

    It's ok , others desereve a clean thread about this error, mine is hard to follow.
    I re-installed windows powershell integrated scripting env (ISE) from features, I also installed WinRM IIS Extension feature.
    I still can't see powershell directory in IIS..
    LVL 31

    Expert Comment

    Have a look at the IIS log file, and see if you can find the request that resulted in the 403 response.  You will see the number 403 near the end of the relevant line.  Note the times in the log files are in GMT.
    LVL 11

    Accepted Solution

    this thread has become a snowball - read also for full story.

    finally solved, I was NOT unable to re-install exchange 2010 management tools because I had no option to uninstall - old public folders needed to be removed and I had no powershell directory to administer exchange in order to make changes . so I was literally stuck, I had to force shutdown and preper a new server, use ntdsutil to to transfer fsmo roles to the new server - clean AD metadata and remove the server from shema, performed a new E2003 installation with NOT with the same organization name (depands if your forest is in good condition you will not need it nor the following steps)
    as my old 2003 server  , then I used and made necessary changes in user's "exchange general"  tab in AD domain to all users and made restore from tape (very problematic if you restore to a server with a different name,  try- B2D and then DUPLICATE backup job and you will have database)
    mounted databases and bingo. everything is working even better then before.
    for every step in this long story I had a very good reason, don't do if your not sure what it means.
    those steps took me 4 days (FULL days)
    thanks to very good tools mentioned above I saved allot of time.
    for those who did not manage to uninstall exchange as a result of the error above  and are frozen in a non functioning production exchange organization please read carefully and do research . again read carefully and do allot of research.
    LVL 8

    Expert Comment

    I had the same issue, but after reading dematzer's first reply above, I checked the SSL settings and found that SSL had been enabled on the PowerShell virtual directory.  Removing this fixed the issue for me.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    What Should I Do With This Threat Intelligence?

    Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

    Create high volume marketing opportunities using email signatures with these top 10 DOs and DON'Ts of email signature marketing.
    Resolve Outlook connectivity issues after moving mailbox to new Exchange 2016 server
    In this video we show how to create a User Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Mailb…
    In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…

    758 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    8 Experts available now in Live!

    Get 1:1 Help Now