Workload: Expected Sensor State Matrix

Products

• Carbon Black Cloud Workload

Issue/Introduction

What is the expected state when a VM is on an old sensor, has been Powered Off, is Deleted, cloned, Reverted To a Snapshot,or vMotioned?

Environment

• Carbon Black Cloud: All Versions
  • Workload
• vSphere: All Supported Versions

Resolution

VM has a sensor version prior to 3.6	The sensor will appear on the Endpoints tab instead of Workloads tab.
VM is powered off	After 30 days of inactivity, the sensor is marked as inactive. It will persist on the Enabled tab with Inactive status until removed from the Carbon Black Cloud console.
VM deleted (Sensor not deregistered before deletion)	A delete action is triggered from the vCenter Server when a VM gets deleted from the vCenter Server. The workload sensors that are inactive for three or more days and have received a delete action from the vCenter Server gets Deregistered automatically. The deleted VMs are displayed as Deregistered.  Sensor persist on the Enabled tab with the Deregistered status until removed from the Carbon Black Cloud console.
VM deleted (Sensor deregistered before deletion)	Sensor will persist on the Enabled tab in the Deregistered status until removed from the Carbon Black Cloud console.
VM reverted to a snapshot prior to sensor installation	After 30 days, the sensor is marked as inactive. The VM is available for sensor installation on the Not Enabled tab. If the installation is triggered on the VM again, there will be two entries for the same VM on the Enabled tab after new installation.
VM reverted to a snapshot when an older sensor was installed	If the sensor version is below 3.6, it will move to the Endpoints tab of the Carbon Black Cloud console. If the sensor is still  on 3.6+ after reverting, it will continue to display on the Workloads tab.
VM reverted to a snapshot with a different registration ID	The sensor appears on the Workloads > Enabled tab as a new entry. If the previous entry had not been removed, there will be two entries for the same VM.
VM with a sensor is cloned	Refer to the Cloning Guide
VM is vMotioned to another vCenter Server which is not connected to the appliance	Sensor stays in the Registered -> Active state on the Enabled tab. The details panel may not show any additional data.