Using bulk enrollment for Android devices

You can use bulk enrollment to register multiple Android devices quickly.

NOTE: See Registration considerations for points to consider before using this registration method.

Before you begin:

  • The Android SDK must be installed on the computer used to register the devices.
  • Enable USB debugging. For more information on USB debugging see http://developer.android.com/tools/help/adb.html.
  • Install Mobile@Work on each device.
  • Use a USB cable to connect the devices to the provisioning computer.

Example adb shell:

$ adb shell am start "mirp://www.example.com%26user=cc%26pin=316940%26quickStart=false"

Sample values include:

Table 1. Sample values for adb shell

Key

Value

user

User name that would have been typed into the username field if using iReg. Required.

pin

Registration Pin. Required.

quickStart
• Set to TRUE: Do not display the splash screen. The Privacy screen is not displayed. The Apps@Work shortcut is not created. On Zebra devices, Device Administration privileges are set automatically.
• Set to FALSE: The user must tap Continue on the Welcome screen to proceed. When quickstart is set to false the user must choose whether to accept Apps@Work shortcut creation, must Acknowledge Privacy policy, and accept Device Admin priviledges. Optional defaults set to FALSE.

Here is an example of a bulk enrollment script:

for i in `adb devices | grep -v devices | grep device | cut -f 1`

do

echo "Registering $i"

adb shell am start "mirp://app183.auto.mobileiron.com%26user=cc%26pin=316940%26quickStart=false"

done

You might receive these error messages when you use bulk enrollment.

Table 2. Bulk enrollment error messages

Error

Resolution

mirp scheme not found

Example mirp scheme:

am start "mirp://app183.auto.mobileiron.com%26user=cc%26pin=316940%26quickStart=false"

 

URL is invalid

Occurs if no data string is sent at all. Verify that the URL is correct.

No server information found

Server information missing or improperly entered.

No user information found

Verify that user key was entered.