Event banner
Event details
131 Comments
- How long has Autopilot Pre-provisioning (White Glove) been in Public Preview, and when might it be GA? Is it problematic with time-outs? Is user-driven better and more stable and recommended? thank you!
- Since moving to W10 21H2 (could be coincidence) we've seen a lot of AP timeout issues in User ESP, when nothing else (as far as we're aware) has changed. Our AP timeout is set to 24 hours but the computer isn't powered on for more than a few hours. We've checked the timezone etc. using W32tm /resync /force
- Cristina_Osorio
Microsoft
Hi, it is up to your business requirements to use pre-provisioning or user-driven mode, there is no specific guidance outside of using what makes more sense for your organization.
- Can we check in the autopilot phase to flip a W10 into W11?
- Cristina_OsorioHi, Windows feature updates or Windows version change have to be done in regular Windows Update scan after user logs in the device
- i used rings but i was wondering if it's something that can have has a check for W11 readiness, If yes then upgrade
- You guys having issue with password reset for HDJ in the Autopilot phase. For us most of the times we need to ask the end user to power off the computer.
Can we have a native Autopilot task sequence (like Configuration Manager), for better control so we know when, and in what order, apps/scripts/etc. are installing please?
- Joe_LurieHi Michelle- if you are using the Autopilot into co-management, you can use the ProvisionTS switch to use a CM task sequence. But for traditional Autopilot, I'd love to get your need for requiring apps to install in a specific order, and why dependencies don't satisfy that need.
- Many reasons: (1) (for example), we use a script to remove the pre-installed versions of Office on MS Surfaces, which needs to run before we install the version we want. (2) makes troubleshooting trickier if apps etc. are installed in a random order. (3) the only way to install apps during Device ESP is by assigning them to a device, and assign to a user to install during User ESP. With a Config Mgr TS we don't have to assign apps to devices/users. This has a knock-on effect for us when we need to change apps/scripts deployed via AP, as they then deploy to all the 2,000+ live built computers.
- Heather_Poulsen
Community Manager
Welcome to Windows Autopilot: notes from the field at the Microsoft Technical Takeoff. Let's get started! Have a question? Post it here in the Comments. Subject matter experts will be answering during the live broadcast and throughout the week.
- Is there a method of disabling the auto-reboot during OOBE if the device has a policy to enable Full device encryption? the issue we have is during white-glove (pre-provisioning) the device reboots automatically because of the encryption policy enabled, however the required apps do not finish installing before the auto-reboot occurs which breaks OOBE pre-provisioning before we ca reseal the device.
- JuanitaBaptisteHi Don, if you have an app that requires a reboot in OOBE, you should set the reboot to be managed by Intune so that it does not interfere with the Autopilot flow. If you cannot define the reboot flow of the policy, there are some settings that can cause issues with Autopilot because it requires a reboot to be enabled. We recommend moving those policies post-OOBE for now.
Are there any news on getting autopilot database (or device registration service) robust enough, so we are not facing double used AAD entries from different autopilot hardware anymore?
Or does anybody know a way to fix these devices without needing to completly deleting and re-registering the device in autopilot again?
- JuanitaBaptisteAre you referring to devices that are hybrid joined? For hybrid devices, there will be two objects by design which we are looking into resolving.
- +1 to a have insight on auto re-enrollment's after replacing hardware components. (Timestamp, the previous object id, the new object id, the new and old AAD ID of the device) Does the auto re-enrollment qualify as a means of enrollment per DFCI requirements? Meaning, after auto re-enrollment will DFCI continue to work on the device? One of the requirements for DFCI is enrollment of the device by Microsoft or a CSP. Thx
- JuanitaBaptisteHi John, depending on the hardware components change, the OEM would need to re-register the device as a new device for DFCI to continue to work. We are looking into this process more to make it a better experience.
Ever since the Return of key functionality for Windows Autopilot sign-in and deployment experience was announced on July 27, 2022, we are still not able to have the UPN pre-populate on the Azure sign in page. I opened a case three weeks ago to address this and no progress is being made. Please provide clarification on this functionality. I am not sure why this is based on the OEM. We are assigning users ourselves.
Also, is there a way to know if a device was automatically re-enrolled after replacing hardware components?
- Please believe me 🙂 as mvp guy… its based on the hardwAre suppliers (oem) … as a recommended advice… please advise them to get in contact with microsoft
- In our last monthly sync with Lenovo, they basically said they are still trying to understand what they need to do on their end. I understand the OEM dependence on the re-enrollment process after hardware change, but what does OEM have to do with pre-populating UPN on Azure sign-in page during Autopilot setup? OEM is only uploading hashes for our devices. We manually assign to user when we deploy the laptop.
