VM Clones and Carbon Black Workloads

When you manually clone a virtual machine on which the Carbon Black Cloud Workload is enabled, you might see some inconsistent behavior. The parent and the clone VM might present under both Enabled and Not Enabled tabs.

You might observe a similar behavior in the Carbon Black Cloud console. The problem occurs when the Carbon Black sensors use the same ID to identify both the VMs to the back end. To resolve the problem, you must perform manual steps and reregister the cloned VM with the Carbon Black Cloud.