Zero-touch enrollment is the preferred method for deploying Android devices at scale, and for good reason. Devices enroll automatically at first power-on, no manual setup is required at the endpoint, and the entire process is invisible to anyone at the deployment location. But zero-touch is not available for every Android deployment. It requires devices purchased through certified zero-touch resellers, and it is not compatible with all Android hardware, particularly older devices, custom Android builds, or hardware from manufacturers outside the zero-touch program.
For these deployments, Moki’s Android Agent pre-registration provides a comparable level of enrollment automation without the zero-touch hardware requirement. Understanding how it works and when to use it helps organizations choose the right enrollment path for each device type in their fleet.
What Android Agent Pre-Registration Does
Android Agent pre-registration allows IT administrators to configure a device’s enrollment details in Moki’s dashboard before the device is activated, so that when the Moki Agent application is opened on the device for the first time, it automatically enrolls and configures without requiring any manual input at the device level.
Without pre-registration, enrolling a device through Android Agent requires someone at the device to enter enrollment credentials, select a configuration, or scan a QR code. This is manageable for small deployments but becomes a logistics problem at scale when devices are shipping to dozens of locations with non-technical staff on the receiving end.
With pre-registration, the process works like this:
- The device’s serial number or identifier is registered in Moki’s pre-registration system before the device ships
- The correct configuration profile and device group assignment are linked to that registration
- When the Moki Agent is installed and opened on the device, it recognizes the pre-registered device, pulls the correct configuration, and completes enrollment automatically
- The device appears in the Moki dashboard fully configured and assigned to the correct group without any manual steps at the endpoint
The result is an enrollment experience that closely mirrors zero-touch in its practical outcome: a device that arrives at a location, is powered on, and becomes fully operational without requiring IT involvement at the site.
How to Set Up Pre-Registration in Moki
Pre-registration is configured through the Moki dashboard before devices ship. The setup process involves:
- Obtaining the serial numbers or device identifiers for the devices being deployed, typically from the vendor or through the purchase documentation
- Entering those identifiers in Moki’s pre-registration system and assigning each device to the correct configuration profile and device group
- Ensuring the Moki Agent application is installed on the device before it ships, either pre-installed by the hardware vendor or included in the initial device setup at a staging location
- Shipping the device to the deployment location with instructions for the receiving staff that cover only the physical setup: plug in the device, power it on, and open the Moki app
When the Moki Agent app opens on a pre-registered device and connects to the internet, enrollment completes automatically. The device receives its configuration profile, installs required apps, applies lockdown or kiosk settings, and appears in the Moki dashboard as enrolled and configured.
For organizations that stage devices at a central location before shipping, the Moki Agent can be installed and the device powered on at the staging location to confirm pre-registration is working correctly before the device ships to the field.
When to Use Android Agent Pre-Registration Instead of Zero-Touch
The choice between zero-touch and Android Agent pre-registration comes down to the specific hardware in the deployment and the procurement channel being used.
Use Android Agent pre-registration when:
- Devices are being purchased from vendors that are not part of the Google Zero-Touch program, which includes many specialized Android hardware manufacturers in industrial, medical, and custom display categories
- The fleet includes legacy Android devices that were purchased before zero-touch was available or that run Android versions below the zero-touch minimum requirement
- The deployment uses custom Android builds or modified AOSP firmware that does not support the standard Android Enterprise zero-touch provisioning framework
- The organization’s procurement process does not allow purchasing through zero-touch certified resellers due to existing vendor relationships, contract requirements, or pricing considerations
- A hybrid fleet includes some devices eligible for zero-touch and others that require Agent-based enrollment, and a consistent enrollment workflow is preferred across both categories
Use zero-touch enrollment when devices are being purchased new through certified resellers, when the hardware is mainstream Android from manufacturers in the zero-touch program, and when the deployment scale justifies the additional procurement coordination that zero-touch requires. Moki’s Android Enterprise page covers the zero-touch setup process in detail.
Running Both Enrollment Methods in the Same Fleet
Many organizations operate fleets that include both zero-touch eligible devices and Agent-enrolled devices. Moki manages both from the same dashboard, and devices enrolled through either method appear in the same device groups, receive the same configuration profiles, and are monitored through the same alert and reporting system.
The enrollment method does not affect ongoing management. Once a device is enrolled, it is managed identically regardless of how it was provisioned. This means organizations can use the most appropriate enrollment method for each hardware type without creating a management split between device categories.
Pre-Registration and the Device Deployment Playbook
For organizations that have documented their device deployment process in a deployment playbook, the pre-registration workflow should be included as a documented procedure alongside the zero-touch enrollment steps. The playbook should cover which device types use pre-registration versus zero-touch, the step-by-step process for registering devices in the Moki system before they ship, and the instructions provided to receiving staff at deployment locations.
This documentation ensures that pre-registration is executed consistently across every deployment rather than relying on institutional knowledge held by the person who set up the original process.
Schedule a Moki demo to see Android Agent pre-registration in action alongside zero-touch enrollment, or start a free trial to begin configuring pre-registration for your Android devices. Moki’s support team can walk through the pre-registration setup process for your specific hardware and deployment scenario.