Driverfeed no longer works with VMs
This used to work on version 8 and prior. It does not work on version 9. Quest has redefined driverfeed to search for the machine ID, which is not available for VMs. They assign a code for the machine ID to a directory name, such as "0a3e". The machine ID is retrieved using "wmic baseboard get product". For a VMware VM "440BX Desktop Reference Platform" is returned. Surely they could key off that to identify that it's a VM. Also, since the PXE platform has VMXNET3 drivers, they can detect whether those are in installed and active. The same is true for a Hyper-V virtual machine.
Robert Becker shared this idea