Enrolling Android devices using QR Code

QR Code or Device Enrollment Configurations are a quick and easy way to enrol your Android devices. By creating a QR Code configuration, you can choose the default Group or Profile and a naming convention for the devices that are enrolled using this QR Code.

QR Code enrollment allows you to skip the entire process of entering/sharing credentials or license keys and cuts down the time of enrollment. 

The feature works for both EMM & Non-EMM devices, that is it can be used with devices where MobiLock Pro has been downloaded via afw#mobilock or where MobiLock Pro has been downloaded from Google PlayStore.
Enrolling through a QR Code DOES NOT skip the permissions page. These device level permissions need to be given manually like earlier.

This tutorial guides you through the process of creating a QR Code configuration & how to use MobiLock Pro client to enrol using QR Codes.

Before You Begin

  1. You have created at least one Android Profile on MobiLock Dashboard.
  2. MobiLock Pro Android client v3.6.0 or above has been installed on device.

How It Works

In brief,

  1. Administrators of MobiLock Dashboard can create QR codes and distribute it to their employees or IT team.
  2. Employees or IT team can download the MobiLock Pro client from Google Play Store and scan the QR Code. Once the QR code is scanned, permissions page is shown directly.

Create a QR Configuration on MobiLock Dashboard

  1. Once you are logged into Dashboard, navigate to Device Enrollment > QR Code.
  2. Click on CREATE.
  3. This will open a Dialog where you need to do the following,
    1. Enter a Configuration Name.
    2. Choose either a Device Group OR an Android Profile OR an Apple Profile.
    3. Specify a Device Naming Convention that will be used to auto-generate device names.
  4. For this demo, Enter a Configuration Name, choose the Android Device Profile that you have created earlier an a naming convention. Once you have entered the details, click SAVE.
  5. Once the configuration is saved, it will appear in the list. A configuration has the following things,
    1. QR Code - That can be used to scan using the MobiLock Pro client v3.6.0 and above.
    2. Enrollment URL - This is not required for Android devices at present.
  6. The additional actions on a Configuration are,
    1. Download - This will download the configuration file that can be used to auto-enroll Android devices, by copying them to /sdcard/.
    2. Email - This will send an email to your account with QR Code and the details on how to set up.
    3. Edit - Helps you in editing the Configuration. Note that editing won’t impact the devices that are already enrolled.
    4. Deactivate - If you no longer wish to use this configuration or think it is compromised, then you can deactivate the config.
    5. Rotate - If you think that the configuration is compromised, you can use this option. This will generate a new QR Code and URL. Note that the previous QR Code and URL will no longer be valid.

Steps on MobiLock Pro Client

If you are setting up the device using afw#mobilock, please refer to the guide here. If you have downloaded the client from Google Play Store or installing directly via MobiLock apk, then follow the below steps.
  1. Install the latest MobiLock Pro Client
  2. Open the QR Code image or view it on Dashboard, clearly.
  3. Launch MobiLock Pro client.
  4. Click on Enroll button and select Scan QR Code
  5. You would be shown a Camera View. Point this Camera to the QR Code on your screen so that en entire QR Code fits in the frame and can be scanned.
  6. If the QR Code is valid and your account has valid licenses, then the device will login and show you the permissions screen.
For devices that are enrolled using afw#mobilock, after the MobiLock Pro app is launched, a Camera view will be shown directly so that the QR Code can be scanned.
Once on the QR Code scanning screen on device, the options to on-board the device using Sign-In credentials and/or License Key can be accessed by clicking on the 3 Dots Menu and switching to the landing page.

How did we do?