Discovery of Hyper-V servers does not populate the hyper_v_instance table

[chrisdimo]

We are implementing Discovery into our environment ( Running Dublin ), and even though Discovery picks up correctly our Hyper-V servers it does not seem to detect the Virtual Machines running on them.   The Wintel guys mentioned that the Hyper-V systems are running a "core install" of Windows. So wondering if perhaps some exe's required by probes are not present perhaps.

Any ideas would be greatly appreciated.

[doug_schulze]

Chris,

Take a look at the windows server classifiers you would see that to trigger the Hyper-V probes there is a condition script that defines that those probes should go if hyperv is true... Well to see how we determine that take a look at the windows classify sensor and search for 'hyperv' in the script.. well to set that hyperv is true we are looking to see a result from the WMI query (in the windows classify probe) root\virtualization\Msvm_ComputerSystem.Name

So to make a short story long, check and see that you are getting a value back from that query, its the first domino to fall in the Hyperv discovery..

[chrisdimo]

Ok, so I've managed to get further, and can see the VM's from the XML output. But, the xml is giving me this warning :

<?xml version="1.0" encoding="UTF-8"?>

<results probe_time="21064"><result>

<Warning>Invalid class "Msvm_ComputerSystem"

</Warning>

followed by a heaps of these

<PrivateProperties>StartMemory=4096,ShutdownAction=0,VirtualNumaCount=1,MigrationFailureReason=0,OfflineAction=1,DefaultMoveType=4294967295,VmID=B02A4AEE-EAA8-44ED-B1C2-0DD1C28527A0,CheckHeartbeat=1,VmState=2,MigrationProgress=0,MigrationState=0</PrivateProperties><Name>SCVMM MELMD0216</Name><Type>Virtual Machine</Type>

So it does appear as if it is finding the HyperV VM's, just not classifying them correctly.

I'm new to service now so appreciate everyone's help

[doug_schulze]

So it looks like there might be something 'wonky' with your WMI namespace for the computer system because the rest of the XML looks "right", check with your admin to see why the computer is not answering that Msvm_ComputerSystem class..

[mamann]

Chris,

I just ran into a similar issue on Windows 2012 Datacenter R2 full install with the Hyper-V role installed.

It looks like there is another namespace that can be queried to get the Msvm_ComputerSystem class in new versions of Windows and is also used for specific installs.

I'm building a workaround for this and can update this after I've confirmed it's working