- Managing device features and behavior
- Managing devices with IT policies
- Importing IT policy and device metadata updates
- Creating device support messages
- Enforcing compliance rules for devices
- Sending commands to users and devices
- Deactivating devices
- Controlling the software updates that are installed on devices
- Create a device SR requirements profile for Android Enterprise devices
- Create a device SR requirements profile for Samsung Knox devices
- View users who are running a revoked software release
- Managing OS updates on devices with MDM controls activations
- View available updates for iOS devices
- Update the OS on supervised iOS devices
- Configuring communication between devices and BlackBerry UEM
- Displaying organization information on devices
- Using location services on devices
- Using Activation Lock on iOS devices
- Managing iOS features using custom payload profiles
- Managing factory reset protection for Android Enterprise devices
- Create a Factory reset protection profile
- Manually obtain a user ID for a Google account
- How factory reset protection responds to device resets
- Considerations for using a specific Managed Google Play account when setting up a factory reset protection profile
- Clear factory reset protection from a device
- Setting up Windows Information Protection for Windows 10 devices
- Allowing BitLocker encryption on Windows 10 devices
- Managing attestation for devices
- Migrate iOS devices to use a hardened channel
- BlackBerry Docs
- BlackBerry UEM 12.17
- Administration
- Managing device features
- Managing factory reset protection for Android Enterprise devices
- How factory reset protection responds to device resets
How factory reset protection responds to device resets
There are several ways that a device can be reset to the default factory settings. Depending on which way that the device is reset, factory reset protection responds differently. For more information about trusted and untrusted resets, visit support.blackberry.com/community to read KB56972.
- Deactivation of theBlackBerry UEM Clientis not considered a trusted reset because the device user is not verified before the device is deactivated. Therefore factory reset protection is triggered when the device resets and the deactivation has completed.
- Sending the "Delete all device data" command from the management console can be either a trusted or untrusted reset. If you select the "Remove factory reset protection" option when you send the command, factory reset protection is not triggered when the device resets.
- Resetting the device from device settings requires the user to authenticate themselves before the reset. This is considered a trusted reset and factory reset protection is not triggered.
- Device bootloader/recovery or debugging tools (ADB) can be used to reset the device to factory settings and are considered untrusted because the user identity is not validated before the factory reset occurs. Therefore factory reset protection is triggered when the device resets.