api
4 TopicsNeed a way to switch zero touch configs with API
Hi ya'll, Just beginning to manage Android devices with Microsoft Intune and Google Zero Touch. Everything works great but I am looking for a way to automate switching a device between different zte enrollment profiles (configurations) e.g. fully managed, dedicated, azure ad shared mode etc. I've done this successfully on the Windows side. The basic flow is that when a device asset record gets updated in our asset management database, a middleware I created calls Intune APIs to name the device and move it into the proper security groups so it gets the right policies and apps. I wanted to replicate this flow on the Android side, but things work a little different with Intune for Android than it does for Windows. If I choose to use the Google ZTE iframe that's built-in to Intune, it makes everything a corporate-owned, fully managed device with no option to switch between different enrollment profiles (configurations). The other option is just to switch them in the Google Zero Touch portal manually for each device. But as I said, I want to try and automate switching the enrollment profile/configuration. Thinking about scaling up here and what that looks like. I'm aware that there is an Android Management API but it appears it's geared toward EMMs and developers, not necessarily a public API that my organization can use to access its own data. My questions for the community: Is there a way my org can use the Android Management API to configure device records in ZTE? Does anyone have any experience with automation in the Android Enterprise world? How does your org switch between enrollment profiles? Feel free to answer what you can. Appreciate it!1.1KViews0likes1CommentNot able to set wallpaper on managed chromebook using the Policy API from GWS
Hello Team, While testing the wallpaper management functionality using the Chrome Policy API, we observed that the wallpaper does not get applied on managed ChromeOS devices, even though the API calls return a successful response. When we upload the wallpaper image using the uploadPolicyFile endpoint, it successfully returns a valid downloadUri.and wallpaper gets applied on device. However, when we attempt to apply this uploaded image as a wallpaper using the Policy API, the request completes successfully (200 OK), but the wallpaper does not apply on the chromebook device. We’d appreciate your help confirming the following points: Are there any additional parameters, permissions, or policy fields required for either of the following? chrome.users.Wallpaper chrome.devices.managedguest.Wallpaper Are there any known propagation delays, caching behaviors, or policy refresh constraints that could affect wallpaper deployment on managed devices?Solved37Views0likes2Comments