Hyper-V host cannot be managed anymore

Question

Hello,

I cannot connect to or manage my hosts anymore from my jump server.

I use the same account with same rights on all the machines : one jump server, two hosts with local admin rights.

When I tried to manage locally with PowerShell, I get this error message :

Move-VM : The operation on computer 'Snnnnnnnnnnnnnnnnn0' failed: 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.

WinRM is running and well configurated :

PS C:\Users\nnnnnnnnn> WinRM QuickConfig

WinRM service is already running on this machine.

WinRM is already set up for remote management on this computer.

I got this message from my jump server :

PS C:\Windows\system32> Enter-PSSession Snnnnnnnnnnnnnnnnn0

Enter-PSSession : Connecting to remote server Snnnnnnnnnnnnnnnnn0 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.

At line:1 char:1

+ Enter-PSSession Snnnnnnnnnnnnnnnnn0

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

**+ CategoryInfo          : InvalidArgument: (Snnnnnnnnnnnnnnnnn0:String) [Enter-PSSession], PSRemotingTransportException** 

**+ FullyQualifiedErrorId : CreateRemoteRunspaceFailed**

I checked on many sites for help but still not working.

Thank you

Answer 1

Hello,

Thank you for posting in Microsoft community.

This error usually indicates a problem with the WinRM service configuration or network communication between the jump server and the remote host. Have you checked the network connection between the jump server and the remote host? You can use the Ping command or other tools to test network connectivity.

In addition, may I know what specific operation did you perform that got the error? If you are managing Exchange server, the following can help troubleshoot the problem.

• Make sure that the user who is trying to connect has a Remote PowerShell Enabled status. To determine whether a user is enabled for Remote PowerShell, you have to start Exchange Management Shell by using an account that is enabled, and then run the following command:

    (Get-User <username>).RemotePowershellEnabled
  

  This query returns a response of True or False. If the output is displayed as False, the user is not enabled for Remote PowerShell. To enable the user, run the following command:

    Set-User <username> -RemotePowerShellEnabled $True
  

• Make sure that the WSMan module is registered but not enabled at the Server level. Also make sure that the WSMan module is enabled for the PowerShell virtual directory. Then, verify that the following WSMan module entry is included in the <globalModules> section of the C:\Windows\System32\Inetsrv\config\ApplicationHost.config file as follows:

XML:

    <globalModules>
        <add name="WSMan" image="C:\Windows\system32\wsmsvc.dll" />

Note: You must follow these steps even if the WinRM IIS Extension feature has been removed. This is because the uninstall procedure does not automatically fix the ApplicationHost.config file.

For more information see: WinRM can't determine content type of HTTP response - Exchange | Microsoft Learn

I hope this will help you. If you have any follow-up questions, please contact us.

Best regards

Jacen

Answer 2

Hello Jacen,

None of the resolution solution provide by this web page works : it's not an IIS nor an Exchange server. The folders and parameters are not present. My servers are Hyper-V core hosts.

Regards