You’ll now see all the policies deployed to the device from MEM including policy version, apps, settings, etc. Back arrow to the Device Policy screen and select the three dots in the upper right hand corner again, then check the box next to “ All policies“. Open the Android Device Policy app and select the three dots in the upper right hand corner > select device details > scroll down and look for “ Model” and tap until debug items is enabled. I was poking around settings and I discovered a really helpful option for devices enrolled with MEM. As such, contact Google to provide feedback about other debug features you may need in the CloudDPC.
The process is specifically for the CloudDPC Google provides for EMMs utilizing the Android Management API (which MEM does). Note: the process above may not work (and probably doesn’t) for other EMMs who create their own DPCs. If you’re using the Managed Home Screen (as shown below), tap on the back arrow several times (ok 15 times) and on the menu select “Launch Android Device Policy app” which takes you to the DPC app where we can view and sync policy. From there you can sync the device and view which apps were installed and policy settings. Once enrolled, locate the DPC app by navigating to Google Play and selecting and opening the Android Device Policy app. The DPC is automatically installed on the device during enrollment. When devices are enrolled with MEM they utilized what is called a Device Policy Controller (DPC). For the purposes of this post, I’m going to focus on Device Owner (Android Enterprise), however these methods may be applied to other enrollments as well. There are various enrollment methods Goole offers for Android devices, such as Device Admin, Work Profile, and Device Owner. If the troubleshooting information doesn’t reveal what you’re looking for we can head over to the device for direct troubleshooting. Start with the troubleshooting console and work forward.
It provides a consolidated view of policies, apps, compliance, and much more. There are several tools that can be utilized to troubleshoot Android devices and as with most troubleshooting, it’s a process of peeling back the layers until the issue is found and remediated.įor devices enrolled with Microsoft Endpoint Manager (MEM) I recommend starting with the Troubleshooting section within the MEM Intune console. In this months post I dig into logging and debugging Android devices enrolled with Microsoft Endpoint Manager.
Additionally, learning how to debug a device is not a bad thing, in fact anyone can do this. When managing devices at some point there will be some sort of issue that requires a deeper level of troubleshooting.
0 kommentar(er)
