PowerShell Remoting Error When Trying to use Invoke-Command Against a Domain Controller

I wrote a blog article last year titled “Welcome to PowerShell Hell” where the Antivirus I was using on my workstation had caused issues when trying to connect to remote machines with PowerShell. I recently reloaded my workstation with Windows 8.1 and reloaded the Antivirus which is now at version 7 (Eset NOD32). Remote connectivity via PowerShell worked without issue and without having to change any settings except when trying to use the Invoke-Command cmdlet against domain controllers which I find to be very strange.

Here’s the error that was received when attempting to use the PowerShell remoting Invoke-Command cmdlet against a domain controller:

[dc01] Connecting to remote server dc01 failed with the following error message : The WinRM client cannot process
the request. It cannot determine the content type of the HTTP response from the destination computer. The content type
is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
+ CategoryInfo : OpenError: (dc01:String) [], PSRemotingTransportException
+ FullyQualifiedErrorId : -2144108297,PSSessionStateBroken


The solution was to exclude PowerShell.exe and PowerShell_ise.exe from the protocol filtering in the Antivirus software as shown in the following image:



1 Comment

  1. Yuriy Samorodov

    Thank you very much for the solution. It appears that ESET is a pain in a lot of ways.


Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: