Windows Autopilot: Pre Provisioning for deployment

[@1nsurr3ction]

You guys are producing some amazing videos, really helpful. Thank you for doing this

[@theCMC]

Many Thanks for the feedback its really appreciated. Its what helps us produce more.

[@mohibmalik5792]

23:30 That's because MS has made some changes to the authentication experience for Autopilot deployment, and UPN doesn't pre-populate anymore on OOBE landing page. Great video. Thanks 🙏

[@theCMC]

Thanks Malik

[@danimoosakhan]

If this is the case, then what is the point of assigning primary user to the autopilot device? 3:40

[@mohibmalik5792]

@@danimoosakhan exactly

[@freddy5849]

@@danimoosakhan So you can install applications assigned to a user during pre-provisioning.

[@webclanka4490]

Very nice, thanks!

[@jujigatame4800]

Thanks mate - just ran through this with Windows 11. Some minor changes in Intune and OOBE, but still very relevant. One issue I keep running into is policy forced restarts during the pre-provisioning stage. I think this is due to some password policies that we enforce. If I allow the restart it will never finish - I need to open command line (with Shift + F10) and run "shutdown -a" to skip the restart. Not ideal but works for now.

[@theCMC]

Thanks for the feedback. Other peoples experience always helps others 👍

[@Dezbateri]

Thanks for the video. I wonder how multiple autopilot profiles coexists with pre provisioning and normal Autopilot. What i've encountered is after a device is pre provisioned and the end-user boot up for the first time the assignment changes from the pre-provisioning profile to a standard autopilot profile. So at the end the device doesn't stay in pre-provisioning profile even if you group tag it.

[@amarshaurya9878]

Nice video 📸📸📸 We'll explained

[@uemauthority]

Informative content, thank you. Do we think pre-provisioning will be made generally available anytime soon?

[@theCMC]

I hope so!

[@michaelpietrzak2067]

I'm sorry, I searched the channel and couldn't find a "Getting started with Autopilot" video. Can you perhaps post the link? I saw some others but not one from you. Regards

[@theCMC]

The Ultimate Guide to Intune Autopilot - How to use Windows Autopilot with Microsoft Intune kzbin.info/www/bejne/qme1faupfKiAbKM

[@michaelpietrzak2067]

@@theCMC Thank you very much!

[@theCMC]

@@michaelpietrzak2067 you’re welcome!

[@andrewmccallum5699]

Well presented video Andrew, thanks!

[@theCMC]

Glad you liked it!

[@octabrain77]

Great content, thanks! Do you know if it's supported to deploy a ppkg package (created with Windows Configuration Designer) during the technician flow?

[@unkownuser2320]

autopilot profile & ESP has to be assigned to the machine. please share default settings and what are settings has to be enabled

[@shoaibalichaudhary5675]

my device always gets stuck on device setup -> app (identifying). it will stay on this part for like 30-50 mins. what could cause this?

[@summoner2100]

This is where I'm getting stuck right now. It's not doing the app installs during the device stage during the whiteglove part. What am I missing?

[@theCMC]

Hi Sorry this is so late, Im sure you have resolved this by now but to note it is not recommended to deploy win32 and line-of-business apps at the same time with Autopilot. However you can now do this with the NEW Autopilot device preparation profile so worth trying out

[@mirkopappalardo9002]

Wooww but i have a question. do you know if the pre-provisioning has a deadline? 14 days after reseal?

[@theCMC]

Good question not heard that before. I don’t recall ever seeing any limits. I checked the Microsoft docs and again can’t see any reference to this

[@chebrets]

is there any way to apply device name template based not only on numbers but also on alphabetical symbols?

[@theCMC]

Symbols cannot be used. You can add a device name template in the Windows Autopilot deployment profile. The options available are: Create a unique name for your devices. Names must be 15 characters or less, and can contain letters (a-z, A-Z), numbers (0-9), and hyphens. Names must not contain only numbers. Names cannot include a blank space. Use the %SERIAL% macro to add a hardware-specific serial number. Alternatively, use the %RAND:x% macro to add a random string of numbers, where x equals the number of digits to add. Only Letters, numbers and hyphens can be used.

[@nazmulislam5807]

At what point do you get asked to set up MFA for new user?

[@theCMC]

MFA is a user identity security process. Its not until the end user then switches the device on and enrols with their credentials and MFA if switched on will appear. The end user experience will also go through the ESP setup. You will see the MFA prompt at 25:18 in this video.

[@cloudhandle]

Is 'Allow White Glove OOVE' is it now 'Allow pre-provisioned deployment''?

[@fsalomito]

Yes

[@akustudios2877]

How is device there available under devices in groups even before the autopilot ?

[@theCMC]

Could you specify a time for me to check, please?

[@akustudios2877]

4:30 exactly the device in the group how is it available before autopilot, are devices registered from work or school account before autopilot just to attach device based policy to them ? Little confused in this part. Thanks for the quick reply !!

[@theCMC]

@@akustudios2877 the AAD device is either added via the Hardware Hash import method, or via an OEM or Partner. It could also be there if the device has been previously AAD joined and Wiped.

[@akustudios2877]

So just adding hardware hash will make the device available under devices to set policies for autopilot? Or the last part you said if I’m understanding it correctly, the device was previously AD joined and then manually wiped or wiped from endpoint. Since we have not deleted the floating device we are using the same device to assign polices so when autopilot is kicked in the device later picks up the polices assigned to it in phase one of autopilot?

[@akustudios2877]

My question again is how is device available under devices before autopilot? What if I have to set device based polices for a new laptop that’s never been in touch with any MDM, As far as what I understand device is only available under devices when it’s enrolled, which has not happened before autopilot. So how do I set device based policy when there is no device in endpoint portal yet? Any help on this is much appreciated!! Great content!!!

[@professor3095]

Pre Prov. doesnt work on a vm with tpm and bitlocker policy