No Matches Found!
Try with a different search term
Multiple Instances of devices that continue rebooting at random after a single "soft reset" command from the online portal on MobiControl earlier that day or in the days prior.
Devices are Honeywell CK65 running Android 10 & 12
Is there a way to clear any "history" of commands from MobiControl that could be causing this issue?
From your description, I don't think the device reboots are "at random", but rather a logical consequence according to some MDM administrators' request(s) when each such device gets powered up and synced with the MobiControl server.
Have you erroneously sent "soft reset" action to group/group(s)-tree(s) of devices instead of to the few device(s) of interest?
Also, reboot should only happen at most once for each device getting back on-line. Is that the case? Or is there any device (with or without any noticeable occurrence pattern) that gets rebooted more than once?
Without any additional information I would agree with Raymond on this. Scripted commands will be queued up and processed on devices the next time they are powered on and connected to SOTI if they are not currently connected when the script is first sent. If you were to send a soft reset script to a group of devices any not currently connected would soft reset at some future point when they do connect to the SOTI server again. If there is some level of evidence of the same device rebooting multiple times after this command has only been issued once then that would be worth looking into. This however does sound more like the expected behavior.
.png)
Hi Alex,
Thank you for posting on SOTI Pulse!
Could you let us know how many devices are experiencing the issue and are there any devices that are working without issue?
Are there currently any profiles or configurations that would make this behaviour expected on the devices?
If possible, please provide a screenshot or a log file so we can have a timeline on the device's behaviour after the reset takes place.
Kind regards,
Technical Support Specialist | SOTI | +1 905.624.9828 | SOTI.net lDiscussion Forum | Log a Case Online l Facebook l LinkedIn l Twitter
Hi Alex,
I agree with previous comments, in addition to that alternatively if it's not the latest agent version on this device, you can try to upgrade the agent version on ONE of your devices for test purpose and monitor whether it'll be same behavior or not.
And for test purpose what you can also try is; you can create a new Folder on WebConsole (no profile, no package assigned, empty folder), and you can move a test device (that you don't upgrade its version) to this folder and monitor whether you'll see these disconnected logs. I hope it helps.
Zafer
