The following represent some of the most commonly asked questions around zero-touch.
As of March 2018:
As of March 2018:
The device will display a message stating it has been added to the zero-touch program and automatically factory reset within an hour.
The config won’t apply until after the device is reset. Anything after the “checking for updates” prompt is too late.
Nothing until the device is reset, at which point it will not be prompted to enrol into management.
Nothing until the device is reset, at which point the new config will apply.
The device will allow normal setup, however once connected to a network will prompt the user to reset, or will reset automatically after an hour.
It will be forced to enrol back into management automatically following the data erase, unless a config has not been applied, or has since been removed.
This action results in the device being irreversibly removed from zero-touch management. Please contact the device reseller to add it back in. The IMEI will be required.
No, please use an EMM solution for day-to-day device management.
No, it does this extremely quickly.
Work-managed and work-managed work profile (fully managed work profile).
No, only authorised resellers.
Yes, if they have been added into the console as an admin or owner.
These are a selection of DPC-specific key-pairs which manipulate the enrolment experience. An example may be pre-populating the EMM server, or enabling system applications. They vary between EMMs so do validate before attempting to use one.
Yes, however this only affects new devices added and not those already on the console.
Yes, via the CSV template provided.
Yes, either by requesting a new console from a new reseller, or adding a new reseller through the existing console.
No. While zero-touch is mandatory for Android Enterprise Recommended, devices that don’t meet Google’s requirements for storage or spec can and still do support provisioning via zero-touch.