A water-utility golden image for historian jump VMs was cloned with the Carbon Black Cloud sensor still registered. Only one of many clones appears in the console. What is the correct repair?
Select an answer to reveal the explanation.
Short Explanation
Cloned sensors are like photocopied library cards — the desk only honors one copy. Generalize the image with the Carbon Black Cloud VDI/clone procedure so each jump VM gets its own ID.
Full Explanation
When a water-utility golden image for historian jump VMs was cloned with the Carbon Black Cloud sensor still registered and only one of many clones appears in the console, follow the Carbon Black Cloud VDI/clone procedure so each VM receives a unique sensor ID. Cloned sensors that share an identity collide in the console, so most clones never appear as distinct civic workloads. The supported clone/VDI cleanup and re-registration path restores unique inventory for historian jumps. Merging all clones into one NSX-T security group so a single sensor ID covers the fleet fails by concept because an NSX group cannot invent unique CBC sensor identities for clones. Deleting the Workspace ONE UEM smart group that maps to the golden image fails by concept because removing a UEM smart group does not fix duplicated CBC sensor IDs from cloning. Installing Guest Introspection in VMware Tools and removing the Carbon Black Cloud sensor fails by concept because Guest Introspection does not replace CBC prevention inventory for jump VMs. Exam caveat: golden-image clones need the CBC VDI/clone procedure for unique sensor IDs—do not merge NSX groups or delete UEM smart groups as the sensor fix. Operational check: apply the CBC clone procedure on the golden image and clones, confirm each historian jump appears uniquely Online, verify prevention policy assigns, and document the clone steps in the water-utility image build guide for civic OT endpoints.