The Attempt To Connect To Powershell Using Kerberos Authentication Failed The WinRM Client Received

最新推荐文章于 2023-07-26 15:56:29 发布

转载最新推荐文章于 2023-07-26 15:56:29 发布 · 744 阅读

网络环境搭建专栏收录该内容

20 篇文章

订阅专栏

本文介绍了解决Exchange Server中使用Kerberos认证连接PowerShell出现的状态码500错误的方法。通过卸载并重新安装WinRM-IIS扩展，可以轻松解决此问题。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

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

Import-Module ServerManager

Then run this command te remove the service.

Remove-WindowsFeature WinRM-IIS-Ext

Then we need to reinstall WinRm. To do so run this command as seen below.

Add-WindowsFeature WinRM-IIS-Ext

Add-WindowsFeature WinRM-IIS-Ext

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.