soti mobicontrol
9 TopicsManaged configuration to Gboard has disappeared from MDM
The ability to apply a managed configuration to Gbaord has disappeared. We think this is due to a recent change to the Gboard app where Google has removed this ability. Environment: MDM = Omnissa Workspace One UEM (we are also hearing reports of this impacting SOTI customers as well) Rugged Zebra Mobile devices, majority running either A11 or A13 Leads: Managed App configs are still present on Chrome & ServiceNow Now Agent, hence why we believe this is not an MDM Console issue. We have escalated to Omnissa support anyway, who have in turn escalated to Google. Is anyone else seeing this issue?Solved1.2KViews3likes30CommentsDistribute apps with existing package names via Managed Google Play / MDM
Hi, in general, Android Enterprise devices are always getting the latest version of an app that is available via Managed Google Play. But, there are some edge cases like: older version needed (example: Citrix Workspace app deprecated app for Android 11 and below, might be problematic for special devices like handheld-scanners) beta tests (example: Microsoft Teams, would be awesome to provide this inside the Work profile) In both cases you are receiving APKs from the vendors. For Citrix Workspace they are available here: Download Earlier Versions of Workspace app for Android - Citrix I've tried to discover possibilities to publish them via Intune (should be equal for other MDMs): Private App in Managed Google Play Problems: Package Name not unique: The package name com.citrix.Receiver is already used by another application. APK too big. Limit of 100 MB Distribute app via Google Play Console / Developer private app scoped to Org. ID but, same problems as on Managed Google Play Change package name to something like "com.citrix.Receiver.contoso" tested with: https://apktool.org/ upload: package name now OK, but signature invalid "APK signature is invalid or does not exist. Error from apksigner: string_arg: "ERROR: JAR_SIG_NO_MANIFEST: Missing META-INF/MANIFEST.MF" Did I oversee something? Asking the vendors to build a custom app with own bundle name isn't feasible. Is there no way to publish such apps via MDM to Android Enterprise devices?Solved3.4KViews1like2CommentsZero Touch Enrollment Network Specifications
Hello! I'm looking for information regarding the network specifications for the Zero Touch Enrollment as well as any phone-home network requests. Are there any logs we can pull from ZTE or the Android device during enrollment? The reason I'm asking: We have thousands of devices that have been enrolled in SOTI MobiControl over the last few years, and about 1000 of these were enrolled via ZTE. We've had no issues with this until early March. I can't find a rhyme or reason for this, but certain devices that were successfully enrolled, configured by an MDM, QC'd, boxed up, shipped to the end user, and then powered on will get the message below before the eSIM is activated. These are Honeywell CT47 devices with dual SIM cards (1 physical Nano SIM and 1 eSIM). The device above was added to ZTE using the IMEI number over a month ago and was successfully enrolled, but when powered on later and connected to Wi-Fi, it reset itself before the eSIM could be activated. This issue is only happening to devices that are factory reset while on-site and connected to the Wi-Fi only. My best guess is that the Wi-Fi network is blocking something during the enrollment process, as this reset issue is not happening on devices that have been enrolled and working for months. Thanks for your time!76Views1like4Comments