News
Abstract
In 2016, with Android N (Nougat/7.0), a specialized environment called Direct Boot Mode was introduced by Google for the Android OS.
When an Android-powered device is switched on, it boots in the Direct Boot Mode before the user unlocks it with their screen lock authentication mechanisms during the very first instance. In this specialized mode, while the OS is fully functional, the access to any app’s private data is completely restricted and only apps that are updated to be Direct Boot Mode are allowed to run.
Content
Subsequently, for effective device management, IBM MaaS360 had supported the Android Enterprise solution sets for the following actions to be executed in Direct Boot Mode.
- Reset Password: This action helps in quickly recovering a device and preventing loss of productivity when the user has forgotten the password or has been locked out because of multiple incorrect attempts.
- Wipe: In scenarios where the device is deemed to be lost or misplaced or stolen, a remote wipe can be triggered to help reduce the risk of corporate data leakage.
Prerequisites
- MaaS360 Android Agent 8.65 or higher.
- Target devices must be compatible with Direct Boot mode.
- Target devices must be online with adequate network coverage.
Was this topic helpful?
Document Information
Modified date:
23 September 2024
UID
ibm17169561