I guess because of this article: https://support.isafe-mobile.com/en/support/solutions/articles/77000502716-wie-mache-ich-ein-update-an-meinem-ger%C3%A4t-mit-android-10-
that those devices are working like consumer devcies.

So you can setup a system update policy (automatic, windowed or postpone updates) but nothing more.
This takes always the risk getting a oem update causing issues. Depending on your use case this can be very critical.

What you can do in advance is to block the relevant apps (application run control) which are responsible for detecting the upgrades on entire fleet but keep some test devices out.
Those test devices get automatic updates and you can check them daily (or create a notification mechanism via Signal policy (or legacy alert rule)) and if they get a new firmware, test it and diable the blocking of the apps mentioned before until they receive that update. To be honest: I really don't like that way and it needs to be tested carefully as it could happen that if you block such apps they may not enable themselves after unblocking or getting the device unstable or so.

Another possibility is to block such updates on network side (if possible) but you need some devices detecting them as you need to get to know if there are new ones available or the vendor will announce you about that (our experience is that this nearly never works as you most likely see it on your devices before the vendor tells you).

So, as long as the vendor doesn't provide a similar system for oem updates like E-FOTA or Zebra's way with direct file handling or so, there's no way to take real good control of it.

We have been using the iSafe IS530 for 4-5 years now and I can confirm what Rafael & Matt are saying.

Did not find any way to block OS updates, mind the Android 13 update with a lockdown/kiosk mode installed on the device. This as we found out the hard way that package names changed in A13.

User installed the A13 OS update and could not use the Phone app, the name of the package change.

Updates are pushed monthly and must be accepted/installed by user.

Thanks Rafael, Matt and Onno for responding to the post, your expertise and willingness to help are greatly appreciated!

Has your query been resolved? If this post did not assist you in resolving the issue completely and you have additional questions, please do not hesitate to reach out or you can contact SOTI Support (support@soti.net) to open a new case and one of our support engineer will be there to assist you.

Kind Regards,

Technical Support | SOTI Inc. |1.905.624.9828 | support@soti.net | www.soti.net |