Ok, so that’s a bit misleading. The actual issue is that ConfigMgr’s detection routine for some virtual machines is broken. This apparently started around May 2014 but I noticed it for the first time on a new ConfigMgr v1511 installation.
Nicolas Pilon of System Center Dudes has a great technical write up on the issue: Is_Virtual_Machine in v_R_System is not showing properly with a virtual machine under VMWare ESXI 5.1 https://www.systemcenterdudes.com/is_virtual_machine-in-v_r_system-is-not-showing-properly-with-a-virtual-machine-under-vmware-esxi-5-1/
He also posted a bug on Microsoft Connect which needs to be up-voted by more people to get any attention from Microsoft: Is_Virtual_Machine in v_R_System is not showing properly with a virtual machine under VMWare ESXI 5.1 https://connect.microsoft.com/ConfigurationManagervnext/feedback/details/878316/is-virtual-machine-in-v-r-system-is-not-showing-properly-with-a-virtual-machine-under-vmware-esxi-5-1
The purpose of this blog is to provide a workaround until there is a patch.continue reading on CatapultSystems.com