
Install apps on an Android phone remotely: from the Play Store on the web, with Family Link on a child phone, or with an MDM for company devices.
Enroll Android devices with a QR code: what the IT admin QR code screen means, the six-tap setup, prerequisites, and fixes for common enrollment errors.


Content writer, trio.so
Android QR code enrollment puts a new or factory-reset Android device under company management by scanning a code during setup. On the first Welcome screen, tap the same spot six times, connect to Wi-Fi if asked, and scan the QR code from your device management console. The device downloads the management app and applies the company's settings and apps on its own. It works on Android 7.0 and later, for fully managed company devices, dedicated devices and company-owned devices with a work profile.
If you are looking at a phone screen that asks for an "IT admin QR code", the next section explains what it is and how to get past it; if you are the IT admin, the rest of this guide covers requirements, the step-by-step setup and the fixes for common failures.
The screen that asks you to scan a QR code from your IT admin (on Samsung phones and other Android devices) is the company enrollment scanner. It opens when someone taps the Welcome screen six times during first setup, or when a company has registered the device for automatic enrollment.
Android Enterprise is Google's framework for managing Android devices at work and in schools. It replaced the older device administrator approach, which Google began phasing out in 2017, with stronger security controls, app management through managed Google Play, and separation between work and personal data. See what Android Enterprise is and why device admin is no longer the way to manage Android.
It supports several setups: fully managed devices (company-owned, work only), dedicated devices (single-purpose devices such as kiosks), company-owned devices with a work profile (work and personal use), and personally owned devices with a work profile (BYOD). Each fits a different need, and modern enrollment methods typically require Android 7.0 or later.
Android Enterprise offers several ways to enroll a device. The right one depends on who owns the device, how many you have, where they are bought and who sets them up.
The most automatic method. Devices bought from an authorized zero-touch reseller are assigned to your company before they ship and set themselves up on first boot.
QR code enrollment balances automation and access. IT creates a QR code with the enrollment details, and the person setting up the device scans it on the Welcome screen.
NFC enrollment transfers the setup details from an NFC programmer device or tag to the new device by touching them together.
Instead of a QR code, the person setting up the device types an identifier at the Google sign-in prompt. For Android Device Policy that is afw#setup; other management apps use their own. The device downloads the management app, then asks for a QR code or an enrollment token.
Samsung's Knox Mobile Enrollment does for Samsung devices what zero-touch does for others: devices registered in the Knox portal enroll automatically, with Samsung-specific options on top.
The device policy controller (DPC) identifier is the code typed at sign-in in the token method, such as afw#setup. It tells the setup wizard which management app to install.
On a personal phone, signing in with a work account or opening an enrollment link from IT creates a work profile: a separate space for work apps and data, managed by the company, while the rest of the phone stays private. See Android work profile.
| Method | Android version | Setup effort | Best for | Key limitation |
|---|---|---|---|---|
| Zero-touch | 8.0+ | None per device | Large rollouts, devices shipped to staff | Must buy from a zero-touch reseller |
| QR code | 7.0+ | A few minutes per device | Batches, mixed device sources | Device must be in hand, new or reset |
| NFC | 6.0+ | A few minutes per device | Fully managed devices | Needs a programmer device or tag |
| Token (afw#setup) | Varies by management app | Several minutes per device | A few devices, camera problems | Typing errors |
| Knox Mobile Enrollment | Samsung devices | None per device | Samsung-only fleets | Samsung devices only |
| Work profile (account or link) | Varies by management app | A few minutes, done by the employee | BYOD programs | No control over the whole device |
The process has three phases: IT creates the QR code, someone scans it on the device, and the device configures itself.
The IT admin creates an enrollment QR code in the device management console. The code holds what the setup wizard needs to start: where to download the management app, a checksum to verify it, an enrollment token that ties the device to your company and, optionally, Wi-Fi details. The settings and apps themselves come from the management server after enrollment.
Most tools create the code when you choose an enrollment profile. You can print it, show it on a screen or send it to whoever prepares the devices. Treat it like a key: anyone with the code can enroll a device into your company until it expires or is revoked.
On the first Welcome screen of a new or factory-reset device, tap the same spot six times. The device asks you to scan a QR code. On some devices and Android versions it first asks for Wi-Fi so it can get a QR reader. After the scan, the device checks the code, downloads the management app and starts enrollment.
Once the management app is installed, it contacts the management server and applies the company's settings: screen lock and password rules, required apps, Wi-Fi and VPN, restrictions such as blocking USB debugging, and registration in the console. It usually takes a few minutes, depending on the number of apps and the network speed. The person setting up the device cannot skip it.
QR enrollment fails if any of these is missing.
Your organization needs an Android Enterprise connection in your management tool, either with a managed Google Play account or a managed Google domain. This one-time setup gives your company an identity in Android Enterprise, lets you approve apps in managed Google Play and makes enrollment tokens possible. Without it, enrollment fails at registration.
Your management tool must support Android Enterprise and have an enrollment profile for the device type: fully managed, dedicated, or company-owned with a work profile. A typical profile includes:
A device that has already been set up must be factory reset before QR enrollment. Some devices from consumer channels may also be tied to a previous owner's Google account (factory reset protection) until that account is removed.
The device needs internet access during enrollment to download the management app and its settings. You can put Wi-Fi details in the QR code, connect to Wi-Fi by hand before scanning, or use mobile data.
Wi-Fi details in the QR code save a step, but the code then carries your network password. For sensitive networks, use a separate enrollment network with limited access.
Follow these steps in order.
In your management console, create an Android Enterprise enrollment profile and choose the management mode: fully managed, dedicated, or company-owned with a work profile. Add the restrictions, required apps from managed Google Play, security policies and network settings, then turn on QR code enrollment for the profile.
Create the QR code from the profile. Most tools let you download it as an image or show it on screen.
For a few devices, print the code or show it on a monitor where the devices are prepared. For larger batches, set up a staging area with the code on a screen. Keep the code where only the right people can see it, and check when it expires.
New devices are already in the right state. For used devices, factory reset them: on most phones, Settings > System > Reset options > Erase all data (factory reset). The exact path varies by manufacturer.
The device restarts on the Welcome screen. Don't go past it before you start QR enrollment. A device that has finished setup cannot be enrolled by QR without another reset.
Hold the device so the whole code is in view, about 15 to 30 cm away. It scans by itself. The device then shows that it will be managed by your organization and asks you to continue. Accept, and wait while it downloads the management app. Don't interrupt it.
The management app installs and applies the company's settings: security settings, apps from managed Google Play, certificates and network settings. This takes a few minutes and the device may restart once. The setup cannot be skipped.
When setup completes, the device opens to the home screen (fully managed) or finishes creating the work profile (company-owned with a work profile). In the management console, check that the device appears with the right enrollment type, that required apps installed and that its compliance status is correct. If something is missing, ask the device to sync and check its logs.
Samsung Knox Mobile Enrollment (KME) is Samsung's own automatic enrollment for Galaxy devices. Devices are registered in the Knox portal, through Samsung or an authorized reseller, and assigned to a profile that points to your management tool. When such a device is set up, it enrolls automatically, without anyone scanning a code.
A Knox-specific QR code is usually not needed. Standard Android Enterprise QR enrollment also works on Samsung devices. Knox adds Samsung-specific options, such as Knox license settings and extra security controls, for management tools that support them.
Fleets that are all Samsung often use KME for its automation. Mixed fleets usually combine zero-touch or QR enrollment for other brands with KME for Samsung.
Most failures fall into a few groups.
The device does not read the code because of glare or shadows, a blurry or small code, a damaged camera, the wrong distance, or a screen that flickers on camera.
Use even light without glare, print the code at least 5 cm (2 inches) wide on matte paper, test the camera first, and hold the device 15 to 30 cm away.
The scan works but the management app does not download. Common causes: the network drops, the code points to the wrong location, a firewall or proxy blocks Google Play, or the device's Google Play services are out of date.
Check the internet connection, confirm the enrollment profile in your console, allow Google's domains through your firewall and proxy, and try again on a clean network.
The device enrolls but some settings do not apply. Causes include conflicting policies, restrictions the device or Android version does not support, badly formatted certificates and timeouts.
Look at the console logs to see which policy failed, test new policies on one device first, check that your devices support the restrictions you need, and validate certificates before you add them.
On a company-owned device with a work profile, enrollment may complete without creating the profile. Causes include an old Google Play services version, leftovers from a previous profile, too little storage or a bug in a specific Android version.
Make sure the factory reset completed, update Google Play services, free up storage and check the manufacturer's notes for known issues.
The IT admin has three jobs in QR enrollment: set it up, run the rollout and fix what breaks.
Setup: connect Android Enterprise, create enrollment profiles with the right policies, test enrollment on one device of each model, write short instructions for whoever prepares the devices, and create the QR codes you need.
Rollout: set up a well-lit staging area, work through devices in batches, confirm each device enrolled before it goes to its user, and note failures so you can spot patterns.
Ongoing: watch the console for failed enrollments and compliance problems, block apps or allow only approved apps as needs change, update enrollment profiles when policies change, and train the help desk on common enrollment questions.
If you are short on staff, enroll a small batch first, fix what you learn, then scale up.
QR code enrollment fits when:
Other methods fit better when:
QR enrollment costs nothing beyond the devices and some hands-on time, which makes it the usual starting point for small and mid-sized fleets.
A QR code saves typing on one phone; across a fleet it is the difference between a quick staging day and a week of setup. trio.so enrolls company Android devices as fully managed with a QR code, and personal phones with a work profile. See Android device management.

Related reading: what is Android Enterprise, managed Google Play, Android work profile and device admin on Android.
trio.so enrolls company Android devices as fully managed with a QR code.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.





Related
The related industry news, interviews, technologies, and resources.

Install apps on an Android phone remotely: from the Play Store on the web, with Family Link on a child phone, or with an MDM for company devices.

How to add apps to an Android work profile: the work Play Store, why an app is missing, Samsung steps, moving apps, and how IT uses managed Google Play.

Android MDM vs iOS MDM differs in deployment, security architecture, and management approach. Both platforms offer robust features with distinct enterprise advantages.

Android MDM provides centralized control over Android devices in your organization, enabling security enforcement, app management, and compliance through remote administration capabilities.

What is Android OS fragmentation, and why does it matter to enterprises? It leads to security risks, patch delays, and device management headaches.

How to remote wipe an Android phone with Find Hub, what erase removes, what happens if the phone is offline, and how IT wipes company devices.

What an Android work profile is, what IT can and cannot see, how to set one up step by step, and how it compares with a fully managed company phone.

What managed Google Play is, how it binds to an MDM, how apps are chosen, pushed and published privately, and how it differs from the Play Store.
14-day free trial. No credit card required.
trio.so for MSPs: one console, separate clients