Views:

There are 3 options to resolve this:

  • Option 1: Configure data center gateway to Workload Security to let the cloned DSA be identified and add VMware vCenter as data center gateway. A reactivation with wanted policy for the clones is needed to help them find the right host entry.
  • Option 2: To prevent the issue from happening, change the cloning process to not clone VMWare resources with active DSA’s. Instead, clone a resource with the DSA inactive and activate the DSA afterwards. This way, the DSA will be activated with the updated unique BIOS UUID and ensure a dedicated Manager computer resource. To address the issue for existing DSA’s, please reset and activate all impacted DSA’s.
  • Option 3: Workload Security has a controlled update, currently being rolled out globally. This change will be able to identify DSA’s with the same configuration and a unique Virtual UUID (BIOS UUID) during a heartbeat and automatically create a new computer resource in the Manager.
 
Please consider enabling automatic upgrade in the Agent upgraded system setting options.
 

Option 3 only works for a virtual machine clone with a unique Virtual UUID (BIOS UUID). For some visualization applications, the cloned virtual machines may not have a unique Virtual UUID (BIOS UUID). In such situations, it is recommended to follow the vendor documentation to change the Virtual UUID (BIOS UUID) to be a unique value and reactivate the DSA with Workload Security.

It is expected to see more computer entries being created as the issue is being resolved, as the unique virtual machines get assigned a unique computer resource in the Workload Security Manager. As such, this may increase the host count and be reflected in the license usage or billing.