Hello! I would like to have our managed devices reboot daily. In my research, it was suggested to use the Task Scheduler. I also found a list of commands and tried both: reset/H and reset/s.
Neither test worked.
Has anyone been successful in scheduling device reboots?
Yes this should absolutely be achievable using Task Scheduler. reset /s is a legacy script so make sure when creating the script that you're referencing in your Task Scheduler Profile that you create it as a legacy script and not a Javascript script (which is the default selection).
Hello Staci Z,
Thank you for your post on SOTI Pulse. Rafael Schäfer, Matt Dermody, and Raymond Chan, thank you for responding to the post your expertise and willingness to help are greatly appreciated!
We're glad you've been able to find a solution. Please let us know if there are any other details or links we can assist you with, and then we can close it at our end
Please let us know so we can proceed further accordingly.
keep in mind if your devices have a screenlock with password/pin/... configured and you do so that your devices may stay offline after the reboot until they get unlocked the first time.
Hi Rafael,
This is a great point and we do have a screenlock on. I will be sure to communicate with my team.
Thank you.
We pointed that to Soti already to support "direct boot support" but it seem not that easy but would cover that need.
In the past Zebra devices have been able to come online afterwards but not sure if this is still the case for their latest models (as Android has changed a lot and we don't use new Zebra devices).
But we see this definitely on all other brands we have in place.
Have you done any test of your script on your targeted device(s) by first using the send script action from the web-console? Some script commands may not function properly for some device brand/model/firmware or device agent version, enrollment mode, active MDM api's, etc. Typos in script can also be screened out before using the script in task scheduler profile.
As pointed out by Matt, make sure the right script type has been chosen (or specified with a proper shebang in some supported script deployment cases).
Also, make sure your task scheduler profile has been deployed (and not pending installed) on your targeted device.
