if you are getting this error on Exchange 2013 CAS below is the fix. I have no idea what went wrong but both my CAS servers (lab environment stopped working). I was lucky enough to find the similar post for Exchange 2010 and soon after

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.

WinRM1

 

FIX

SERVER MANAGER—–Features——Add Features——-WinRM IIS Extension —- you are done!

 

 

One thought on “Exchange 2013-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.

  1. Look, here’s another solution.

    Open a Powershell session as Admin

    Run this command:

    POWERSHELL>$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://YOURSERVER/PowerShell/ -Authentication Kerberos -Credential $UserCredential

    POWERSHELL>Import-PSSession $Session

    POWERSHELL>Add-PSSnapin microsoft.exchange.management.powershell.snapin

    And Voila!

    Than will let you work as Exchange Management Shell, same commands.

    Good luck

    EDIT: If you are working logged in your exchange server, just type the last command on powershell:

    Add-PSSnapin microsoft.exchange.management.powershell.snapin

    Source: https://social.technet.microsoft.com/Forums/lync/en-US/aa3c936f-bec1-4e24-b38f-81685df718c7/exchange-management-shell-fails-to-connect-to-exchange-server-2013?forum=exchangesvradmin

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s