Using ADB to provision a Fully Managed (DO) device causes unexpected behavior during the Knox license activation process
Environment
- Knox SDK / 3rd party MDMs
- Knox license activation
- Android Enterprise - Fully Managed (DO) devices
Overview
Some UEM developers have reported unexpected behavior during the Knox license key activation process. This behavior includes the Knox End-User License Agreement (EULA) prompt not appearing, or the app never receiving a broadcast result after the license activation attempt.
Cause
Prior to the license activation, the devices were set as a Device Owner (DO) using the adb command, adb shell dpm set-device-owner. Provisioning DO using an adb command bypasses parts of the Knox Platform for Enterprise (KPE) provisioning process, which can cause unexpected side effects.
Resolution
Provision DO using one of the official enrollment methods, such as QR code, NFC, Sign-URL, or DPC identifier.
Additional information
For more details on how to enroll and provision a device in DO, please refer to the Android Management API Documentation.
Back to KBAsOn this page
Is this page helpful?