Carbon Black Cloud: Auto-Deregistration of VDI endpoints fails when managed by vCenter

Products

• Carbon Black Cloud Audit and Remediation (formerly Cb Live Ops)
• Carbon Black Cloud Endpoint Standard (formerly Cb Defense)
• Carbon Black Cloud Enterprise EDR (formerly Cb Threathunter)

Issue/Introduction

• Enabled deregistration of VDI sensors that have been inactive for a specified timeframe
• Auto-Deregistration of VDI Sensors is failing

Environment

• Carbon Black Cloud Console: September '20 (0.58.1)
• Carbon Black Cloud Sensor: All Supported Versions
• Microsoft Windows: All Supported Versions
• VMware vSphere: All Supported Versions

Cause

Virtual Machines that are managed by vCenter are currently excluded from the scheduled task to deregister VDI endpoints.

Resolution

• Manually deregister VDI sensors that have been inactive for the specified timeframe by following the instructions documented in the following article: CB Defense: How To Uninstall/Deregister Sensors From the Web Console
• Manually delete sensors that have been deregistered for the specified by following the instructions documented in the following article: Carbon Black Cloud: How To Manually Delete Uninstalled/Deregistered Sensors From The Console

Additional Information

Carbon Black is currently investigating why Auto-Deregistration of VDI Sensors is excluding vCenter managed Virtual Machines. In the meantime please continue to manually deregister inactive sensors and delete deregistered sensors as specified in the articles above. This KB will be updated with the backend release that will contain this fix once it has been confirmed.