DeepManage

Features

Device enrollment for Android

Get a new or reset Android device from the box to fully managed in a few minutes. Scan a code, and the device downloads the agent, joins your server and receives its policies.

Enrollment profile and QR code

What you can do

  1. QR code enrollment

    A factory-reset device scans the profile QR code in the setup wizard, downloads the DeepManage agent and sets itself up as device owner.

  2. NFC enrollment

    The console generates the NFC data for a profile, so a device can be provisioned by tapping it against a programmed phone or tag.

  3. Enrollment profiles

    Each profile sets the enrollment method, Wi-Fi details, expiry date, maximum number of devices and the device group and organization new devices join.

  4. Userless enrollment

    Devices can enroll with the profile key in the QR code, without anyone typing a user name or password. A user can be assigned later from the console.

  5. Many devices from one code

    One profile QR code can enroll a whole batch of devices. A device limit and a renewable key keep a leaked code from being misused.

  6. Work profile options

    Company-owned devices can be set up with a work profile (COPE) instead of full management, and personal phones enroll with a work profile through a link.

  7. Terms and conditions approval

    Users approve your terms text in the setup wizard. Every version is kept with a SHA-256 signature, and each approval is recorded per user and device.

  8. Device identity certificate

    Each enrolled device gets its own certificate from a key stored in Android's keystore, so it connects with its own identity instead of a saved password.

How enrollment works

Every enrollment starts from an enrollment profile in the console. The profile decides how the device will identify itself, which Wi-Fi network it uses during setup, and where it lands once it is enrolled: which device group and organization it joins, and therefore which policies it receives.

For a company-owned device the steps are short:

  1. Factory reset the device, or take a new one out of the box.
  2. In the setup wizard, open the QR reader and scan the profile’s code (or use the NFC data).
  3. The device connects to Wi-Fi, downloads the DeepManage agent and makes it the device owner.
  4. The DeepManage wizard shows your terms of use, finishes setup and runs the first synchronization.

From that moment the device appears in the console with its hardware, operating system and policy status.

Typical setups

Situation Method Result
Company phones given to staff Profile QR code with user name and password Fully managed device linked to a user (local or LDAP)
Kiosks, vehicle tablets, shared handhelds Profile QR code with the profile key (userless) Fully managed device without a user
Company devices that allow personal use Profile QR code with the COPE option Work profile on a company-owned device (Android 11 and later)
Employees’ own phones Enrollment link or link QR code Work profile on a personal device, no reset needed
Devices that cannot use a provisioning QR Install the agent, then scan a server QR code Manual setup that still connects to the right server

Read more about these models in our guide to device ownership models, or see how they play out for company-owned devices and personal devices with a work profile.

Enrolling many devices at once

You do not need a separate code for each device. One profile QR code can enroll as many devices as you allow, which makes it practical to prepare a whole delivery on a table. To keep control:

  • set a maximum number of enrollments for the profile,
  • set a valid until date after which the code stops working,
  • renew the key if a printed code goes missing.

Each new device is placed in the profile’s device group and organization automatically, so it receives the right apps and rules without manual sorting.

What the administrator sees

The Device Enrollment page brings all methods together: corporate profiles with their QR codes and NFC data, the link for personal devices (which you can copy or send by e-mail), and the manual setup code. Each profile shows its status, method and how many devices have enrolled with it. On a device’s detail page you can see how it enrolled, whether its hardware key attestation was verified, and when its certificate expires.

Enrollment in Android Enterprise mode

In Android Enterprise mode enrollment codes are created in the Android Enterprise menu. A company device enrolls with a QR code as fully managed or with a work profile (COPE), and a personal phone enrolls with a work profile (BYOD) through an enrollment link. If your reseller has assigned devices to your organization, zero-touch or Samsung Knox Mobile Enrollment enrolls them automatically on first start; the console prepares the configuration. For the differences between the two modes, see Android Enterprise vs classic mode.

Limits worth knowing

  • Full management requires a factory reset. Android does not allow an existing, already configured device to be turned into a fully managed one.
  • The COPE work profile option needs Android 11 or later. Older devices are set up fully managed instead.
  • QR provisioning depends on the device’s setup wizard. Very old Android versions may need the manual setup path.

Once devices are enrolled, the next steps are usually app management and, for single-purpose devices, kiosk mode.

Frequently asked questions

Which enrollment method should I use?

Use a profile QR code for company-owned devices that you reset and set up yourself. Use the enrollment link for personal phones that need a work profile. NFC is an option for devices and sites where scanning a code is impractical.

Does every device need a user?

No. With userless enrollment the device enrolls with the profile key alone. This suits kiosks, shared devices and vehicle tablets. You can assign a user later, or require pairing so that a device without a user is marked noncompliant.

What if an enrollment QR code is shared by mistake?

Renew the profile key in the console. All printed or shared copies of the old code stop working at once, and devices that are already enrolled are not affected. You can also set an expiry date and a device limit on each profile.

Do devices have to be factory reset?

For full management, yes. Android only lets an app become device owner during the first setup. Personal phones do not need a reset, because they enroll with a work profile next to the user's own apps.

Can the user skip the terms of use?

If you turn on terms approval in the policy, the device asks for approval during setup and again after each new version of the text. The console shows who approved which version, on which device and when.

See DeepManage on your own devices

Tell us about your fleet and we will prepare a demo environment for your team.