Enrolling Corporate-Owned Android Devices

The first step to manage your corporate owned Android device, is to enroll it in MobiLock dashboard. MobiLock offers quite a few mechanisms to enroll your corporate owned devices. Here is a list of options, the prerequisites and the description on when to use them,

In this guide we will see how to enroll an android device using Sign In credentials and using a QR Code. We will also look at how to onboard a device using afw#mobilock and then use a QR Code to complete enrollment.

Enroll using Sign In Credentials

Before you Begin

  1. Valid Sign In credentials that are used to sign-in to Dashboard.
  2. An Android device running 4.0 and higher.

Visual Guide

Please watch the video below for a quick visual walkthrough.

Steps

  1. Install MobiLock Pro client from Google Play Store or install the MobiLock apk directly.
  2. Launch MobiLock Pro client.
  3. Click on Enroll
  4. From the options menu, select Sign In.
  5. Enter your Email ID and Password in the respective text input fields.
  6. Click Sign In. You will be asked to give MobiLock Pro the permissions to make and manage Phone calls. Click on Allow.
  7. If the credentials are correct, then the device would sign-in and show you the Device Name screen. Enter a name for your device and click Submit.
  8. If you have created a Device Group or Device Profile on MobiLock dashboard, then you can enter the group key or select the profile.
    If you don't want this device to be a part of any group or profile, you can select Skip.
  9. You would be shown the Permissions screen. The permissions are divided into 3 sections,
    1. Mandatory Permissions: Clicking on the toggle button next to each of the permission will take you to a system screen, where among other applications you would see MobiLock Pro. Enable MobiLock Pro for each permissions and hit the back key to come back to permission screen. Click Next once you have given all permissions and see green ticks next to each one.
    2. Runtime Permissions: These are the run-time permissions and are required for an optimal Kiosk/Agent experience.
    3. Set MobiLock Pro as Launcher: This option is shown if MobiLock Pro is set to run as Kiosk which is the default (and only) option as of today. Click on the Setup MobiLock Pro button and from the list of options select MobiLock Pro as the launcher and select Always.
  10. That should be it. If all steps are completed properly, then you should see the MobiLock home screen with all the applications that you have allowed from Mobilock Dashboard.

Enroll using QR Code

Before you Begin

  1. A QR Code created using Device Enrollment > QR Code option in MobiLock dashboard as described here.
  2. An Android device running 4.0 and higher with camera.

Visual Guide

Please watch the video below for a quick visual walkthrough.

Steps

  1. Install MobiLock Pro client from Google Play Store or install the MobiLock apk directly.
  2. Launch MobiLock Pro client.
  3. Click on Enroll
  4. From the options menu, select QR Code.
  5. Scan the QR Code by placing it between the markers shown on screen. If the QR Code is valid & scanned properly then the device would sign-in.
  6. Once the device signs in successfully you would see the Permissions screen. The permissions are divided into 3 sections,
    1. Mandatory Permissions: Clicking on the toggle button next to each of the permission will take you to a system screen, where among other applications you would see MobiLock Pro. Enable MobiLock Pro for each permissions and hit the back key to come back to permission screen. Click Next once you have given all permissions and see green ticks next to each one.
    2. Runtime Permissions: These are the run-time permissions and are required for an optimal Kiosk/Agent experience.
    3. Set MobiLock Pro as Launcher: This option is shown if MobiLock Pro is set to run as Kiosk which is the default (and only) option as of today. Click on the Setup MobiLock Pro button and from the list of options select MobiLock Pro as the launcher and select Always.
  7. That should be it. If all steps are completed properly, then you should see the MobiLock home screen with all the applications that you have allowed from Mobilock Dashboard.

Enroll using afw#mobilock

Before you Begin

  1. Enroll for Android for Work on MobiLock dashboard as described here.
  2. A QR Code created using Device Enrollment > QR Code option in MobiLock dashboard as described here.
  3. A completely new or factory reset, Android Enterprise Recommended device. For a full list of devices please check here.

Steps

  1. Switch on the device and select Language and Country.
  2. Power On the device.
  3. Select your language and configure a WiFi. A WiFi connection is needed to download MobiLock Pro client.
  4. When you see the screen asking you to configure GMail account, enter afw#mobilock
  5. Wait for the MobiLock Pro client to be downloaded.
  6. Click Install when prompted.
  7. Once done you should see the MobiLock Pro landing screen, which shows a camera view. In this screen,
    1. You can scan a QR Code if you have created a QR Code Configuration. You can scan a QR Code that you have created on MobiLock Dashboard.To create a QR Code configuration refer this document.
    2. If you would like to setup the device using a License Code or Sign-In credentials, then click on 3 dots menu option and navigate to the start page.
  8. On the Permissions Page, Set MobiLock Pro as Device Owner.
  9. Complete the Setup by choosing to Create an AfW account.
  10. MobiLock Pro performs silent setup in the background to make the device managed, which usually takes 10-15 minutes. You can check the state of the setup by clicking on 3 dots menu and selecting Diagnostics and the AfW Setup card will display the status. 

Frequently Asked Questions

Question: Why does MobiLock ask for permissions?

Answer: MobiLock Pro requires these permissions to give you a fine-grain control on your corporate owned devices. If you would like to know why a certain permission is used please contact our support at support@mobilock.in and we would be happy to elaborate.

Question: Nothing happens when I click on the toggle next to the permission name. What should I do?

Answer: On some devices the permission might not be exposed to third party applications although it is an Android OS standard. A Skip button would appear wherever MobiLock application can detect that the permission is not accessible. Click on Skip to complete setup.

For MobiLock application to work we would require the Usage Stats OR the Accessibility permission. You have to choose between either one of these permissions.

Question: When I try to enable Usage stats permission, i see a error dialog, asking to contact support. What should I do?

Answer: This happens when third party applications are not able to access this permission. You can choose to select Skip on this dialog and then select Accessibility permission. In case you are using Accessibility permission, make sure to test the basic functionality of MobiLock before giving the device to your employees.

Question: On Samsung devices and on devices where I have used the afw#mobilock flow, I don't see the Runtime permissions screen. Is this expected?

Answer: This is expected. On these devices MobiLock app can simplify the enrollment process due to enhanced privileges and hence it attempts to auto-grant the permissions to itself.

Question: Although I am setting up the device for the first time I see that some permissions are already enabled and have green tick?

Answer: This happens because MobiLock app is not able to determine the state of that permission properly. To confirm that MobiLock has indeed the permission, please navigate to System Settings and verify that MobiLock indeed has the permission by searching for the relevant permission which has the green tick.

Question: I am trying to enroll a device running Android 4.4 and I don't see all the permissions as shown in video. Is this expected?

Answer: Yes. On Android version less than 6.0, most of the runtime permissions are auto-granted by the Android OS and hence these are not required to be given explicitly.


How did we do?