No Matches Found!
Try with a different search term
No Matches Found!
Try with a different search term
There's a new home for Articles. Find Articles on Our Product Support Page.
Recently we have had trouble sending certain commands to our handhelds. One of the most common ones we have seen is the error message below when sending the Check-in Command. ERROR Error sending the Check-in action to 1 device(s). When I go to the logs for this device, it shows the request for the Check-in but does not show it as resolved on the next line like it would when it normally works. Is this a known issue? Further details below: Handheld Models: TC56 + TC57 Android Oreo 8.1 SOTI MobiControl Version: 15.4.2.1020
I've been getting this error for a while when I want to send check in to devices.Error sendin the check-in action problem Could there be something I missed? what would you suggest we do?
Hi everyone, Currently in SOTI Mobicontrol we have default setting for Update Schedule, usually it's every 2 hours, and everytime the device check in, it will looking for update and do Locate device location. I was wondering if the device location when doing check-in can be shown to us? For now i just can check the log and see that "device located" Is there a way to see the location? Thanks & regards, Randy Saputra
Hello, Our users are using a web app but every time their TC51 reconnect to the WIFI they return automatically to the lockdown screen (and they lose their current work...) We already disabled the "doze mode" as indicated in this thread: https://discussions.soti.net/thread/stop-returning-to-lockdown-on-reconnecting-to-server/ And we also unchecked the "Update when device connects" option as indicated in https://discussions.soti.net/thread/lockdown-closes-open-app-and-refreshes-lockdown-homescreen-when-network-connection-changes-android-8/ After some tests, we discovered that the lockdown screen appears every time there's a "Device (Agent) checked-in" and indeed there is a "Device (Agent) checked-in" triggered when a TC51 reconnects to the WIFI. As I understand, this is a security feature to force the device to return into "user mode". But in our case the device is already in "user mode"... Or maybe I misunderstood ? It seems that this problem started when we updated the MobiControl agent on our devices Zebra TC51. We need some assistance please. How can we avoid this return to the lockdown screen at every "Device (Agent) checked-in" ? We are currently using Server MobiControl 14.4.2.1307, Agent MobiControl 13.9.0.1046 and Zebra TC51 (Android 6.0.1) Thanks for your help. Frederic
We have been having issues with our Samsung tablets running Oreo 8.1, Mobicontrol Cloud v14.3.2.1171. We recently injected the ELM agent version 13.7.3.1045 and most of our devices are using this and today I see that there is a newer version available, 13.7.5.1013, but I can see neither agent listed in the Release Notes located at https://docs.soti.net/soti-mobicontrol/android-agent/release-notes/v137/android-oem-agent-maintenance-releases/ I would like to see what is fixed in these versions to know if we should upgrade but right now I can't tell. In general we are struggling to find any patterns or trends regarding the following issues and hope that a newer agent might provide some relief: Boot loop: the device at the lockscreen will accept the password but will return right back to the password prompt without indicating an incorrect password, Only way forward is soft reset from Mobicontrol console or hard reset on the device (long hold on power button) Collected Data: sometimes stops collecting, will resume after a restart Odin Mode (or Download Mode): numerous reports of devices going into Odin Mode, which is typically done by holding Power, Vol Up and Vol Down simultaneously. Too many users reporting for this to be user error only. We never had the problem until after upgrading Mobicontrol from 13.3 andgoing with the 13.5.x version of the agent. Devices not checking in: Some devices will go offline from Mobicontrol even though they are connecting to the network via WiFi or 4G (they can browse the web, sync data with our survey app, etc, just won't connect to Mobicontrol). Resolved with restart. Thought this might be related to Doze, sent "no doze" script to all devices and agent sleep issue shows fixed in MCMR-16238 False Low RAM Alerts: We have an alert set up to warn us when available memory drops below 768 MB, we get multiple alerts daily on multiple devices that this threshold is exceeded but whenever we investigate we have yet to find a single device actually running that low on RAM, even if we remote tot he tablet within a minute of the alert having been received. None of these is absolutely related to the agent but I can't rule it out either, would really like more comprehensive notes for each release Thanks, Matt
Is there anyway to stop the lockdown screen exiting all apps on reconnecting to the SOTI server? Our devices (TC75) are out on the road, and the users are using an app, which when the device reconnects to the server after losing signal, lockdown closes/hides the open apps and returns the user to the lockdown home screen. This is a pain for the users. I've seen this happen while on remote control, be using the app. the device goes offline and when it reconnects I see the lockdown, and the app has to be reopened - normally remembers where the user was, but sometimes closes the app completely. Thanks for any suggestions. Gary
Does anyone know why iPhones stop communicating with SOTI? I have seen a number of devices lately, that just stop checking in. At the same time, users are reporting their device passcodes are not being accepted. Requesting a check-in from the device rarely causes them to connect to SOTI, nor does a forced restart. Not really sure why they aren't keeping their 2 hour scheduled connection. Let me know if i can provide any further information.
If a device is not able to check-in agentlessly with MobiControl, it essentially means it cannot be managed. It would be nice to have a troubleshooting procedure for this kind of scenario.
Top-tier experts who are delivering outstanding content. Should have more than 7000 points.
Experts who are consistent with great content. Should have more than 1000 points
Highly experienced members with valuable inputs. Should have more than 700 points
Beginners taking the initiative. Should have more than 500 points
