Deploying Windows is getting even easier with the next generation of Windows Autopilot. In this Ask Microsoft Anything (AMA) session, get insight and tips to help you take advantage of faster, more configurable self-deployment capabilities, streamlined device preparation, and enhanced reporting!
-------------------------------------------------------------------------------------------------------------------------------
➡️ To see the full Q&A, visit aka.ms/AMA/WindowsAutopilot
This session is part of Tech Community Live: Windows edition. This session will also be recorded and available on demand shortly after conclusion of the live event. To view other AMAs from Tech Community Live: Windows edition, see aka.ms/TCL/Windows.
-------------------------------------------------------------------------------------------------------------------------------
Here's what's covered:
0:00 - Introductions
7:35 - Is it normal that I still don't see Autopilot Device preparation policy blade under enrolment?
9:40 - Why was Autopilot Device Preparation developed? What advantages should it offer? Who is the target group to use it? Is it primarily for government customers?
15:35 - There are several Autopilot deployment methods such as: user driven mode, self-deploying, reset, and pre-provisioning and support for existing devices. What is everyone's favorite? What would you recommend and why? What have you all seen a lot of businesses use?
22:40 - In Autopilot device prep if I'm not declaring my company devices in Corporate Device Identifier, is there any other way to identify them?
24:00 - Will there be improvements during Autopilot for application installation in the way that installations of apps will be done more in parallel than one after the other to speed up the enrollment time of a device?
30:15 - One concern I have with Self-deploy mode is that a primary user is not set. So IT Ops teams would have a more difficult time looking a user up to find their device. Are there any plans to add an option to set the first user to login (or something to that effect) as the primary user? Or some other control to update the primary used like how SCCM can set a devices primary user based on usage?
38:45 - Using Windows Corporate Identifiers, would we need to upload all known devices, or would existing Autopilot traditionally registered devices be still corporately identified?
42:55 - During Autopilot, can you force Feature Updates?
46:50 - A challenge we are seeing today is clients who have tons of existing devices and want to onboard them and make them Entra-ID Joined and Intune Managed. It's challenging without IT intervention, registering the hardware hash, run them through Reset process, etc... Having an end-user do this is very impactful and won't work for most clients. Can we automate this through Autopilot - where users go through some basic steps and then device kicks into AP, goes OOBE, etc.
49:55 - If we use Autopilot device prep, will we get the option to associate the device we add using that method with our tenant when that feature becomes available? Hope my question makes sense.