Android nightly reboots
As far as I know, there is currently no such feature of scheduled reboot for Android devices in MobiControl.
I have requested Soti more than once in the past few years to add a new feature of supporting scheduled script, but it is still not there.
I'd also like the ability to schedule a script based on some device event like a reboot, wifi disconnect, or battery swap. I know you can use startup scripts with SOTI Lockdown but I'd want the ability to trigger them at startup without having to use the Lockdown launcher.
You are correct that this has not been included in the current versions of MobiControl yet, but can be achieved VIA script and a file sync rule to accomplish a reboot at a particular time.
I have inquired on the status of this feature request and it's plausibility as a new feature in any upcoming versions of MobiControl for you.
I have received a response that "we are aware of the need for this and are evaluating what it will take to introduce this functionality within MobiControl".
Matt, I would suggest filing a case and submitting a Feature Request VIA a Technical Support Specialist to make sure we are aware of the scope of the other useful suggestions for scheduling scripts.
Thank you for your inquiry,
Technical Support | SOTI Inc. |1.905.624.9828 | firstname.lastname@example.org | www.soti.net |
Add a "reset" script command in the pre-script for an Android File-Sync rule and set predefined schedules time for such file-sync operation.
The above approach needs that the device to be on-line at/near the scheduled reset time, during which the script is sent from the server to the device for execution when file-sync operation is "initiated" by the server. When performing reset with such approach, care should also be taken to program file-sync options and rule end-time to make sure unnecessary reset won't be performed (e.g. when an administrator interactively initiate file-sync operation for all file-sync rules on the web-console).
A scheduled script approach does it differently. The script and the required schedule are "pre-pushed" onto the device. As long as the device is not powered off at scheduled time, the pre-pushed script will be executed once by the device agent irrespective of whether the device is on-llne or not, or whether the server is on-line or off-line. There may be configurable options to handle the case whether the script will be executed on power-up if the device was off during the scheduled time.
Thanks. I haven't had a need for File-Sync so need to dig into that. Thanks for the feedback!
14.3 just finally introduced the ability to run scheduled Scripts:
Preliminary tests on v14.3 server show that this first implementation is basically OK. However, there are at least the following shortcomings:
- Like file-sync rule schedule or update schedule in advanced setting, the time schedule for script execution is restricted to be 0/15/30/45 minutes past any hour of device/UTC time in the web-console UI. This is unacceptable because unlike the other schedules, which involve deployment server that can be busy serving many tens/hundreds of devices during the same minute so that larger time jitter should be tolerated, scheduled script is pre-pushed to be run on target device and a much lower jitter should be achievable. Thus administrator should be allowed to specify any time down to minute or even second accuracy.
- There are no option(s) to specify script priority and maximum delay (after the specified scheduled time) after which script execution should be cancelled altogether. These help to handle cases in which the device is powered off, or busy working on some other tasks/scripts or higher priority, or in deep sleep during the scheduled time.
Agree on your perspective here Raymond, there is need for some more granular control of the scheduled actions.
My specific use case corresponds with the headline of the forum post, where a customer wants to schedule reboots of old devices. I can't see how this would work with the task scheduler. Unless you force the package to be reinstalled on check-in schedule, which wouldn't make any sense for a reset of the device. Or am I maybe missing something in the feature set which would allow me to do this once pr. day?
As I see it the only usable function is to use file sync, for this particular use case. But what I'd really like to do was having the device time used for offlien execution, and then time out if 15 minutes passed the scheduled reset do to powered off device..