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.
Hello, I’m having an issue creating a specific folder under sdcard/Android/media and placing a .json file there via a file sync rule. This works on our AOS 13 devices but not on AOS 14. We recently upgraded from SOTI 15.6.6 to 2025.1.2.1007, which may be related. Additionally, the app install is extremely slow on AOS 14 (over an hour with no success), and after revoking the profile I now have to manually run the uninstall script—previously this happened automatically. From what I’ve read, Android 14’s scoped storage may block this path. I tried creating a new profile with Zebra OEMConfig and granting Manage External Storage to net.soti.mobicontrol.androidwork, but it hasn’t helped. Community posts suggest the app may need to use a different, more accessible directory, but I’d like to exhaust all options first. Any guidance would be appreciated. Device: Zebra MC93OS: AOS 14SOTI Agent: 2026.0.1.1158OEM Version: 14-23-05.00-UG-U00-STD-HEL-04
My organization has been having issues where sites where we have deployed tablets will ignore the tablet's battery health and then when the tablet is required for a monthly safety inspection, for instance, the battery is dead. We were hoping to use SOTI to send out automated reminders to charge a device when a battery gets low or dies. As far as I can tell there are only two options for this: Compliance Policy - Allows the use of the %ENROLLEDUSER_EMAIL% alias to send a notification based on the device, but we can't customize the message and I don't know if the standard device compliance violation email is approrpriate for such a notification. Signal Policy - Allows us to customize the message being sent, but can't use the %ENROLLEDUSER_EMAIL% alias because the field is expecting a properly formatted email. Are there any other avenues we can take?
Hello, I'm trying to connect SOTI to an email in my office365 environment in order to set up a "send from" address for signal notifications. I'm having some issues and I would like some help trying to figure out what I might be doing wrong. I have SMTP Auth enabled on the mailbox I'm trying to send from. Microsoft's documentation insists I use TLS 1.3 or 1.2 as authentication especially because Basic is depricated but the option isn't available (or naming isn't consistent). At this point I've used every authentication method with SSL on and off, both office smtp ports (587 and 25), and a few different usernames/passwords and still nothing. Any help would be appreciated! Thanks, Andi
The Screen share ability has stopped working for us using the "downloadable plugin". If I enroll a new device it will work but then after a few hours it stops working and I only get "waiting for Screen". Any ideas on what to check on? Device: Zebra TC22/52/73
Hey everyone, I'm trying to write a script in SOTI Surf where it will automatically fill/set the value of an input field on a page. Testing in some other environments (Velocity, W3Schools) the script below works fine, but when I try and use it in Surf, it doesn't seem to like it. It throws an error about the HTMLElement not having a property 'value'. Has anyone successfully done something like this in SOTI Surf? Just wondering if I'm missing something or if theres a limitation to the scripting in Surf. FYI, I'm just testing on the Google home page, so that element id is the search bar. Any help or guidance is greatly appreciated! document.getElementById("APjFqb").value = "Test Text";
Hi Everyone, I hope you all had a great start into the week. I am searching for a solution to display a QR or other type of barcode in the starting page of a lockdown. We want to use a barcode instead of the device name to identify the devices. At the moment there are stickers on the outside of the device but in an industriell environment the devices often loose the stickers. Any idea how to do this? Thank you very much.
Hi everyone, I'm trying to update a Zebra data collector and I'm getting this error. Does anyone know what might be happening? Log pers. (Mx OTA falhou: /sdcard/NE_FULL_UPDATE_14-15-22.00-UG-U92-STD-NEM-04.zip) Script: install_system_update "/sdcard/NE_FULL_UPDATE_14-15-22.00-UG-U92-STD-NEM-04.zip"
Hi,I'm building a new lockdown pre-auth and post auth with shared device login (Entra ID) (HTML coded)Is it possible to also put a Macro in the lockdown to display information from the screen Lockdown Logged-In User?i would like to display which user is currently logged-in on the device itself.I also experience some issues with the Log Off functionality when a device should be put back in the cradle.
Hi,I'm building a new lockdown pre-auth and post auth with shared device login (Entra ID) (HTML coded)Is it possible to also put a Macro in the lockdown to display information from the screen Lockdown Logged-In User?i would like to display which user is currently logged-in on the device itself.I also experience some issues with the Log Off functionality when a device should be put back in the cradle.
Hi, How to handle agent failed install using ppkg enrollment on modern windows.
Hi everyone, I am currently struggling with several issues regarding the ZEBRA OTA Service in MobiControl 2024.1.2 and wanted to reach out to the community to see if others are experiencing similar roadblocks. We are seeing the following behaviors across our fleet: OTA Device Sync Errors: Frequent synchronization errors when communicating with the FOTA service. "Update Pending" Stalls: Devices remain in an "Update Pending" state for an extended period. In most cases, they never actually start the update and eventually flip to "Update Failed." Artifact Download Failures: For certain firmware versions displayed in the console, the installation fails completely. The error logs usually indicate that the artifact could not be downloaded, even though the version is listed as available. What we’ve tried so far: Restarting SOTI Services (multiple times). Attempting to reset the OTA Service (which often gets stuck on "Reset is in progress"). My questions to the community: Have you seen this "Update Pending" loop recently? If so, did you find a way to "nudge" the devices to start the download? Are there specific network requirements or firewall exceptions for the artifact download servers that might have changed recently? Is there a known stable MC Agent version that handles FOTA more reliably for Android Enterprise? I would appreciate any tips, workarounds, or experiences you can share!
I need to upgrade to version 2025.1.2 to allow the update to my VPP token. The last upgrade we did to 2025.1.0.1007. Update: Sorry I forgot to finish this! When we did the last update it was a nightmare of things not working afterwards. Has anyone upgraded and had any issues? Sue
Concerns status display in devices In version 2024, the online/offline status is clearly visible with the colors green and black. In version 2026, the online/offline status is now displayed with the colors green and gray. To me, the difference is no longer as noticeable at a glance. Is there a way to change the GRAY color?
My Mobicontrol server is offline and so I have no enterprise binding. Using Mobicontrol I have deployed Zebra OEM config (com.zebra.oemconfig.release) to Android 13-14 Zebra scanners in my enviroment specifically to apply Datawedge settings as it was recomended by Zebra since using MXCONFIG with a StageNow XML is deprecated.The managed configuration transaction items inlclude downloading the datawedge.db and applying it. All other configuration items are left blank or "do not change" is set. This feature is working just fine. I am seeing a serious issue with all devices that I have deployed OEM config to. Every time the device re-applies OEM Config's transactions it is repeatedly disconnected from Wifi. Once it is finished applying the connection is stable again for an hour or so. Then the issue loops. Has anyone encountered this issue or have any recomendations?
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.
New contributors starting their journey. Should have more than 250 points.
