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
- Retrieve the OS update zip file/package from the OEM
- Navigate to File/Action under Devices > Provisioning > Components > Files/Actions to upload the zip file. Install manifest should contain OS Upgrade action with the uploaded zip file selected
- The zip file needs to be downloaded to Hub's internal storage directory. Use the wildcard $osupdate$ in the file download location, which will find the correct file path regardless of OEM.
- Example: $osupdate$/update.zip
- Add the File/Action to a Product manifest. Configure any other criteria, such as assignment and deployment conditions.
- Hub downloads zip and calls OS upgrade API
- Device reboots into recovery and installs the update (or in case of A/B update, device simply reboots into new version when ready)
- Hub performs post-update validation to ensure the new build got installed
- Hub will also update the build number Custom Attribute that gets reported to the 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.
Was this page helpful?