Environment
- Cb defense Web Console: January '18 release and later
- Cb Defense Sensor: 3.1.x
- Mac OS: All Supported Versions
Symptoms
- Update device to Mac OS 3.1 Sensor
- Within Desired policy enable Controlled Uninstall feature by selecting "Require Code to Uninstall Sensor" option and saving policy
- Controlled Uninstall feature is not successfully enabled upon the sensor side and is still able to be uninstalled without prompting for Company Deregistration Code
Cause
- Upon first policy edit, the setting is not being applied/saved successfully; This is a known issue in the 3.1 Mac OS Sensor.
Resolution
- This issue will be fixed in a future version of Cb Defense Sensor for Mac; This article will be updated accordingly once the fix is implemented.
- As a temporary workaround, Please perform the following to make the setting apply:
- Uncheck the "Require Code to Uninstall Sensor" option
- Save policy
- Check the "Require Code to Uninstall Sensor" option
- Save policy
- Wait for sensor to check in at least twice before retesting the controlled uninstall.
Additional Notes
The controlled uninstall was first introduced with January '18 Release and Windows sensor 3.1. It is now also available for Mac endpoints starting with Mac sensor 3.1.
Related Content
MacOS CbD Sensor 3.1 Release Notes
Cb Defense User Guide (Chapter 4: Deploy and manage sensors Pg. 43 Uninstall Sensors)
Rolling Out the January ‘18 Release of Cb Defense
Cb Defense January 2018 Release Notes
Cb Defense: How to Perform an Attended Installation of the Sensor
Cb Defense: How to Perform an Unattended Installation of the Mac Sensor
