There's a new home for Articles. Find Articles on Our Product Support Page.
how to enroll device with qrcode and auto fill enrollmentID this my provision { "android.app.extra.PROVISIONING_DEVICE_ADMIN_COMPONENT_NAME":"net.soti.mobicontrol.androidwork/net.soti.mobicontrol.admin.DeviceAdminAdapter", "android.app.extra.PROVISIONING_DEVICE_ADMIN_SIGNATURE_CHECKSUM":"hn8mSNJMPcovWbnnWrb-uMpWZjNlNp-jyV_2A-Whumc=\n", "android.app.extra.PROVISIONING_SKIP_ENCRYPTION": "false", "android.app.extra.PROVISIONING_LEAVE_ALL_SYSTEM_APPS_ENABLED": true, "android.app.extra.PROVISIONING_LOCALE": "", "android.app.extra.PROVISIONING_ADMIN_EXTRAS_BUNDLE": { "enrollmentId": "", "PROVISIONING_MODE":"FULLY_MANAGED_DEVICE" } }
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?
Hi, On Android Classic devices, we are deploying applications through a package included in a profile. We have noticed that some apps open automatically after installation. After reviewing the package, we can see that the "Automatically Run Activity After Install" checkbox is unchecked: We would also like to mention that the packages are created via API, and through the API we can see these flags: Any idea what could be causing this? Thanks in advance.
Hi, i am a bit confused. We do not have google binding and are enrolling couple honeywell devices with the honeywell provissioner. This works well. The question popped because of the recent updates soti published (agent & plugin) we enrolled the devices with the AE agent (GoogleMobiControl-2026.0.1.1158.apk) Did we do something wrong choosing the AE generic Agent? The OEM version seems much older (2025.1.2.1214)?
how to soti mobicontrol 15.3 Android enterprise create phone call list into device I have list of telehphone number , then i want to crate telephone number into contact, Have script or menu to do that?
Hello! We're currently experimenting with bluetooth connectivity with some of our devices but no matter what I try. The popup to confirm the bluetooth pairing never shows up. We're testing on a Zebra KC50 device in kiosk lockdown mode. What we're trying to achive is using Soti's own Settings Manager and from there pair different perephirals like a Zebra scanner and different brands of bluetooth keyboards. It can "pair" but it never completes the pairing process as the bluetooth pairing popup doesn't show. The settings manager has access to turn on/off bluetooth, scan and pair. Then we're also using Zebra OEMConfig powered by MX which we have enabled pairing popup from but the popup never actually shows on the device while in kiosk mode. Any advice on how to solve this or if it is possible?
In Google Play Console, where can I view the results of the "Application Feedback" feature after it has been enabled?
Hello, Is there a solution that allows the agent to go online without entering a PIN? Device = Zebra OS = A14 Thanks
eSIM profile management is ineffective. I have properly created an eSIM profile policy and pushed it to the devices, which run Android 15 and Android 16 respectively. The status shows as Assigned, but the device logs all indicate Activation Failed in the end. I am unsure of the cause and would greatly appreciate your assistance.
Create a new configuration file - Manage Google Play allocation to multiple devices without enterprise registration, the configuration file is waiting to be installed. I don't know if it's because the device without enterprise registration does not support managing Google Play or if it's a system issue?
Hello everyone, maybe someone here can help me. We have the issue that we are currently running a few devices with MobiControl version 14.4, and we are using the Google Chrome browser. We would like to open a website in fullscreen mode from the lockdown. Does anyone have an idea how we can do this? In MobiControl 2025.1, there are the app configurations where this can be set. Unfortunately, we cannot use SOTI Surf here because the integration with the proxy fails, and the helpdesk has not been able to assist me either. Is there a way to configure Google Chrome under MobiControl 14.4? Or does anyone have an alternative browser that could work? Thanks and best regards
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
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.