Android Enterprise
The phone enrols to the company before anyone finishes the wizard.
Zero-touch enrols company-owned Android devices at first power-on or after a factory reset. We are an Android Enterprise zero-touch reseller: devices bought from us are added to the organisation’s account. At startup, once there is a network, the handset downloads the chosen device policy controller (DPC) from Google Play. For us that is usually FAMOC or Knox Manage. There is no path that says “this is my personal phone”.
World Support Service sells and deploys MDM, including FAMOC and Samsung Knox, and is an Android Enterprise zero-touch reseller. The named mobile-network partner is Play. We are not an official FancyFon or Samsung partner. There is no price list.
Four steps before the device reaches people
-
01
Buy from a reseller
The reseller creates the zero-touch account on the first such purchase. The Google account has to be a company account, not a private mailbox.
-
02
Configuration
In the portal you name the DPC, the policy data from the MDM console, and the text a person sees at startup.
-
03
First power-on
The device asks Google whether this identifier has a configuration. With no network, enrolment waits.
-
04
The DPC takes the device
The controller installs from Google Play. A factory reset returns to the same configuration for as long as the account holds the device.
What zero-touch will not do
- Google services and Google Play have to be present and enabled. Manufacturers leave some models out of the programme.
- The programme takes hardware bought from a zero-touch reseller, not a phone from a consumer shelf. Android 9 and later is the usual base; some models work from Android 8, Pixels earlier.
- The DPC has to be on Google Play and able to run a fully managed device. From Android 10 a work profile on company-owned hardware is also possible.
- These are company devices. A phone an employee bought privately does not enter the fleet this way.
Security angle
- The user cannot skip enrolment in the setup wizard.
- After a reset the device returns to the company, not to an empty Android, until you remove it from the account.
- Zero-touch itself does not set the APN. The console started by the DPC does: FAMOC or Knox Manage.
- A SIM on the private APN is a separate lock. MDM enrolment does not replace the operator’s SIM list.
NIS2 and KSC
The device is on an inventory before it is handed to an employee. That is order in the description of assets and of the initial configuration. It does not decide whether an entity is essential or important, and it is not NIS2 or KSC compliance.
Request a proposal APN types and connection types +48 698 355 667
Device count, the role (POS, fleet, scanner, machine) and whether the hardware is company-owned go in the form. Prices are not published.
Related
On the same path
-
MDM and private APN
Enrolment, the profile, and a console reached only from the APN.
-
POS terminals
The screen stays in kiosk mode. The terminal SIM stays on the private APN.
-
IoT devices
Android in a machine or a scanner is in MDM. A sensor stays on the SIM.
-
Temperature
The logger rides a SIM in the APN. A screen gateway, if any, uses zero-touch.