AutomoxAutomox
Find & Share Worklets

Windows Autopilot Enrollment

Maulik_Busa
September 9, 2024 at 7:11 pm UTC
#Windows#Autopilot

Hi All, 

I was wondering if anybody tried to leverage Automox for pulling hardware hash for windows Autopilot in their company environment. i want to enroll multiple devices to autopilot but still little confused with pulling hardware hash for all devices and manually upload it to Intune which sucks. 

 

Thanks in advance.

This discussion is archived and closed to replies. Continue it in the Automox Community Slack.

Discuss on Slack

Replies (8)

jack.smithOctober 2, 2024
#1

Hi @Maulik_Busa 

You can get that right out of WMI

powershell4 lines
$hash = (Get-CimInstance -Namespace root/cimv2/mdm/dmmap -Class MDM_DevDetail_Ext01 -Filter "InstanceID='Ext' AND ParentID='./DevDetail'").DeviceHardwareData
$serial = (Get-CimInstance -Class Win32_BIOS).SerialNumber
Write-Output "serial: $serial"
Write-Output "hardware hash: $hash"

If some of those devices are already in Intune you might even be able to use a `Windows Autopilot deployment profile` and point that at a dynamic Entra Group that grabs the devices you want. Sure is easier than having to build a CSV file for import. 

Maulik_BusaOctober 15, 2024
#2

Thanks for your reply @jack.smith,  Although i found a way around by creating autopilot profile in Intune itself and deploy it to enrolled endpoints in Intune. 

celery_manNovember 1, 2024
#3

Thanks for your reply @jack.smith,  Although i found a way around by creating autopilot profile in Intune itself and deploy it to enrolled endpoints in Intune. 

Could you elaborate your solution?

jack.smithNovember 1, 2024
#4

Use a dynamic group in Entra AD that is populated by approved models. Any existing devices we PXE boot into Microsoft Deployment Toolkit where a task sequence will Inject drivers, Apply the Operating System (from a reference build automatically rebuild/updated monthly), then launch the device into Autopilot. 

Reference https://mickitblog.blogspot.com/2022/09/imaging-using-mdt-with-autopilot.html and https://mickitblog.blogspot.com/2022/09/imaging-using-mdt-with-autopilot.html

From there Autopilot takes over for allowing users to setup the device, get it Entra AD joined and into Intune. Once within Intune the rest of the policies take over.

celery_manNovember 1, 2024
#5

We are a cloud based environment and do not have SCCM deployed. Per your comment I thought you meant this was purely Intune doing the work.

Thanks for the info.

jack.smithNovember 1, 2024
#6

We are a cloud based environment and do not have SCCM deployed. Per your comment I thought you meant this was purely Intune doing the work.

Thanks for the info.

No SCCM. Just MDT. Intune is good at MDM. Autopilot is good at OOBE for end users. Neither are OS Deployment onto bare metal. 

celery_manNovember 1, 2024
#7

We are a cloud based environment and do not have SCCM deployed. Per your comment I thought you meant this was purely Intune doing the work.

Thanks for the info.

No SCCM. Just MDT. Intune is good at MDM. Autopilot is good at OOBE for end users. Neither are OS Deployment onto bare metal. 

I wasn’t referring to bare metal. All of the clients are already in Intune and I thought this post was saying you can grab the hardware ID out of all Intune devices for future Autopilot wipes and/or deployments. 

Maulik_BusaNovember 5, 2024
#8

@celery_man i ended up creating one autopilot profile and deployed it to all Intune enrolled devices from intune itself. For those devices which werent enrolled in intune but was in automox, i created intune profile and deployed it via automox and process go on on its own until they registered in autopilot. 

Although i dont understand your question at why you need hardware hash once it enrolled in autopilot. but if you still need it then you can also export hardware has from Intune as well. 

Thanks

Back to all discussions