Sync issue between SCVMM and Failover cluster manager

Refresh the affected cluster and each node from VMM, then use the resulting Jobs entry—not Failover Cluster Manager alone—to identify why the host and VM inventory is stale.

1. Refresh the VMM inventory

In the VMM console:

1. Go to Fabric → Servers → All Hosts.
2. Select the affected cluster and choose Refresh.
3. Refresh each affected Hyper-V host.
4. Open Jobs, locate the refresh jobs, and record:
   • Status and error code
   • Complete error text
   • Affected host or cluster
   • Recommended Action

Alternatively, run the following in a VMM PowerShell session. Replace the example names and ensure the cluster query returns exactly one object before continuing:

$clusterName = "VMHostCluster01.contoso.com"
$cluster = @(Get-SCVMHostCluster -Name $clusterName)

if ($cluster.Count -ne 1) {
    throw "Expected one cluster; found $($cluster.Count)."
}

$cluster[0] | Read-SCVMHostCluster
Get-SCVMHost | Where-Object VMHostCluster -eq $cluster[0] |
    Read-SCVMHost

Read-SCVMHostCluster refreshes cluster properties displayed by VMM ^1^. Read-SCVMHost refreshes host status, volumes, and network-adapter information ^2^.

After completion, compare:

• Host state and VM placement in VMM
• VM owner node and status in Failover Cluster Manager
• The refresh job result in VMM

The supplied PowerShell pages are currently scoped to the VMM 2025 module view. If “SCVMM Windows 2022” means System Center VMM 2022, confirm these cmdlets are available in the installed VirtualMachineManager module before using them:

Get-Command Read-SCVMHostCluster, Read-SCVMHost
Get-Module VirtualMachineManager -ListAvailable

2. If the refresh reports a communication or permissions error

For Needs Attention, Not Responding, or Access Denied:

1. In VMM, right-click the host and select Properties → Status.
2. Open the category marked with a red exclamation point.
3. Match its error to the corresponding failed job.

Errors such as 2915, 2916, 12710, 13926, 20506, or 406 commonly identify WMI, WinRM, node-contact, or permissions failures. Warning 13926 specifically means that not all cluster nodes could be contacted, so VMM’s VM, storage, or network inventory can be inaccurate ^3^.

If the error is Access Denied, an authorized domain or server administrator should verify that the VMM service identity has the required local-administrator membership on every affected host. If Group Policy manages that group, correct the applicable Restricted Groups policy rather than making a temporary local change.

Do not rebuild WMI merely because inventory is stale. If the problem began specifically after the WMI repository was rebuilt and the host now shows Needs Attention, recompile the MOF files on that host from an elevated Command Prompt, then refresh it:

cd /d %windir%\System32\Wbem
for /f %x in ('dir /b *.mof ^| findstr /v /i uninstall') do mofcomp %x

That resolution applies to the documented post-WMI-rebuild condition ^4^.

3. If this followed a VMM upgrade

Only if VMM was recently upgraded, display Agent Status and Agent Version Status under Fabric → Servers → All Hosts:

• Access Denied: right-click the host and select Reassociate.
• Upgrade Available: evacuate the clustered host or place it in maintenance mode, then select Update Agent.

Updating the agent can restart VMMS and potentially disrupt running VMs, so migrate VMs away first ^5^.

4. If the refresh still fails without a clear cause

Capture a VMM trace on the VMM server while reproducing one refresh failure:

New-Item C:\vmmlogs -ItemType Directory -Force
logman delete VMM
logman create trace VMM -v mmddhhmm -o $env:SystemDrive\VMMlogs\VMMLog_$env:computername.ETL -cnf 01:00:00 -p Microsoft-VirtualMachineManager-Debug -nb 10 250 -bs 16 -max 512
logman start VMM
# Reproduce one failed cluster/host refresh in VMM.
logman stop VMM

The ETL will be under C:\vmmlogs. This logging procedure explicitly applies to System Center 2022 VMM ^6^.

The next diagnosis requires the exact failed refresh job code and text, plus confirmation whether the product is System Center VMM 2022, VMM running on Windows Server 2022, or both.

References

1. Read-SCVMHostCluster-Description
2. Read-SCVMHost-Syntax
3. Troubleshoot Needs Attention, Not Responding, and Access Denied hosts in Virtual Machine Manager
4. Needs Attention host status after you rebuild the WMI repository
5. Upgrade System Center Virtual Machine Manager
6. How to enable debug logging in Virtual Machine Manager