In the console go to "Rules" -> klick on the Robot ("Android Plus") -> right click Add Devices -> Create Add Device rule

hi,

tnx, i did create a rule, but not sure what settings are the best or if there is any trick for that, to download API, server deploy, google play.. there i have a problem. Because I did try some enrolment, but it was not ok, i cannot connect on talbet to the server.

I can't say anything to your network setup/restrictions etc..

But the opinions might be different on "which is the best setup". We use Google Zero-Touch and fully managed devices (android enterprise), so every device which has an internet connection during enrollment will be located directly into our mdm.

So, all our devices are useless if someone will steal it and wants to use it online (if you enroll it offline and then put it online, it will be reset to factory defaults after 1 or 2 hour(s)) and they are easy to enroll for every employee who has to do it themselves maybe.

But you have to ensure that the devices and the server are reachable from every location you need it.

Hi Darko,

Using Zero-Touch Enrollment for Android-Enterprise device is a good way to implement device-theft-deterrence.

If your device needs to be enrolled with OEM specific classic Android-Plus device agent, you still have the choice to use "Factory-Reset-Protection" to implement some level of  device-theft-deterrence.

There are so many different options available in the Add-Devices rule to support different use-cases, and it is hard to define any best-practices that is applicable for all cases.

Maybe you can provide more information about your use-case, and others can then comment on what options are likely preferred.