Horizon instant clone Internal templates are auto deregistered and eventually deleted

Products

• Carbon Black Cloud Endpoint Standard (formerly Cb Defense)
• Carbon Black Cloud Enterprise EDR (formerly Cb Threathunter)

Issue/Introduction

Horizon instant clone Internal templates are auto deregistered and eventually deleted.

Environment

• Carbon Black Cloud Console: All Supported Versions
• Carbon Black Cloud Sensor: All Supported Versions
• VMware Horizon 8: And Newer
• Instant Clone Desktop Pools: All Supported Versions

Cause

This occurs when all of the following are true:

• The 'internal template' is in a policy that is configured to 'Auto-deregister VDI clone sensors that have been inactive'.
• A VDI from the newly created or rebased pool doesn't register within the policy's specified timeframe for deregistration.
• The "Delete sensors that have been deregistered for" setting is configured.

Resolution

Follow the best practice of assigning the internal template (and golden/master images) to a policy that is not configured to Auto-deregister VDI clone sensors that have been inactive, and the VDI to one that does.

Additional Information

• The problem of the Sensor uninstalling when the Horizon instant clone comes online will not start until the 'internal template' is auto deleted per the CBC console settings. 
• When the 'internal template' registers with the CBC backend, it is initially classified as an instant clone. This classification persists until one of the actual instant clones registers, which triggers a reclassification.
• The 'internal template' is managed by Horizon, and is only powered on during the instant clone pool creation and subsequent rebasing events.
• While not recommended, if for some reason you need to configure the policy where the 'internal template' is located to Auto-deregister VDI clone sensors that have been inactive. Use a time frame that is sufficient for at least one of the instant clones come online and register with the CBC Backend.