Normally, the Device ID is captured by the OEM using the OA3 tool. However, if you need to import an old device or perhaps a VM you may need to acquire it manually.
To do this, you’ll simulate running the OA3 tool by running a PowerShell script, which captures the device Hardware ID just like the OA3 tool.
Follow these steps to run the PS script:
- Open an elevated Windows PowerShell prompt and run the following commands. These commands are the same regardless of whether you are using a VM or a physical device:
md c:\HWID Set-Location c:\HWID Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted -Force Install-Script -Name Get-WindowsAutopilotInfo -Force $env:Path += ";C:\Program Files\WindowsPowerShell\Scripts" Get-WindowsAutopilotInfo.ps1 -OutputFile AutopilotHWID.csv
2. When you are prompted to install the NuGet package, choose Yes.
See the sample output below:
PS C:\> md c:\HWID Directory: C:\ Mode LastWriteTime Length Name ---- ------------- ------ ---- d----- 3/14/2019 11:33 AM HWID PS C:\> Set-Location c:\HWID PS C:\HWID> Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted -Force PS C:\HWID> Install-Script -Name Get-WindowsAutopilotInfo -Force NuGet provider is required to continue PowerShellGet requires NuGet provider version '184.108.40.206' or newer to interact with NuGet-based repositories. The NuGet provider must be available in 'C:\Program Files\PackageManagement\ProviderAssemblies' or 'C:\Users\user1\AppData\Local\PackageManagement\ProviderAssemblies'. You can also install the NuGet provider by running 'Install-PackageProvider -Name NuGet -MinimumVersion 220.127.116.11 -Force'. Do you want PowerShellGet to install and import the NuGet provider now? [Y] Yes [N] No [S] Suspend [?] Help (default is "Y"): Y PS C:\HWID> $env:Path += ";C:\Program Files\WindowsPowerShell\Scripts" PS C:\HWID> Get-WindowsAutopilotInfo.ps1 -OutputFile AutopilotHWID.csv PS C:\HWID> dir Directory: C:\HWID Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 3/14/2019 11:33 AM 8184 AutopilotHWID.csv PS C:\HWID>
3. Verify that there is an AutopilotHWID.csv file in the c:\HWID directory. This file contains the complete Hardware ID.
You will need to upload this data into Intune to register your device for Autopilot. If you are using a physical device instead of a VM, you can copy the file to a USB stick. If you’re using a VM, you can right-click the AutopilotHWID.csv file and copy it, then right-click and paste the file to your desktop (outside the VM).
If you have trouble copying and pasting the file, just view the contents in Notepad on the VM and copy the text into Notepad outside the VM. Do not use another text editor to do this.
And that’s it, the device is now registered.