If the ESP is turned off, the device still goes through those phases to apply policies and applications assigned to the device and user. Most unexpected reboots tend to happen during the Configuration, Scripts, or App Install phases of the Autopilot provisioning sequence, as depicted above. Scripts or App Installers that explicitly execute a reboot (rather than cleanly exiting with a return code) will cause an "unexpected reboot" and interrupt the user experience. This means that Intune must be conducting the reboot based on return codes that come from the completed app package install or the completion of a running script. Specifically, a reboot can occur only during the Device phase of the ESP and only when the reboot is triggered by Intune. Reboots are only supported within a narrow period during Windows Autopilot to provide a smooth user experience. Account setup applies configuration policies, scripts, and applications assigned to the user.Device setup applies configuration policies, scripts, and applications assigned to the device.Device Preparation starts the configuration and app installation tracking to determine when the next stages are complete.The Enrollment Status Page (ESP) displays the setup progress status for Device preparation, Device setup, and (user) Account setup. Understanding the Windows Autopilot deployment processĭuring an Autopilot deployment, configurations, scripts, and applications are automatically applied throughout the device setup with little interaction required from the user.Īn overview of the Windows Autopilot provisioning sequence when setting up a new device. In this post, we've put together a list of scenarios that might be causing these unexpected reboots, and what can be done about them. When a device reboots during Windows Autopilot, cached credentials are cleared and the autologin functionality is disabled. If you’re not getting this "ideal experience", especially if the user must enter their credentials repeatedly, there's a good chance it's because the device is unexpectedly rebooting at some point during start up and the provisioning has to be nudged along. It may take some time to download and install all the programs and settings, but the user only needs to sit back and let the magic happen. When a user powers on their PC for the first time, the ideal scenario for Windows Autopilot deployments is that it connects it to their network to log in and automatically provisions itself while the user has little to do to complete the setup. By: Juanita Baptiste – Sr Product Manager | Microsoft Intune
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |