Environment
- Cb Defense Web Console: January '18 Release and later
Question
Why do some devices show Unassigned on the Sensor Management page? Most of the devices like this also show Unassigned for the Username, but there are some where there is a real username.
Answer
Most Sensors will either show Manually Assigned or the name of the Group they match when Auto-Assign is turned on. However, some Sensors will show Unassigned for the Group even when there is a Policy shown. This is expected, as the sensor does not currently match any existing Groups. There is no expected link between the Username showing Unassigned (typical for the Master Image for VDI clones) and the Group showing Unassigned.
The Group will be updated from Unassigned when
- Device has a policy manually assigned using the Take Action menu
- Device is assigned to a Group using Auto-Assign
Additional Notes
With the January '18 Release of the Web Console, the Enrollment page has become the Sensor Management page. Along with this change, Mass Sensor Management (MSM) was introduced, which gives the ability to create Groups and have Sensors assigned to them automatically. Due to the addition of Groups, the column which used to solely display the Policy to which a Sensor belonged now displays the Group and Policy. The following options can be displayed for the Group value in this column.
- Manually Assigned (Sensors previously installed and assigned to a Policy either at or after install)
- Unassigned (Sensors which have Auto-Assign enabled but are not yet assigned to a Group)
- Group Name (Sensors which have been assigned automatically to the Group you have created)
Related Content
Cb Defense: How To Change A Sensor From "Manually Assigned" To Auto-Assigned
Rolling Out the January ‘18 Release of Cb Defense
