We have a number of Macs in our organization and many of them run a Windows virtual machine of various flavors though Parallels. However, they often have generic machine names, have generic user names like Administrator and when they use NAT’d networking, they have a completely generic non-routable IP, often 10.211.55.3. That makes it difficult to determine what group the machine belongs to. Is there any way, either through the BES client itself, or through relevance clauses to determine the identity of the Hypervisor Mac? Possibly through the ethernet address or long Parallels-… serial number of the VM?
I don’t have a machine in front of me to run Q&A on, but I did set that up as a retrieved property earlier. There are a number of machines with Parallels-… serial numbers that have reported back and they all report Manufacturer-Parallels Software International Inc. Model=Parallels Virtual Platform.
Here is a property that can detect many different types of virtual systems:
q: exists string value whose (it as lowercase contains “vmware” or it as lowercase contains “vmware” or it as lowercase contains “parallels”) of selects “Manufacturer, Model from Win32_ComputerSystem” of wmi
If you only want to detect the type of virtualization, try this:
q: (if (it contains “vmware”) then “VMWare” else if (it contains “parallels”) then “Parallels” else if (it contains “virtual”) then “Virtual” else “Physical”) of (concatenation of string values of selects “Manufacturer, Model from Win32_ComputerSystem” of wmi as lowercase)
I think I may have misstated my intent. I don’t necessarily need to know the machine IAMAVM is virtualized via Parallels, VMWare or Hyper-V, which is what the relevance clause you’ve suggested would provide. I’m trying determine which specific machine is hosting IAMAVM, specifically with Parallels VMs. I’m hoping that there is something that Parallels puts in the registry that would identify the host machine. Or, especially if the VM is using a NATed IP, that some network relevance statement would be able to identify the ethernet address of the host machine.
Ah… I don’t think that the guest knows its host from this point of view… although we are working on some things in this area that might help… but for the moment, I don’t have an answer for you…