Duplicate Vcenter Records creation & deletionwhen vcenter triggered from ADM process classification.DescriptionCenter records can potentially get deleted based on when/how the "VCenterDatacentersSensor" Script Include is executed. This can occur in the following scenarios: 1) A discovery schedule where a Behavior is set where the first phase discovers the OS portion of the Server (ex. Linux) to where we then find the vCenter via Process Classification. Then, in the second phase, runs vmapp port probe by itself, and discovers the vCenter this way as well.--- This causes an issue where the second phase vCenter Discovery can overwrite/delete the first phase vCenter Discovery record. 2) More than one process matches the filter in the process classifier If some body wants to avoid such duplicate record creation & deletion. Then they can update the vcenter process classification record The current logic for vcenter process classifier is Command contains vpxd The workaround which can be implemented is Command is vpxd This will lead to matching the process classifier only on a single vcenter process instead of multiple processes. Thus avoiding duplicate record creation.Steps to Reproduce NAWorkaroundNARelated Problem: PRB1599809