Carbon Black Cloud: How To Deploy Sensor to a Persistent VDI Primary Image

Products

• Carbon Black Cloud Endpoint Standard (formerly Cb Defense)

Issue/Introduction

To deploy Carbon Black Cloud Sensors to a Persistent VDI Primary Image, which is subsequently cloned

Environment

• Carbon Black Cloud: All versions
• Microsoft Windows: All Supported Versions
• Persistent Virtual Desktop Infrastructure (VDI) Primary Image

Resolution

Please see our Persistent VDI Installation Guide

Additional Information

• Make sure that the primary image never registers as a clone ('repcli reregister now' should not be run on primary image) or gets deregistered unintentionally
• Install the sensor with the CLI_USERS parameter to ensure Repcli Authentication is configured
• 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
• VDI=1 has been deprecated and should no longer be used
• Devices which are referenced as the primary image for another device are no longer considered for automatic deregistration of VDI sensors based on last contact