Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Hyper-V discovery

Log in to subscribe to topics and get notified when content changes.

Hyper-V discovery

Microsoft Hyper-V is a virtualization application that is included with the Windows Server 2008 operating system.

A physical machine running Hyper-V is divided into partitions (virtual machines), including a parent partition running Windows Server 2008 and child partitions running supported guests. The parent partition manages the virtual machines with the Hyper-V Manager application. On Windows Server 2008 this is done through the Microsoft Management Console (MMC) service. On Windows 7, use the Remote Server Admin tools.

Hyper-V supports the following functionality:
  • Failover clustering: Failover is managed with Failover Cluster Manager.
  • Live migration: Virtual machines can be moved between failover cluster nodes without bringing down the virtual machine.
Warning: DO NOT switch from probes to patterns if you are already running Discovery with probes, and your CMDB is already populated. If you do so, it is possible that the pattern Discovery process does not synchronize on the same values that the probe Discovery process does. This could result in duplicate CIs in your CMDB.

Supported versions

Discovery is supported for these Hyper-V Server versions:
  • 2008
  • 2012
  • 2012 R2
  • 2016
  • 2019 (Patch 3 and later)
Important: Discovery of Hyper-V running on Windows 2016 is supported for patterns only. If you upgraded and are still using probes and sensors for Discovery, see KB0694773 for instructions on configuring Hyper-V probes.


Configure Windows credentials with Domain administrator rights. You should also Enable PowerShell for the MID Server used to discover Hyper-V servers and instances.

Classifier, probes, and pattern

Table 1.
Classifier Probes Pattern
Hyper-V Server

The classification applies to stand-alone Hyper-V servers only (servers not running on Windows 2008).

  • Horizontal discovery probe: launches patterns
  • Windows - ADM^
  • Windows - Installed Software^
  • Hyper-V - Cluster*
  • Hyper-V - Resource Pools*
  • Hyper-V - Virtual Machines*
  • Hyper-V - Virtual Networks*
  • Several other Windows probes also run, such as Windows - Identity, Windows - software, and so on.*
Hyper-V Server

*For new instances, these probes are inactive on the classifier. Discovery uses patterns for discovery.

^These probes remain active by default, even when Discovery uses pattern discovery.

To use patterns, verify that the correct pattern is specified in the horizontal pattern probe on the classifier. See Add the Horizontal Pattern probe to a classifier for instructions.

Data collected

Table 2. Virtual instances
Label Field Name Data Description Stored in Table
Object ID^ object_id ID cmdb_ci_hyper_v_instance
Name^ name name cmdb_ci_hyper_v_instance
State state
  • On
  • Off
  • Suspended
  • Changing
  • Stuck
CPUs cpus Count cmdb_ci_hyper_v_instance*
Memory memory Quantity in MB cmdb_ci_hyper_v_instance*
Network adapters nics Count cmdb_ci_hyper_v_instance*
Disks disks Count+ cmdb_ci_hyper_v_instance*
Disks size disks_size Capacity in GB+ cmdb_ci_hyper_v_instance*
Virtual Base Board Serial Number baseboard_serial Virtual serial number cmdb_ci_hyper_v_instance
BIOS Serial Number bios_serial Virtual serial number cmdb_ci_hyper_v_instance
Chassis Serial Number chassis_serial Virtual serial number cmdb_ci_hyper_v_instance
BIOS GUID bios_guid Globally unique identifier (GUID) cmdb_ci_hyper_v_instance
*Attributes that are put in the cmdb_ci_hyper_v_instance table when using the Hyper-V Server pattern. For upgrades, probes and sensors continue to put these attributes in the cmdb_ci_vm_instance table.

^Newly discovered attribute when using the Hyper-V Server pattern.

+Discovery can only return this information if the virtual machine is running.

Table 3. Virtual servers
Label Field Stored in table
Name name cmdb_ci_hyper_v_server
Chassis type chassis_type cmdb_ci_hyper_v_server
Short description short_description cmdb_ci_hyper_v_server
OS Address Width (bits) os_address_width cmdb_ci_hyper_v_server
Operating System os cmdb_ci_hyper_v_server
Host name hostname cmdb_ci_hyper_v_server
IP Address ip_address cmdb_ci_hyper_v_server
OS Version os_version cmdb_ci_hyper_v_server
OS Service Pack os_service_pack cmdb_ci_hyper_v_server
Is virtual virtual cmdb_ci_hyper_v_server
Table 4. Virtual networks
Label Field Name Data Description Stored in Table
Name name Name of the virtual network cmdb_ci_hyper_v_network*
ID object_id Globally unique identifier (GUID) cmdb_ci_hyper_v_network*

*Attributes that are put in the cmdb_ci_hyper_v_network table when using the Hyper-V Server pattern. For upgrades, probes and sensors continue to put these attributes in the cmdb_ci table (name) and the cmdb_ci_vm_object table (object_id).

Table 5. Resource pools
Label Field Name Data Description Stored in Table
Name^ name Name of the resource pool. cmdb_ci_hyper_v_resource_pool
ID object_id Globally unique identifier (GUID) cmdb_ci_hyper_v_rpool_comp
Capacity capacity Maximum amount of the appropriate allocation unit cmdb_ci_hyper_v_rpool_comp
Allocation units allocation_units Units of measurement used (for example, MB or GB) cmdb_ci_hyper_v_rpool_comp
Resource type resource_type Type of resource discovered (for example, memory, or hard drive space) cmdb_ci_hyper_v_rpool_comp
Table 6. Clusters
Label Field Name Data Description Stored in Table Reference Table
Windows Cluster name Reference field displaying the Windows Cluster on which the Hyper-V cluster resides. cmdb_ci_hyper_v_cluster cmdb_ci_win_cluster


Discovery creates records in the CMDB for the host machine, the parent partition running Windows Server 2008, and all the virtual machines running on the Hyper-V server. Discovery finds the stored templates and maps all the relationships between components.

The instance modifies these tables for use with multiple virtualization products:
Table Purpose

Virtualization Server [cmdb_ci_virtualization_server]

Contains data on all discovered virtualization servers.

Virtual Machine Instance [cmdb_ci_vm_instance]

Contains data on all discovered virtual machine instances.

Virtual Machine Object [cmdb_ci_vm_object]

Contains data about various objects associated with a Hyper-V server, such as partitions, networks, resource pools, and clusters.

Table 7.
Parent table Relationship Child table
Hyper-V Virtual Machine Instance [cmdb_ci_hyper_v_instance] Registered on::Has registered Hyper-V Server [cmdb_ci_hyper_v_server]
Hyper-V Virtual Machine Instance [cmdb_ci_hyper_v_instance] Connected by ::Connects Hyper-V Network [cmdb_ci_hyper_v_network]
Hyper-V Network [cmdb_ci_hyper_v_network] Provided::Provides Hyper-V Server [cmdb_ci_hyper_v_server]
Hyper-V Resource Pool [cmdb_ci_hyper_v_resource_pool] Defines resources for:Gets resources from Hyper-V Server [cmdb_ci_hyper_v_server]
Hyper-V Resource Pool Components [cmdb_ci_hyper_v_rpool_comp] Contained by::Contains Hyper-V Resource Pool [cmdb_ci_hyper_v_resource_pool]
Hyper-V Cluster [cmdb_ci_hyper_v_cluster] Members::Member of Hyper-V Server [cmdb_ci_hyper_v_server]
Hyper-V Server [cmdb_ci_hyper_v_server] Runs on::Runs Windows Servers [cmdb_ci_win_server]
Windows Servers [cmdb_ci_win_server] Instantiates::Instantiated by Hyper-V Virtual Machine Instance [cmdb_ci_hyper_v_instance]
Windows Servers [cmdb_ci_win_server] Virtualized by::Virtualizes Hyper-V Server [cmdb_ci_hyper_v_server]

Clone Hyper-V virtual machines

When importing (cloning) Hyper-V virtual machines, make sure each virtual machine has a unique ID. Discovery identifies virtual machines with duplicate IDs as the same machine.

  1. Export the virtual machine from the Hyper-V server.
  2. Import the virtual machine into a different server, making one of the these choices:
    • Move or restore the virtual machine: This selection clones the image, using the same ID, and moves it to another server. The original image remains on the Hyper-V server.
    • Copy the virtual machine: This selection copies the virtual machine, using a different ID, and moves it from the Hyper-V server. This is the best selection and does not require any further action before you run Discovery.
  3. If you import the Hyper-V clone using the Move or restore selection, be sure to delete the original image from the Hyper-V server.

    When Discovery encounters two virtual machines with the same equivalent serial numbers, it creates only one configuration item (CI).