Unlock

Unlocking the device passcode is supported as follows:

Table 1. Support for unlocking the device passcode on Android devices

Android Enterprise device

Prior to Android 7.0

Android 7.0 through the most recently released version as supported by MobileIron

Work Managed Devices

Supported

Supported

Work Profile Devices

Supported

Not supported

Work Profile on Company Owned Devices

N/A

Not supported

Android (not using Android Enterprise)

Supported

Not supported

Unlock is not supported because these versions of Android do not allow a command to change the device passcode.

Procedure 

  1. Go to Device & Users > Devices.
  2. Select the check box for the device.
  3. Click Actions > Unlock.

Unlock behavior on Android:

  • The Unlock command causes Mobile@Work for Android to attempt to remove the existing passcode from an Android device. If the attempt is successful, the user will be able to access the device with the default Swipe.
  • On devices with Mobile@Work, the default passcode is always set to 0000.
  • If the Administrator forces a password reset, the Mobile@Work client itself will try to unlock the device, if possible, or the user can unlock the device using the default password, 0000. The user is forced to change that password to one that conforms to password requirements defined in the Security policy. This applies to devices in:
    • Device Admin or Device Owner modes using an OS older than Android 7 through the most recently released version as supported by MobileIron.
    • Managed Device with Work Profile (COPE) mode (Android versions 8-10 only) and Work Profile on Company Owned Devices mode (Android 11 through most recently released version as supported by MobileIron.)
    • Profile Owner supporting Work Challenge using Android 6 through the most recently released version as supported by MobileIron. Device user of Android 6 device in Profile Owner without Work Challenge support may unlock with “0000” (the default) password, but is not forced to change the password.

  • The passcode reset flow would only be triggered when the profile/device is locked. If the administrator sends a "Unlock" command and the profile is not locked then Core will not reset it to 0000 and not bring up the password reset screens. Otherwise, the only time Core will reset to 0000 and bring up the reset screens would be when the profile or Android device is locked. This is applicable to Mobile@Work 11.1.0.0 through the latest version as supported by MobileIron and to the following Android Enterprise modes:

    • Device Admin mode (on some devices)

    • Device Owner mode

    • Work Profile mode

    • Managed Device with Work Profile mode

    • Work Profile on Company Owned Device mode

  • Android Enterprise Work Managed mode-registered devices that are in kiosk mode move out of kiosk when you send the UNLOCK command from Core. This only happens when the password is mandatory as per the Security Policy on Core.
  • For Android Enterprise devices, see Unlocking an Android Enterprise device.