The following represent some of the most commonly asked questions around zero-touch.
OEMs supporting zero-touch include:
- HMD Global
The complete list of zero-touch devices can be found here.
Regions in which zero-touch resellers can be found include:
The complete list of resellers can be found here.
Nothing until after the device is reset.
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.
Does enrolling via zero-touch slow down or cause any delay to the setup process while it’s retrieving the zero-touch config?
No, it does this extremely quickly.
Fully managed (including COSU) and fully managed with work profile.
No, only authorised resellers.
Only console admins or owners from the customer portal, or the reseller. End-users cannot remove their device from zero-touch enrolment.
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 account 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.
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.
A collection of DPC extras for various EMM/UEM vendors can be found here: Android Enterprise zero-touch DPC extras collection
The upload may complete successfully, but the device will not initiate the zero-touch enrolment flow once connected to a network. The device will need to be deregistered and re-registered with the correct manufacturer.
Yes, on an opt-in basis. As no Android Go device would meet Android Enterprise Recommended requirements, zero-touch is not mandatory. Check with the OEM before purchase.
Need something else answered? Comment below or tweet @jasonbayton. Questions may be republished on this document.