Mobile@Work features

This topic describes the supported features and other information about the Mobile@Work for iOS and the Mobile@Work for Android clients after migrating the respective devices from Core to Cloud.

For more information about Mobile@Work for Android and Mobile@Work for iOS, see product documentation at https://www.ivanti.com/support/product-documentation.

For the migrated devices, the Mobile Threat Defense features are supported. For MTD-related features, see the Cloud Threat Defense Solution Guide in the Ivanti Support Community at Cloud product documentation.

Starting from release 12, irrespective of whether the Mobile@Work client that is registered in the device supports migration or not-the device can be migrated. For devices that have unsupported Client versions and are migrated to Cloud, the device will be marked as Client Unmigratable in the LUI portal to indicate the unsuccessful migration to the administrator. The administrator can mark the Client Unmigratable devices as Resolved.

Mobile@Work common features

  • The Forgot Password functionality will work only for new devices migrated after Migration Portal R6 release.

  • The user custom attributes will be pushed to Cloud only for new devices migrated after Migration Portal R6 release. The user custom attributes should be re-created in Cloud (via ETL) before triggering migration, otherwise the migration will fail.

Mobile@Work for iOS features

  • Before migrating a device, users must upgrade to Mobile@Work for iOS 12.1.0 (or later versions) for the Forgot Passcode and Reset Passcode features to work. If the Mobile@Work for iOS client is upgraded after the device migration, the features will not work.
  • When a device running Mobile@Work for iOS is migrated from Core to Cloud, the Privacy tab in the Settings menu will be no longer available in Mobile@Work.
  • During the migration of a device from Core to Cloud, if there are any errors, then Mobile@Work will notify the user that the migration failed and will provide the following options:
    • Send Mobile@Work Logs - Contact Cloud Support with the logs for troubleshooting any issues.
    • Exit - Close the client and relaunch Mobile@Work.
  • Post-migration of a device, if the administrator retires the device, Mobile@Work notifies the user that they cannot use this client because it was retired. The user is prompted with the following option:
    • Install Go App - Go to the App Store to install the Go for iOS app.
  • Post-migration of a device, the re-enroll option is not supported in Mobile@Work.
  • Post-migration of a device, if the device is registered with a local user, the local user must reset their passcode. The administrator can either send an email to user or set the passcode directly in the Cloud administrator portal.
  • Post-migration of a device, Mobile@Work for iOS allows AppConnect app authorization to communicate with Cloud. Derived credentials are not supported.
  • Post-migration of a device, if the AppConnect Policy was configured on Core, the passcode is prompted on launching the Mobile@Work client.

  • During the migration of a device, only the configurations are cleared from the system, not the policies. If Cloud fails to send any new or updated policies, then the older policies from Core are enforced on the migrated devices.

  • A new key-value pair migrate_from_email_exchange_host is required to configure the migration of email accounts, and the value should be the previous email_exchange_host key that was set up on Core.

  • The Email+ inbox re-sync can be avoided only for new devices migrated after Migration Portal R6 release.

Mobile@Work for Android features

  • Mobile@Work handles the following device registration settings during the migration of Android devices. Mobile@Work will try migration thrice before reporting error code and message to the Migration Portal. After reporting the error, Mobile@Work displays the error message to the users. During a subsequent check-in, if there is a migration request, Mobile@Work initiates the migration again.

    • Enable Minimum Version

    • Minimum Security Patch Level

    • Manufacturer Whitelist/Blacklist

    • Minimum SafetyNet Certification

  • During the migration of a device from Core to Cloud, if there are any errors, then Mobile@Work will notify the user with a message such as, "There is a severe error while migrating. Contact support with console logs and you may want to reinstall this app."
  • During migration, errors (if any) are reported to the Migration Portal.
  • When a device running Mobile@Work for Android is migrated from Core to Cloud, if the administrator marks the device as retired, Mobile@Work notifies the user that they cannot use this client because it was retired. The user must uninstall the Mobile@Work client and install the Go for Android app from Google Play Store. The user is prompted with the following options:
    • Send Logs - Contact Cloud Support with the logs for troubleshooting any issues.
    • Exit - Close the app.
  • Post-migration of a device, the red logo is displayed on some screens instead of the blue logo. This behavior can be ignored.

  • A new key-value pair migrate_from_email_exchange_host is required to configure the migration of email accounts, and the value should be the previous email_exchange_host key that was set up on Core.

  • For Android Enterprise devices, post-migration of a device, the Email+ app will need to be re-synced to continue receiving and sending email messages. The content in local folders, such as Draft and Outbox, will be removed and no longer available. The inbox should be refreshed for the email list to display.

Resolved issues for Mobile@Work clients

This section includes resolved issues fixed in the current releases of the Mobile@Work clients that are related to the migration of a device from Core to Cloud.

There are no resolved issues in this release.

Known issues for Mobile@Work clients

This section includes known issues found in the current releases of the Mobile@Work clients that are related to the migration of a device from Core to Cloud.

These are the known issues in this release:

  • AC-20296: In some devices, after setting up Work Profile on a device migrated from Work Managed Device mode, the "Device Out Of Compliance" message may be displayed in the UI. As a workaround, restart the device or turn off/on the Work Profile.

  • AC-20278: After setting up and enabling Work Profile on a device migrated from Work Managed Device mode, no container is displayed. Also, the client cannot be launched in personal space. This issue is observed only in Samsung Galaxy S10 and Nexus 9 devices.

Limitations for Mobile@Work clients

This section describes the limitations found in the current releases of the Mobile@Work clients that are related to the migration of a device from Core to Cloud.

There are no third-party limitations in this release.