Release Notes for 10.91

List of features and enhancements that are introduced in MaaS360 Cloud version 10.91.

Portal

Support to enable non-GMS device management through the MaaS360 portal

MaaS360 now allows activation of non-GMS/Android Open Source Project (AOSP) device management through the MaaS360 portal. This feature eliminates the need for contacting support and simplifies the process of managing these devices alongside GMS-enabled devices. To activate non-GMS device management, navigate to MaaS360 Portal > Setup > Services > Mobile Device Management and then select the Enable non-GMS/AOSP device enrollment option. It is enabled, administrators can enroll non-GMS devices, apply device management policies, send remote actions, and manage devices directly from the MaaS360 portal.

Enhancements to the email templates for License Management

MaaS360 improves the readability of the email templates that are sent as part of License Management and includes important information such as the Charge Agreement number.

Enhancements to Advanced Search feature for Devices

The Advanced Search functions for devices are enhanced to include a new attribute that is named iTunes Account that tracks the status of iTunes account on iOS devices.

Android

Configure the minimum OS version requirement for Android Enterprise enrollments

MaaS360 now allows administrators to set a minimum OS version requirement for Android Enterprise devices, ensuring that only devices running compatible OS versions are enrolled in MaaS360. When this setting is enabled, only devices running the specified OS version or higher will be able to enroll in MaaS360.

The path to the new setting in the MaaS360 Portal: Setup > Settings > Advanced Enrollment Settings > Advanced Management for Android Devices > Set lowest Android OS version allowed for enrollment.

For more information, see Configuring directory and enrollment settings in the IBM MaaS360 Portal

Automatically allow all apps from the App Catalog in Kiosk for multiple app mode >>

MaaS360 introduces the new Allow all apps from app catalog policy, which automatically allows all apps from the App Catalog to be used in the Kiosk without adding them individually to the App IDs for the allowed Apps policy for each app. The apps from the App Catalog distributed and installed on the devices are displayed in the Kiosk.

Note:
  • The Allow all apps from app catalog policy is deselected by default.
  • This policy setting is available only when the Show custom Home page with allowed Apps option is selected in the COSU Mode Type.

    For more information, see https://www.ibm.com/docs/en/maas360?topic=device-cosu-corporate-owned-single-use-kiosk-mode.

  • The apps from the kiosk policy will be displayed first, according to the policy's order, and apps from the App Catalog will be displayed later at the end of the UI in the Kiosk.

Support to allow/disallow all apps from the App Catalog in App Compliance >>

Previously, apps distributed from the App Catalog were allowed by default in the App Compliance. Configured Allowed Apps is an existing policy setting. This setting only applies to apps installed by users.

In this release, MaaS360 introduces the new Allow all apps from app catalog policy, where administrators can control and allow/disallow all apps from the App Catalog based on this policy.

Note:
  • By default, Allow all apps from app catalog policy is selected.
  • If Allow all apps from app catalog policy is deselected, and the App IDs are configured in the Apps to be allowed policy, then only configured apps are allowed on the device.

For more information, see https://www.ibm.com/docs/en/maas360?topic=cpsaed-application-compliance.

Web services API

The following web services were updated for this release:

  • The Device Basic Search (v2) API is enhanced to include a new parameter that is named itunesStoreAccountEnabled that identifies and returns the status of iTunes account on iOS devices. You can also perform a search on devices based on this parameter.

  • For a License Management enabled customer, the Create Device Enrollment API has been enhanced as follows:
    • If the licenseNames parameter value is not provided while executing the API, the default license configured in the MaaS360 Portal (Setup > Settings > License Settings > Basic > Auto-assign licenses for self-enrollments) will be used to assign licenses to devices during enrollment.
    • If the licenseNames parameter value is not provided and a default license value is not configured in the MaaS360 Portal, then an appropriate error message is displayed to indicate the same.

For more information, see MaaS360 Webservices - Reference Guide.