Carbon Black Cloud: VDI Primary Image Sensor Keeps Uninstalling Itself

[#1]

Environment

• Carbon Black Cloud Console: All Versions
• Carbon Black Cloud Sensor: 3.3.x and Below
• Microsoft Windows: All Supported Versions

Symptoms

• VDI Primary Images are turned on for maintenance
• Cb Defense removes itself from the primary image
• Sensors on VDI's cloned from the primary image are deleted, resulting in missing active VDI's from the Cb Defense Console
• "Auto-deregister VDI Clone sensors that have been inactive for" is enabled via Policy (Sensor tab on Policies page) or Sensor Settings (Sensor Options > Sensor Settings on Endpoints page)

Cause

"Auto-deregister VDI Clone sensors that have been inactive for" is enabled in your environment at the time the primary image is turned on after

Resolution

• Leave the primary image off at all times in the environment 
• If bringing the primary image up for any reason re-install the sensor
• For 3.4 and above please use: Cb Defense: How To Upgrade VDI Master Image For Non-Persistent Clones

Additional Notes

• The primary image is treated as another VDI in the console when installed with VDI=1
• If the primary image hits the time specified for the setting "Auto-deregister VDI Clone sensors that have been inactive for" and then connects to the backend, the sensor on the primary image will be removed

Related Content

Carbon Black Cloud: How To Automatically Delete Deregistered/Uninstalled Sensors From The Console
CB Defense: Auto-Delete Deregistered Sensors & Auto-Deregistration of VDI Sensors Failing RESOLVED
Cb Defense: Deregistered Sensor FAQ
Cb Defense: How to deploy sensor to a non-persistent VDI Master Image?