Controlling the software updates that are installed on devices
You can control the device software releases that are installed on
Samsung KNOXdevices, and
BlackBerry 10devices. For
Android Enterprisedevices, you can also set an update period for apps that are running in the foreground.
Android Enterprisedevices with
Work space onlyand
Work and personal - full controlactivations, you can specify whether the user can choose when to install available software updates or whether software updates are automatically installed. You can specify different rules depending on the device model and currently installed OS version. For all
Android Enterprisedevices, you can also set an update period for apps that are running in the foreground because, by default, when an app is running in the foreground,
Google Playcan't update it. You can also control how
Google Playapplies the changes to the device, for example, specifying whether the user can allow the change or whether the change occurs only when the device is connected to a
Samsung KNOXdevices, you can use Enterprise Firmware Over the Air (E-FOTA) to control when firmware updates from
Samsungare installed. Controlling firmware versions ensures that users’ devices are using firmware versions that their apps support and comply with your organization’s policies. You can use a device SR requirements profile to create firmware rules for the
Samsung KNOXdevices that are activated on
UEM. You can schedule when firmware updates are installed and specify when forced updates must be installed. For more information about E-FOTA, visit enterprise-fota.
On devices running
BlackBerry 10OS version 10.3.1 or later that are activated with
Work and personal - Regulatedor
Work space only, you can limit which software release versions that
BlackBerry 10devices can have installed using a device SR requirements profile. You can also add exceptions to the global settings for specific device models. For example, you may want to test a software release before making it available to your organization.
On devices with
MDM controlsactivations, you can't control when and how users update their device OS but you can use compliance profiles to restrict a device OS version. For all devices, to enforce a particular action if a restricted software release version is installed on a device, you must create a compliance profile and assign the compliance profile to users, user groups, or device groups. The compliance profile specifies the actions that occur if the user does not remove the restricted software release from the device.
You can't control the software releases installed on
iOSdevices, but you can can force supervised
iOSdevices to install an available update. For more information, see Update the OS on supervised iOS devices.