Enable ADB debugging is grayed out - This setting is managed by your administrator

Hi Christophe_Roux​!

Can I please check if you were meant to ask your question in the Android Enterprise community or int the ChromeOS community? 

Thanks, 

Emilie 

I don't know the end point but in our MDM at least for Android you can enable/disable ADB via a feature control profile:

So, there must be a setting available to allow/disable it.

But I'm pretty sure it's this one (as said for Android): https://developers.google.com/android/management/reference/rest/v1/enterprises.policies?hl=en#DeveloperSettings

So, not sure about Chrome or even Chrome OS or Chrome admin console but i found this one:

https://help.mobileguardian.com/hc/en-us/articles/360010957200-How-Do-I-Disable-Developer-Mode-in-Chrome

After reading again your answer proposition, I see that your proposed solution is for Android hardware which do not apply for Chromebook (using Chrome OS). I know that Android Os and Chrome Os are related but for this specific issue (downloading an Android Studio developed application from Chrome OS to an Android Hardware), Android OS and Chrome OS are not equivalent.

As Google was not able to unlock the Chromebook toggle "Enable ADB Debugging", I found a work around using "Wireless debugging"; it used to work but now it fails when pairign the device: there are two options: 1) a QR code (does not work, the QR code is not recognized by my Android phone) 2) pairing with a 6 digit codes; this second option used to work but not any more: the chromebook says "an error occured during pairing"; and the Android phone says it is paireed with a new device (it has a list of the paired devices and the chromebook is listed but the chromebook on his side is nto paired).
So nwo it becomes an Android concern: it should not register the chromebook as pairde when the chromebook says it had a problem pairing with the device and failed pairing.
I hope to have soon an update of Android Os and Chrome Os in order to solve these both errors.

Now the issue concerns Android on two levels:

I have found a work around using "Wireless debugging", it uses wifi.

For this to work, it needs pairing the device on the Chromebook.

There are two options:

1. use a QR code: here is the first Android concern: the Android phone fails to identify the QR code;
2. pairing with a 6 digit code: this used to work for a few times, but now when entering the 6 digit code given by the Android phone, the Chromebook says the paring failed due to an error; the Android concern in this case is that even if the pairing failed, the Android Phone registers the Chromebook in the list of registered devices (but the Chromebook do not); then it seems the Android Phone is missing a final check to verify that the Chromebook succeeded pairing.

Thanks for sharing your experience! It sounds frustrating to have ADB debugging grayed out despite being the admin. Hopefully, Google Support provides a clear solution soon. Others facing the same issue, sharing your steps or workarounds here could help the community.