How to use Autopilot pre-provisioning

[@XsterTHEmINEK]

Very helpful and good video 👍

[@MrMarcLaflamme]

No matter how many times I read or hear an explanation of "Only fail selected apps in technician phase", my brain still does not comprehend what the heck it does or means.

[@getrubix]

Same- if I'm looking at it and focusing really hard, it starts to make sense... kind of like "magic eye"

[@JBreezedorsett]

Hey Steve My Friend! Another great video! With the Autopilot pre-visioning configurations setup, what makes this method different from this New Windows Autopilot device preparation method?

[@ShawnOfeoiwnofne]

I had turn off Pre-Provisioning. Every time we let our workstations sit for a day or more after reseal, it would forget that it was in the middle of the Autopilot process and skip past the user provisioning part causing all kinds of issues.

[@ironmaidenfreak001]

Thanks for the video. It might be a stupid question, but is this already with Autopilot V2? because it had the classic ESP layout. And can we monitor the install process in Intune?

[@getrubix]

Pre-provisioning is not available in APV2

[@al73r]

How are you preloading the device to be enrolled? Currently i use a pkg file that hits intune to load the hwid. From here it enrolls the device into intune and reboots. Upon rebooting the first prompt is to login with your email for the company. One issue im finding now is on certain hardware it locks defaultuser0 after that reboot blocking the ability to login to the company. This is from ms erasing some registry keys. My solution is to create a local administrator account and let laps adjust. Would love to know another method.

[@getrubix]

The device is being enrolled by the hardware vendor or reseller, or even directly from PowerShell to register to Autopilot. With pre-provisioning, there is no need to login as the user. The idea is everything is self deployed to the device before the user signs in.

[@al73r]

@@getrubix I found that an older image i built worked flawless and didn't have the defaultuser0 bug. I wonder if i loaded too many drivers into my boot.wim? Rather odd behavior and i was able to isolate it. Yes I use a script to have our deployment center run our ppkg which auto loads into intune. I went this route to encrypt the script to not expose our tenants graphapi secret keys as well.

[@2Corinthians96]

Steve, where did you get your glasses? 😂

[@getrubix]

LensCrafters. Whatever was closest to the door 😁

[@SwarupDhar-k6y]

At which point during pre-provision device joins to Entra? the technician flow or the user flow?

[@getrubix]

Technician

[@SwarupDhar-k6y]

@@getrubix Thank you. In our domain only a selected group of users can join the device to entra, if we try Pre-provisioning will it fail?

[@getrubix]

Most likely, yes.

[@SwarupDhar-k6y]

@@getrubix Yup, we need to open door for all user to entra join and block BYOD may be

[@pontuswendt767]

Thanks for the video, do you have the diagram anywhere? :)

[@getrubix]

Not yet but I have something new coming where I'll be posting all the diagrams/docs used in the videos 😃

[@pontuswendt767]

@@getrubix Thanks man! :D