I frequently get this question from customers and partners: “How can I control Application and OS Updates in iOS and Android“. So I’ll drop a note here.
Update management includes:
- Configuring the behaviour of OS upgrades (major), patches, public apps (via App/Play Store, VPP) and private apps (via App/Play Store or directly via EMM)
- Scheduling updates to happen (or NOT happen) at specific times For example, do not update between 8AM and 6PM, when the user is working.
- Manually pushing or rolling back an update to a single device or group of devices (troubleshooting, 0day immediate security patch etc)
- Controlling the visibility of update to the user, or blocking an update to specific devices altogether (known compatibility issue with business/mission-critical apps)
- Version control: i.e. upgrade to version X, not just to the latest version available. A very common case with public app stores.
- Pre-release support: alpha/beta users, multiple adoption rings.
- Controlling the updates delivery to that they only happen on Wi-Fi, or on Cellular.
- Granular control of all of the above per device group/type, per user group/name/type, per app etc.
- Controlling user ability to influence any of the above (allow costly cellular updates, defer/deny critical updates, update manually to an unsupported OS version etc)
Suddenly, things are not that simple, are they? Long story short, the winner is BY FAR the …Windows 10! 🙂 Watch the video on managing Win10 Updates with UEM here (tech and WorkspaceONE implementation and design/philosophy – much recommended). Now, let’s go back to iOS and Android an see what have we got there.
NB: This info may become out of date when new OS capabilities are released. If you notice anything outdated – leave a commend and I’ll update the post.