Carbon Black Cloud: VDI Primary Image Sensor Keeps Uninstalling Itself
book
Article ID: 290128
calendar_today
Updated On:
Products
Carbon Black Cloud Endpoint Standard (formerly Cb Defense)
Issue/Introduction
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)
Environment
Carbon Black Cloud Console: All Versions
Carbon Black Cloud Sensor: 3.3.x and Below
Microsoft Windows: All Supported Versions
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
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