I recently upgraded to Exchange 2010 on my home network. Everything went well, but when I started the Exchange Management Console for the first time I got this error when trying to open the Server ConfigurationClient Access node:
—————————
Microsoft Exchange
—————————
Connecting to remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
—————————
OK
—————————
After looking at the various settings for WinRM, firewall etc, I noticed that the WinRM IIS Extension was missing from my features list. I added it through Server Manager:
Microsoft Exchange
—————————
Connecting to remote server failed with the following error message : The WinRM client received an HTTP server error status (500), but the remote service did not include any other information about the cause of the failure. For more information, see the about_Remote_Troubleshooting Help topic.
—————————
OK
—————————
After looking at the various settings for WinRM, firewall etc, I noticed that the WinRM IIS Extension was missing from my features list. I added it through Server Manager:
I could have used ServerManagerCMD.exe as well, but it has been depricated. The command would be:
servermanagercmd.exe -install WinRM-IIS-Ext
Or the PowerShell Server Manager cmdlets:
Import-Module ServerManager
Add-WindowsFeature WinRM-IIS-Ext
After the feature had been installed the error disappeared and Exchange Management Console worked without incident.
I had originally followed the steps outlined in this article on TechNet to install the prerequisites for Exchange on Windows Server 2008 R2, but those instructions do not mention the WinRM IIS Extension.
Thank you very much for your post. It was very useful for us …
Congratulations
Awesome! Thank you so much!
I had Exchange 2010 installed on Server 2008 R2 STANDARD. I upgraded to Server 2008 R2 ENTERPRISE . Both the EMC and EMS stopped working. Ran the command for Powershell and everything worked!
Thanks a million!
Thank You! —– Just stumbled across your post… It fixed my issue.
Thank you! Fixed my issue aswell.
Thanx ….. After searching a lot found this post.EMC started as soon as the feature was installed.