Managing Android OS Upgrades with Workspace ONE UEM

Organizations have several ways to initiate OS updates for managed Android devices. Some fo these methods are OEM-specific.

• Push OS Upgrades to Work Managed Android devices Android 10 and higher using Product Provisoining
• Use Samsung KNOX E-FOTA ONE to manage OS upgrades for Samsung devices

You may also set a policy that manages the automatic installion of new Android System Updates made available by your device manufacturer or carrier. For more information on this policy, see How to Configure Android Profiles

OS Upgrades using Product Provisoining

Upgrade Android Work Managed devices remotely with a local zip file through the OS Upgrade File-Action.

This OS Upgrade task applies specifically to Work Managed devices running Android 10.0 or later. If you want to OS Upgrade on Zebra devices, then see Create an OS Upgrade for Zebra Devices, Android 8.0+.

Procedure

1. Retrieve the OS update zip file/package from the OEM.

2. Navigate to Devices > Provisioning > Components > Files/Actions > Add Files/Actions > Android and complete the following:

   • General - Fill the required metadata.
   • Files - Upload the zip file and store under Download Path $osupdate$ such that path reads $osupdate$/<filename_update>.zip (Using $osupdate$ ensures the correct location is picked by the OS for the update file to be stored)
   • Manifest - Choose OS Upgrade action with the uploaded zip file selected.
   • Save.

3. Navigate to Devices > Provisioning > Product List View > Add Product > Android.

   • General - Fill the required metadata. Use smart groups and assignment rules to filter the target devices.
   • Manifest - Pick Files/Action - Install for the File/Action created above.
   • Conditions, Deployment Dependancies - Fill as requirement, refer to other documentionation for details on how to use these features.
   • Save and Publish.

4. Wait for the Hub to download the zip and calls OS upgrade API.

5. Your device reboots into recovery mode and installs the update (or in case of A/B update, device simply reboots into new version when ready)

6. Hub performs post-update validation to ensure the new build got installed.

7. Hub will also update the build number Custom Attribute that gets reported to the UEM console.

Results

After successful validation, product goes to complete/compliant state, and the build number custom attribute for the device is updated to the new version.