none
EMC and EMS 2010 failed connecting RRS feed

  • Question

  • EMC and EMS 2010 failed connecting with this error

    Connecting to remote server failed with the following error message : The WinRM client received an HTTP status code of 301 from the remote WS-Management service.

     

    Saturday, April 17, 2010 2:41 PM

Answers

All replies

  • Hi

    Without knowing anything about your environment..

    Can you check your Default Web Site so that HTTP and HTTPS ports are correct under bindings
    (port 80 and 443)

    Also give us some more details about your setup


    Jonas Andersson MCTS: Microsoft Exchange Server 2010, Configuration | MCITP: EMA | MCSE/MCSA Blog: http://www.testlabs.se/blog
    Saturday, April 17, 2010 2:48 PM
  • Kindly go through the following steps.

    1. make sure IIS WinRM extension is installed
    2. open powershell and run command : WinRM Quickconfig
    3. Open IIS 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

    The following link provide that this could issue with the permission

    http://exchangeserverpro.com/exchange-2010-management-console-initialization-failed

    http://www.exchange-powershell.com/2010/02/04/troubleshooting-exchange-2010-management-tools-startup-issues/


    With Best Regards Anbu
    Saturday, April 17, 2010 4:41 PM
  • Please check the redirection settings on the IIS, as the code 301 indicates a failure for the URL redirection

    Also, please see if there’s any related error event in the application log after reproduce the issue


    James Luo
    TechNet Subscriber Support (http://technet.microsoft.com/en-us/subscriptions/ms788697.aspx)
    If you have any feedback on our support, please contact tngfb@microsoft.com
    • Proposed as answer by Horsebox_irl Monday, June 28, 2010 1:02 PM
    Monday, April 19, 2010 3:52 AM
    Moderator
  • Hi,

    Any update? Have you try the options?


    With Best Regards Anbu
    Monday, April 19, 2010 6:37 PM
  • Does not work.

    5. run Remove-PowershellVirtualDirectory command
    says it's not a recognized cmdlet.

    Tuesday, March 31, 2015 7:46 PM