omnissa workspace one
6 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?Solved625Views3likes24CommentsDistribute 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.2KViews1like2CommentsSamsung Secure Folder and DUAL messenger features - not available in COPE
Dear community, hope everyone had lovely Christmas time! I just wanted to raise one issue you also might been run into. It's about Samsung Secure Folder and Dual Messenger features on COPE enrolled devices. Unfortunately these features are not available in COPE enrolled Samsung devices. We used to have all 10k fleet enrolled as BYOD and Secure Folder/Dual Messenger features were/are available. Now only personal owned devices are enrolled as BYOD and corporate owned devices are enrolled as COPE method. Unfortunately there is no setting available for us to make this work on the COPE enrolled devices on EMM side. According to Samsung, they have not updated Secure Folder software in 5 years and and don't necessarily expect we will get any update. The "error message" is very misleading: "Security policy prevents the installation of Secure Folder". Because there is no security policy setup in EMM (Microsoft Intune) for this feature. It's just pure Samsung thing. As mentioned... Samsung Secure Folder solution does not work on COPE enrolled Samsung devices but nice surprise is that on ThinkPhone (Motorola) , Secure Folder works even on COPE. This also implies that Samsung really could make it work if they wanted to put in the development effort, as it is not totally restricted by the Android Enterprise architecture of COPE since the ThinkPhone is able to do it. But so far Samsung does not seem to still support this app much. More on this topic from here: https://communities.vmware.com/t5/Workspace-ONE-Discussions/Android-Samsung-Impossible-to-enable-Dual-Messenger-feature-or/td-p/2260737 -jarmo6.7KViews1like4Comments