Release Notes for 10.90

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

Portal

Support to import and export MDM policy settings in the MaaS360 portal >>

Administrators can now seamlessly export MDM policies from one MaaS360 account and import them into another. This feature makes it easier for customers handling multiple MaaS360 sandbox and production accounts for different business units to maintain uniform policy settings across all accounts.

Extended the Notify action in Security Dashboard to Windows devices >>

MaaS360 makes the Notify action available for Windows devices, allowing administrators to send notifications about risk incidents to these devices from the Security Dashboard. In the previous releases, MaaS360 added the Notify action support for Android and iOS devices.

Android

Granular reporting for Kiosk mode status >>

MaaS360 introduces granular reporting for Kiosk mode status. The Device Summary page now displays detailed kiosk failure states from both the MaaS360 agent and kiosk apps. The newly added kiosk state labels provide a clear distinction between kiosk failure states (Error: Download failed) and kiosk exit states (Exited: via Admin action). Administrators can use Advanced Search to filter devices based on these new kiosk states. Additionally, MaaS360 enhances logging to enable administrators to collect detailed failure state information from affected devices. This update addresses multiple defects in devices, where either the Kiosk mode was not applied, or devices exited Kiosk mode upon reboot. Furthermore, MaaS360 evaluates kiosk status during every policy evaluation and attempts to reapply kiosk settings in scenarios where the kiosk exits randomly without a known reason.

Advantages:

  • Collects precise failure state information for quicker and more accurate troubleshooting.
  • Provides better awareness of the exact kiosk status on devices.
  • Saves time in reviewing kiosk-related issues.

Note: The device groups created with the old Kiosk mode status in your MaaS360 account are no longer valid. For example, in the new enhancement, MaaS360 has divided the Exited state into granular states. Therefore, administrators must redefine advanced search conditions based on the new Kiosk mode statuses.

Android 14 zero-day support >>

MaaS360 announces zero-day support for Android 14. With this support, new Android 14 devices that are enrolled in MaaS360 and existing devices that are upgrading to Android 14 continue to work seamlessly without disruption. MaaS360 ensures that both IT and end-users can take advantage of the new features that are built into Android's updated operating system from the day of release.

Behavior changes

When MaaS360 runs on Android 14, there will be behavior changes that impact some of the features in the MaaS360 app.
  • Schedule exact alarms permission is denied by default >>

    SCHEDULE_EXACT_ALARM is no longer pre-granted to apps targeting Android 13 and higher. If an existing app already had this permission, it'll be pre-granted when the device upgrades to Android 14. MaaS360 introduces a new tab New Permissions which displays the permissions required by the new version of the MaaS360 app. When users upgrade to MaaS360 for Android app version 8.30, the MaaS360 app now presents the list of mandatory permissions, including Alarms & reminder, enabling users to easily view and grant the permissions required by the MaaS360 app.

  • Discontinued support for new Device Admin enrollments >>

    Starting from Android OS version 14, MaaS360 discontinues support for Device Admin enrollments. If users try to enroll Android 14 devices in Device Admin mode, MaaS360 will display an error message and block the enrollment process. However, devices that are already enrolled in Device Admin mode will continue to function properly when they are upgraded to Android 14.

Apply custom wallpaper and lock screen configuration for shared devices >>

MaaS360 automatically applies the wallpaper and lock screen configurations from the default Android MDM policy when the shared device is in a selective wipe or signed-out state. Administrators can leverage wallpaper and lock screen configurations to show contact numbers or custom text, such as sign-in instructions. In the previous releases, MaaS360 removed all configurations including the wallpaper and lock screen configurations from the shared device on selective wipe and sign-out.

Simplified Android Enterprise integration in MaaS360 >>

MaaS360 adds minor user interface enhancements to the Mobile Device Management service, making it easier for administrators to set up Android Enterprise in the MaaS360 Portal. Once linked to an Android Enterprise account, MaaS360 indicates the connection status with a Connected label with a green tick mark. If administrators want to disconnect the Android Enterprise account, they can click the Discontinue button instead of clearing the Enable Android Enterprise Solution set checkbox.

Enhanced Reset Passcode Interface in MaaS360 Portal >>

When resetting the passcode through the device-level Reset Passcode action, MaaS360 displays the Passcode Complexity level for Android 12+ devices. This enhancement allows administrators to set the passcode based on the passcode policy settings that are currently applied to the devices.

iOS

iOS 17 zero-day support >>

MaaS360 announces same-day support for iOS 17. With this support, new iOS 17 devices enroll with MaaS360 and existing devices upgrading to iOS 17 continue to work seamlessly without any disruption.

Advanced iOS supervised policy settings >>

MaaS360 introduces new supervised policy settings and deprecated some of the existing policy settings for iOS 17 devices.

New DEP enrollment Skip Items >>

MaaS360 adds new Skip Item panes in the Add Profile workflow of DEP (Device Enrollment Program). Administrators can now customize the enrollment process by letting users skip the Safety, Intended User, and Terms of Address panes.

Enhancements to the Push OS Update command >>

MaaS360 added new features that simplify the OS update process and ensure that devices are always running the selected OS version with the necessary security enhancements.

MaaS360 adds the Latest Version option in the Select OS Version menu for the group action. When this option is selected, MaaS360 automatically deploys the most recent OS version applicable to each device model. In the previous releases, administrators had to manually identify and apply the latest OS version that was compatible with each device model.

Deploy Rapid Security Responses (RSR) through MaaS360 Portal >>

Administrators can now use the Push iOS Update action to remotely deploy Rapid Security Responses (security patches) to iOS devices. When deploying OS updates, MaaS360 displays the complete list of software versions and RSR versions that are currently supported by Apple.

Note: The Rapid Software Response (RSR) versions are displayed in both device level and group actions. New Rapid Security Responses are delivered only for the latest versions of iOS and are compatible only with the corresponding base OS versions.

Certificate-based authentication for the Extensible Single Sign-On Kerberos >>

MaaS360 now supports certificate-based authentication for the Extensible Single Sign-On Kerberos. To perform certificate-based authentication, administrators must select a user-level certificate template in the Identity Certificate field in the Kerberos Extensible Single Sign-On policy settings. If administrators do not select a certificate, MaaS360 uses credential-based authentication wherein the users are prompted to provide the username and password of the user.

Prerequisite: User certificate templates must be configured on Cloud Extender.

macOS

macOS 14 Sonoma zero-day support >>

MaaS360 announces same-day support for macOS 14. With this support, new macOS 14 devices enroll with MaaS360, and existing devices upgrading to macOS 14 continue to work seamlessly without any disruption. MaaS360 also adds new policy restrictions that are introduced with macOS 14 Sonoma. For a detailed list of macOS 14 functionality restrictions, see macOS 14 Sonoma restrictions.

Enhancements to the Push macOS Update command >>

Administrators now have more control over updating macOS devices to specific versions. Instead of automatically updating to the latest OS version, administrators can now select the desired macOS version from available options in the MaaS360 portal. Additionally, MaaS360 introduces the Latest Version option in the Select OS Version menu for the group action. This option automatically deploys the most recent macOS version applicable to each device model.

Note:

  • The device action displays OS versions based on the device's current macOS version and model number. For the group action, MaaS360 presents a static list of macOS versions currently supported by Apple.
  • MaaS360 does not install the macOS version if it is incompatible with the device model or if the device is already running a newer software version.
  • Supported on macOS devices running 11 Big Sur and later.

Enhancements to the Restart Mac command >>

MaaS360 now adds the ability to notify users before restarting the devices. When administrators select the Notify User option in the Restart Device action, MaaS360 notifies the user to restart the device at their preferred time. A forced restart will only occur if the device is at the login window with no logged-in users. The user can dismiss the notification and ignore the request. No further notifications are displayed unless administrators resend the command.

Improved FileVault Recovery Key Management for macOS Devices >>

When a macOS device is enrolled, the device generates a FileVault recovery key which is retrieved by MaaS360. If users forget their Mac login password, they can use the recovery key to unlock the disk and reset their password. However, if the macOS device is wiped or re-enrolled, the existing FileVault recovery key is rendered invalid. To address this issue, MaaS360 now allows administrators to create a smart group of re-enrolled devices with outdated recovery keys and then issue the group-level action Escrow FileVault Recovery Key to regenerate the recovery key for those devices.