KACE Product Support Question

report for VM host

08/06/2012 3504 views

Could the Kace identify the VM host? and run the report for list of vm host, group by vm host name. sample vm01, vm02,vm03's vm host is esx01 vm04, vm05 host is esx02

Answer Summary:
1 Comment   [ + ] Show comment


  • Make A Smart Label with the following exact text in the rules:
    System Model = VMware Virtual Platform
    OR System Model = Virtual Machine
    OR System Model = VirtualBox

    This will cover all VMWare, MS HyperV, and Sun VirtualBox essentially giving you a label for vms.

    You can also approach it from the opposite direction when trying to narrow it down to what you have by testing a label with the following:
    Chassis type != desktop AND Chassis type != laptop
    careful though: MS Hypervisor defines vm as a desktop chassis
    Model: Virtual Machine
    Chassis Type: desktop
    But it will help you narrow what kind of devices you have and make a label accordingly.

All Answers


Is HKLM\SOFTWARE\MICROSOFT\Virtual Machine populated with the info on your VMs? If so you can write a custom inventory then run the report against that data.

What VM solution are you using?

Answered 08/06/2012 by: dugullett
Red Belt

  • It looks like that's used for Hyper-V, Virtual PC and the like:


Looks like ESX going off of what he said above. 

This key would show systems that are probably VMs/have VMware Tools installed, but it wouldn't identify what host it reports to.


It appears you would have to either modify the vm/.vmx file or query vCenter directly in order to be able to identify the host of a VM.

Some links that might be helpful:





Answered 08/06/2012 by: jknox
Red Belt


If neither of those work you can always create a .reg file with the name of the host, and have Kace inventory that. I'm not sure how many VMs you have? It could be somewhat of a hassle.

Once that is created I can help you with the report. 

Answered 08/06/2012 by: dugullett
Red Belt

  • If they have unique IP ranges, you could use regex to target those machines and then install the .reg file with a machine smart label.

    • A combination of that and something like "software title = vmware tools" or "system model = VMware Virtual Platform" should narrow it down.
      • Nice! It hadn't occurred to me to add software title or system model, but that would certainly add another check to make sure the .reg recipient is a VM.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ