A factory reset is one of those device events that can either be a smooth, automatic recovery or an operational disruption, depending entirely on the management infrastructure in place. For devices enrolled in a properly configured MDM platform like Moki, a factory reset triggers an automatic re-enrollment sequence that restores the device to its intended configuration without any manual intervention at the device. For devices without that infrastructure, a factory reset means starting the setup process from scratch, manually reconfiguring every setting, reinstalling every app, and re-applying every security policy.
Understanding how re-enrollment works after a factory reset, what determines whether it is automatic or manual, and how to configure your deployment for seamless recovery is practically important for any organization managing devices at scale. Factory resets happen more frequently than most operators plan for: as part of device troubleshooting, during hardware refresh cycles, when replacing failed devices, and occasionally as an unexpected result of OS updates or user actions.
Why Factory Resets Happen on Managed Devices
A factory reset returns a device to its out-of-box state, clearing all installed applications, configurations, and data. On managed devices, this also removes the MDM enrollment, which is what triggers the re-enrollment question.
Factory resets on managed kiosks and signage devices occur in several predictable scenarios. Troubleshooting is the most common: when a device has a persistent issue that cannot be resolved through remote management, a factory reset and re-enrollment is often the fastest path to restoring the device to a known good state. Hardware refresh cycles involve factory resetting devices before they are reassigned or disposed of. Replacement devices are factory fresh by definition and require enrollment as part of the swap process. OS updates occasionally trigger behaviors that are most cleanly resolved by a full reset and re-enrollment.
In each of these scenarios, the speed and ease of re-enrollment determines how much operational disruption the reset causes. For a self-ordering kiosk in a restaurant during operating hours, the difference between a five-minute automatic re-enrollment and a 45-minute manual setup process is the difference between a brief service interruption and a significant operational event.
How Automatic Re-Enrollment Works on Android
For Android devices enrolled through Android Enterprise using zero-touch provisioning, factory reset recovery is designed to be fully automatic. When a zero-touch enrolled device is factory reset, the zero-touch configuration persists at the account level rather than on the device itself. When the device powers on after the reset and connects to the internet, it contacts Google’s zero-touch service, recognizes the device’s serial number as registered to the organization’s account, downloads the MDM enrollment profile, and begins automatic re-enrollment.
The device proceeds through the same enrollment sequence as its initial setup: it enrolls in Moki, receives the correct configuration profile based on its group assignment, installs required applications silently, applies kiosk lockdown settings, and appears in the Moki dashboard as enrolled and configured. The entire process typically completes within a few minutes of the device connecting to the internet, without any manual input at the device.
For Android devices enrolled through Moki’s Android Agent with pre-registration, re-enrollment after a factory reset requires the Moki Agent to be reinstalled on the device. If the device still has its serial number registered in Moki’s pre-registration system, opening the Agent app will trigger automatic enrollment and configuration pull without requiring manual input. If the pre-registration needs to be refreshed, the Moki dashboard allows the device to be re-registered before the Agent is launched.
How Automatic Re-Enrollment Works on iOS
For iOS devices supervised through Apple Business Manager, factory reset recovery is also automatic. When a supervised iOS device is factory reset, the device remains registered in Apple Business Manager by its serial number. When the device is powered on and connected to the internet, it contacts Apple’s servers, is recognized as belonging to the organization, downloads the MDM enrollment profile from Moki, and proceeds through supervised activation.
The supervised enrollment process applies all profile settings, installs VPP-licensed apps, and configures the device according to the Moki profile without any user interaction. For devices in Single App Mode, kiosk lockdown activates as part of the enrollment sequence. The device is customer-facing ready within minutes of connecting to the network.
The critical requirement for both iOS and Android automatic re-enrollment is that the device was originally enrolled through the appropriate automated provisioning channel. Devices enrolled through Apple Business Manager re-enroll automatically after a factory reset. Devices that were activated manually with a personal Apple ID and enrolled in MDM through a manual process do not have the same automatic re-enrollment capability, which is a strong operational argument for purchasing iOS devices through Apple’s channel from the start.
How Re-Enrollment Works for BrightSign
BrightSign players managed through Moki use serial number-based pre-registration rather than a carrier-level provisioning framework like Apple Business Manager or Google Zero-Touch. When a BrightSign player is factory reset, it loses its Moki enrollment. Re-enrollment requires the player’s serial number to be registered in Moki’s BrightSign management system and the player to connect to the network so it can receive its configuration.
For BrightSign deployments with serial numbers already registered in Moki, a factory-reset player that connects to the network and is activated follows the configuration associated with its serial number, resulting in automatic re-enrollment. If the serial number registration needs to be refreshed or was not set up in advance, a brief registration step in the Moki dashboard precedes the automatic enrollment.
Making Re-Enrollment Seamless: What to Do in Advance
The difference between a factory reset that resolves in minutes and one that requires extended manual setup is almost entirely determined by decisions made before the reset occurs. The following practices make re-enrollment seamless regardless of when a factory reset happens.
For Android fleets, purchase all devices through zero-touch certified resellers and ensure every device is registered in the zero-touch portal before deployment. This registration persists through factory resets and is the foundation of automatic recovery. For devices being added to an existing fleet, register their serial numbers in the zero-touch portal before they ship to locations.
For iOS fleets, purchase all devices through Apple or an authorized reseller that automatically adds them to Apple Business Manager. Ensure the Moki MDM server token is connected to ABM and that the enrollment profile is assigned to devices before activation. Devices purchased through this channel re-enroll automatically after any factory reset.
For all platforms, maintain accurate group assignments and configuration profiles in the Moki dashboard so that a re-enrolling device receives the correct profile immediately. A device that re-enrolls but lands in the wrong group or receives a generic default profile still requires manual correction.
Document the re-enrollment process for each device type in the device deployment playbook so the person performing a factory reset knows what to expect and what to verify after the device comes back online.
Verifying Re-Enrollment Completed Correctly
After a factory reset and re-enrollment, the Moki dashboard provides the verification that the process completed correctly. Check that the re-enrolled device appears in the correct device group, has the expected configuration profile applied, shows the correct apps as installed, and has kiosk mode or lockdown active if applicable. A remote screen view for Android devices allows visual confirmation that the device is displaying the correct interface before it goes back into service.
Moki’s compliance monitoring surfaces any device whose post-enrollment configuration does not match the expected profile, providing a safety net that catches re-enrollment issues before they affect customers or operations.
Schedule a Moki demo to see how the re-enrollment process works for your specific device types and deployment scenario, or start a free trial to test the automatic re-enrollment workflow with your hardware before it is needed in a production situation. Moki’s support team can advise on configuring the pre-registration and provisioning setup that makes automatic re-enrollment possible across your fleet.