Autopilot provisioning and the last mile of a rollout

Preparing laptops for new hires with Autopilot, and learning that the hard part of a rollout is never the automation, it is the handoff.

I set up laptops for four new hires through Windows Autopilot this week, and one of the profiles refused to provision on the first try until I traced the failure and fixed it.

Autopilot is the modern way to prepare a Windows device: you register it, assign a profile, and it configures itself for the new user on first boot so you are not imaging by hand. When it works it is close to magic. When it fails, the error messages are thin and you learn to read the enrollment and compliance records carefully. That troubleshooting, not the happy path, is the actual skill.

I also finished a laptop inventory and reported it at an operations sync, and pushed the long-running endpoint removal down to its last four machines, blocked only by an update to the remote management agent that kept failing to apply.

Here is the part people underrate: the automation was the easy ninety percent. The last mile, actually getting a configured device into a specific person's hands on their start date, coordinating with their manager, confirming building access and peripherals, is where the real work is. You can have a perfect provisioning pipeline and still fail the new hire if the handoff is sloppy.

That is why I now treat provisioning as two projects. The pipeline, which is engineering, and the handoff, which is communication and scheduling. The pipeline you build once. The handoff you get right every single time, because every new hire is a first impression.

Closed fifty-one tickets that week. The four laptops mattered more. A new hire who logs in on day one and everything just works is the whole point of the automation, and it only counts if the last mile is as disciplined as the script.

Build the pipeline. Then obsess over the handoff.

← All writing · Portfolio