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.
On a device that is not in lockdown mode, is it possible to set a homepage URL for the default browser? For example, can this be done via a shortcut or another method?
I have use case I use Lockdown kiosk for tablet ans i have scenarion want to know telephone number of SIM and use sentintent script and it return telephone number i can see telephone number if without lockdown but if lockdown active i can not see telephone number So, I want to save telephone number data into ini file and show in to custom data Can I,
I have some questions about the device profile policy and need to consult. In the function control, 4 profiles were created. Now I have found a problem. As long as one of the 4 profiles disables Bluetooth or camera, the device will disable Bluetooth or camera, regardless of the order of pushing policies. In addition, the other 3 policies will not take effect even if Bluetooth or camera is turned on. What is the priority rule for device effectiveness? Why does the new push not overwrite the previous push? Will there be similar logic in other policy configurations?
We're planning to start with Soti connect (cloud) with Zebra ZT421 (MQTT). Whitch network ports are needed (inbound and outbound).
Is there any way that when uploading custom APK into Mobicontol that that it will recoginzed the app version and build number. That way we can use that for versioning our apps. While testing them. Otherwise we have to delete the app and policy before we can upload the newer version. The system only recognizes app version and not build.
The Custom Images dropdown in LockDown contains too many files not being used and scrolling through them takes forever. Some of these need to be removed. Where else are these images stored? This is for an android+ work managed device hosted on the soti web console. I cannot find this in new version 2025.1.
Initial Background: We have a Zebra TC52 that was enrolled and functional but then was physically damaged. Since it was assumed to be permanently unusable, it was deleted/unenrolled from our Devices in the SOTI Console. Later the device was examined in more detail and found to be reparable and so we proceeded to do so. After repair it was found that the device was not un-enrolled properly as it was offline, so the technician performed a local factory reset of the device and attempted to re-enroll via StageNow barcode scan. After this attempt, it appears that the device partially deployed. It did not appear in the SOTI Console, but Lockdown has been applied on the device. Many apps did not load or partially loaded, several stating 'Package not Found' when we attempt to run them, and SOTI MobiControl Settings Manager states that it has not been configured. The biggest problem then is that the Administrator password to exit Lockout was not correctly configured, and use of our actual password, blank, "password", "admin", etc. fail to be accepted. Our password continues to work on all other enrolled devices, so the problem is isolated to this one unit. The Problem: From the SOTI Console standpoint the Device has not appeared in the list from the new enrollment, and we have Permanent Delete enabled so the original Device is also no longer present, so there is no interface we can leverage to interact with the device from the Console side. From the device standpoint it is in Lockdown, and cannot be taken out of it with a password as it appears no valid password was ever set. As a result a further factory/enterprise reset from the OS is not possible, as Settings cannot be accessed due to Lockdown restriction. Likewise USB Debugging to allow ADB access cannot be enabled. Zebra employs Recovery Protection due to the Android Enterprise account being present, which disables the ability to access ADB or SD card boot options in the Recovery boot. This account cannot be removed due to Lockout, and I am unaware of any way to bypass Zebra Recovery Protection to initiate a Factory Reset. Do we just have a bricked device at this point, or is there a way allowed by Lockdown and/or Zebra Recovery Protection to force enrollment/un-enrollment/reset?
When MobiControl connects to the CLA, it invokes the GetCertificate method to communicate with the Agent. At present, this method generates a COM-based Certificate Request and submits it to the Certificate Authority for certificate issuance. Because Certificate Request objects are created on the CLA side, the CLA encounters performance bottlenecks. To address this, the flow will be updated so that the Certificate Request is created only on the MobiControl side and then passed to the CLA as a parameter in the GetCertificate method. The CLA will simply reuse this object, reducing its processing load. Customer Impact: For customers who have applied security policies on the Certificate Authority side that validate the request based on the process name, an update will be required. With this change, the process name may appear as one of the following: Soti.Cloudlink.GrpcServer.exe MCDeplSvr.exe
One of the features that was brought up by SOTI during our POC was the app catalog. It was billed as similar to the app store in Intune. However, now that we are trying to set it up, it appears that the only people that can use it are those with admin rights on the local machine. If they have admin rights then they can install whatever they want, something that we are trying to get rid of. So, question is, am I reading the documentation correctly, is the regular user unable to install from the App Catalog?
We’re running into an issue with our Zebra VC8300 devices on Android 14 where DataWedge configurations are not importing. Our current process works fine on Android 13 — the .db file is stored on the device in /sdcard/, and we push it via SOTI MobiControl using the DataWedgeMgr XML. <wap-provisioningdoc> <characteristic version="9.2" type="DataWedgeMgr"> <parm name="ConfigurationFile" value="/sdcard/UlineMX/datawedge.db"/> <parm name="AutoImporting" value="1"/> </characteristic></wap-provisioningdoc> On Android 14, the same .db file will not import — even if I go into the DataWedge app on the device and attempt to import it manually. No errors appear; it simply doesn’t apply the configuration. I also tried creating a new StageNow Profile with a higher MX but that did not solve the problem. Has anyone run into this with Android 14? Did the import location change? Is there a new permission requirement for DataWedge to access files? Is .db importing deprecated in favor of another method? Any insight or workaround would be appreciated.
We have disabled the GMS services on our devices, which worked perfectly under Android 11, 12, and 13. Now, under Android 14, the Google Play services are still being queried. Is there a way to disable this? If so, where? We haven't found a solution for this yet
We are currently facing an issue where no phone calls go through when we activate the lockdown. The phone itself is enabled on the lockdown and works, but incoming calls are not displayed. We Use Zebra TC77 and TC78 with Android 14 SOTI MobiControl 2025.1 We've also tried everything and attempted to read and release the activity, but always without success. Does anyone have an idea?
Hi All I can see lots of posts regarding remote control stays black on Android 13 and 14 Samsung devices and generally the advice is to start your RC session, once connected to the device it will show a black screen, use Page Up on your keyboard, followed by the PIN (you won't see it on screen) followed by enter and you will then be able to see the screen. This method works fine for android 12 and 15 devices, but not for android 13 and 14. The android 13 and 14 devices just can't be woken remotely - has anyone got any extra tips or know if an agent is available to support this function. In the past we've just been told this is just the way android 13 and 14 are, but since it is still in support and these are still supported devices (the OS can't be upgraded) then has there been any fixes or workarounds? The test device in question is SM-G780F (max OS is 13) We have Samsung on android 12 and typing the PIN on black screen is fine We have Samsung on android 14 and it has the same issue as android 13 - can't get past the black screen even after typing PIn in blind. We have Samsungs on android 15 and no issues. Any advice appreciated, but please note what I have already tried above and the comparison between android 12 and 15 above. Many Thanks
Hi All, I hope you can help me with this. The Calculator app in Kiosk Lockdown is showing a “Package not Found” error after we upgraded TC57 devices from Android 8.1 to Android 13. However, on TC57 devices that are still running Android 8.1, the package appears and works normally in Kiosk mode. Thanks in Advance
Does anyone have a working example for this? How to get the downloadOptionsReferenceID in specific.
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.
