Exchange 2010 Management Console Winrm Error
Contents |
Exchange TeamFebruary 4, 201014 0 0 0 EDIT 12/7/2010: For additional help resolving those issues, please see our newer blog post Resolving WinRM errors exchange 2010 management console initialization failed winrm cannot process the request and Exchange 2010 Management tools startup failures. In this blog post,
Kerberos Authentication Failed Exchange 2010 Management Console
we will be highlighting some of the most common errors that may be seen when attempting to open
Exchange 2010 Management Console Initialization Failed System Load Quota
the Exchange Management tools (Exchange Management Console and Exchange Management Shell). To start off, you first need to be aware that in Exchange 2010, all management is done via
Exchange 2010 Management Console Initialization Failed Access Denied
Remote PowerShell, even when opening the Management Tools on an Exchange server. Where this differs from Exchange 2007 is that there is now a much larger dependency on IIS, as Remote PowerShell requests are sent via the HTTP protocol and use IIS as the mechanism for connections. IIS works with the WinRM (Windows Remote Management) service, and the exchange 2010 management console initialization failed using kerberos authentication failed WSMan (Web Services for Management) protocol to initiate the connection. When you click on the Exchange Management Shell shortcut, a Remote PowerShell session is opened. Instead of simply loading the Exchange snap-in (as we did with Exchange 2007), PowerShell connects using IIS to the closest Exchange 2010 server via WinRM. WinRM then performs authentication checks, creates the remote session and presents to you the cmdlets that you have access to via RBAC (Role Based Access Control). Since all Remote PowerShell connections go through IIS, we have identified some of the most common errors that may be exhibited when attempting to open the Exchange Management tools along with the most common causes of those errors and how to address these issues. We have attempted to list these in order of frequency. Issue: Connecting to remote server failed with the following error message: The WinRM client cannot process the request. It cannot determine the content type of the HTTP response from the destination computer. The content type is absent or invalid. For more informat
360 games PC games exchange 2010 management console initialization failed change occurred in the remote forest Windows games Windows phone games Entertainment All Entertainment exchange 2010 management console slow Movies & TV Music Business & Education Business Students & educators exchange 2010 management console initialization failed w3svc Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet https://blogs.technet.microsoft.com/exchange/2010/02/04/troubleshooting-exchange-2010-management-tools-startup-issues/ Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Lumia All https://support.microsoft.com/en-us/kb/2027064 Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
(500) 23 Replies One quite common error I faced during the Exchange 2010 era is the WinRM HTTP Error: http://www.aurelp.com/2013/01/19/solved-exchange-2010-connecting-to-remote-server-failied-with-the-following-error-message-the-winrm-client-received-an-http-server-error-status-500/ If i use the management tools GUI i get an error message saying: “Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500), but the remove service did not include any other informaition about the cause of the failure. For more information, see the about_Remote_Troubleshooting exchange 2010 Help topic. It was running the command ‘Discover-ExchangeServer -UseWIA $true -SuppressError $true’.” Using the Exchange Management Shell is get a similar error: “Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500), but the remove service did not include any other informaition about the cause exchange 2010 management of the failure. For more information, see the about_Remote_Troubleshooting Help topic. + CategoryInfo : OpenError: (System.Manageme….RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException + FullyQualifiedErrorId: PSSessionOpenFailed” FIRST THING YOU MUST DO: DO NOT PANIC ! DO NOT REBOOT THE SERVER !!! I WILL EXPLAIN HOW TO SOLVE THIS IN A FEW EASY STEPS: 1. When you open the EMC ( Exchange Management Console ), you will get an error similar to this: 2. Go to START / Administrative Tools / Server Manager / Features / Add Features / And check WinRM IIS Extensions / NEXT / NEXT / CLOSE: !!! IF YOU ALREADY HAVE THIS ROLE INSTALLED, JUST REINSTALL IT ! 3. Close / Reopen EMC and it will work like a charm ( NO REBOOT REQUIRED ): ENJOY. And if you encounter any problems feel free to comment / contact me. This entry was posted in Exchange Server HowTo and tagged Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500), do not panic Connecting to remote server failied with the following error message: The WinRM client received an HTTP server error status (500), exchange server 2010 Connecting to