The latest Windows Server 2022 updates have broken Hyper-V polling

Hyper-V servers updated to 20348.3207 no longer can poll Hyper-V host details, but still can see hardware metrics (memory, CPU, etc). We have tried all the usual tricks (unmanage/manage, remove the server & re-discover, etc). Servers are polled via WMI, and we have ensured that WMI connectivity is still valid between them and the poller. I can find no relevant messages in the logs. SAM is 2025.1. We have a high priority ticket open, but so far have gotten no support. Has anyone else seen this behavior?

Find more posts tagged with

sam

Hyper-V

Accepted answers

All comments

marcrobinson

This sounds like something on the MS side potentially. Are you to see the metrics via wbemtest? Using the same account/security that is polling the server? While I don't suspect an update to wmi has happened, it is not out of the realm of possibility.

Kita

I am interested to hear if others are having similar problems.Disabling and enabling polling resolved the issue. Within the VIM Collector logs, there were signs of the following error message: https://support.solarwinds.com/SuccessCenter/s/article/Unable-to-poll-server-through-WMI-due-to-DNS-records.

morr_rva

There was more than that. We were instructed to bring down the poller, update the database to remove polling jobs that appeared to be hung, and then stop polling on the servers & restart it. There really isn't a good explanation as to why it was specifically affecting Hyper-V, other than the possibility that there may have been some internal changes at the Microsoft end that maybe weren't documented, either WMI or possibly .NET.

mapujece

Check WMI namespace root\virtualization\v2 using wbemtest to verify access to Hyper-V classes. Ensure the polling account has permissions for CIMV2 and Virtualization WMI. Restart Winmgmt, vmms, and al qusais metro station Host Compute Service. Review Event Logs under Hyper-V-VMMS for errors. If the issue started after updating to 20348.3207, consider rolling it back on a test machine. A possible Microsoft patch may be needed.