Microsoft starts public testing of Windows Autopilot for HoloLens 2

Microsoft has announced a public preview of Windows Autopilot for HoloLens 2. This is the first public release since May 2020, where a private testing had started.

Starting with Windows Holographic version 2004, HoloLens 2 supports Windows Autopilot Self-Deploying Mode. Administrators can configure the out-of-box experience (OOBE) in Microsoft Endpoint Manager and enable end-users to prepare devices for business use with little to no interaction. This reduces inventory management overhead, cost of hands-on device preparation and support calls from employees during the setup experience.

Windows Autopilot is a collection of technologies used to set up and pre-configure new devices, getting them ready for productive use. You can also use Windows Autopilot to reset, repurpose, and recover devices. This solution enables an IT department to achieve the above with little to no infrastructure to manage, with a process that's easy and simple.

Here are some details regarding this public preview.

Windows Autopilot for HoloLens 2 Public Preview

• Windows Holographic, version 2004 (released May 2020) or newer is required to use Windows Autopilot. We began shipping devices with this version pre-installed in late September 2020. To confirm the build version on devices, or re-flash to the latest OS, you can use the Advanced Recovery Companion (ARC). You can find instructions here. Please contact your reseller or distributor to ensure that Autopilot-ready devices are shipped to you.
• The public preview now enables you to configure Windows Autopilot for HoloLens devices using Microsoft Endpoint Manager controls, for all customer tenants. Get started by logging into Microsoft Endpoint Manager admin center and select Devices > Windows > Windows enrollment, and then under Windows Autopilot Deployment Program, select Deployment Profiles > Create profile > HoloLens (preview).
• Windows Autopilot for HoloLens supports Self-Deploying mode and Azure AD Join. Self-Deploying mode joins the device into Azure AD, enrolls the device in Microsoft Endpoint Manager (or another mobile device management, MDM, service), and applies all device targeted policies (such as certificates, networking profiles, and kiosk settings) before the user logs in.
• For device registration, we recommend that you work with your reseller or distributor to ensure that when devices are delivered to you or your users, they are Windows-Autopilot-ready. Microsoft Cloud Solution Providers can assist you in that process. If you wish to register HoloLens devices manually using the hardware hash, please see Register devices in Windows Autopilot. For more general information, see Adding devices to Windows Autopilot.
• Windows Holographic, version 2004 (build 19041.1103) only supports Windows Autopilot over ethernet connection. Ensure the HoloLens device is connected to ethernet using a "USB-C to ethernet" adapter before turning it on. Upon device boot, no user interaction is required.  If you are planning to roll out Windows Autopilot to many HoloLens devices, we recommend that you plan for the adapter infrastructure. We do not recommend USB hubs as they often require additional third-party drivers to be installed which is not supported on HoloLens.
• Windows Holographic, version 20H2 (build 19041.1128) or later adds support for Windows Autopilot over Wi-Fi, in addition to the use of an ethernet connection. For devices connected via Wi-Fi, the user must:
  • Continue past the first interactable moment.
  • Choose the language and locale.
  • Go through eye-calibration.
  • Establish network connection

Some more details can be found here.