Versions Compared

Old Version 7

changes.mady.by.user Former user

Saved on

compared with

New Version 8

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

What's new in this release

...

  • 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. 

  • Support for H2 database (DB)
    WSO2 EMM by default will work with the H2 DB and not MySQL database. If the database files do not exist, then WSO2 EMM will create the database. This is beneficial to end users as they will be able to start WSO2 EMM without configuring the database.

  • Ability to login using the username
    In previous WSO2 EMM releases the user had to always use his/her email address as their username to login as opposed to using a username itself. In this WSO2 EMM release, by default users will be able to login to WSO2 EMM using their username. The username will be unique for each tenant. Therefore, if the username is present in more than one tenant, the user will have to select the tenant that he/she has been registered under. For more information, Accessing the EMM Consoles.
     

  • 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.
     
  • Support for multi-tenancy
    WSO2 EMM supports multi-tenancy. Thereby, multiple tenants will be able to share WSO2 EMM; while, being able to maintaining their own customized settings.
     
  • Improved API security
    The APIs that are exposed to the devices have been secured in WSO2 EMM using OAuth.
     
  • Consistency in keystore password
    Previously, the passwords used for CA, RA and wso2mobilemdm.jks were different. However, to maintain consistency across the entire WSO2 platform, the keystore passwords have been changed to wso2carbon. 
     
  • 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.

...

For the list of known issues, go to WSO2 EMM 1.1.0 - Known Issues.

Fixed Issues

For the list of fixed issues, go to WSO2 EMM 1.1.0 - Fixed Issues.