Discovery of Hyper-V servers does not populate the hyper_v_instance table
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-05-2014 07:42 PM
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.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2015 07:04 AM
Ah ok that makes more sense.
I tagged Doug Schulze from SN in the previous thread and he might be able to shed some light on potentially any progress of this being supported.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-17-2015 08:04 AM
We have made the changes that you listed above.
I can see in the "WMI: Classify (nodes: 28)" payload that there is allot of data but still getting:
<Warning>Invalid class</Warning>
<Warning>Invalid class</Warning>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-08-2015 01:44 PM
That's normal because one of the two CIM class paths we're using for each element won't exist.
