Should we replace Autopilot with the deployment process from an acquired site?

November 14, 2026 5 answers
Asked by u36~coatcheck_501

Our current process ships devices to new hires for Autopilot setup. Leadership wants us to mirror an acquired site's PXE imaging process and have a technician sign in as each user before the device is issued, so the user doesn't have to wait for setup.

What should we consider before making that change?

Answers

2r+foldline.508

First find out which wait they're trying to eliminate. Autopilot pre-provisioning can let a technician start the device setup before delivery without signing in as the user. It still takes staff time and may not eliminate every user-side setup step, but it's worth testing before replacing the whole workflow.

Also look at which applications actually need to block the first sign-in. If some can arrive later, that may shorten the wait without adding an imaging process.

b73~foghorn_619:

Test it with the same app assignments and policies used for new hires. A quick setup with a stripped-down test profile won't tell you much about the real wait.

Reply to this answer
f902!pktqueue_5

There's a real tradeoff here. Having someone ready to work sooner can be worth more than the technician time, especially for expensive short-term staff. But that doesn't mean every laptop needs the same hands-on treatment.

Compare the full costs and timing for both approaches, including shipping, support time, setup delays and batches of new starters. A pre-staged option for people who genuinely need it on day one may be enough.

Reply to this answer
Zabble

Signing in as the user deserves its own review, separate from the question of PXE versus Autopilot. How will the technician authenticate, what access will that give them, and how will the activity be recorded? Ask security and compliance to review the proposed workflow before anyone starts sharing passwords.

Temporary access passes are one possible mechanism, but using one to sign in as another person still needs an approved process. It isn't automatically a substitute for thinking through access and audit requirements.

Reply to this answer
Brelton.6y

Don't overlook the upkeep of the PXE side. Someone has to maintain the images, update software and troubleshoot deployment failures. Count that ongoing work along with the time spent preparing each machine, not just the wait saved on the first morning.

Reply to this answer
n691~keycase_4

I'd also check the onboarding schedule before assuming the wait is harmless. Some people may have orientation while the laptop finishes. Others may not even start setup until someone needs to show them something, which makes the delay a lot more visible. A clear instruction to start setup early could help, but it won't solve every case.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions