Embedded Files
Before a new or repurposed Windows device can be deployed using Windows Autopilot, its unique hardware identifier (hash) must be registered in the Intune. This document outlines the required PowerShell steps to securely capture and upload these device hashes. It covers the manual export method (CSV) to ensure all devices are properly staged for zero-touch deployment.
Pre-requisite:
Pre-requisite:
FlashDrive
Internet Connection
1. Insert the Flash Drive into the device.
2. At the OOBE (Out-of-Box Experience) screen, press Shift + F10 to open Command Prompt.
2. At the OOBE (Out-of-Box Experience) screen, press Shift + F10 to open Command Prompt.
3. In command prompt, type “powershell” to run powershell.
3. In command prompt, type “powershell” to run powershell.
4. Type the following commands to install the script to be able to extract the device hash.
4. Type the following commands to install the script to be able to extract the device hash.
Set-ExecutionPolicy Bypass -Scope Process -Force
Install-Script -Name Get-WindowsAutopilotInfo -Force
Type “Y” to proceed
5. Perform to extract the device hash. Type the command
5. Perform to extract the device hash. Type the command
Get-WindowsAutopilotInfo.ps1 -OutputFile “D:\hwid.csv”
Note: Perform the command below if GroupTag is required by the client. Replace “Esevel”.
Get-WindowsAutopilotInfo.ps1 -GroupTag “Esevel” -OutputFile “D:\hwid.csv”
6. Once the extraction finishes, a new .csv file containing the hardware hash will be generated on the drive. We can proceed to share this to Client for them to upload it on their Intune.
6. Once the extraction finishes, a new .csv file containing the hardware hash will be generated on the drive. We can proceed to share this to Client for them to upload it on their Intune.
Page updated
Report abuse