MDT and Autopilot

[plumyeti]

Has anyone used MDT to deploy a Windows 11 image to Windows 10 machines that will be enrolled to Intune (Autopilot)

 

The majority of machines here at my new school are Windows 10. We have Intune and Autopilot all setup and ready to go.

 

Can I use MDT to install Windows 11 and then let autopilot do the rest, has anyone done this?

 

I just can't stand the idea of going around each individual PC with a USB and manually typing commands.

 

Open to other solutions/ideas.

[djm968]

This has been grabbed straight from ChatGPT -  No idea if it will do what you need, but does possibly contain some useful info on how to capture and import Hardware Hashes Into Intune.

 

1. Prepare Your Windows 11 Image in MDT

You can use:

• A clean ISO from Microsoft

• A custom WIM (optional)

In MDT:

1. Import the OS under Operating Systems

2. Create/modify a Task Sequence to install Windows 11

3. Add drivers, applications, updates as needed

4. Ensure the Task Sequence ends before OOBE begins (standard MDT behavior)

No Autopilot enrollment happens during imaging—this is expected.

---

2. Deploy the Image to Windows 10 Machines

Boot the Windows 10 devices using:

• MDT PXE

• MDT USB boot media

• LiteTouchPE_x64.iso

Run the Task Sequence to install Windows 11.

After the deployment is complete, let the computer reboot to the Windows 11 OOBE screen, but DO NOT complete the OOBE yet if you need to harvest the hardware hash manually.

---

3. Capture Autopilot Hardware Hash

You must register each device with Autopilot.

There are 3 options:

---

🅰 Recommended: Capture hardware hash during MDT Task Sequence

Add a Task Sequence step after OS installation but before reboot:

Add PowerShell script:

Use:

mdt\scripts\Get-WindowsAutoPilotInfo.ps1 -OutputFile \\YOURSERVER\SHARE\AutopilotHashes\%SerialNumber%.csv 

You can download the script from Microsoft:
Get-WindowsAutoPilotInfo.ps1

This automatically gathers the device hash and places it on a network share.

---

🅱 Alternative: Capture hash manually at OOBE (Shift+F10 command prompt)

Run:

powershell -executionpolicy bypass -file Get-WindowsAutoPilotInfo.ps1 -OutputFile AutopilotHWID.csv 

Copy the CSV to a USB drive.

---

4. Import Hardware Hashes Into Intune

In the Intune portal:

1. Navigate to
   Intune Admin Center → Devices → Windows → Windows enrollment → Devices (Autopilot)

2. Click Import

3. Upload the CSV hardware hash file(s)

After ~10–30 minutes the devices appear in the Autopilot device list.

---

5. Assign an Autopilot Deployment Profile

Still in Autopilot:

1. Go to Deployment Profiles

2. Create a new profile for Windows 11

3. Assign it to the imported devices
   (You can use a device group + dynamic membership if preferred)

Recommended settings:

• Join type: Azure AD Join

• MDM Enrollment: Intune

• Skip privacy settings, EULA, etc: Yes

• User-driven or Pre-provisioned (White Glove) depending on your scenario

---

6. Complete OOBE on the MDT-deployed Windows 11 machine

Now the device is known to Autopilot.

When the Windows 11 device boots into OOBE:

1. Connect to Wi-Fi or Ethernet

2. Device contacts Autopilot service

3. Autopilot profile is applied

4. Device automatically:

   • Azure AD joins

   • Enrolls into Intune

   • Applies policies and apps

 

[highsky]

Yes, this is what we used:

https://www.deploymentresearch.com/using-mdt-with-windows-autopilot-for-existing-devices-task-sequence-template-and-scripts/