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.
Hey, I wanted to reply yesterday, but for some reason I couldn't reply. I clicked on “Post,” but nothing happened. That's why I created a new post. Pulse | Community Support @Raymond Chan Unfortunately, it didn't work. Here is the error code.
Hey everyone, I'm currently trying to figure out how to disable the Quickshare app. Users have the option to access the Android Bluetooth settings via kiosk mode. (com.android.settings/.Settings$BluetoothSettingsActivity) Unfortunately, this also gives access to Quick Share. How can I disable it? The device and Android version are as follows. - Zebra TC 26 - Android 11 (11-64-10.00-RG-U00-STD-HEL-04) - MX version 13.5.1.7 Thank you very much for any help ^^
Hi, We are facing an issue with enrolling our Barcode devices. We cannot enroll them with the enrollment ID of the enrollment policy since maybe a month ago, but we can enroll them by the enrollment URL of the same policy. We dont face this issue with other device types neither with other enrollment policies. Anyone faced this issue before and how to make it work again? Thanks Jakub Broch
Hello, I am trying to overcome an issue i have with a Zebra Tablet, Model ET40. the Tablet has a connection to a bluetooth scanner (also zebra device) that has to be connected manually (but thats another story all together). the issue is the devices (currently only 1 enrolled as part of test) are being shutdown every week during the weekend and when a new work week starts the devices are being turned on and seemingly lost the pairing to the bluetooth device, and since we are working in Kiosk mode the users have to call on IT to re-connect the device manually. is there a way to disable the unpair on device shutdown, or make the device re-pair on activation? Appriciate your Help, Bar Y.
My Mobicontrol server is offline and so I have no enterprise binding. Using Mobicontrol I have deployed Zebra OEM config (com.zebra.oemconfig.release) to Android 13-14 Zebra scanners in my enviroment specifically to apply Datawedge settings as it was recomended by Zebra since using MXCONFIG with a StageNow XML is deprecated.The managed configuration transaction items inlclude downloading the datawedge.db and applying it. All other configuration items are left blank or "do not change" is set. This feature is working just fine. I am seeing a serious issue with all devices that I have deployed OEM config to. Every time the device re-applies OEM Config's transactions it is repeatedly disconnected from Wifi. Once it is finished applying the connection is stable again for an hour or so. Then the issue loops. Has anyone encountered this issue or have any recomendations?
Hello, until now we used the barcode from this thread Pulse | Community Support to enroll non-GMS Zebra devices in China, which worked well. However, with MX14 it does not work anymore. Is there a new code or is there a describe how to create one by ourselves? We tried to create one following WS50: Registrierung bei SOTI MobiControl mit StageNow, but still does not work. Best regards, Eduard
Hi, we have some Zebra Helios devices Non-GMS. I have recently tried to upgrade some from A10 to latest Android 14 (14-32-12.00-UN-U00-STD-HEL-04), and figure out that Velocity (2.1.45) crashes just after start. I'm struggling to get support from Zebra and Ivanti, wondering if anyone here has ever experienced the same. The same device works fine with Android 13 (13-29-10.00-TN-U00-STD-HEL-04)
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?
Hi, in the release notes for MobiControl 2025.1 is mentioned: Use Zebra LifeGuard Without Google PlayThis feature allows administrators to automatically provision the Zebra enrollment app for Zebra LifeGuard as an Enterprise app via App policy without compromising security compliance and avoid interfacing with Google Play services. How does this actually work? I don't find anything more about it, then just this entry. If I choose an Enterprise app it either needs an APK or an URL to download the app?
Check out the latest episode of SOTI TV where I had the honor being a guest speaker. Topics include:• Choosing the right rugged devices & mobility tools• Reducing downtime with remote diagnostics & lifecycle management• Closing security gaps and vulnerabilities introduced by end usersCurious to know what the community thinks and if you'd like to counter or debate any of the points I made. https://youtu.be/h0DO6vADDDo
Hello team, I have one article from you as mentioned below: https://discussions.soti.net/articles/000001443 Can you please provide the JSON code to use the EnrollmentURL instead of the EnrollmentID ? "{"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_ADMIN_EXTRAS_BUNDLE":{"enrollmentid":""}}" I have replaced the enrollmenturl in place of enrollmentid but that did not work or may that is not a correct way to change the parameters.
Hi all, We, as a partner, are facing the challenge of remotely upgrading Android 10 and 11 devices to Android 13. We have been following this two articles to upgrade devices with Android 10, and 11 to Android 13: https://supportcommunity.zebra.com/s/article/000027787?language=en_USchttps://techdocs.zebra.com/lifeguard/a13/#migrationprocedure We have successfully been able to upgrade devices from Android 10 and Android 11 to Android 13, however we are facing a challenge due to devices that are configured on custom APN network, those devices that we have upgraded to Android 13 will load the default APN settings which are incorrect, and the device will not connect after upgrade because it will not have internet access. So we would like to ask here if anyone would have a solution for devices that are on custom APN (4G/5G) networks and are without Wi-Fi how to reload, or reconfigure the APN network in the process of upgrading it? Any ideas would be great on that matter.
Hi all, we, as a partner, are facing the challenge of remotely upgrading Android 10 and 11 devices to Android 13. Affected are different customers with different devices. Mainly Zebra devices but also other OEMs. It is not possible to perform the upgrade via LifeGuard OTA, configured in the MobiControl console. Neither it’s possible to transfer the OS ZIP file to the device and start the upgrade via script. Crucial for this is the change from full disk encryption to file based encryption from Android 11 to Android 13. All our customers want to upgrade their devices OTA, without any interaction directly done on the devices. They have hundreds and thousands of devices, distributed all over the world. A workaround from Zebra is provided to prevent data loss: https://supportcommunity.zebra.com/s/article/000027787?language=en_US But for this workaround, its complex to set it up in the first place and according to reports it comes with problems and bugs during and after the upgrade process. To get a clean upgrade and SOTI enrollment, it is recommended to factory reset the devices, upgrade them, and reenroll them in SOTI. Because of the manual processes, it is not suitable for our customers. Even by configuring the processes in tools like StageNow, there are sill too many manual steps involved for the end users. What are your experiences with that topic? Do you have any solutions or workarounds? I would love to hear how other partners or customers are solving that. Thank you in advance.
Hello, We have over 1K+ Zebra TCxx devices in use at our warehouses. All devices are deployed with a locked screen, granting access only to the apps necessary for their tasks. Occasionally, a device gets lost or damaged. While this can happen, we'd like to see if we can reduce such incidents by requiring users to log in before they can access applications. We tried the shared device feature, but encountered a few issues: When Soti Identity is down (FE: when there is an update), users cannot log in, which means the scanners are unusable. The default shared device login screen includes a link to the terms and conditions. Through this link, users can access various other websites (possibly something we could block). It seems likely that other companies are facing similar issues. So, here’s our question 😊 Has anyone found an ideal solution to this problem? If so, could you share some details about it? Thanks very much in advance! Best regards,Robbert
Hello, we want use available TC57 devices in our production area. Is there an possibility to deactivate WAN/Sim Cards? Thank you Gunert
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.
