In the current incarnation of Hypervisor autodiscovery, the only option for setting customer on discovered VMs is to set a single customer for every discovered device (i.e. one customer per discovery job). Our environment (and others', I expect) makes this an unusable implementation of the feature- we have many, many different customers' VMs in our vCenter.
A more useful feature/option for hypervisor discovery for us would be to set customer based on VM folder in vCenter- that way we can organize our VMs in vCenter by Customer, and autodiscovery can correctly assign them.
This affects hundreds and hundreds of devices for us- it's also the only thing that stands in the way of us deleting devices that have erroneous data and re-discovering them without having to manually intervene and set customer. We've been using Device42 for years, and love it, but updates/changes to the software and to autodiscovery (as well as history of changes made by us) have generated a lot of bad/missing data, and by far the best method for correcting this on VMs is simply deletion/rediscovery.
Please sign in to leave a comment.