For most Windows shops, "zero-touch enrollment" has become shorthand for Windows Autopilot. With Autopilot, each device's hardware hash is registered with Microsoft before it ships, so it sets itself up and enrolls in management when the employee signs in. No imaging bench, no IT ticket.
But Autopilot isn't the only way to get there.
Some teams would rather not depend on hardware hash registration, Entra ID, or a specific reseller. Many already run Google Workspace as their identity provider and want employees to sign in to new devices with the account they use every day.
You get the same out-of-box experience by setting up Windows ahead of time, and Iru customers in retail, e-commerce, and consumer tech already roll out devices this way. Microsoft has supported provisioning packages for years, and Iru has supported this approach from day one.
So we're making the playbook public. Here's how it works, what it looks like for employees, and how to choose the right approach for your fleet.
How it works
Autopilot has the device contact Microsoft at first boot to look up how it should be set up. Here, those instructions are already on the device: IT puts them in a provisioning package (PPKG) that Windows reads during setup. The device skips the usual setup questions and lands at a sign-in screen ready for work, with no Autopilot registration needed.
A typical flow looks like this:
- Pre-configure Windows. IT builds a provisioning package with the out-of-box experience (OOBE) choices already answered, plus Iru's Windows enrollment script and any sign-in components, such as Google Credential Provider for Windows (GCPW).
- Deliver it to the device. The configuration reaches the device by USB, from the factory, or over the network (more on each below).
- The employee signs in. They power on, see a work sign-in screen, and log in with their corporate identity.
- The device enrolls and gets its settings. The Iru agent checks in, and the device receives its apps, settings, and policies automatically.
The result looks and feels like Autopilot to the end user. The difference is how the configuration gets there.
Building the provisioning package
The package itself takes a few minutes to build with Microsoft's free Windows Configuration Designer (WCD), available from the Microsoft Store. You'll also need Iru's Windows enrollment script, which is available only to Iru customers. At a high level:
- Prepare the Iru script. WCD runs command files, not PowerShell scripts directly, so the Iru Windows enrollment script is wrapped in a .cmd file first.
- Create a WCD project. Choose Advanced Provisioning and target All Windows Desktop Editions.
- Add the script as a provisioning command. Under Runtime Settings > ProvisioningCommands > DeviceContext, add the files and set the command line that runs them.
- Export and build. Export the project as a provisioning package (.ppkg).
- Test it. Run the package on an unenrolled device, then check Settings > Accounts > Access work or school to confirm it's connected to Iru.
From there, the same .ppkg can go on a USB stick or into a factory image from your hardware provider.
Deliver zero-touch without Autopilot
1. USB provisioning package (PPKG)
The simplest, lowest-cost option. You build a provisioning package, copy it to a USB stick, and insert it during first boot. Windows reads the package during setup and applies your configuration automatically.
One caveat: Windows only picks up the package from USB during the out-of-box experience. That makes it a great fit for new devices or devices you've just reset, and less practical for machines already in use.
Best for: smaller fleets, pilots, and teams that want zero touch without new infrastructure or vendor agreements.
2. Custom builds from your hardware provider
Dell, HP, and Lenovo can ship devices with your custom Windows image already applied at the factory. Some resellers, such as CDW, offer this service too. The device arrives at the employee's door ready to sign in, with no USB stick and no IT touch.
Best for: organizations buying hardware at volume that want devices drop-shipped directly to employees.
3. PXE from on-prem infrastructure
If you already run on-prem deployment infrastructure, you can push a custom build to devices over the network with PXE boot. This also works when a device is reset, so you can reprovision without anyone carrying a USB stick around. The trade-offs: you need PXE servers and a custom image to maintain, and devices must be on the same network as the PXE server, which rules out remote employees.
Best for: organizations with existing on-prem imaging infrastructure, such as campuses, labs, and offices with large on-site fleets.
See it in action: Google sign-in to managed device in about two minutes
In this demo, a Windows 11 device boots from a custom image configured for Google Workspace sign-in through GCPW. Here's what the employee sees:
- Setup runs on its own. Windows shows "Just a moment" and skips every OOBE screen. No region, keyboard, network, or account prompts.
- A work sign-in screen appears. The lock screen leads to "Other user: Sign in with your work account." Iru is already at work here: it deployed Chrome and GCPW before anyone signed in.
- The employee signs in with Google. They enter their Google Workspace email and password, then accept the notice that their admin can manage the device.
- Windows prepares the profile. After "Preparing Windows," the employee lands on a desktop with Chrome and Edge ready to go.
- Iru is already there. Within a minute, the Iru agent is in the system tray, Iru Self Service is available, and the device reports no app updates required.
From lock screen to a managed, up-to-date desktop took about two minutes, with zero IT involvement and no Autopilot registration.
Choosing the right method
Every approach reaches the same zero-touch outcome. The right one depends on how you buy hardware, where your devices go, and what infrastructure you already have.
| Method |
Setup effort |
Where it works |
Works on reset? |
Watch out for |
| USB provisioning package |
Low |
Anywhere IT can plug in a USB stick |
Yes, at OOBE |
Needs a hands-on step at first boot; package only applies during OOBE |
| OEM or reseller custom build |
Medium (one-time setup with vendor) |
Devices drop-shipped from the factory |
Yes, if the PPKG is in the base image (needs extra configuration) |
Vendor programs, lead times, and image updates to manage |
| PXE from on-prem |
High, unless already in place |
On your network |
Yes |
Requires on-prem infrastructure; devices must be on the same network, so it doesn't suit remote employees |
Many teams mix methods: factory images for new hires, and a USB package or PXE for resets and repairs. Autopilot can sit alongside these too. Zero touch is the goal, and you choose the path.
Zero touch, your way
Autopilot is a solid option, but it shouldn't be the only one. Whether you hand out a USB stick, have devices imaged at the factory, or push builds over your own network, Iru picks up the moment the employee signs in and handles the rest: apps, settings, updates, and Self Service. It's the same approach our customers already use in production today.
Want to see how this would work for your Windows fleet? Book a demo.