Here’s a short summary of the new features and improvements released today.
Custom policy configuration for Windows 10 devices
In addition to built-in configuration profiles, you can now customize or extend the management capabilities of Windows 10 devices by creating custom configuration service provider (CSP) policies in Miradore. With the custom policies, you can allow or deny actions on a device and define its behavior and appearance. For further details, see Custom policy configurations for Windows 10.
Android system update management
We added two new Dashboard widgets for checking the status of system updates on your Android devices. With the widgets, you can now see which of your Android devices have (or have not) installed the newest system update. For more details, see How to check your devices' Android version, security patch level, and the availability of system updates.
In addition, we released a new configuration profile called "System update policy" for customers with the Premium plan. With the Android system update policy, administrators can control the installation of system updates remotely. They can, for example, specify a maintenance window during which the devices are allowed to install the updates without user interaction. For further details, see Android system update policy.
Please note that Android system update management requires Miradore Android Client 2.9.0.
Resolved issues and minor improvements
- As we reported recently in our knowledge base, device unenrollment didn't remove the Android work profile although Miradore's user interface stated that the unenrollment was successful. We have fixed the problem in Miradore Android Client version 2.9.0.
- Application update policy failed on some Android devices stating "failed to get device via EMM API".
- Miradore couldn't push managed app configurations to Android devices if the configuration contained multi-select data.
- Miradore now reports a configuration profile deployment as failed if the device's Android Client is too old to support the profile. Previously in this kind of situation, the deployment got stuck in Waiting status.
- The Merge devices action didn't set the retired date for the device.
- The Retire action was not available for iOS devices currently in lost mode, now it is.