During OOBE, open a command prompt (Shift+F10), run the given PowerShell command, and upload the hardware hash.
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 PowerShell.exe -ExecutionPolicy Bypass Install-Script -name Get-WindowsAutopilotInfo -Force Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned Get-WindowsAutopilotInfo -Online
To install the script and capture the hardware hash directly from the local computer.
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 New-Item -Type Directory -Path "C:\HWID" Set-Location -Path "C:\HWID" $env:Path += ";C:\Program Files\WindowsPowerShell\Scripts" Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned Install-Script -Name Get-WindowsAutopilotInfo Get-WindowsAutopilotInfo -OutputFile AutopilotHWID.csv
Why are you seeing this?
You might be wondering why are you seeing this post. Well, I've seen many people struggling while trying to build an autopilot machine (I'm talking about myself ngl), be it for testing purpose or otherwise with the OOBE hardware hash upload scripts. First they (they means me... it's me.. sigh) will open the command prompt, then the explorer, then search for msedge, then open msedge and set it up and then search for the OOBE scripts for hardware hash upload on the internet, copy it and then...🥲
Well, with the help of this post, I've made it a little easier and created a direct link, which an admin can input in the command prompt in the OOBE screen to open this page and just click the copy button up top to get the OOBE code and get started with the hardware hash upload and the enrollment process.
Steps you need to do follow on the OOBE screen to get here:
- Press Shift+f10 to open command prompt.
- Type the following text in the command prompt to get here.
start www.bit.ly/koulinc
- That's it! Now just hit the copy button up top and and right click on your command prompt on the OOBE screen to paste the script and get started.
0 Comments