Replies posted by w4lter

@jasonbayton im sorry for the late response, did not get a Notification.we’re just using Samsung KME and within the Work Profile Enrollment also the Samsung Knox Service Plugin.What do you mean exactly with, other active Knox admin apps?in the list of device admins there is nothing left to disable, just the “Enrollment Service” app.

@jasonbayton KSP is in use, but just for 2 Features (Date move Personal->Work, Screenshots Work Profile saved in Work Profile)I will try my luck again at Samsung. Thanks Jason

@jasonbayton yes, this is what Company Portal gave back, while “Enrollment Service” is still active as Device Admin:   

Hi Jason, thank you very much for your fast answer.I dont get it, why Samsung Knox Support rejected me with the Information, that the Enrollment Service does not come from Samsung. Maybe i will try it again to consult them.The Story behind is “quite” simple.I’ve had the case where a user left the company AND was somehow allowed to keep the mobile phone. Technically it was clear, a Retire (Relinquishing ownership) is the right way - at least, it sounds like this.Anyway - the user which left the company started of course in a new company, and they told him you can enroll you BYOD Device with Company Portal. Well, the answer is no - Company Portal cannot take over the control, because Enrollment Service is active as Device admin app. So Company Portal is not able to take over the Device admin role :-).So, somehow a new learning. COPE = all the time a WIPE… :-) 

Which E-Mail App are you using?For example, with Microsoft Outlook, this is not supported - here you need to search you GAL Contacts within Outlook App. Just your own Contacts can be synched to native Contacts App (which of course breaks time to time)

Same issue also in our Environment. (COPE, MS-Intune)It seems that this really just applies to A-Series Devices, no single report from S-Series Users.

Hi @Emilie_B , Yes we're using MS Intune and no I didn't create any ticket so far. But I've created a Reddit post, and they say it just doesn't work unfortunately.i was working with Lizzy (here Google Community) and with Microsoft Support on it. There was never a solution for it.Because our fleet is working with Samsung devices, we've decided to go with Samsung Calendar instead of Google Calendar on COPE Devices.Maybe you have a look into a diffrent 3rd Party Calendar.

same thing for Samsung Devices with Samsung KME.that message is no longer visible after the enrollment profile is downloaded. but with a factory sealed device, there is no chance to hide it.i assume the easy solution would be, that the device is doing the network setup right away after the language selection to check for enrollment profiles.

hi, sorry - i have no idea how i could prevent installs on COPE devices. just know how to release an app to a managed google play store.do you have any screenshot or google guide? thanks.

thanks! so, in my opinion, it should be not a problem to release for example Candy Crush with a new app identifier, for example: official:com.king.candycrushsaga new one:com.King.CandyCrushSaga I'm quite sure, that Intune App (COPE/fully managed Devices) are not able to handle those 2 app identifiers afterwards, while Company Portal App (BYOD Devices) is able to handle this.PS: Intune Admin Portal will find both Apps in Google iFrame. Also releasing both apps to devices will be fine. Just COPE devices will not receive the second app. Super weird case...

hi,i want to make an update of my initial post, because there are new findings. a bit late, but we found out that the app developer used the "same" App Identifier, but case-sensitive, so for example: App 1: com.android.myappApp 2: com.Android.MyApp in my point of view, i was thinking google does not allow this, but also on android itself it's possible to install apps side-by-side with that App Identifier like in my example. It seems, that "Intune App" which is the controller on COPE Devices is not able to handle case-sensitive App Identifier, while "Company Portal App" on BYOD Devices is able to handle this. On COPE Devices, App 2 is not visible because (i guess) Intune App is thinking that App exists already. Also interesting finding -> if i set in Intune App 2 as "Uninstall" then App 1 will be uninstalled. If i set in Intune App 2 as "Required" then also App 1 will be installed. I'm quite sure this is a 100% Microsoft (Intune App) issue, but Microsoft

hi jason, group assignments are set to "Available for enrolled devices" without any filters. pretty straight forward. i have on my table 2 devices enrolled with my user (im allowed to the app, because im member of one assigned group)BYOD -> App is visibleCOPE -> App is not visible and not searchable

Hi Martin, Have you attempted to search for the application using its complete package name? For instance, with the ChatGPT App:  BR,Walter 

Hi Jason, Thank you for the prompt response. I have a quick question to ensure my understanding is correct: "...or uploading apps to a developer account not directly linked to a bind, but shared as private apps instead." Bind A = old EMMBind B = new EMM We have uploaded several private apps to "Bind A" and shared these apps with "Bind B" to make them available on the other managed Play Store, which works well. (Sharing process: Console Bind A -> Setup -> Advanced settings -> Managed Google Play -> entered Organisation ID from Bind B) Our current plan is to create new package IDs and upload them to our Developer Account, then share them again via Advanced settings in Managed Google Play with Bind B. If I understood you correctly, we can forego creating new package IDs and simply re-upload using the current package IDs? What would be the behavior on the devices? I assume there's no way to avoid uninstalling and reinstalling the apps, co

the only solution right now is, to pair the phone directly with bluetooth to the car itself. most car's headunits have a built-in telephonebook where contacts get downloaded - here, you can find work profile contacts. this settings should be Enabled for this: 

double post, please follow this link: https://www.androidenterprise.community/t5/admin-discussions/intune-cope-device-google-calendar-crashes/td-p/4728

 @ReeceK  I've had contact with Samsung Enterprise Support, they did an analysis of Samsung DumpState Logging. When there is no Google Account added to the Device, Google Calendar starts immediately the Sign-In Process for logging in into a personal Google Account - Personal Google Accounts are of course blocked on Work Profile side. I'm pretty sure, it has of course also something to do with Intune, but is there a way to prevent the Google Sign-In Process, when there are already "local" Calendars available?It seems, you cannot use Google Calendar without a Google Account...?

What we mean is, you create a ticket at MS and provide the ticket # (via PM) to @ReeceK or so if MS request involving Google.oh god, you are right - i was to fast with my response. will do that, thanks.

can you provide me some informations, how to open a ticket at google, especially for google calender?i just know how to open a request regarding our android enterprise managed google play account, but for google apps i really have no idea. thanks.

serval reasons... -) people want to have a "Week" view, Outlook just provides 3-Day View (please, dont ask, you know, there are always some special ppl) -) connect personal calendar -> work calender together -> this is it seems broken with outlook at the moment. outlook just crashes. we wanted to mitigate this with google calendar.

@Moombas @ReeceK  any idea how we could address this to microsoft? any chance to get logs from google calendar itself? i want to start making pressure in direction of microsoft to fix this asap.

had the chance to try a COPE enrollment on Ivanti EPMM (Core) - no issues there. i guess this has something to do with Intune 😞