EXCHANGE2010 Management Console does not open the problem summary (there is a solution summary and a real case cases)

Here first summarizes some EXCHANGE2010EMC cannot open the error (the server name is replaced by a)

===EXCHANGE2010 Management Console Error Summary

Error 1: A fails to connect to remote server A and displays the following error message. Consult the logs and documentation for the WS-Management service that is running on the target (typically IIS or WinRM). If the target is a WinRM service, run the following command on the target to parse and configure the WinRM service: "WinRM quickconfig"

Error 2: The connection to the remote server failed with a message like this: The WinRM client was unable to process the request, and he was unable to determine the content type of the HTTP response from the target computer. Content type is missing or invalid

Error 3: A connection to the remote server failed with the message as follows: The Ws-management service could not process the request. A system load quota of 1000 requests per 2 seconds has been exceeded. Send future requests or increase system quotas at a slower rate. The next request from this user will be denied at least xx milliseconds

Error 4:powershell a remote connection to the server (this is an approximate explanation)

= = = Summary of solution methods

1. See if the WinRM IIS Extensions feature is installed, do not install it, cmd enter the WinRM quickconfig command configuration, and the diagram has a description of the WinRM IIS extension

650) this.width=650; "src=" Http://s2.51cto.com/wyfs02/M00/84/1D/wKioL1eF7N7RoZl_AAC_3gPo5RE770.png "title=" Installed role. png "alt=" Wkiol1ef7n7rozl_aac_3gpo5re770.png "/>

2. Error 4 can be used (get-user username). Remotepowershellenabled View the returned value if it is false, the PowerShell remote is not enabled, use Set-user username-remotepowershellenabled $ True (This applies to error 4, if not resolved, try other methods to resolve)

Run remove-powershellvirtualdirectory in 3.Powershell, and then run New-powershellvirtuallirectory

Enter Iisrest in 4.CMD or PowerShell

5. Finally check if ad time is synchronized with Exchange Server time (one PowerShell cannot remotely connect to the server)

= = = Real case Sharing--Problem description

The customer opened EXCHANGEEMC in the click on the image location when there was a strange error (forget to cut, only error map)

An error message appears when you click the arrow point

650) this.width=650; "src=" Http://s1.51cto.com/wyfs02/M02/84/1E/wKiom1eF8LzDhuuCAAIjOWkBRqM763.png "title=" Installed role. png "alt=" Wkiom1ef8lzdhuucaaijowkbrqm763.png "/>

I found that when I clicked a lot of options, there was an error

650) this.width=650; "src=" Http://s5.51cto.com/wyfs02/M01/84/1D/wKioL1eF8KfgXf14AAAXUxDNiI4966.png "title=" Exchange error message. png "alt=" Wkiol1ef8kfgxf14aaaxuxdnii4966.png "/>

= = = Problem Analysis

Error message: Remote connection to server: The WinRM client receives an HTTP Server Error state (500), but has no relationship to the remote service.

This error is obviously a winrm pot, to see if the WinRM IIS extension is installed properly (as I've summarized workaround one by one)

= = = Resolution method

After verification, it is true that the WinRM IIS Extensions feature is not installed, and the Exchange Management Console is refreshed after installation to have normal access

This article from "Sameold" blog, declined reprint!

EXCHANGE2010 Management Console does not open the problem summary (there is a solution summary and a real case cases)