PatchDayAlert
War Story · 3 min read · 553 words By Colten Anderson · Field Notes

Moving 1,200 laptops from SCCM to Intune Autopilot: what changed and what I'd do differently

A mobile fleet managed from on-prem infrastructure meant multi-day laptop setups and devices that drifted whenever they stayed off the network. Here's how the move to Intune and Autopilot cut setup to a couple of hours.


For years, swapping one laptop at ITA Group took three to five days. A technician imaged the device on-prem, waited for SCCM to push the application set, worked through whatever failed, and then scheduled time with the user. Multiply that by a four-year refresh cycle across roughly 1,200 devices, and the service desk spent a lot of its week on device builds.

The bigger problem was how we managed devices after deployment. Most of our tooling sat on on-prem infrastructure, but the fleet was highly mobile. When a laptop didn’t check in to the corporate network regularly, it fell behind on policy, patches, and inventory, and we usually found out when something broke.

Environment

  • About 1,200 Windows endpoints, mostly laptops, used by a largely mobile workforce
  • Existing management: SCCM and Group Policy, both dependent on network connectivity
  • Target: Microsoft Intune for configuration, compliance, and app deployment, with Windows Autopilot for provisioning

My part

This was a team project, and I want to be precise about what I did:

  • Architecture. I was in every architecture session and led most of the design discussion: how devices would enroll, how policy would be structured, and how we’d sequence the move.
  • Application packaging. I packaged a few of the applications for Intune deployment.
  • GPO-to-Intune policy migration. I helped translate existing Group Policy settings into Intune configuration policies.

Other team members handled the remaining packaging, policy work, and day-to-day rollout execution.

Rollout and validation

We didn’t run a big-bang cutover. The pilot group was IT staff who were already due for new laptops through hardware refresh. That gave us technically capable users who could describe failures clearly, on hardware we were replacing anyway.

After the pilot, we tied the rollout to the four-year refresh cycle: each device moved to Intune and Autopilot when it came up for replacement. That spread the support load and avoided re-provisioning working hardware just to change management platforms.

We validated through Intune reporting, device logs, and compliance status. Compliance looked consistently better than it had under on-prem management, especially for devices that rarely touched the corporate network.

Results

  • Laptop setup went from three to five days to about one to two hours of technician time, plus roughly 30 minutes with the end user.
  • Patching got faster. We could push updates when they were needed instead of waiting for devices to reconnect to on-prem infrastructure.
  • We could see the whole fleet. Device status and location became visible from an asset management perspective, regardless of where the laptop was.

What I’d do differently

Tying the rollout to the refresh cycle kept risk low, but it meant running SCCM, Group Policy, and Intune side by side for a long time. Every policy change had to be considered in two places, and the devices still on the legacy stack kept the old connectivity problems until their turn came up.

Next time I’d set a firm end date for the legacy stack and move a batch of non-refresh devices to Intune early, so the overlap period is measured in months rather than refresh cycles.


This case study describes a project at ITA Group, where I led the service desk and systems administration team. It contains no internal configurations, tenant details, or proprietary data.

Share

Related field notes

Get the free CVE triage cheat sheet

Subscribe and we'll email you the one-page triage flow for fresh CVEs. Plus the weekly digest.

Subscribe