Endpoint Services, Windows Autopilot, Collect Hardware Hash During Out Of Box Experience (OOBE)

Collect the Windows Autopilot hardware hash for a new Windows computer during the out-of-box experience (OOBE) so the device can be enrolled in Microsoft Intune.

Article Summary

Collect the Windows Autopilot hardware hash for a new Windows computer during the out-of-box experience (OOBE) so the device can be enrolled in Microsoft Intune.

Symptoms / Problem Statement

A technician needs to enroll a new Windows computer into Intune using Windows Autopilot but does not yet have the device’s hardware hash.

• “I need to enroll a new Windows computer into Intune but can’t find the hardware hash.”
• “The organization requires a hardware hash for Autopilot registration.”

Environment

• New Windows computer (OEM or vendor-agnostic)
• Windows 11 (OOBE)
• Microsoft Intune / Windows Autopilot enrollment
• Internet access required

Prerequisites / Access Requirements

• Technician access to the device at the first-boot (OOBE) stage
• Wi-Fi or Ethernet connection for internet access
• USB thumb drive to copy the hardware hash CSV file
• Device has not completed Windows setup (must be at the initial OOBE screens)

Resolution

1. Prepare the device

1. Power on the Windows computer and stop at the initial Windows setup screen (region/language selection).
2. Press Shift + F10 to open Command Prompt.

2. Launch PowerShell and allow scripts

3. From Command Prompt, start PowerShell:

   powershell

4. Allow scripts to run for this session:

   Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

3. Connect to the Internet and install NuGet

5. Connect the device to the Internet (required to download the Autopilot script).
   • If using Wi-Fi, run:

     start ms-availablenetworks:

   • Select a network and connect.
6. Install the NuGet package provider:

   Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force

   If prompted to trust the repository, type Y and press Enter.

4. Install the Autopilot script and export the hardware hash

7. Install the Autopilot export script:

   Install-Script -Name Get-WindowsAutopilotInfo -Force

8. Export the hardware hash to a CSV file on the USB thumb drive:

   Get-WindowsAutopilotInfo -OutputFile C:\AutopilotHash.csv

   Note: C:\ is used as an example and represents the USB thumb drive. The actual drive letter may differ.

   To identify the correct USB drive letter, run:

   Get-Volume

5. Power off the device and wait for Autopilot enrollment confirmation

9. After exporting the hardware hash and copying the CSV file to the USB thumb drive, power off the computer.
10. Provide the hardware hash CSV file to the Endpoint Services team following established procedures.
11. Do not continue Windows setup or reset the device until confirmation is received from Endpoint Services that the device has been imported into Windows Autopilot and assigned an appropriate deployment profile.
12. Once confirmation is received, power on the computer and proceed with setup. The device will evaluate its Autopilot enrollment during OOBE.

Troubleshooting

• Install-Script or Install-PackageProvider fails: Confirm the device is connected to the Internet and retry the commands.
• No Wi-Fi networks appear: Verify Wi-Fi is enabled and rerun start ms-availablenetworks:.

Search Criteria

• Autopilot hardware hash
• Intune Autopilot OOBE
• Get-WindowsAutopilotInfo

Keywords

Autopilot, hardware hash, Intune, OOBE, Windows 11, PowerShell, NuGet, Windows enrollment

Additional Information

Endpoint Services is responsible for importing hardware hashes into Autopilot and assigning deployment profiles.