MaaS360 Cloud 10.67 Release Summary

Content

iOS / macOS MDM

iOS 11.3 enhancements >>

MaaS360 announces following iOS 11.3 enhancements:

>> Enable authentication for autofill

This restriction enforces Face ID authentication on iOS 11.0+ devices before autofill of password or credit card information action happens in Safari browser or Apps. This function is supported on iOS devices with face identification support.

>> Configure delay for software updates

This restriction forcefully delays device software updates on iOS 11.3+ devices for the number of days the restriction is applied. User visibility to software updates is restricted.

>> Option to skip privacy screen setup during the addition of DEP profile

The following screen setup can be skipped during iOS 11.3+ DEP device enrollment. Home Button Sensitivity, Privacy, OnBoarding, Touch ID settings, and ToC is renamed as Terms and Conditions are included in Skip Setup Items list during the addition of new DEP profile.

>> Option to skip proximity setup during device wipe action

MaaS360 provides Disable Proximity Setup on next reboot setting in device wipe action. This setting disables support for automatic setup on iOS 11.3+ devices. Automatic setup is Apple feature that helps set up your new iPhone 8 / iPhone 8 Plus / iPhone X, by just holding your new Apple device near an iOS 11.0+ device you already own.

Delete Apple School Manager (ASM) data from MaaS360 portal >>

MaaS360 introduces support to delete synced Apple School Manager (ASM) data from MaaS360 application portal. Contact IBM MaaS360 Customer Support team to request deletion of synced ASM data from the portal. On completion of ASM data deletion, ASM integration with MaaS360 is disabled by default and if needed, customer administrator might manually enable ASM integration from the MaaS360 portal.

Auto naming for DEP devices displays detailed model name >>

MaaS360 extends capabilities to display detailed model name for auto naming enabled DEP enrolled ioS devices. Previously, the model name displayed device model such as iPhone, iPad, iPadAir. From this release, the model name includes specific details of device model such as iPad 7, iPhone 6 Plus., hence allowing display of more meaningful model names.

Device custom attributes support for iOS policy settings >>

MaaS360 extends support for including device custom attributes as placeholder values in iPCU settings and anywhere with %attribute_name% in iOS policy. 

Configure cellular roaming settings by using Web Services API >>

MaaS360 introduces Web Services API function to configure cellular roaming settings for an iOS device. This function is in addition to the existing iOS policy settings for configuring cellular roaming profile from Advanced Settings > Cellular in an iOS policy. Customers can invoke APIs that are specific to cellular roaming settings and configure data roaming and voice call roaming settings for an iOS device. MaaS360 support for configuring cellular roaming settings by using iOS policy remains unaffected by this functionality.

AirPrint printer configuration for macOS >>

MaaS360 extends configuration of AirPrint printers from iOS to macOS MDM devices. New attribute that is called AirPrint is added under Configuration setting in macOS MDM policy. The function allows devices that are connected to the same network to print over the air via Wi-Fi.

Swedish language support on macOS agents >>

Hej, hur mår du. MaaS360 adds Swedish language support for MaaS360 App Catalog, Packager, and macOS agent.

Static password support for macOS WPA/WPA2 (Enterprise) Wi-Fi profile >>

MaaS360 extends static password support for macOS WPA/WPA2 (Enterprise) profiles. In the previous releases, the support was only available for iOS policies. With this support, when the policy reaches the device, macOS devices automatically gain access to corporate Wi-Fi network without authentication.

New restrictions added in macOS System Preferences >>

MaaS360 adds two new restrictions such as TouchID and Wallet & Apple Pay settings. You can enable these settings from macOS MDM policy > Restrictions > System Preferences.

New alerts for VPP and DEP in MaaS360 My Alert Center >>

MaaS360 adds new alerts for VPP and DEP services to notify customers about VPP or DEP client context mismatch and DEP T&C validity expiry. These alerts are displayed in My Alert Center in the MaaS360 portal home page. The alerts are included in addition to the existing VPP and DEP alerts for token expiry.

Locked profiles for iOS support is disabled in MaaS360 instance >>

MaaS360 announces the end of life for MaaS360 Security Profile (Locked Profile) for iOS support in MaaS360 M1 instance. This support withdrawal impacts only for those customers with Locked Profile for iOS support enabled for their MaaS360 accounts. During enrollment, an additional profile was being pushed along with MDM profile if Lock Profile for iOS support was enabled for the customer account. With disablement of Locked Profile support from 10.67 release, this function is no more allowed for a customer account. Note: For those profiles that are added until this release, it remains unaffected by this function disablement.

Android

Support for Chrome OS (Chromebook) device management >>

MaaS360 announces a partnership with Google to manage Chrome OS devices alongside other endpoints in an enterprise from a single unified management solution. With this support, administrators can easily enroll Chromebooks into MaaS360 portal via Google admin console. MaaS360 also leverages Google APIs to allow the administrators to enforce security policies on Chome OS devices.

Note: This feature is beta at this moment. Please contact MaaS360 support in order to enable this feature.

Trusteer Threat Management enhancements >>

MaaS360 adds support for enforcing the Trusteer Threat Management policies through Persona policies for mixed mode (MDM+SPS) customers. 

Dual SIM card reporting >>

If a dual-SIM card device is enrolled, the MaaS360 agent now reports network information pertaining to both the SIMs to MaaS360 portal. With this support, MaaS360 also allows the administrators to search a device by its secondary SIM ICCID and IMEI numbers. 

Support for auto-renewal of certificates for secondary accounts >>

MaaS360 adds support for automatic certificate request and renewal support for secondary accounts. With this support, the MaaS360 agent automatically sends a certificate request and renews the certificates in the background. Previously, the secondary accounts had to be re-configured on certificate expiration.

Platform

Web Services API for Device Group refresh action >>

MaaS360 introduces API for Device Group refresh action in addition to the existing Refresh action in the MaaS360 portal user interface (UI). The API when invoked, performs the same action as existing refresh action on the UI. From this release, a total number of 500 refresh attempts are allowed for a customer account for a day (based on UTC time format). This limit count of 500 is inclusive of both API and UI refresh actions.

Auto-provisioning enhancements for portal administrators account- phase II >>

MaaS360 enhances sync process between the corporate directory and MaaS360 portal for auto-provisioned administrator accounts. The enhancement includes an asynchronous method of fetching portal administrator account status from Active Directory (AD) by using Cloud Extender 2.94 module. This module offers periodic checks and deactivates any auto-provisioned account if the user account is no longer in AD or not included in an auto-provisioned group.

Search by Platform Serial Number in Global Search >>

MaaS360 adds support to search devices by Platform Serial Number device attribute in Global Search in addition to other search parameters that Global Search currently supports. Search by Platform Serial Number is supported only for Android and iOS device platforms.

End User Portal (EUP) enhancements >>

MaaS360 provides resolution for End User Portal (EUP) error that occurs when a user tries to reset new login password by using 'Forgot Password' link. Previously, users had to contact an administrator to reset the password. The fix that is provided in this release is applicable only for user accounts with auto-generate user password settings.

Revamped user experience when inviting additional administrators >>

MaaS360 introduces an upgrade to invite user forms based on new user experience design. These forms are replacing the existing forms that are used by a new portal administrator to signup to an IBMid for getting access to a MaaS360 subscription. In this scenario, if a  new administrator does not previously have an IBMid, the administrator receives an invite email with a URL. This URL can be used for signing up to an IBMid before accessing MaaS360 account.

Enhancements to retrieve MaaS360 login credentials >>

MaaS360 enhances username and password retrieval method for portal login. If customers forgot MaaS360 login credentials, it can be retrieved by using the instructions sent to their registered email address. This function is supported only for customer accounts that use MaaS360 credentials for authentication mode. This function is not supported for AD, LDAP, SAML, and IBMid authentication methods. Previously, only password retrieval was supported and to retrieve username, customers had to contact IBM MaaS360 Customer Support team.

MaaS360 also launches a single URL login.maas360.com that customers can use to login to MaaS360 account irrespective of MaaS360 instance in which the customers hold an account.

Single page for configuring MaaS360 Settings >>

MaaS360 introduces a single Settings page that allows customers and partners to easily access MaaS360 settings from one location under Settings page. The following settings are accessible from Settings page for customers: Device enrollment settings, User settings, App Settings, Doc settings, and Administrator settings. Partners can manage these settings for customers accounts under them. To avail this capability, MaaS360 customers and partners need to be on the new user interface.

Partners

MaaS360 partners get new user interface for application portal >>

MaaS360 extends new user interface (UI) for application portal to partners. In the previous release, this feature was limited to customer accounts. All new MaaS360 partners get new UI by default. Existing MaaS360 partner accounts that are created post 10.66 release gets old UI by default with an option to toggle between old and new UI from the portal. New customer accounts created post 10.66 under any partner account, continue to remain on new UI with no toggle option and pre 10.66 customers continue to get toggle option between new and old UI.

Windows

Support for Microsoft HoloLens device management >>

MaaS360 announces a partnership with Windows to manage HoloLens devices alongside other endpoints in an enterprise from a single unified management solution. With this support, administrators can easily enroll Windows HoloLens devices into MaaS360 using the normal enrollment workflow. MaaS360 also leverages Windows APIs to allow the administrators to enforce security policies, compliance riles, and device actions on HoloLens devices.

Support for new device-level action on Windows 10 devices >>

MaaS360 adds new device-level action to allow the administrators to upgrade licenses and change product key on Windows 10 devices.

Cloud Extender and MEG 2.94

Support for multiple Cloud Extender masters in an Exchange environment (both On-Premises Exchange 2010, 2013, 2016 servers and Office 365 servers) >>

The Cloud Extender 2.94 release removes the functionality that only allowed the administrator to designate one master Cloud Extender in an Exchange environment. Multiple Cloud Extenders now collaborate through a shared data area to determine which Cloud Extender becomes the master. This new functionality eliminates any issues that an administrator might encounter with misconfiguring a designated master Cloud Extender, since configuration is done in the background.

MEG syslog integration with IBM Security QRadar >>

IBM Security QRadar can now collect MEG gateway authentication and resource logs via any configured syslog server.