Android Enterprise General Discussions

Hi all! I'm want to start testing the AMAPI via the testing options provided by Google. Just to test policies that are not yet embedded in mainstream EMM solutions.  I'm following this guide: Android Management API - Quickstart - Colab (google.com) as a starting point. All goes well until the step "provision a device". And cannot get a token or QR code visible.  When running the code in block 22, no token is returned.  I tried entering the policyname mannully but that returned a long error haha, so I'm assuming I just need to run the code and it will generate a token that I can use in block 23. Correct? If so, why is it not returning anything?  Hope someone is able to help, thanks! Michel

For years now, we have wanted to enroll our company-owned Samsung smartphones with Google Zero Touch (COPE) and adapt our service to move away from the work profile enrollment via company portal, which is time-consuming for the user. Since we are responsible for several thousand devices, we obviously test extensively and over a long period of time before we actually make a change to the productive service. We are mainly using the A-Series Enterprise models. Unfortunately, for years now, we have been repeatedly encountering problems as soon as there is an OS, MDM or Samsung OneUl update. It now almost feels as if stable operation is not possible with this trio. We've had better experiences with other device manufacturers, but unfortunately we've never had the feeling that we could run a stable productive service. It would be a nerve-wracking experience every time an update was due. Has anyone had similar experiences, or does anyone here use the desired scenario descr

I'm trying to make a basic MDM service for Android TV. In the beginning, I was testing everything on an Android phone, but when I started working with TV, I realized that TV devices are not supported by "Android Management API". I know that I'm not the first person who asked a similar question, but there was only one answer pointing out that it's not possiblehttps://support.google.com/work/android/thread/158930652/how-can-i-enrollment-android-tv-with-android-api-management?hl=en Maybe something has changed recently and now there is a solution.

Hi, we are trying to use Customer API according to the documentation: https://developers.google.com/zero-touch/reference/customer/rest/v1/customersMethod: customers.list works fine (GET https://androiddeviceprovisioning.googleapis.com/v1/customers)I am able to use Oauth2 authentication, get access token and use it for the above.When trying to use other methods (e.g.Method: customers.configurations.list) with my access token, I always receive a ToS error:​{"error": {"code": 403,"message": "The user must agree the terms of service for company id XXXXX at https://partner.android.com/zerotouch","status": "PERMISSION_DENIED","details": [{"@type": "type.googleapis.com/google.android.device.provisioning.v1.TosError","latestTosAccepted": false}]}}How can accept these terms of service and fix the above error? When I open the zero touch portal with the same user, there's no option to accept anywhere (I have the owner role). When terms of service are opened from the bottom left of the screen, the

We are using Microsoft Intune MDM to manage over 2000 Android devices and are having difficulty allowing devices to communicate with Intune from within our network.  We have followed several network requirements docs including the following: Network endpoints for Microsoft Intune | Microsoft LearnAndroid-Enterprise-Migration-Bluebook_2019.pdf (googleusercontent.com)Android Enterprise Network Requirements - Android Enterprise Help (google.com) We must have checked and double checked the URLs and ports from these documents a dozen times. We were able to get devices to check in at one point but after a few months they all stopped checking in again. For this reason, we believe that there must be a URL that points to an Endpoint or Endpoints that change periodically.  If we whitelist the entire *.google.com domain all devices are able to check in immediately however we are unable to do this as it would mean allowing access for every single device that connects

Hello, I have access to https://partner.android.com/zerotouch (or to the nice new portal 🙂) to manage which configuration I want to send to our devices. The account I use is "owner". I have created a project with Partner API in Google Cloud. For now I try to query my device list with androiddeviceprovisioning.googleapis.com using OAuth 2.0 Playground with that URI : https://androiddeviceprovisioning.googleapis.com/v1/partners/my_company_ID/devices/*But all I succeed is to have an access denied :{  "error": {    "status": "PERMISSION_DENIED",     "message": "Request had insufficient authentication scopes.",     "code": 403,     "details": [      {        "reason": "ACCESS_TOKEN_SCOPE_INSUFFICIENT",         "@type": "type.googleapis.com/google.rpc.ErrorInfo",         "domain": "googleapis.com",        

Hi all, I have a simple question:Are there touchpanels or whiteboards (75 inch and larger) that can be managed by Android Enterprise?Thanks in advance. Robert

Hey! We have encountered a potential problem with a few devices. The devices use automatic enrollment. Users have to continue in the setup wizard and enroll the device against the MDM before it can be used.For some devices, we have found a way to break out of the setup wizard. Without a restriction payload, apps can be sideloaded and data can be modified in the main user. Although the navigation bar, app drawer and some other features are restricted, this is sufficient for manipulation.If you go back in the navigation bar, you end up back in the setup wizard and the device looks like it has just come off the production line.My expectation with COPE enrollment was that the enrollment would fail because data had already been changed in user0. However, the enrollment could be completed without any problems and the previous adjustments were retained.Does anyone know when CO enrollment is no longer possible? Does this restriction depend solely on whether the setup wizard has already be

Hello, We've just started testing Zero Touch and one of our AZT early adopter device users recently left the company. We're trying to give his device to another tester however after a wipe of the device it's prompting to verify identify and asking for the previous users PIN / Google account (which we don't have) before the AZT assigned MDM enrollment kicks in... We were not expecting Zero Touch enrolled devices to be locked to previous users at all. Expected this to be similar to Apple DEP enrolled devices where we can easily wipe and re-issue those without any hooks to the previous users apple ID.Is this expected behavior for Zero Touch that a Corporate Device registered in Zero Touch is still hooked in to a users Google account and we cannot wipe and reissue the Corporate Device to a different user?

Hello everyone,Currently, we are using Android Enterprise devices enrolled (COPE) on the Workspace One MDM. We have started migrating to Microsoft Intune and would like to add the same Google account for the Managed Play Store that we are using on Workspace One, as the two EMMs will need to coexist for some time. Additionally, on this account, many developers have made privately developed applications available for our company, so we would like to avoid having to create a new account. Is it possible to simultaneously use the same Managed Play Store account on two different EMMs?

Hi, I had previously made a policy for a device and provisioned it. I made a second policy and tried to provision another device, but when I ran the code to generate the QR code it generates a link for me but when I click it, it says 404 Not Found - I did it through the Android Management API Quickstart notebook. What could cause this? All the previous code for executing the policies and generating the token worked fine with no errors.

can I check if this is still the latest Bluebook from 2019? https://static.googleusercontent.com/media/www.android.com/en//static/2016/pdfs/enterprise/Android-Enterprise-Migration-Bluebook_2019.pdf it looks like a couple of the URL's are still incorrect as listed as *gstatic.com and *gtv1.com without the additional "." enforcing the subdomain, this could cause a misconfiguration and possible security issue. and if any new URL's need to be excluded from proxy and firewalls thanks 

[Personal information hidden]   *Personal information hidden for privacy reasons in line with the Community Guidelines

회사가 EDLA를 체결을 하였는데, GMS 사용을 정식으로 할 수 있다는 것은 알고 있습니다. 혹시 이와 관련한 문서를 확인 할 수 있는 곳이나 받아볼 수 있는 방법을 없을까요? 거래처에서 EDLA 를 하면 무엇이 좋고 안받았을 경우엔 어떤 문제가 있는지에 대한 공식적인 문서를 받고 싶다는데, 어떤 자료를 제공하면 될지 난감합니다. 

Iam trying to setup zero-touch enrollment for android devices using intune. My reseller is telling me they are unable to add my account to enable the linking of zero touch (even though they are a authorized reseller), and tell me to contact google support...? I have linked our admin-email in the account creation, and i can manage the account in the "normal" account management, but in the ZTE portal i simply get "no account found".

Hi we are one of the leading Android device seller company from India and we sell devices directly to customers and also to companies. We need ZT so that we have applied for the Android partnership program for ZT multiple times but the application is getting rejected again and again. We tried to send email multiple times to the ae community but there is no exact reason mentioned . Can you help me to approve it?

Why am i getting the error "404. That’s an error. The requested URL  "https://zerotouch.googleapis.com/v1/customers/$CustomerId/devices/$Imei" was not found on this server. That’s all we know." Im following the instructions provided here. https://developers.google.com/zero-touch/reference/customer/rest/v1/customers.devices/get Im just trying to search for an imei number in my zero touch portal located here https://partner.android.com/zerotouch I was able to retrieve authorization code using https://accounts.google.com/o/oauth2/auth and scope=https://www.googleapis.com/auth/androidworkzerotouchemm Then I able to generate access token from authorization code but when attempting to retrieve an imei number using "https://zerotouch.googleapis.com/v1/customers/$CustomerId/devices/$Imei"  customers get method. I get the error stated above. Can someone help!

How can i setup work in my phone. 

Hi,   Currently I have a Google Workspace login with 20+ accounts, and this account[Personal information hidden] is the super admin of the workspace.Recently one of the employees left the company, so we set up the forwarding option from her inbox [Personal information hidden] to mine, Hannah's.Then I deleted her account since is no longer needed but I still receive her emails and I do not want that. Is there a way to end this?   Literally I tried everything.   *Personal information hidden for privacy reasons in line with the Community Guidelines

My org. recently started with management of Android units, and use Google ZeroTouch for deployment, and Intune as a MDM software. We set up our Google Zero Touch account before we ware ready to manage our androids phones. So several of the phones we bought after we set up our google portal is added in the zero touch portal from our distributor, but i quickly before we started using the phones removed the konfiguration profile from the phone.  But now i am finished with testing different provision methods and setups in intune and i am ready to provision this setup to our phones. We have no problem provisioning new phones, but phones that are in our portal, but with a removed configuration profile i cant seem to manage again.  I know that i cant add phones into the portal myself, but i really thought it would be possible to re provision configuration onto the phones that already are a part of the portal. Does anyone know if i am doing something wrong, or if this is ev

Hi everyone. It's possible Edit QR Code to add only one system app or any other app? Thank you.

Requirement is only trusted network will allowed office 365 application like Outlook, teams & etc. Applications will allowed to open through trusted network else not able to open the applications.

Hello everyone,   I hope you are having a good week.   A management solution helps you to set up, secure and manage your devices in your organisation. I see it like a comfy hub for you to ensure that your devices are working as you expect (whatever size your company is). So understandably, one of the biggest decisions when getting started with Android at work is choosing the right EMM (Enterprise Mobility Management) for your needs. There is a solution out there to meet almost every need and use case, and sometimes knowing where to start can be tricky.    We are lucky here in the community, that many people have already been through this decision and there is a huge amount of experience. The Solutions Directory is a useful place to explore partners and solution options, but there are also many questions and things to consider beforehand, so this got me thinking it would be great to share community tips/advice around this.   What tips would you recomme

I i have started  to notice a new issue recently while enrolling  a new device in android device  management. The  issue is  that while enrolling a new device to EMM(using the generated qr code), all the required app gets installed successfully but after some time  it produces  a crash with error "Google Partner setup has stopped". Clearing the cache  is not  working  for me.  Also lot  of  my devices which is  at client locations are getting  this issue as   well, I   dont have direct physical access to these locations as well,  is  it  possible to  fix the  issues, maybe by  making  any  changes in the  policy. Also, i have not made any  recent  changes in my policy  , this issue started coming up from the  last   week onwards 

We are using Android management API to enroll managed devices. We have a custom app that is required for setup. For this app we also send managedConfigurations in the policy, some string data. To get the data are using RestrictionsManager in the app, so when the app is first opened from "required for setup" action, we create the RestrictionsManager's object to get the managedConfigurations but there is this issue that we face. Scenarios:When we create a fully managed device then their is not issue, custom app gets the managedConfigurations. But if we create a work-profile and set the custom app as required for setup and when the app try to get the  managedConfigurations then null is returned. This issue specifically rising in the Moto devices that we have for testing (Moto G32 devices). For some reason it works fine sometimes, so if we enroll the devices let's say for 15 times in work-profile, then it may work 3-5 times, this is not for sure, it may work and it