Windows Autopilot Hardware Hash (Hardware ID) – Step‑by‑Step

From a Running Device (PowerShell)

1. Open PowerShell as Administrator.
2. Install the script module if needed.
3. Export to CSV (e.g., to C:\Temp).

# Install module (if not present)
Install-Script -Name Get-WindowsAutopilotInfo -Force

# Allow running the script if needed
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope Process -Force

# Export CSV with hardware hash
Get-WindowsAutopilotInfo -OutputFile "C:\Temp\Autopilot.csv"

From OOBE (Shift + F10)

1. At first‑boot OOBE screen, press Shift + F10.
2. Open PowerShell: powershell
3. Run the export commands to a USB or local path.

powershell
Set-ExecutionPolicy RemoteSigned -Scope Process -Force
Install-Script Get-WindowsAutopilotInfo -Force
Get-WindowsAutopilotInfo -OutputFile "D:\Autopilot.csv"   # e.g., USB drive

From Intune‑Managed Devices

Push the script via a device script or Win32 app to collect and centralize CSVs (e.g., to a network share).

# Example silent collection to a share (adjust paths/permissions)
$Out = "\\SERVER\Share\Autopilot\$(($env:COMPUTERNAME)).csv"
Get-WindowsAutopilotInfo -OutputFile $Out

From OEM / Reseller

Request the Autopilot hardware IDs (CSV) for your order. Vendors can supply ready‑to‑upload files mapped to your tenant.

• Provide tenant ID and order details.
• Validate CSV headers/format on receipt.

Using MDT / ConfigMgr Task Sequence

Add a “Run PowerShell Script” step early in the TS to export CSV to a share.

powershell.exe -ExecutionPolicy Bypass -File GetWindowsAutopilotInfo.ps1 -OutputFile "\\SERVER\Share\%COMPUTERNAME%.csv"

Verify CSV Before Upload

• HardwareHash present per device.
• SerialNumber and WindowsProductID included.
• CSV is UTF‑8 and comma‑separated.

Open Windows Autopilot

1. Go to the Intune admin center.
2. Navigate to Devices → Windows → Windows enrollment.
3. Open Devices (Windows Autopilot).

Import the CSV

1. Choose Import or Import devices.
2. Select the CSV created earlier.
3. Submit and wait for processing to complete.

Assign Deployment Profile

1. Create or select a Windows Autopilot profile.
2. Assign it to imported devices / group.
3. Optionally assign ESP and device naming.

Device Grouping (Optional)

• Use a dynamic group on devicePhysicalIds if desired.
• Auto‑assign profiles and apps to the group.

(device.devicePhysicalIDs -any _ -contains "[ZTDId]")  # Example dynamic query

Verify Device Status

• Check import status and device records.
• Confirm serial numbers and hashes match.
• Power on device to start Autopilot flow.

Troubleshooting Tips

• CSV header or encoding errors → re‑export UTF‑8.
• Hash missing → rerun script as admin.
• Wrong tenant mapping → confirm OEM file and tenant ID.