Day 1: Windows Autopilot User-Driven Mode¶

📌 Today we will discuss about Windows Autopilot with User-Driven Mode. This article provides an overview and step-by-step guidelines to perform a Windows Autopilot user-driven scenario when the devices are strictly Microsoft Entra joined. Link: https://learn.microsoft.com/en-us/autopilot/tutorial/user-driven/azure-ad-join-workflow

Demo Image

I. Theory¶

  • 1/ What is autopilot user-driven mode
    • Device is used by a single user

    • User-run deployment

    Autopilot User-Driven Mode lets end users set up their devices themselves with minimal IT involvement. After turning on the device and signing in, the device automatically joins the organization, enrolls in Intune, and applies company policies — ready for use.

  • 2/ When do we use user-driven mode
    • The device will be delivered directly to the end users without IT intervention
      • Requires no interaction from IT team/OEM/reseller.

    • The device will be used primarily by a single user

    • Doesn’t require TPM attestation, so it works on physical devices and VMs.

II. Deployment¶

Step 1: Set up Windows automatic Intune enrollment¶

1/ Sign in to the EntraID

Demo Image

2/ In the EntraID screen > search the keyword MDM and WIP, click on MDM and WIP

Demo Image

3/ In Mobility (MDM and WIP) > choose Microsoft Intune

Demo Image

4/ In Microsoft Intune

4.1/ MDM user scope

  • check All

Demo Image

5/ After settings like the picture above, select Save

Step 2: Allow users to join devices to Microsoft Entra ID¶

1/ Sign in to the Microsoft Entra ID.

Demo Image

2/ In the EntraID screen, under Identity in the left hand pane, select Devices.

Demo Image

3/ In the Devices | Overview screen, under Manage in the left hand pane, select Device Settings.

Demo Image

4/ In the Devices | Device settings screen that opens, under Users may join devices to Microsoft Entra, select All

Demo Image

5/ After settings > select Save

Step 3: Create a device group¶

Create a dynamic device group for use with Windows Autopilot

1/ Sign into the Microsoft Intune admin center.

Demo Image

2/ In the Intune Admin Portal, select Groups, then select All groups

Demo Image

3/ In the Groups | Overview screen, make sure All groups is selected, and then select New group.

Demo Image

3/ In the New Group screen that opens:

  • For Group type, select Security.

  • For Group name, enter a name for the device group [All Autopilot Device]

  • For Group description > skip

  • For Microsoft Entra roles can be assigned to the group, select No.

  • For Membership type, select Dynamic Device.

  • For Owners > skip

  • For Dynamic device members, select Add dynamic query.

The Dynamic membership rules screen opens.

Demo Image

4/ In the Dynamic membership rules screen

4.1/ at the Rule syntax box, select edit at the top-right hand side

Demo Image

4.2/ Paste in the following rule in the Edit rule syntax screen under Rule syntax

(device.devicePhysicalIDs -any (_ -startsWith “[ZTDid]”))

Demo Image

4.3/ Once the rule is pasted in, select OK. 4.4/ Once the desired rule is entered, select Save on the toolbar to close the Dynamic membership rules window.

Demo Image

5/ Select Create to finish creating the dynamic device group.

Demo Image

6/ Wait until the notification is successful

Demo Image

Step 4: Configure and assign Windows Autopilot Enrollment Status Page (ESP)¶

  • What is ESP

    ESP is often configured to wait for only specific apps (instead of all), so users can get to the desktop faster.

  • A. Upload A Package App

    1/ Visit the link here: Zoom Installers

    2/ Download Zoom workspace desktop app for Meeting (64bit)- MSI Installer Or using the link here: https://zoom.us/client/latest/ZoomInstallerFull.msi?archType=x64

    Demo Image

    3/ Sign in to the Microsoft Intune admin center. 4/ Select Apps > Apps | Overview > Windows.

    Demo Image

    5/ In Windows | Windows Apps, select Create

    Demo Image

    6/ In the Select app type pane, under the Other app types, select Line-of-business app.

    Demo Image

    7/ Select Select. The Add app steps are displayed.

    Demo Image

    8/ In the Add app pane, select Select app package file.

    Demo Image

    9/ Upload the ZoomMSI file downloaded recently, select OK

    Demo Image

    10/ In App information, select Next

    • Name: Zoom

    • Description: skip

    • Publisher: Zoom

    • App install context: Device

    • Ignore app version: No

    • Command-line arguments: /qn

    • Upload Logo

    • The other fields: skip

    Demo Image Demo Image

    11/ At the scope tags screen, select Next

    Demo Image

    12/ At the Assignments screen, Assign to the desired group, select Next

    12.1/ At the Required header, select add group

    Demo Image

    12.2/ Enter [All Autopilot Device], Check box, click Select

    Demo Image

    12.3/ Ensure the target group is there, select Next

    Demo Image

    13/ At the review + Create tab, select create

    Demo Image

    14/ Wait until the uploading zoom is completed

    Demo Image

    15/ Wait until the uploading process is successful

    Demo Image
  • B. Create ESP Profile

    1/ Sign into the Microsoft Intune admin center. 2/ In the Home screen, select Devices in the left hand pane.

    Demo Image

    3/ In the Devices | Overview screen, under Manage devices by platform, select Windows.

    Demo Image

    4/ In the Windows | Windows devices screen, under Device onboarding, select Enrollment at the left pane side.

    Demo Image

    5/ In the Windows | Windows enrollment screen, under Windows Autopilot, select Enrollment Status Page.

    Demo Image

    6/ In the Enrollment Status Page screen that opens, select Create.

    Demo Image

    7/ The Create profile screen opens. In the Basics page:

    • Next to Name, enter [ESP - Autopilot User-Driven Mode]

    • Next to Description, skip

    • Select Next.

    Demo Image

    8/ In the Settings page, toggle the option Show app and profile configuration progress to Yes.

    Demo Image

    8.1/ After toggling the setting to Yes > configure these settings following

    • Show an error when installation takes longer than specified number of minutes: 60

    • Show custom message when time limit or error occurs: Yes

    • in the box message: [Installation exceeded the time limitation set by your organization. Please try again or contact your IT support person for help]

    Demo Image

    8.2/ After entering the message > turn on these settings below

    • Turn on log collection and diagnostics page for end users: Yes

    • Only show page to devices provisioned by out-of-box experience (OOBE): Yes

    • Block device use until all apps and profiles are installed: Yes

    • Allow users to reset device if installation error occurs: Yes

    • Block device use until required apps are installed if they are assigned to the user/device: Selected

    Demo Image

    8.2/ After choosing [selected] mode > click on +select apps

    Demo Image

    8.3/ At the Select apps > search Zoom > Click on Zoom and select

    Demo Image

    8.4/ Ensure Zoom is listed in the Blocking apps list > select Next

    Demo Image

    8.5/ After adding Zoom, at [Only fail selected blocking apps in technician phase] > Select No > then select Next

    Demo Image

    9/ at Assignment tab > click add groups

    Demo Image

    9.1/ At the select groups to include

    • Search [All autopilot device]

    • Check box and click Select

    Demo Image

    10/ Ensure the target group is listed in the list, select Next

    Demo Image

    11/ At the scope tags, select Next

    Demo Image

    12/ At the Review and create tab, select Create

    Demo Image

    13/ Waiting until the notifications shows [profile successfully created /assigned]

    Demo Image

Step 5: Create and assign Windows Autopilot profile¶

1/ Sign into the Microsoft Intune admin center. 2/ In the Home screen, select Devices in the left hand pane.

Demo Image

3/ In the Devices | Overview screen, under By platform, select Windows.

Demo Image

4/ In the Windows | Windows devices screen, under Device onboarding, select Enrollment.

Demo Image

5/ In the Windows | Windows enrollment screen, under Windows Autopilot, select Deployment Profiles.

Demo Image

6/ In the Windows Autopilot deployment profiles screen, select the Create Profile drop down menu and then select Windows PC.

Demo Image

7/ The Create profile screen opens. In the Basics page:

  1. Next to Name: [DeployProfile - Autopilot User-Driven Mode]

  2. Next to Description

  3. Next.

Demo Image

8.1/ In the Out-of-box experience (OOBE) page:

  • For Deployment mode, select User-driven.

  • For Join to Microsoft Entra ID as, select Microsoft Entra joined.

  • For Microsoft Software License Terms, select Hide

  • For Privacy settings, select Hide

Demo Image

8.2/ In the Out-of-box experience (OOBE) page:

  • For Hide change account options, select Hide.

  • For User account type, select Administrator.

  • For Allow pre-provisioned deployment, select No.

  • For Language (Region): Skip

  • For Automatically configure keyboard: No

  • For Apply device name template: UserDr-%SERIAL%

  • Next

Demo Image

9/ In the Scope Tags tab, select Next

Demo Image
10/ In the Assignments tab
  • Under Included groups, select Add groups.

Demo Image
  • select the group that created in the Step 3 [All Autopilot Device]

Demo Image
  • Next

11/ In the Assignments, click Create

Demo Image

12/ Wait until the notification is successful

Demo Image

III. Admin Workflow¶

Before a device can use Windows Autopilot, the device must be registered as a Windows Autopilot device. Registering a device as a Windows Autopilot device makes the Windows Autopilot service available to the device.

Step 1: Register devices as Windows Autopilot devices¶

  • We use the [upload hardware directly] method to register a target device into autopilot service

1/ On a device that is currently undergoing Windows Setup and OOBE:
  1. At the select country and region screen, press keys Shift+F10.

Demo Image
  1. The command prompt window will open

Demo Image
  1. In the cmd windows, open PowerShell by running the following command:

PowerShell Command¶
powershell.exe
Demo Image
2/ At the PS PowerShell command prompt, run the following PowerShell commands:
  • PowerShell

PowerShell Command¶
Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned
Install-Script -Name Get-WindowsAutopilotInfo -Force
Demo Image
  • If prompted to do so, agree to install NuGet from the PSGallery, enter Yes (Y)

Demo Image
  • After install the module, run the commands below

PowerShell Command¶
cd 'C:\Program Files\WindowsPowerShell\Scripts\'
powershell.exe -execution bypass Get-WindowsAutopilotInfo.ps1 -Online
Demo Image

3/ When the last command of Get-WindowsAutopilotInfo -Online runs, a Microsoft Entra ID sign-on prompt is displayed. Sign in with an account that is at least an Intune Administrator.

Demo Image Demo Image

4/ After the sign-in is successful, the device hash uploads automatically.

Demo Image

5/ Make sure that uploading hash is successful

Step 2: Verify device has a Windows Autopilot profile assigned to it¶

1/ Sign into the Microsoft Intune admin center.

Demo Image

2/ In the Home screen, select Devices in the left hand pane.

Demo Image

3/ In the Devices | Overview screen, under By platform, select Windows.

Demo Image

4/ In the Windows | Windows devices screen, under Device onboarding, select Enrollment.

Demo Image

5/ In the Windows | Windows enrollment screen, under Windows Autopilot, select Devices.

Demo Image

6/ In the Windows Autopilot devices screen, select Sync in the toolbar.

Demo Image

7/ Wait for the sync to finish. The sync might take several minutes.

Demo Image

8/ After the sync completes > Search the serial number of target device at the search bar

Demo Image

9/ Make sure the profile status is assigned like the picture above

IV. User Workflow OR User experience¶

Registering a device as a Windows Autopilot device just makes the Windows Autopilot service available to the device. Registering a device as a Windows Autopilot device doesn’t mean that the device has used the Windows Autopilot service. It just makes the Windows Autopilot service available to the device.

Step 1: Deploy the device¶

  1. Power on the device.

2. The out-of-box experience (OOBE) begins and a screen asking for a country or region appears. Select the appropriate country or region, then select Yes.

Demo Image

3. The keyboard screen appears to select a keyboard layout. Select the appropriate keyboard layout, then select Yes.

Demo Image
  1. An additional keyboard layouts screen appears, select Skip

    Demo Image

5. The Let's connect you to a network screen appears. At this screen, either plug the device into a wired network (if available), or select and connect to a wireless Wi-Fi network.

Demo Image

6. Once network connectivity is established, the Next button should become available. Select Next. 7. At this point, the device might reboot to apply critical security updates (if available or applicable). After the reboot to apply critical security updates, the Windows Autopilot process begins.

Demo Image Demo Image
  1. Once the Windows Autopilot process begins, the Microsoft Entra sign-in page appears, Sign-in with your org account, select Sign in

    Demo Image

9. After authenticating with Microsoft Entra ID, the Enrollment Status Page (ESP) appears. The Enrollment Status Page (ESP) displays progress during the provisioning process across three phases:

  • Device preparation (Device ESP)

  • Device setup (Device ESP)

  • Account setup (User ESP)

The first two phases of Device preparation and Device setup are part of the Device ESP while the final phase of Account setup is part of the User ESP.

Demo Image

10. Once Account setup and the user ESP process completes, the provisioning process completes, the ESP finishes, and the desktop appears. At this point, the end-user can start using the device.

Demo Image
  • Ensure the device already has the Zoom app installed, you can see it it the desktop screen Day 1: Windows Autopilot User-Driven Mode

Demo Image
  1. You can check the hostname, make sure that the device name follows the format UserDr-%SERIAL%

Demo Image

V. References¶