There's a new home for Articles. Find Articles on Our Product Support Page.
We have 2000+ Zebra TCXX devices, and we are migrating from Android 10 to Android 13. When Android 13 devices boot up, they do not come online in Soti until the user enters the 6-digit PIN. Our users are bad about remembering their PIN and we cannot send a PIN change command now, since the device is offline. We also have an issue supporting devices now. If we need to send a device restart command to the device, we now no longer are able to remote in or send scripts until the user interacts with the device (enters the PIN). These are all company owned devices using Android Enterprise. How do we resolve this issue and get devices online BEFORE the user enters the PIN?
Hi. We are trying to change app permission by admin user, However, Admins cannot change app permission in Admin mode as shown in below screenshot. Is there any way to change it.?app package name: lsretail.omni.inventory.android
I want to script when I want to send script set Date time , No SIM , Time synchronize not work.
Is there a way to generate a report on which devices downloaded and viewed files in the Content Library for Apple devices. My goal is to upload a training video in the SOTI MobiControl's Content Library and have the end user play that training video in their device, and track this activity. Device: iPad 10th Generation OS: iPadOS 18.0.1
I'm looking to find the solution to display device's serial number in lock screen.I haven't found a way to set this through SOTI MobiControl. I've tried using the profile configuration by going through Profile > New Profile > Apple > iOS > Configurations Tab > + > Lock Screen Message > (filled in footnote message) > (but it does not dynamically display Device Serial Number in Asset Tag Information) Any input would be greatly appreciated! Device: iPad 10th Generation OS: iPadOS version 18.0.1 Serial Number: X1G7T5Ik4
We are testing a new HW device and the bluetooth package shows installed in the list of application for this device. I added it to the lockdown template (end up adding all 3) and it still says package not found when i click on the icon for it. Is there a separate bluetooth app i need for this to work? I can see the bluetooth setting on the device and confirmed it works but i can't get it to open from the lockdown kiosk. model: CT37 OEM: 514.00.02.0034-G
Hello team, Recently Chine client has been reported after they enrolled some MC3300x NonGMS Android 10 device the network SSID showing unknow(Column), Network BSSID(In device details). I got this article from the SOTI: https://discussions.soti.net/articles/000002122 But this wasn't helpful as Devices are NonGMS. But the earlier devices were showing the Network SSID and the difference in the new Devices are OEM version is lates 10-16-10.00-QN-U142-STD-HEL-04 (working device 10-16-10.00-QN-U0-STD-HEL-04) MX Version : 10.5.x (Old 10.2.x) MC Agent v15.4.2.1025 (old 2024.0.5.1062)
Hello all, this week our Lenovo P11s are updating to Android 14 from 13. The p11s that have not updated yet still work with remote access. The P11s that have updated... do weird things, the screen is not full screen, can't use gestures to access the app list or switch apps (this is an issue as the P11s don't have a show button option). What I have tried: 1) Soft reset 2) switching to admin mode and checking for any stuck messages about the update, dismissing the messages does not resolve the display issue or remedy remote access control of the tablets. 3) attempted to send the agent, error: latest agent already installed 4) switched them all to admin mode and physically checked notifications and update messages, did not help. help?
Hello, I am part of the IT department in my company, which uses SOTI MOBICONTROL for managing our ZEBRA TC72 terminals. I'm not the one managing SOTI strategies, but I am currently developing an application that sends certain data via email. I need to identify either the person or at least the terminal sending this data, whether by the name of the terminal or its serial number. Directly through the Android APK, I cannot retrieve the serial number, and all terminals have the same name (TC72). I would like to know if it is possible through SOTI either to retrieve the serial number to send it via email, or to rename the terminals using a strategy such as {name of the group it belongs to}-001 (auto-increment). The terminals with SOTI have a homepage that is an HTML page where the serial number is displayed. if(ip) customDataArr.push("IP: %ip%"); if(mac) customDataArr.push("MAC: %mac%"); if(serialNumber) customDataArr.push("Serial: %serialnum%");If you have any suggestions on how to achieve this, I would be grateful. Thank you for your attention.
Hi all, I'm using Samsung Knox Service Plug-in (KSP) to push policies to our fleet of 2 device types below: Samsung Galaxy Tab A7 Lite (SM-T227U).Samsung Galaxy Tab A9+ (SM-X218U). I followed the steps outlined in these 3 articles to grant Special Access Permissions to SOTI MobiControl and the Files by Google app, but have not seen all policies succesfully apply to the Tab A7 Lite. https://docs.samsungknox.com/admin/knox-platform-for-enterprise/knox-service-plugin/kbas/kba-1261-grant-special-permissions-for-an-app/ https://docs.samsungknox.com/admin/knox-platform-for-enterprise/knox-service-plugin/kbas/kba-1151-policies-not-applying-after-installation-on-device/ https://discussions.soti.net/articles/000002579 All policies are being applied to the Tab A9+, but only some policies are applied to the Tab A7 Lite. I pushed KSP via Managed Google Play, and have tried pushing the configuration policies in both the Managed App Config page and the Profiles section using OEMConfig for Samsung. I have entered valid Knox Platform for Enterprise (KPE) license keys, and yet I'm not sure why all policies don't take effect on the Tab A7 Lite. In debug mode, the Knox Service Plug-in app states all policies have applied successfully, or that the latest policies have already been applied, and yet this isn't true as the special access permissions aren't turned on for MobiControl, one of the policies I configured. I have sent logs, including Configuration Results, Received Policies, and dump state device logs to Samsung support, but no one has been helpful so far. Battery restriction shows as unrestricted when I followed the steps in Samsung's knowledge base. I also don't receive any errors of any kind in the KSP app while debug is on. It only says that all policies have successfully been applied, even though they have not upon checking after, so I'm not sure what to try next. The policies I configured to be pushed are: Device-wide policies (Selectively applicable to Fully Manage Device (DO) or Work Profile-on company owned devices (WP-C) mode as noted) Enable device policy controls ON Application management policies Enable application management controls ON Battery optimization allowlist: com.samsung.android.knox.kpu Package Name for Auto-Launch: com.samsung.android.knox.kpu Enable permission controls ON Permission Controls Permission Policy: Notification Access Package or Component Name: net.soti.mobicontrol.androidwork/net.soti.mobicontrol.notification.SotiStatusBarNotificationListenerService Permission Policy: All files access, Appear on top, Change system settings, Alarms & Reminders, Usage data access, ALLPackage or Component Name:net.soti.mobicontrol.androidwork/net.soti.mobicontrol.ui.MainActivity Permission Policy: All files accessPackage or Component Name: com.google.android.apps.nbu.files The policies not being applied are: All Files Access Notification Access For the apps: SOTI MobiControl Files by Google This only affects Samsung Galaxy Tab A7 Lite devices (SM-T277U). They are running Android 14, although some are running Android 13. The version of Knox Service Plug-in is 1.4.72 (24.06) The Galaxy Tab A9+ (SM-X218U) hasn’t had any issues and all policies are applied successfully. The issue is only with Galaxy Tab A7 Lite devices. Any assistance would be greatly appreciated.
I have successfully configured and gotten the needed url to work in chrome using: intent: myurl.dev.odoo.com#Intent;scheme=https;package=com.android.chrome;end and/or browser:// myurl.dev.odoo.com (also needed to define chrome as an allowed app with Launch://com.android.chrome) BUT: It does not work in SOTI browser as the link requires camera access and SOTI browser sends the allow camera message to the background. Using the above solutions, users have Chrome with full access to the internet, very much not wanted. Is there anyway at all to get browser launched camera permission to work in SOTI browser? The solutions at the start were the work arounds that I found discussed in the forums. Failing that, how to: 1) hide the chrome button in the SOTI Browser app allow list? 2) manage chrome to create an allow list?
THE FEATURES OF MY SYSTEMS ARE: SOTI VERSION:20241.0.1052 acteristics of our customers are: • Brand: Honeywell Model : Thor VM1A,VM3A OS: Android Version: 11.12
Hi there! We're managing a large number of Samsung Galaxy Tab Active3 devices using SOTI MobiControl. Is there any way to change the Popup Style of Notifications via Script or similar for a large numer of devices? The setting is found under Notifications > Popup Style, here's a Screenshot from the device (german). We want it changed from "Kurz" (Short) to "Detailliert" (Detailed).
We use SOTI to deploy iOS devices and are interested in the version of one app that is installed. Is there any way to pull this onto the device list for easy viewing? Currently I have to run the app version report but this does not include the time when the device last connected so is not overly helpful for identifying app version issues. It's a lot of effort to pull 2 different reports and then join them (especially as the dates export as text and are not easily converted)
Hi for several years we use soti surf as a browser, but today we get strange errors. Kiosk: On multiple devices zebra we get the error pages cannot befound. This is due: http://https:// someone know this behavior? thx Marcel
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.