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.
Hi all, We are in a bit of a pickle regarding Shared Device mode using EntraID Currently we have this setup:User Logs into device using their EntraID and passwordSet Session PIN is promptedOnce connection to Entra is made, device moves to Post-Lockdown screen folder.I have configured the Post-Lockdown screen so users cannot shut down the device without signing out first. This ensures the user signs out, the PIN is cleared, and the device is ready for the next user tomorrow.Here is the problemThere have been instances where devices have powered off due to battery depletion or similar issues. As a result, the device shut down while the previous user was still logged in.When the device is then charged and turned on, some users have forgotten the PIN they used, or its another user whos grabed the device and they do not know the PIN.Because the Device PIN initiates BEFORE the SOTI MDM, it shows the device as Offline and I am unable to clear the passcodeThis is a big issue and is basically bricking devicesHas anyone found a way around this?
Running on Android Enterprise, mostly Zebra handhelds. Agent version 2026.0.1. As part of an OS upgrade workflow, we have our devices in Lockdown mode with a "Device upgrade in progress" screen. After the upgrade completes, we remove the profile that puts it in Lockdown mode, and want to bring it to the app launcher. However, my experience is that the Agent app will launch, and either show the Device Configuration screen, or (if there is a Shared Device configuration) launch them into the Log In screen we have configured. This ends up creating confusion, especially if they're greeted with a Log In screen rather than their app list. Is there a way to configure/suppress this? I'm looking at ways to work around it (by explicitly launching the Home app) but would prefer to suppress it at the source.
Feature Request: Date Operators (Older Than) for "Android Security Patch Level" in Compliance Policies & Filters Problem: Currently, the property Android Security Patch Level is treated as a String in Compliance Policies and Virtual Groups. Users only have operators like "Equals", "Contains", or "Starts With". Requirement: Administrators need to set automated compliance rules based on the age of the patch (e.g., "Block devices with Security Patch older than 60 days"). Current Limitations: Text filters (e.g., "does not start with 2026") require manual maintenance every month/year. Workarounds using Scripts (to write os.securityPatchLevel into a Custom Attribute of type Date) are often blocked by Android Enterprise restrictions (e.g., on Zebra devices with strict policies), leading to script errors. Goal: Please change the data type of Android Security Patch Level to Date or add a specific compliance criterion "OS Patch Age" that allows numerical comparison. SOTI Version: 2025.0.0.1 Greetings,M. Klein
Mobicontrol Version: 2025.1.2.1007 Agent 2026.0.2.1278 Zebra TC27, Android 14 I use the Mobicontrol lockdown, I have added this tile, in order to provide access for the user to 1 website.The website is a O365 registrered enterprise app, and it remember the username/email.My user used a private email, and now the browser keeps giving me error message.If I open Chrome browser, then user can log in, so user/permission/access is working.I would like to "wipe" the application, but I understand that a "webview" is used, and I can't find any earlier tickets with a, for me, usable method like wipeapplication chrome or Soti surf. So I need help with wiping the "built in" single page browser used by Lockdown
I am trying to enroll a raspberry pie 4 running Emteria OS on to SOTI using Android Classic but I am having connecting to the device. I have tried using adb but the OS isn't asking me to trust my system. I have also tried using wireless adb but when I type in the code, it errors out. I've notice that the default tranfers mode always goes back to "no data transfer". Also tried using the enrollment ID but it states it can't be enroll because it does not support encryption. I've also tried installing an APK but can't install it because it states it's not compatible. I've reached out to support but we were unable to enroll the device. Has anyone been able to enroll a raspberry successfully with Android classic? Any help would be appreciated
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
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"
Hello there, I have a common issue with Company portal stealing token from MS Authenticator, which results in MS Authenticator being unable to register device as shared device. However I alraedy set Authenticator as "high-priority" and "open after installation". Also placed company portal in same app policy and gave it "postpone" priority and a bunch of MS apps in between. Still every other device I have to fix manualy by removing both apps and clearing cache and metadata of Authenticator and re-installing just it first. Side note: I can not avoid Company portal, as it is required by my mother company policy to run any MS stuff (Intune MAM). Thank you in advance for your best practices.Detail:Enrollment type: Work managed (fully managed device in kiosk mode)Device: Any (mainly Samsung & Zebra)Server version: 2025.1 (MC cloud)Android version: 15
Hello,Did anybody else noticed this behavior/bug/feature/limitation? :) (it seems to be happening in both User and Administrator mode)Soti Mobicontrol version 2024.1.2.1046COSU (Work Managed Device) Samsung phones with Android 14 and Agent 2026.0.1.1158
I have an enterprise application that I have to update regularly and every time I do it takes forever to flow down to the devices. I have 1200 devices now but this speed has been this way since I put my first 100 devices into my 2024.1 instance. Not sure if I am missing something but is there anyway to speed up the flow of the updated APK to all devices?
<pre id="tw-target-text" class="tw-data-text tw-text-large tw-ta" dir="ltr" tabindex="-1" role="text" data-placeholder="Traduction" data-ved="2ahUKEwjX79SM7eyQAxV3cKQEHSlLF54Q3ewLegQIDBAV" aria-label="Texte traduit : Hello, I hope you are well. I am writing to find out if other SOTI administrators are experiencing this issue in their companies. I have Samsung XCOVER 7 phones that are shared by several users on the same day. We have applications on these phones that require SSO authentication via Microsoft 365. When the phone is passed around, it is very difficult for the user to log in to these applications because SOTI Surf (or another browser) caches the last 365 login for SSO. I am forced to manually clear the app data and cache, but this is not manageable. Do you have any ideas for automating this more easily? Ideally, we would like to have profile-based management on these phones, but I don't know if that is possible. Thank you very much for your help. Have a good day,">Hello, I hope you are well. I am writing to find out if other SOTI administrators are experiencing this issue in their companies. I have Samsung XCOVER 7 (Android 15) phones that are shared by several users on the same day. We have applications on these phones that require SSO authentication via Microsoft 365. When the phone is passed around, it is very difficult for the user to log in to these applications because SOTI Surf (or another browser) caches the last 365 login for SSO.I am forced to manually clear the app data and cache, but this is not manageable. Do you have any ideas for automating this more easily? Ideally, we would like to have profile-based management on these phones, but I don't know if that is possible. Agent version : 2026.0.1 Build 1158Server version : 2025.0.2.1059 Thank you very much for your help. Have a good day,
Hi, I've got a Zebra MC3300ax devices with the Version 11-20-18.00-RG-U00-STD-HEL-04 that i am trying to update up to 14-32-12.00-UG-U03-STD-HEL-04 Version, i have copied the file with File sync to a set location and once it is done i have sent the script (Type Legacy) : install_system_update /sdcard/update/HE_FULL_UPDATE_14-32-12.00-UG-U03-STD-HEL-04.zip to which i get the log error Custom log (Mx OTA failed: Any idea what could be the cause of this? i have tried moving the file to diffrent locations and even diffrent update files to slightly lower versions but it always give the same error. Best Regards, Bar
Hi, Is there a way to run a script locally on the device at boot or startup? More specifically, I would like to run a script that toggles Data Roaming on (if it is not already enabled) every time the device starts up. This serves as a safeguard to ensure that Data Roaming is always enabled, as our app requires it to maintain an internet connection. The script should run locally on the device without needing an internet connection, similar to the boot-up procedure that allows our kiosk app to start automatically on device reboot. We are using Samsung Android devices with OS versions 13, 14, and 15. Thanks for your help in advance, Stefan
I need to set up users at certain location so that they can view just the devices at their warehouses, how do i do that?
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.
