Unable to create Virtual Machines in VMM

Question

Hello Team,

Recently, I've been having issues in VMM where Hyper-V nodes that are in a cluster are reporting
'Needs Attention' status, where VMs show Host 'Not Responding'.

Below was the error

Error (20553)
The Windows Remote Management (WinRM) client on the VMM server cannot process the request. A computer policy does not allow the delegation of the user credentials to the target computer hyperv-1.contoso.com.
WinRM: URL: [http://hyperv-1.contos.com:5985], Verb: [INVOKE], Method: [GetAllPerfData], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/scvmm/PerfDataAgent]
Unknown error (0x803381a3)
Recommended Action
Use gpedit.msc and look at the following policy: Computer Configuration -> Administrative Templates -> System -> Credentials Delegation -> Allow Delegating Fresh Credentials. Verify that it is enabled and configured with an SPN appropriate for the target computer. For example, for a target computer name myserver.domain.com, the SPN can be one of the following: WSMAN/myserver.domain.com OR WSMAN/*.domain.com OR WSMAN/*

As per the suggested recommendation, I added the policies on the VMM server, and the Hyper-V hosts started communicating with the VMM server again.
The issue I'm having now is that I cannot create a virtual machine using VMM.
I've got the error below

Error (2927)

A Hardware Management error has occurred trying to contact server 'Cluster01.contoso.com'.
WinRM: URL: [http://cluster01.contoso.com:5985], Verb: [GET], Resource: [http://schemas.microsoft.com/wbem/wsman/1/wmi/root/mscluster/MSCluster_ResourceGroup?Name=SCVMM Tst01 Resources]
Unknown error (0x8033809d)
Recommended Action
Check that WinRM is installed and running on server 'Cluster01.contoso.com'. For more information use the command "winrm helpmsg hresult" and http://support.microsoft.com/kb/2742275.

VMM is having an issue with communicating with the cluster name object. I've made sure that the The SPN registered for the CNO is intact in Active Directory. Everything was functioning well until I encountered the WinRM issue. What am I missing?

WSMAN/cluster0.contoso.com
WSMAN/cluster01
MSServerCluster/Cluster01.contoso.com
MSServerCluster/Cluster01
MSServerClusterMgmtAPI/Cluster01.contoso.com
MSServerClusterMgmtAPI/Cluster01
MSClusterVirtualServer/Cluster01.contoso.com	
MSClusterVirtualServer/Cluster01
HOST/Cluster01.contoso.com
HOST/Cluster01

Windows cluster: 2019

VMM: 2022

Your help is greatly appreciated.

Thanks,

Dera

Answer 1

After opening a case with MS. The issue has been resolved.

Looks like some GPOs were missing on the VMM server.