Guest inventory now actually works. In 2.1.0 the guest fields stayed empty on every host.
⚠️ Upgrading
Redeploy hyper-v-monitoring2.ps1 to every Hyper-V host. Both fixes are in the script. The templates only changed their version number, so re-importing them alone fixes nothing.
Expect the heartbeat trigger to become active. Hyper-V: no heartbeat from <VM> only fires for guests that report an OS name over KVP. Because that field was always empty in 2.1.0, the trigger could never fire. With 2.1.1 it works as intended, so a guest with a real heartbeat problem can alert for the first time. Set {$VM.HEARTBEAT.CHECK} to 0 on a VM host to switch the check off for that VM.
Fixed
Guest inventory was empty on every host. OS name, version, build, FQDN, integration services version and IP address are read from the KVP exchange service. The script queried it in a malformed CIM namespace — the backslashes of root\virtualization\v2 had been lost — and the failing query was silent. Thanks to @sokolum for finding and fixing this in #60.
Guest IPv4 address on Windows Server 2025 hosts. The KVP value NetworkAddressIPv4 no longer comes back there. The address is now read from the VM's network adapters, which the script loads anyway. IPv6 addresses are left out, several IPv4 addresses are joined with ; . The KVP value is still used when the adapters report no address.
Linux guests
A Linux VM publishes guest information only when the Hyper-V guest daemons are installed inside the guest. Without them the VM is monitored as usual, only the guest fields stay empty. On Ubuntu:
sudo apt install linux-cloud-tools-virtual
The README has a new section under Requirements with the package names for other distributions and a check from the Hyper-V host, plus a troubleshooting entry for empty guest fields.