Autopilot Hardware Hash

Tools → Autopilot Hash captures the hardware hash of the machine in front of you — before Windows is installed — and writes a CSV that Intune accepts. It is a capture-only feature: EasyDeploy never talks to Intune, and nothing is registered automatically.

Caution

This is not a Microsoft-documented method. Microsoft’s supported paths assume the device is already running Windows (or that the hash comes from the OEM). Use the WinPE capture when the machine is in front of you, is not part of an OEM order, and you are about to install Windows anyway. Everything after the capture — the CSV import and the deployment — is the standard Intune process.

Official methods, if you have a choice:

• OEM / CSP registration — the supplier uploads the hash to Partner Center; the device arrives registered. Recommended for volume.
• Get-WindowsAutopilotInfo.ps1 on a booted Windows — save a CSV for the portal, or use -Online to upload directly (also works during OOBE via Shift+F10).
• Portal import — Devices ▸ Windows ▸ Enrollment ▸ Autopilot devices ▸ Import.

Microsoft Learn: Manually register devices with Windows Autopilot.

Capturing

1. Boot the EasyDeploy USB into WinPE.
2. Open Tools → Autopilot Hash (no keyboard shortcut).
3. Wait for the capture to finish. The result is written automatically; there is nothing to configure.

Output files

One CSV per capture:

Hash-<SERIAL|NOSERIAL>-<yyyyMMdd-HHmmss>.csv

Example: Hash-L6N0CX05J87824E-20261019-112122.csv

The CSV has the three columns Intune expects:

Device Serial Number,Windows Product ID,Hardware Hash
L6N0CX05J87824E,,T0F9BAEAHAAAAA...

The file is written to every writable target it can reach:

Target	Path	Purpose
EasyDeploy USB	[USB]:\EASYDEPLOY\	Take it with you
Freshly deployed OS volume	<volume>:\EASYPDEploy\	Stays with the machine after deployment
Temporary fallback	X:\…	Only when no other target is writable (WinPE RAM disk — copy it out before rebooting)

Note

The deployed OS volume copy is written when Windows has already been applied. If you capture before deploying, only the USB copy exists — that is expected.

Serial number and NOSERIAL

The serial comes from SMBIOS (Win32_BIOS.SerialNumber). Some firmware reports a placeholder instead of a real value — for example To Be Filled By O.E.M., SMBIOS_STRING_INDEX_0, or an all-zero string. In that case:

• the file name uses NOSERIAL;
• the Device Serial Number column is left empty;
• if the OA3 hardware hash carries a usable serial (SMBIOS record type 14), that value is used instead — so the row and the file name get a real serial whenever the firmware exposes one.

Caution

Intune needs a serial number for a clean device record. A NOSERIAL CSV can still be imported, but review the device in the portal and fix the serial (or register it through your OEM) before relying on it.

Note

The CSV is three columns — it does not include a Group Tag. If your process depends on tags (OrderID), capture with Microsoft’s Get-WindowsAutopilotInfo.ps1 -GroupTag … on a running Windows, or set the attribute in Intune after import.

Importing into Intune

1. Intune admin center → Devices → Windows → Enrollment → Autopilot devices → Import.
2. Select the CSV, wait for the import, then Sync (a second sync within 10 minutes is rejected).
3. Up to 500 devices per CSV.

Order matters: import the CSV before the machine reaches OOBE. If Windows finishes OOBE first, the device completes as a normal install and the Autopilot profile is not applied.

Good to know

• The hash is a hardware identity — treat the CSVs as inventory data, not public files.
• Keep one CSV per machine; the file name already contains the serial and the capture time.
• Capturing does not change the machine. The USB stays bootable and can be reused.
• If you need the hash for a fleet, use the OEM/CSP path — WinPE capture is intended for individual machines outside an OEM order.