[Commercial PC] How to Re-register Microsoft Windows Autopilot After Replacing Motherboard

[Commercial PC] How to Re-register Microsoft Windows Autopilot After Replacing Motherboard

Overview

After a motherboard replacement, Windows Autopilot may no longer recognize the device's existing registration.

Windows Autopilot uses the hardware hash to identify a device. Replacing the motherboard may change the hardware hash. In this case, your organization's IT administrator must remove the old registration and then register the repaired device.

Process overview:

1. Before repair / IT administrator: Delete the device record from Intune. Then deregister the device from Windows Autopilot.
2. During repair / Repair center: Replace the motherboard. Complete the required repair settings.
3. After repair / IT administrator: Capture the new hardware hash. Register the device again.
4. Before deployment / IT administrator: Make sure a deployment profile is assigned. Then start the OOBE (out-of-box experience) deployment.

This identification mechanism is defined by Microsoft Windows Autopilot. This article follows Microsoft's general guidance and explains how ASUS commercial PC users and IT administrators should handle the process. Reference: Microsoft: Windows Autopilot device identification.

Applies to

• ASUS commercial PCs that were already set up with Windows Autopilot and need, or have had, a motherboard replacement.
• The device, Windows version, network, and organization licenses must meet the Microsoft Windows Autopilot requirements.
• Windows Autopilot cloud registration, deregistration, and deployment settings must be handled by the customer's IT administrator.

Process flow

Before repair: Back up data → Delete the Intune device record → Deregister from Autopilot

During repair: Replace the motherboard → Complete the required repair settings

After repair: Capture the new hardware hash → Register the device → Check the deployment profile → Start OOBE

Note: If the motherboard has already been replaced, check for old registration records first. After confirming, register the new hardware hash. Reference: Microsoft: Motherboard replacement guidance.

Step 1: Prepare before you begin

1. Back up your data (before repair): Back up important files. Windows may be reset or reinstalled later in the process.
2. Delete the Intune record (before repair / IT administrator): Delete the Intune device record of the device to be repaired.
3. Deregister from Autopilot (before repair / IT administrator): After deleting the Intune device record, deregister the device from Windows Autopilot.
4. Check repair settings (after repair / repair center): Make sure the required BIOS device information and the Windows product key (DPK) have been set.
5. Prepare the network (before re-registration): Connect to the internet. The script installation requires an internet connection.
6. Prepare an admin account (before re-registration / IT administrator): Make sure the account has permission to register devices.

Deregistration notes: The Intune device record and the Autopilot registration record are separate items. Follow Microsoft's official steps for your device join type, and do not delete the Microsoft Entra ID device object on your own unless the steps require it. Hybrid-joined environments have additional steps for on-premises AD DS.

Reference: Microsoft: Deregister a device, Microsoft: Replace the motherboard.

Step 2: Choose a re-registration method

Choose Method A or Method B. After registration, go to Step 3.

Method A: Register online during OOBE

1. Open Windows PowerShell
   • Connect the device to the internet.
   • On the OOBE sign-in screen, press Shift + F10 to open Command Prompt.
   • Type the following command and press Enter: 
     powershell.exe
2. Install the script and upload the data 
   In PowerShell, run the following commands in order: 
   [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 
   Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned 
   Install-Script -Name Get-WindowsAutopilotInfo -Force 
   Get-WindowsAutopilotInfo -Online
3. Complete sign-in
   • If you are prompted to install NuGet, follow the prompts to install it.
   • Sign in with an organization account that has the Intune Administrator role.
   • The first time you use the script, app permission consent may be required. The IT administrator should handle this according to your organization's policy.
   • After the upload is complete, go to Step 3.

Command source: Microsoft: Directly upload the hardware hash.

Method B: Export a CSV file, then import it into Intune

1. Capture the data on the repaired device 
   Sign in to Windows, open Windows PowerShell as an administrator, and run the following commands in order: 
   [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 
   Note: If the C:\HWID folder already exists, skip the New-Item command.
2. Hand over the CSV file
   • File location: C:\HWID\AutopilotHWID.csv.
   • Send the file to your IT administrator.
   • Use the CSV file exactly as created by the script. Do not edit and save it in Excel, as this may cause import format errors.
3. Import the file (IT administrator)
   1. Sign in to the Microsoft Intune admin center.
   2. Go to Devices > Windows > Enrollment.
   3. Under Windows Autopilot, select Devices.
   4. Select Import, upload the CSV file, and wait for the import to complete.

Command and import source: Microsoft: Manually register devices with Windows Autopilot. Menu names may vary depending on language and service updates.

Network note: This method exports the data first and uploads it later. However, Install-Script needs an internet connection to download the script, so it cannot be considered a fully offline process. Reference: Microsoft: Install-Script.

Step 3: Check registration and deployment

1. Check cloud registration (IT administrator)
   1. Open the Windows Autopilot device list in Intune.
   2. Select Sync.
   3. Refresh the list.
   4. Find the repaired device and check its serial number.
   5. Make sure the correct deployment profile is shown and its status is Assigned.
   6. Open the device properties and make sure Date assigned is shown.

Note: Syncing and profile assignment may take some time. Start deployment only after confirming the status above.

To check the profile settings, see Microsoft: Configure Windows Autopilot profiles.

2. Start deployment (IT administrator)
   • If the device is still in OOBE: Connect to the internet. Restart the device. Make sure the organization's deployment settings are loaded.
   • If the device is already at the Windows desktop: Reset the device according to your organization's IT procedures so that it returns to OOBE.
   • If the deployment settings still do not load after restarting: Check the registration status and the deployment profile. If needed, reset the device according to Microsoft's guidance.

Make sure your data is backed up before resetting. Reference: Microsoft: Restart after registration, Microsoft: Reset the device after repair.

Q&A

Question 1: Why do I need to re-register the device after it has been repaired?

A motherboard repair does not automatically update the Windows Autopilot registration. Replacing the motherboard may change the hardware hash. Your IT administrator needs to capture the new hardware hash and register the device again. Reference: Microsoft: Device identification.

Question 2: How do I fix error 806 or 808?

If you need help from Microsoft Support, prepare the following as requested:

• The CSV file of the device that shows the error.
• Proof of purchase or ownership.
• Device diagnostic logs.

The error code shows the status of the registration record. It cannot be used alone to determine where the replacement motherboard came from. For details, see Microsoft: Troubleshoot 806/808 errors.

Question 3: What if Get-WindowsAutopilotInfo cannot be found?

1. Check whether the Get-WindowsAutopilotInfo script was installed successfully.
2. If it is installed but the command still cannot be found, check whether the current PATH includes C:\Program Files\WindowsPowerShell\Scripts.
3. Fix the installation or PATH issue.
4. Run the command again.

Note: If the script installation fails, fix the error first. Do not continue with the next commands. Reference: Microsoft: Capture a new device ID from the device.