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.
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
Hi, I am running MobiControl (still on 15.6) and I need to delete a profile in the Zebra Datawedge. Before I can install the new version of an application I need to make sure that the old profile is deleted from the device. The Datawedge profile was created by the app but the app is developed not very good, so I need to take care of it. I thought I could do it with a script (sendintent) but somehow nothing is happening. Here is what I tried to send to the device: sendintent -b "intent:#Intent;action=com.symbol.datawedge.api.ACTION;S.putExtra=DELETE_PROFILE,xxxProfileNamexxx;end" The techdocs of Zebra Delete Profile - Zebra Technologies TechDocs are not very useful to me so maybe one of you can send me to the right direction or give me some hints. Thanks in advance
Hello, I'm unable to enroll my TC72 on Android 11 to SOTI. After StageNow auto populated the enrollment ID, it returned "Enrollment Failed" message. We have used the same process and enrollment ID for our other devices, A10 and below. I'm wondering if there are known issues with Android 11 enrollment? Our current MC version is rather old (14.3.4.1087) and I'm wondering if A11 is just not compatible with older console version? I'm thinking of downgrading from A11 to A10. However, I'm still unsure if this is the best approach?
Hi guys, I need to understand how to keep already installed certificates visible (after migrating from A11 to A13) on the device in the setting UI: Settings/Security/More security settings/Encryptions & credentials/Trusted credentiakls/Tab User My customer uses cert provisioning via SOTI profiles "Certificates". Now, the issue is it is a Zebra SD660 (e.g. TC57x) device that has been migrated from A11 to A13 latest patch levels each. It is known that regarding the encryption method change from Full Disk Encryption (FDE) to File Base Encryption (FBE) there will be an enterprise reset performed prior to reboot into A13. Luckily SOTI agent and wifi profile keeps fully installed and survive the migration. Using the Zebra provided ZCP (Zebra Conversion Package) shows the same result. Anyway, ZCP is not an option. In essence all certificates previously installed also keep valid and working. But: The user certs do not show up in the settings UI of the device anymore. This is seen as crucial problem because in any case of an issue the support person will check certificate in this UI via a remote control session. The alternative to (re-)install certs via StageNow CertMgr is no option - certs are only allowed to be installed via SOTI profiles / SCEP. Hope somebody out there have solved similar issue. All best from Germany Jörg
I'm trying to install SOTI MobiControl as a fully managed device to my new Zebra TC72 Android 11. We have to be connected to the company's network/wifi in order to enroll SOTI in the past and we used StageNow to install. However, this time I'm doing this remotely from home. So, I had to install Cisco AnyConnect first to connect to VPN out of the box then install SOTI using an external SD card. It was installed successfully, but I was prompted to create a work profile. Is there a way to install it as a work managed while connected to VPN? Or was it me installing AnyConnect that was causing the work profile? Note: Our SOTI MobiControl version is: 14.3.4.1087
Hello everyone, I would like to know if it is possible to automatically approve the authorizations that MobiControl requests using OEMConfig. In my case it is about Zebra and Samsung devices. Have any of you had any experience with this?
Hello. We have the Mobisys MSB3 app configured as enterprise app. In the app policy we configured the profiles in the Managed App Config. Everything works at first, the devices get the app with the right configuration, but after 1 day the profiles are gone, and the app reverts to a configuration we had in the past. Before using enterprise app source, we had it in managed google play store. We switch to enterprise app source because somehow, we had issues with the app getting updated from google play store (even though we setted the profile for Managed Google Play to never update). The managed google play app policy is not assigned to the devices (only the enterprise app), so i'm not sure what can be the problem here. Maybe a left over configuration from this version? As a workaround, we uninstall the app from the devices, then it gets reinstalled again with the right configuration, but this is quite annoying to do everyday. Devices in use: Zebra TC52/53/8300, ET51/ET40. Android version: 10, 11, 13 Soti Mobicontrol version:15.6.6.1010 on prem
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
