Windows Autopilot – White Glove Deployment

We have discussed different types of Autopilot in the Windows environment. As you remember, Windows autopilot technology simplifies the setup process for new and existing devices, in this article, we will discuss windows autopilot white glove deployment.

What windows autopilot white glove deployment stands for?

The white glow deployment is the autopilot feature, it allows IT persons to provision all device-based applications, policies, and configurations. The end-user will get the pre-enrolled or pre-configured device and the user becomes productive on the device, it consumes user time.

The below image shows Windows Autopilot white glove deployment process.

Windows autopilot white glove deployment configures device apps, settings, policies, and user apps during the OEM/Partner/IT phase and leaves just user settings and policies to be deployed during the end-user phase.

Hardware and OS Requirement:

  • Windows 10 version 1903 or later.
  • TPM 2.0 and device attestation.
  • virtual machines are not supported.
  • device connected via Ethernet (Wi-Fi not supported).

Procedure to enable white glove deployment


Navigate to Autopilot Devices, Upload Hardware hash.

Navigate to Windows enrollment

Home > Devices > Windows > Windows Enrollment >Deployment Profiles

  • Create deployment profile.
  • Fill the required details.
  • Select Yes for Allow White Glove OOBE
  • Click Next to Assign the Device group.
  • Review and Save the profile.

End-user device configuration

  • Boot the device.
  • On the OOBE (which could be a language selection or locale selection screen), don’t click Next.
  • press the Windows key five times  to view an additional options dialog
  • choose the Windows Autopilot provisioning option and then click Continue
Windows Autopilot Configuration

In the Windows Autopilot Configuration screen

The device will check the Windows Autopilot service for the configuration. If everything is correct click the Provision button.

setting up a device fo rWindows Autopilot

If the pre-provisioning process completes successfully, a green status screen appears with information about the device, including the same details presented previously.

Windows Autopilot Configuration

After successfully completing the provisioning process, hand over the device to the end-user.

End user experience

  • Switch on the device, Let it boot up.
  • Select the appropriate language, locale, and keyboard layout
  • Connect Ethernet
  • On the branded sign-on screen, enter the user’s Azure AD credentials
  • Once complete the ESP, user can access the desktop

Thank you for reading this post. You might also be interested in reading about Windows Intune. If you need any help, just drop us a message.

About the Author Ritesh Jangir

Author is Bachelor of Technology in Electronics & Communication graduate in 2013 and have made the career establishment precisely in the field of Cloud IT infrastructure. Got associated with the Microsoft technologies right from the bottom of the ladder as Help desk operator. Working for Microsoft support with Convergys gave an end to end insight on Microsoft Intune and SAAS based technologies. Further worked for multiple clients to migrate their device management strategies from on-prem to cloud mostly Intune and AirWatch (VMware Workspace ONE). Worked with HCL and now with ITC infotech as Intune consultant for planning and implementation of device management for one of the biggest Beer manufacturing company globally.

follow me on: