The cloned VDI will register with the Carbon Black Cloud once the "CB Defense" Carbon Black Cloud Sensor Service starts. These cloned VDI will then appear in the Endpoints or Workloads page of the Carbon Black Cloud Console
Warning: If VDI=1 was used and the sensor is uninstalled from the primary image, cloned VDI will fail to register and display within the Carbon Black Cloud Console.
Note: For non-persistent deployments leveraging Horizon version 7.13, 2012, and later versions, and Carbon Black Cloud sensor version 3.6+, you must remove the batch file (example batch file path: C:\CB.bat) inserted into the golden image previously. This is possible because the registry of HKLM\Software\VMware, Inc.\ViewComposer\ga\AgentIntegration is now automatically set by the the Instant Clone Agent. See Interoperability of VMware Carbon Black and Horizon for details
Make sure that the primary image never registers as a clone or gets deregistered.
The endpoint inherits the policy from the primary image unless you have previously created sensor groups, and the installed sensor matches a sensor group’s criteria. Manual policy assignment post-installation overrides the inheritance.
Non-persistent VDI endpoints should be managed in a separate policy from Persistent VDIs. In Non-persistent VDI policies, we recommend that you enable the setting "Auto-deregister VDI sensors that have been inactive for" to remove any clones that been inactive for the specified duration. In Persistent VDI policies, we recommend that you disable this setting to prevent unintentional uninstall of the sensor.