ServiceNow Discovery of Hyper-V Servers

[Shantanu1]

Hi Experts!

We are currently migrating our VMs from VMware to Hyper-V and are testing the discovery of Hyper-V servers, associated VMs, and clusters.

Our Hyper-V servers are hosted through System Center Virtual Machine Manager (SCVMM) on Windows Server 2022. While the Hyper-V servers can be discovered individually, they are not being discovered via SCVMM when we attempt to discover the Windows hosts.

The expectation is that discovering the Windows host should trigger a Hyper-V pattern to discover the clusters, along with the hosted Hyper-V servers and the VMs running on them. so that we dont need to discover each Hyper V servers individually.

Please suggest if there is an out-of-the-box (OOB) solution for this.

[AndyMcCabe]

From a Case I opened in December

ISSUE: Does Discovery Create CIs for Microsoft System Center Virtual Machine Manager (VMM)
SOLUTION PROPOSED:
=>We have a discovery pattern for Microsoft Hyper-V, supporting both standalone servers and the Hyper-V role on Windows.
=>However, we currently don't have a specific pattern for Microsoft System Center Virtual Machine Manager (VMM).

Further,

• ServiceNow support said "I have checked with the SGC PM, and they confirmed that VMM is not discovered in an upcoming release"

I am about to roll my own VMM discovery - did you go in that direction? if so, perhaps we can prepare notes

[Shantanu1]

Thanks for the response! I too have got a similar response and I will be starting to work on a custom pattern for this requirement and yes definitely we can work to get this documented!

My path will be to discover the VMM first and retrieve the IP address of each Hyper-V, and then trigger the OOB pattern for each hyper-V hosted on the VMM. Did you followed the same or a different approach?

[AndyMcCabe]

I am contemplating modelling the VMM discovery similar to the vCenter

• all conceptual (have not started yet)

Approach

• VMM as an instance of VMM running on a device and identified by app fingerprinting during the discovery of the device
  • Similar to discovery of a Windows Server running vCenter
  • See the ports open or the application installed and running - then collect extra data
• Two branches of discovery
  • 1 at the virtualization /hypervisor level 
  • 2 at the "normal" operating system level ("normal" discovery for specified IP Ranges)

[Marc54]

Did you continue down the custom pattern route? We are also looking at a Nutanix/vCenter approach for this.