Managed 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?
OEM Unlock toggle not available
Hi all, Recently joined the community, first time poster here. TL;DR at the bottom. Hopefully my question has a simple solution but I've looked everywhere (except here of course). I'll try to keep this as simple as possible. Everything is in UAT if that matters. The important bits: Pixel 8a Build BP1A.250505.005.B1 No SIM or eSIM Android Enterprise registered to my UAT Tenant I'm testing some scenarios for automating device compliance with Omnissa using Workspace ONE Intelligence. To test this successfully I'm going to need to flash back to an older Build and probably more than once for demo purposes. The OEM Unlock toggle is not available however, and I this is preventing me from doing my testing. I've read conflicting posts elsewhere regarding carrier unlock, SIM and/or eSIM etc. ADB is working fine but flashing older images is just not working. Any help from the community on how to get OEM unlock enabled would be greatly appreciated. TL;DR: Need to flash a pre 250505 build to my Pixel 8a. Can't toggle OEM unlock as it's greyed out.
High Priority mode takes 10 hours to update apps on devices
Hi everyone, In our MDM Workspace ONE UEM, we are conducting tests to update Google Play applications on corporate devices under the following scenario: New version of a managed app published in the Production track, deployed in High Priority mode to 100% of devices (no staged rollout). The Android devices have a profile installed with the "Auto update" payload configured to "Always auto update", with an all-day window so the update can occur at any time, ignoring the documented restrictions (https://support.google.com/work/android/answer/9350374?hl=en#zippy=). According to our tests, the device updates itself (without manual intervention) in around 10 hours on average. We expected the update to occur more quickly in this scenario, and we require greater agility for Production deployments. Is it normal to wait around 10 hours for an update in this scenario? Is there anything else we can configure to reduce the waiting time? Thank you very much, Vicente
Google Managed Play - Revoke app approval when app requests new permissions.
have a question regarding controlling the managed App version upgrade on device and restricting this via Google managed play https://play.google.com/work. Using managed google play app if I use “Revoke app..” option ( Refer screenshot), App will be unapproved from managed play store and removed from device Managed Private playstore followed by uninstallation from the device whenever there is new permission requested or new release has been pushed by app developer? OR App will be just unapproved from managed play store and will not impact any device already installed the app? 2. App getting Unapproved on managed playstore will see any impact on devices if the app was earlier pushed on Devices as the available app via EMM sol. like Intune. AirWatch ( not required / non-mandatory app) and device have not installed this app and now trying to install the app after this change on Google managed play https://play.google.com/work as unapproved? 3. After approving the app, will new update will be pushed to the device automatically if the app is already installed with old version or device has to reinstall this app with new version?
Samsung 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 -jarmo
