Windows Autopilot pre-provisioning (white glove) network error — No network connection

Introduction:

Windows Autopilot pre-provisioning is method that allows an administrator to setup device level policies and apps before resealing and shipping the device to end user.

When end user boots into PC, they just have to go through configuration and installation that is specific to the user (since device level policies & apps were installed during pre-provisioning).

This reduces time for end users to complete the setup.

Here my intention is to go over an issue that I came across during this setup.

Background:

During pre-provisioning, Microsoft mentions to connect to hard wired network.

I was helping a customer in setting up Windows Autopilot using Azure AD Join. This was a brand new computer with TPM 2.0 that we were using for testing. All other backend work and pre-requirements for Autopilot were completed. The PC was hardwired.

Issue:

As soon as customer goes through the OOBE phase and system tries to connect to internet, it fails.

It ends up showing that there is no network connection (see screenshot)

We checked other computers in the network and we could connect to internet using hardwired cable.

So we know it is not a network issue.

Solution:

We see that, we are not the only one having this issue. There are several other facing this issue.

I could not find a solution to this, however the suggested workaround worked.

1) Shift + F10 to launch CMD window)

2) Type Start ms-availablenetworks:

3) That will show up available wifi networks

4) Choose the network and proceed.

After this it goes through usual pre-provisioning flow. After which you can re-seal the PC.

You can also follow this story at: Endpoint Management and Security: Windows Autopilot network error (root365.blogspot.com)