Forcing OS updates on your fully managed Android devices in a defined window of time.
The aim is to establish an homogenous OS version landscape, and to support users who may not always think about installing OS updates themselves. With an appropriate policy, you can roll out available OS updates in a coordinated manner, keeping your fleet of Android devices up to date.
Under Administration→ Devices→ Details you will see a reminder whenever an update is available for a device (example for Cortado MDM):
Under Administration→ Policies you can now force the available update to be installed onto the users’ devices.
- Click on the plus icon to add a new policy.
- Then select Android and select the Fully Managed Device enrollment method.
- There you will find the OS Updates policy. Enable the policy by clicking Enable restrictions (upper arrow in illus.).
- Let the radio button at Force installation.
- Install the update between (local device time): Enter here the time at which the update window should open and close (middle arrow in the illus.).
- Delay the installation by (30 days maximum): Here you can enter a value for the number of days (0-30) you would like to delay the forcing of updates. Enter the number 10, for example, and the installation of a new update will be forced 10 days after the update becomes available (lower arrow in illus.).
Note! Force automatic OS Updates forces an update when one is available for the corresponding device class. A confirmation from the end user is not requested. The update is downloaded and then installed.
In practice, it makes sense therefore, to run the OS updates when the device is least likely to be in use.
Note! Avoid an update window from 22:00 to 04:00, for example. There is a chance that the device may not cope with the value of the start time being greater than the value of the end time.
- Now select the new policy (upper arrow in illus.) click on Assign (lower arrow in illus.) to assign it to the desired users/group templates/devices.
Warning! Especially if you are using legacy apps, you should absolutely ensure beforehand that the apps are suited to new Android versions. You should also inform yourself of any known problems with the new Android version. It may make sense to increase the Delay days value mentioned above. We recommend that you familiarise yourself with this feature before you roll it out on a broad scale. Configure and roll out this policy for a test group first, to determine whether the recommended settings are suited to your requirements.