After upgrading a Server 2008 server recently that was running Exchange 2010 I came across this error.
The Attempt To Connect To Powershell Using Kerberos Authentication Failed The WinRM Client Received An Http Server Error Status (500)
There are a few variations of the message also namely this one below.
The attempt to connect to http://server.domainname.com/powershell using “kerberos” authentication failed:Connecting to remote server failed with the following message:The WinRm client cannot process the request.It cannot determine the content type pf the HTTP response from the destination computer. The content type is absent or invalid.
The Attempt To Connect To Powershell Using Kerberos Authentication Failed The WinRM Client Received And Http Server Error Status (500)
This is down to the WinRM client becoming corrupt. This is an easy fix to do via the exchange powershell console. do the following.
We first need to enable to server manager plug in. To do so run this command
Then run this command te remove the service.
Then we need to reinstall WinRm. To do so run this command as seen below.
You will now find that you can launch the Exchange Management console without any issues, View to video below for a full step by step guide on fixing the “The Attempt To Connect To Powershell Using Kerberos Authentication Failed The WinRM Client Received And Http Server Error Status (500) ” issue.
A solutionto to a problem where pcs` cannot log into a domain after updates to server 2008r2. This is a problem with the windows firewall.PC`s cannot see server 2008 r2 server or see a server 2008 r2 domain controller.
When installing the exchange 2013 preview you see this error “Unhandled Exception: System.TypeLoadException: Could not load type ‘System.Security.Claims.ClaimsPrincipal’ from assembl
y” here is how to fix