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
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?
Hello, we have updated our smartphones from Android 14 to Android 16 with the new Samsung One UI 8.0. Now it is no longer possible to access admin mode, as nothing happens when you press and hold the back button. Admin mode can now only be accessed via the Soto Mobicontrol Center. Google has assigned a new function (preview) to the Back button in Android 16 when you press and hold it. This means that the previous function of SOTi no longer works. We need a workaround in the Soti app because we cannot access Admin mode without the company Wi-Fi. Best regard
Hello all, we used soti mobicontrol on version v15.5.1, device are Zebras TC78 under android 13 with agent entreprise -> 2024.0.4.1056 I have a website on 3w, where our device try to connect. If i open the web site with google chrome and connect with login pwd all work If i try with soti surf (last version downloaded) and do the same i have an error like this : The action you have request is not allowed. Host xxxxxxx request POST status code 403 If i do the same with our old device Zebra TC75 under android 7.1.2 and soti surf on version v15 5 1 8 all work i can join the site and connect .. Anyone have idea ? on lock down i try to open the web site with this parameter but same result: surf:// xxxxxx Custom surfs://xxxxx After some search, i 've find it's a request POST and we need to configure on soti mobicontrol but our version is old .. Someone can confirm this ? or there is another solution ? Thanks a lot
My Customer as an internal fleet of Zebra Products linked to this on-premise server and wants to drive Samsung Phones on A14 that should be outside in data connection.What should be exactly the best practice ? Using Samsung Knox enrollment or Knox LME Work Profile and Google profile As he holds many firewalling rules In each case, what connectivity should be preserved, from on premise server to outside, and from outside to inside ?Any registration and DNS needed ?
SOTI have any method or android script to force enable installed app on Accessibility Settings ? Agent Version : 2025.2.2.1085Android OS : 9-15SOTI Console Version : 15.3 (on-premise)Device Kind : Android Enterprise
A few months ago, we manually enrolled majority of our Samsung devices into the Samsara Driver beta program for testing out new features & giving feedback to Samsara. Now that we are the end of the beta period, we are advising the on-site teams to go through all of their phones manually to unenroll the phones from beta program. On each of the phones, they have to go into the Google Play Store on each phone to remove it from the program, same what they had to do for enrollment. In my testing of removing a phone from the beta program, uninstalling and reinstalling did not automatically remove it from the beta program. Does MobiControl, and I guess Android as a whole, allow IT administrators to either enroll or unenroll devices from application beta programs? All of our Android phones are enrolled into MobiControl as Work Managed if that makes a difference.
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.
