Windows 10: Windows Autopilot Provisioning

Ted_Walker · Jun 16, 2022

I'm having issues with making the Windows Autopilot provisioning work with a new computer. What I'm trying to do is use the "Technician flow" during the OOBE by pressing the Windows key five times to view the additional options dialog: I then select the Windows Autopilot provisioning option and press continue and reach the following page:Which shows the proper organization and deployment profile, but the user is listed as "Not Assigned", however I've verified under Windows Autopilot devices that I am the user assigned to this device, so I have no clue as to why the "Assigned user" field conti

:)

Brink · Jun 16, 2022

Try out Windows Autopilot white glove pre-provisioning with Windows 10

Windows Autopilot enables organizations to easily provision new devices, taking them from the initial OEM factory configuration to a ready-for-productive-use state. But depending on the amount of software and policies that need to be configured on the device, this provisioning process can take some time.

For many organizations, users aren't used to waiting that long for the device to be provisioned; the time-consuming steps are done before the user ever sees the device because IT technicians or partners perform those steps before the device is delivered. With the release of Windows 10 version 1903, we can support that same type of process with Windows Autopilot, leveraging the white glove pre-provisioning capabilities.

To read more about the Windows Autopilot white glove capabilities, see the main documentation page for the feature. At a high level, here are the steps involved:

Modify your existing Windows Autopilot profiles to opt into white glove pre-provisioning by enabling the "Allow White Glove OOBE" option.

After the device has been registerd with Windows Autopilot and the profile has been assigned, boot the device to start the out-of-box experience (OOBE). On the first language/locale screen, press the Windows key five times.

Choose Windows Autopilot pre-provisioning from the available choices.

Use the presented QR code to reconfigure the device in Intune (see the sample Windows Autopilot Companion app), if necessary.

Click the Provision button to start the pre-provisioning process. This will join the device to Azure Active Directory or Active Directory and enroll it in Intune, then apply all the device-targeted policies, as well as any user-targeted Win32 apps (as long as they are configured to install in the device context).

When the device finishes the pre-provisioning process, click "Reseal" to prepare the device for the user.

Deliver the device to the user so they can complete the process by going through the standard Windows Autopilot user-driven process.

Here's a video that shows the process (edited for time), showing both the technician-driven pre-provisioning process, as well as the user-driven process that happens very quickly.

Behind the scenes, the Windows Autopilot white glove pre-provisioning process leverages the same process used by self-deploying mode (so it has the same TPM attestation requirements), and it requires using a wired Ethernet connection (to avoid having to configure the language, locale, and keyboard as part of the pre-provisioning process, needed before a Wi-Fi connection could be made).

Try it out yourself, and if you have any issues you can ask for help via the "Help and Support" node in the Intune portal.
Click to expand...

Source: https://techcommunity.microsoft.com/...ng/ba-p/740502

Brink · Jun 16, 2022

Try out Windows Autopilot white glove pre-provisioning with Windows 10

Windows Autopilot enables organizations to easily provision new devices, taking them from the initial OEM factory configuration to a ready-for-productive-use state. But depending on the amount of software and policies that need to be configured on the device, this provisioning process can take some time.

For many organizations, users aren't used to waiting that long for the device to be provisioned; the time-consuming steps are done before the user ever sees the device because IT technicians or partners perform those steps before the device is delivered. With the release of Windows 10 version 1903, we can support that same type of process with Windows Autopilot, leveraging the white glove pre-provisioning capabilities.

To read more about the Windows Autopilot white glove capabilities, see the main documentation page for the feature. At a high level, here are the steps involved:

Modify your existing Windows Autopilot profiles to opt into white glove pre-provisioning by enabling the "Allow White Glove OOBE" option.

After the device has been registerd with Windows Autopilot and the profile has been assigned, boot the device to start the out-of-box experience (OOBE). On the first language/locale screen, press the Windows key five times.

Choose Windows Autopilot pre-provisioning from the available choices.

Use the presented QR code to reconfigure the device in Intune (see the sample Windows Autopilot Companion app), if necessary.

Click the Provision button to start the pre-provisioning process. This will join the device to Azure Active Directory or Active Directory and enroll it in Intune, then apply all the device-targeted policies, as well as any user-targeted Win32 apps (as long as they are configured to install in the device context).

When the device finishes the pre-provisioning process, click "Reseal" to prepare the device for the user.

Deliver the device to the user so they can complete the process by going through the standard Windows Autopilot user-driven process.

Here's a video that shows the process (edited for time), showing both the technician-driven pre-provisioning process, as well as the user-driven process that happens very quickly.

Behind the scenes, the Windows Autopilot white glove pre-provisioning process leverages the same process used by self-deploying mode (so it has the same TPM attestation requirements), and it requires using a wired Ethernet connection (to avoid having to configure the language, locale, and keyboard as part of the pre-provisioning process, needed before a Wi-Fi connection could be made).

Try it out yourself, and if you have any issues you can ask for help via the "Help and Support" node in the Intune portal.
Click to expand...

Source: https://techcommunity.microsoft.com/...ng/ba-p/740502

Brink · Jun 16, 2022

Windows Autopilot for HoloLens 2 general availability

Today, we are thrilled to announce the general availability of Windows Autopilot for HoloLens 2! IT administrators around the world can now use Microsoft Endpoint Manager to efficiently set up their fleet of HoloLens 2 devices and effectively deploy them to their production environments.

Traditionally, IT pros spend significant hands-on time configuring and setting up devices that will later be used by end users. With Windows Autopilot for HoloLens, we are simplifying this process. IT admins can pre-configure devices with a few simple operations, and end users can set-up the devices with little to no interaction by connecting to a network and verifying credentials.

Everything beyond that is automated.

Thanks to the valuable feedback you provide during the preview period, we have made continued improvements—to Windows Autopilot self-deploying mode in particular. With self-deploying mode, you can easily:

Join a device to Azure Active Directory (Azure AD).

Enroll the device in MDM using Azure AD automatic enrollment.

Provision policies, applications, certificates, and networking profiles.

Use the Enrollment Status Page (ESP) to prevent access to corporate resources until a device is fully provisioned.

Set up Windows Autopilot for HoloLens in 6 simple steps

Setting up your environment to support HoloLens deployment with Windows Autopilot is straightforward. Simply:

Enable Automatic MDM Enrollment.

Register devices in Windows Autopilot.

Create a device group.

Create a deployment profile.

Verify the ESP configuration.

Verify the profile status of the HoloLens device(s).

For more HoloLens-specific Windows Autopilot information, see our official Windows Autopilot for HoloLens 2 documentation or read our documentation about Windows Autopilot Self-Deploying mode.

Useful information

For device registration to Windows Autopilot, we recommend that you work with your reseller. Microsoft Cloud Solution Providers can assist you in that process. For more general information, see Adding devices to Windows Autopilot.

Windows Holographic, version 2004 (released May 2020) or newer is required to use Windows Autopilot. Windows Holographic, version 2004 (build 19041.1103) only supports Windows Autopilot over ethernet connection. 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.

Support paths

For support on device registration and shipments, please contact your reseller.

For general support inquiries about Windows Autopilot or for issues like profile assignments, group creation or Microsoft Endpoint Manager admin center controls, please contact Microsoft Endpoint Manager support.

If your device is registered in the Windows Autopilot service, and the profile is assigned on the Microsoft Endpoint Manager admin center, but you are still facing issues, please contact HoloLens support.

Click to expand...

Source: https://techcommunity.microsoft.com/...y/ba-p/2596348

Windows 10: Windows Autopilot Provisioning

Windows Autopilot Provisioning

Windows Autopilot Provisioning

Windows Autopilot Provisioning

Windows Autopilot Provisioning - Similar Threads - Autopilot Provisioning

Generic Product ID After Motherboard Replacement Preventing Autopilot Registration

Generic Product ID After Motherboard Replacement Preventing Autopilot Registration

How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

How to avoid "Let´s connect you to a network" when using Autopilot Self-deployment?

Windows Autopilot Provisioning

Windows Autopilot Provisioning

Win11 OOBE "Let's name your PC" breaks Pre-Provisioning Mode HAAD Join Autopilot

Win11 OOBE "Let's name your PC" breaks Pre-Provisioning Mode HAAD Join Autopilot

Try out Windows Autopilot white glove pre-provisioning with Windows 10