PowerShell Remoting Error When Trying to use Invoke-Command Against a Domain Controller
I wrote a blog article last year 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.
1Invoke-Command -ComputerName dc01 {Get-Process} -Credential (Get-Credential)
Here's the error that was received when attempting to use the PowerShell remoting Invoke-Command
cmdlet against a domain controller:
1[dc01] Connecting to remote server dc01 failed with the following error message : The WinRM client cannot process
2the request. It cannot determine the content type of the HTTP response from the destination computer. The content type
3is absent or invalid. For more information, see the about_Remote_Troubleshooting Help topic.
4+ CategoryInfo : OpenError: (dc01:String) [], PSRemotingTransportException
5+ 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:
µ