Interesting questions.

We have tried different methods for patching Zebra devices. We are currently testing patch deployment using a profile with a post-install script that executes the OS update.

We have set up a "patch window" file sync to ensure that we only run OS updates during night.

The filesync rule downloads a file(if its newer) from our Soti server and we use custom data to fetch the information in the file and use it as profile filter,

At 11.45PM a Powershell script on the server changes the file to contain current weekday and Patch=Enabled.

At 5.30AM the script changes the file to current weekday and Patch=Disabled

File sync schedule is at 11:45PM and 5.30AM. 

We have been testing this for a while and are almost ready to run it in production.

Along those lines, does anyone know of a way to limit the attempt of a device to download a package based on IP address or something similar?  Our devices are typically on cell but will be docked into ethernet chargers when not in use.  I'd like to have a filter that prevents download attempt unless on ethernet (or some IP address range)  Anyone had luck with that?

What version of MobiControl are you running? You can restrict updates by battery level as of 13.4 and I think some late maintenance builds of 13.3.  Maybe that could provide the end result you're looking for? I haven't experimented with the setting too much yet but I imagine there is some battery level like -1 or 255 that would indicate that it is currently charging in a cradle. 

Be wary with this property as you only should use it on packages like OSUpdates that you only want to run once and don't care about the unassignment in SOTI. If you were to use a minimum battery level as a threshold for assignment for an APK install for instance then you could run into scenarios where that APK gets automatically unassigned and thereby uninstalled every time the battery gets below a certain level. 

Also, IP range is a Filter Criteria you can use for profile application if you still want to go down that route, but that might be more cumbersome to maintain. 

Same as your original question.  I'm looking to restrict large installs like LifeGuard or full OS packages unless in an ethernet dock.  Running latest (14.1) so that isn't a problem.  I hadn't thought of battery level.  Not sure that is an option though as we will probably have some part of the population that uses the USB cable for charging and thus wouldn't be on ethernet.  Good idea though.  Thanks

You could use the app "OS Manager". It's specifically designed to automatically upgrade OS on Zebra Android devices. It basically replicates the user experience you have on Samsung and iPhone.

I've been through the process of upgrading OS and LifeGuard on Zebra Android devices many times, especially for devices being used in retail. The biggest issues I've seen are offline devices, devices with a low state of charge, devices in use, devices with low WiFi-coverage, distributing information to all users, etc.

So what OS Manager does, it automate the whole process. Users are asked if they want to install now or later. Pressing install now will install the update right away, install later will install the update around 11:30 PM. OS Manager have all kinds of safe guards, including checking state of charge, update-file integrity etc. You can also apply several updates at the same time if needed. 

More information is also available on SOTI Marketplace.

Very cool! I remember seeing this in the App Gallery at some point but then never explored it further. Much appreciated suggestion, I will be giving this a shot very soon.

Not sure what version of MobiControl you are on but as long as I can remember (at least v13 onwards), if you go to the Profile Assign "Options" tab under "Network Restrictions" you can assign a profile to be only available on LAN, Wifi, Cellular, Cellular whie Roaming. 

Hello Matt,

I'm reviving this old topic from you, as I would like to know, after 5y what is your take on this?
What have you learned, seen around and currently use into this process.