Four fixes for problems reported against 2.1.0 and 2.1.1. Thanks to @pefol for the detailed reports.
⚠️ Upgrading
This release needs both steps:
- Redeploy
hyper-v-monitoring2.ps1to every Hyper-V host, for the guest IP fix. - Re-import
Template_Windows_Hyper-V_VM_Guest_2.yaml, for the adapter discovery and VLAN item fixes.
Import order is unchanged: the VM Guest template first, then Template_Windows_Hyper-V_Host2.yaml.
Fixed
The guest IP item could show a warning text instead of an address (#63). On some hosts the deprecated KVP value NetworkAddressIPv4 holds "The following Msvm_KvpExchangeDataItem.Name keys are deprecated: ..." rather than being empty. 2.1.1 fell back to that value when the network adapters reported no IPv4 address. The fallback now only accepts real IPv4 addresses.
VM Network Legacy Adapters Discovery was unsupported on VMs without a legacy adapter (#62), with "no data matches the specified path". That is most Generation 2 VMs. Both adapter discovery rules now discover nothing instead of failing when their filter matches no adapter.
VLAN mode and VLAN allowed list were unsupported on regular adapters (#64). The items were numeric but receive text such as "Untagged" or "1-10,20". They are character items now, as they already were for legacy adapters.
Documentation
The agent on the Hyper-V host needs active and passive checks (#66). The Host template uses active checks, so ServerActive must be set; the VM Guest template uses passive checks, so Server must be set and the agent must be reachable on port 10050. The F.A.Q. said passive only. The template file names in the Usage section are corrected too.