User Profile
jarmo_akkanen
Level 2.0: Eclair
Joined 2 years ago
User Widgets
Contributions
Re: Smart watch notifications for work profile are being blocked by Android Management Policy
PrathikSooonerondraandyRakib Here is the configuration for the MS Intune. Unfortunately "CUSTOM" profile type is only available for BYOD and not for the other methods (COPE/COBO). Please see the image attached below. We opened the ticket to Microsoft to understand how to do this in COPE/COBO. Microsoft also ending support for CUSTOM for BYOD on April 2025. https://techcommunity.microsoft.com/blog/intunecustomersuccess/intune-ending-support-for-custom-profiles-for-personally-owned-work-profile-devi/4287414 Sign in to the Microsoft Intune admin center. Navigate to Devices > Configuration profiles > Create profile. Select Android Enterprise as the platform. Choose Corporate-owned with work profile and then Custom as the profile type. Add a new OMA-URI setting with the following details: Name: Enter a descriptive name. OMA-URI: ./Vendor/MSFT/WorkProfile/PersonalAppsThatCanReadWorkNotifications Data type: String Value: Enter the package names of the personal apps that should be allowed to read work notifications, separated by commas. Thanks Jarmo6Views1like2CommentsRe: Smart watch notifications for work profile are being blocked by Android Management Policy
Hi Rakib Thanks for your reply, much appreciated! Notifications works on Pixel watch (other watch brands as well) when device is enrolled as BYOD. Sometimes, might require to install the same Work Profile app on your personal profile. For example Outlook app. No need to set it up or have a personal Outlook account, just the app installed in personal profile. I just tested with MS Teams and it's not installed in my personal profile and I am still receiving Teams notifications on my Pixel watch. What's important is to enable notifications on your Work apps and of course in the watch settings app itself Need to ensure that notifications for each app to be synced with watch is enabled on your phone paired with watch in "Settings - Notifications - app notifications". Problem is the COPE enrolled devices paired with watch. We have all corporate owned devices enrolled as COPE and this generates lot of complains from end users. thanks Jarmo246Views0likes3CommentsRe: Smart watch notifications for work profile are being blocked by Android Management Policy
Hey, we share the the same issue. Smart watch cannot see/get the notifications if device is enrolled as COPE. I'll check with Microsoft how to get this set in Intune. If anyone already have the info, please share. thanks Jarmo370Views0likes7CommentsRe: Basic WiFi-profiles (configuration profiles) do not deploy into Device
Hey all, Yes, I can confirm Android WiFi issue is now fixed and WiFi profiles can be deployed normally to the devices. CloudDPC updated in production by Google. No actions from end user is required. Case closed. thanks Jarmo716Views1like1CommentRe: Basic WiFi-profiles (configuration profiles) do not deploy into Device
Hi Rakib jasonbayton Moombas mattdermody smithappdevjohn Root cause found! We just got the new important information from our Google Technical Account Manager. “According to Google engineering this issue should be fixed in CloudDPC v124, due for production at the end of January.” Referring to info from Google, issue seems to be on Google side after all. I have asked more details from Google. Could you please open issue resolution bit more? So, Google will make some configuration changes to CloudDPC and this goes to production end of January 2025? I mean... is the configuration (configuration update missing) the root cause which keeps Wi-Fi profiles failing to deploy Android 15 devices enrolling as COPE? Does this require some action from our end and/or from Microsoft to get those changes implemented to EMM (MS Intune) once in production from Google?" I'll keep you all posted once getting answer. thanks Jarmo2KViews2likes0CommentsRe: Widgets on COPE - MS Intune
I got the info from Microsoft yesterday: "At the moment it’s not possible but let me ask our Intune PG if there is anything on the Roadmap or if we need to raise a DCR or similar." I replied to them since we have had case opened to them about this 2 years for now. I think they will take this seriously now.... I'll keep you posted.. thanks Jarmo2KViews0likes6CommentsRe: Basic WiFi-profiles (configuration profiles) do not deploy into Device
Hi colleagues, *UPDATE* We have done lot of testing related to this basic Wi-Fi profile deployment issue. We believe it's Android 15 + COPE issue because all the other scenarios working fine: BYOD enrolled devices get WiFi profiles successfully deployed to device (Android 14/15) COBO enrolled devices get WiFi profiles successfully deployed to device (Android 14/15) COPE enrolled devices get WiFi profiles successfully deployed to device (Android 14) COPE enrolled devices do NOT get WiFi profiles successfully deployed to device (Android 15) At the moment Google passed the case to the wifi team for any changes in the Android V that might be rejected in the ONC (open network configuration) specifications. I'll keep you posted..... jasonbayton mattdermody Moombas smithappdevjohn Thanks Jarmo2.3KViews2likes2CommentsRe: Widgets on COPE - MS Intune
Hi GMenzies jasonbayton Lizzie Moombas Finally there is a solution to get widgets available on COPE enrolled devices. To enable widgets to a specific application, you need to utilize this policy (addCrossProfileWidgetProvider), and make sure to add the package name of the application (for example com.microsoft.office.outlook) that you want to enable its widgets in the parameters. Please contact your MDM vendor (our case MS Intune) and raise a request to implement this API if they haven't done so already. https://developer.android.com/reference/android/app/admin/DevicePolicyManager#addCrossProfileWidgetProvider(android.content.ComponentName,%20java.lang.String) We will test this asap once we get the API implemented by Intune folks. Keep you posted.... Google engineers have tested it using testDPC and it works. Before: Configuration: After: thanks Jarmo2.1KViews4likes8CommentsRe: Basic WiFi-profiles (configuration profiles) do not deploy into Device
Moombas smithappdevjohn Latest info from Google engineers: We tested it on Intune and Knox Manage EMMs and WiFi configuration is NOT working on A15 and COPE mode. However, using our vanilla test DPC it's working properly on the same device and configuration. After all.. might be something EMM (Intune) related.... I'll keep you posted -jarmo2.6KViews1like1CommentRe: Basic WiFi-profiles (configuration profiles) do not deploy into Device
Thank you Moombas and smithappdevjohn for your replies, much appreciated. We (SAP) have Premium Service agreement with both Microsoft and Google. I have opened cases for both. Google already mentioned they have another customer experiencing same issue. I'll keep you posted once we get more info. UPDATE Info: We only have Samsung and Google Pixel devices in use and this issue only occurs with Google Pixel devices. But I think it's because we don't have any Samsung devices running on A15 at the moment. Thanks Jarmo2.7KViews1like0CommentsBasic WiFi-profiles (configuration profiles) do not deploy into Device
Dear all, Since three weeks ago we noticed issue to deploy basic Configuration profiles (WiFi) into devices (MDM is Intune). Problem ONLY occurs with newly enrolled COPE devices running on Android 15. So we think it's Android 15 (Google) issue on COPE enrolled devices because all the other scenarios working fine: BYOD enrolled devices get WiFi profiles successfully deployed to device (Android 14/15) COPE enrolled devices get WiFi profiles successfully deployed to device (Android 14) COPE enrolled devices do NOT get WiFi profiles successfully deployed to device (Android 15) Anyone else noticed the same/similar issue with Configuration profiles with Android 15 clients? Best Regards JarmoSolved2.8KViews2likes19CommentsMicrosoft Company Portal App
Hi all, Seems that latest Company Portal version from Microsoft is having some issue. Problem description: Installation from Play Store is working but launching Company Portal app, it just freezes with logo on the screen. Never does anything, just freezing. We have case opened to Microsoft. Keep you all posted. Version 5.0.6170.0 Published 28.2.2024 Please test if you have BYOD method setup for your company. -jarmo2.9KViews2likes3CommentsRe: Samsung Secure Folder and DUAL messenger features - not available in COPE
Hi Moombas, Good point, we have not tried to provide secure folder as a work app because this app is only used for personal purposes. Employees want to store their private photos, files, banking apps etc... in secure folder. Anyway, thanks for the hint. We will test option to provide secure folder as work app. -jarmo6.3KViews0likes0CommentsSamsung 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.4KViews1like4CommentsRe: What OS rel. your Android fleet is running ?
Moombas App topic is good one and requires always big attention. We also need to make sure our internal apps are supporting and tested with the latest OS. Normally Microsoft etc.. work apps are fully compliant with new OS but sometimes we see issues on personal apps.3.6KViews0likes0Comments