What is new in this release
WSO2 Enterprise Mobility Manager (EMM) version 1.1.0 is the successor of version 1.0.1. It contains several enhancements, which are as follows:
First user experience
In the previous WSO2 EMM releases it was mandatory for the users to fully configure WSO2 EMM before being able to run the product. Now, WSO2 EMM 1.1.0 binary pack comprises of a default Android Agent. Thereby, enabling users to seamlessly download and run EMM without any prior configurations. This will allow users to use Android devices to get a better understanding of WSO2 EMM.
Local notification method for Android devices
The GCM server has a limitation on the number of messages that can be sent to the GCM server. However, this new Local notification method for Android devices does not make use of the GCM server. Thereby, the number of messages sent via the GCM will be minimized. Furthermore, the Local notification method does not send the messages via the payload, as it did in previous EMM versions. Thereby, this will minimize the MDM command loss.
Tenant based configuration
The tenant admin will be able to use the Configuration Manager wizard to setup the tenant's general, Android and iOS configuration details. Thereby, this allows each tenant to customize their settings based on their requirements. For more information, see Tenant Based Settings.
Ability to change password
Previously, users were not allowed to change the default password that was assigned by WSO2 EMM. However, now users are allowed to change their password. Thereby, users will be able to change their default password to a password of their choice.
Removal of devices from WSO2 EMM
Previously, administrators were not allowed to remove devices from WSO2 EMM after they were enrolled. However, now the administrators can use the Enterprise Wipe feature to remove enrolled devices from WSO2 EMM. Thereby, this will enable the administrators to maintain WSO2 EMM efficiently.
Improved API security
The APIs that are exposed to the devices have been secured in WSO2 EMM using OAuth.
Improved compliance monitoring
When the system is clustered, then using the nTask Component, only one node will be allowed to perform the compliance monitoring that will dispatch messages to the GCM or APNS.
Key Features
- Self-service device enrollment and management with end-user MDM console
- Policy-driven device management for security, data, and device features (Camera, Password Policy)
- Deploy policies over-the-air
- Compliance monitoring for reporting, alerting, and device deprovisioning
- Role based permissions for device management
- Provisioning and deprovisioning applications to enrolled devices
- Blacklisting of applications for Android
- Supports App management
- App approval process through a lifecycle
- Discover mobile apps through an Enterprise App Store
- Self-provisioning of mobile apps to devices
The full feature list is available at http://wso2.com/products/enterprise-mobility-manager/