Fix incorrect VM host classification for servers or workstations
In some cases, a Windows server or desktop/workstation appears as an inventory device type of VM host. This happens when the inventory agent detects the Hyper‑V feature on the device.
This article explains how to confirm the detection and how to correct the classification.
- Review the NDI file to confirm how the agent classifies the device.
- Look for the following entry:
<Hardware Class="MGSVM_InfrastructureSDK" Name="Microsoft Hyper-V" Evidence="HYPERV">
<Property Name="Name" Value="Microsoft Hyper-V"/>
<Property Name="Protocol" Value="WMI"/>
<Property Name="Port" Value="135"/>
<Property Name="Version" Value="10.0.17763"/>
<Property Name="HostIdentifier" Value="production.domain.com"/>
</Hardware>- Run the following PowerShell command to check whether Hyper‑V is installed and its status:
Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V
- Review the command output:
- If Hyper‑V is disabled, the service is not running.
Example:
- If Hyper‑V is enabled, the service is running.
Example:
- If the device should not be classified as a VM host, remove the Hyper‑V feature.
- Run an inventory scan from the agent to update the device classification.
After removing the Hyper‑V feature and running a new inventory scan, the device is categorized correctly.
Was this helpful?
