How to Add a Device HWID to Intune Without Losing Your Mind

Alright, folks, let’s talk about hardware IDs and Intune—because nothing screams “sysadmin fun” like adding a device to Autopilot at the crack of dawn. Whether it’s a shiny new device fresh out of the box or something that’s already been messed with (looking at you, end users), this guide will help you wrangle those pesky HWIDs into Intune.

Grab your coffee, plug in that RJ45 cable, and let’s get to it.

Why Should You Care About HWIDs?

Because Microsoft said so. No, really. If you want your devices to play nice with Autopilot and save yourself from the repetitive setup chaos, adding the HWID ensures they’re recognized and pre-configured during enrollment. It’s like giving your device a VIP pass to the Intune party.

Option 1: Adding HWID from OOBE (Out-of-Box Experience)

Got a device straight out of the box? Perfect. Here’s how to make it Intune-ready before the users (or chaos) get involved.

Step 1: Summon the Command Prompt

When the OOBE screen shows up (the one asking you about regions, keyboards, and other boring stuff), press:
Shift + F10.
Boom. You’re now in Command Prompt. The power is yours.

Step 2: Connect to the Internet

If the device is giving you side-eye over Wi-Fi drivers, no worries. Grab an RJ45 cable and plug it into the device like it’s 2005. Need proof it’s online? Run this in Command Prompt:

ping google.com

Look at you, sysadmin extraordinaire.

Step 3: Grab the HWID and Upload It

Switch to PowerShell by typing:

powershell

Now, run these commands to install the Autopilot script and upload the HWID directly to Intune:

Install-Script -Name Get-WindowsAutopilotInfo -Force
Get-WindowsAutopilotInfo.ps1 -Online

No USB drives. No CSV files. Just straight-up magic.

Option 2: Adding HWID from an Installed OS

So, the device is already up and running? It’s fine. This method works whether it’s fresh out of the box or already full of questionable browser toolbars.

Step 1: Open PowerShell

Run PowerShell as an Administrator because you’re the boss.

Step 2: Choose Your Adventure

Option A: Online Method (Direct Upload)

Skip the middleman (aka CSV files) and upload the HWID directly:

Install-Script -Name Get-WindowsAutopilotInfo -Force
Get-WindowsAutopilotInfo.ps1 -Online

Done and dusted. Move on with your day.

Option B: CSV Export Method

Prefer the manual route? Export the HWID to a file instead:

Get-WindowsAutopilotInfo.ps1 -OutputFile C:\HWID\AutopilotHWID.csv

Save that CSV somewhere safe (and not Desktop\New Folder (6)).

Step 3: Upload the CSV to Intune

Log in to the Microsoft Endpoint Manager admin center.
Go to Devices > Windows > Windows Enrollment > Devices > Import, and upload your CSV. Done!

Pro Tips

• No Wi-Fi? No Problem: RJ45 cables are your best friend in OOBE. Old-school, but it works.
• Online Method is King: Why bother with USB drives or CSV files when you can upload directly? Save yourself the hassle.
• Name It Right: Assign meaningful names to devices to avoid "DESKTOP-1283HFF" chaos later.

The Verdict

Adding a device’s HWID to Intune isn’t glamorous, but it beats manually configuring devices one by one. Whether you’re working with a fresh OOBE device or something that’s been passed around the office like a bad email chain, these methods will save you time and (some) sanity.

Now go forth, sysadmin warrior. Reboot your device, test the enrollment, and maybe even take a coffee break. You’ve earned it.

Until the next late-night fix, stay caffeinated and keep deploying.