Autopilot: collect hardware hash from existing devices using SCCM Task Sequence

Question

Hi everyone, I need to collect hardware hash from new PC using a USB task sequence media. My Task Sequence performs the following operations: 1 - Connect to Network Folder 2 - Run Powershell script: ([Get-WindowsAutoPilotInfo.ps1][1] ) 3 - Restart the Pc The task sequence ends successfully and I find the generated .csv file. The problem is that this file is empty, without HW ID that I would need to put the PC in autopilot. ![69102-image.png][2] ![69115-image.png][3] ![69103-image.png][4] I modified the script with these parameters: ![69070-image.png][5] What could be causing this problem? [1]: https://www.powershellgallery.com/packages/Get-WindowsAutoPilotInfo/3.5 [2]: /api/attachments/69102-image.png?platform=QnA [3]: /api/attachments/69115-image.png?platform=QnA [4]: /api/attachments/69103-image.png?platform=QnA [5]: /api/attachments/69070-image.png?platform=QnA

Answer 1

Are the devices already enrolled in Intune?

Answer 2

No, the pc is neither in Intune nor in SCCM.

I need a way to get the hardware ID to put the pc into Autopilot via a USB stick before loading Windows.
And I had thought about creating a Task Sequence in SCCM.

Answer 3

Is your purpose to get these devices into Autopilot? If so, have you looked at using Autopilot for existing devices and using the Autopilot json file? That way you can use Autopilot but the devices don't need to be registered. Once the devices are in Intune after Autopilot, you can then target an Autopilot profile to the devices with the convert devices to Autopilot option enabled. Then it will capture the hardware hash.

Windows Autopilot Deployment for existing devices https://learn.microsoft.com/en-us/mem/autopilot/existing-devices

Answer 4

@Alfio Santoro

Thank you for posting in Microsoft Q&A forum.

>No, the pc is neither in Intune nor in SCCM. And I had thought about creating a Task Sequence in SCCM.

If we want to use the SCCM environment. These computers may need to be managed by SCCM firstly. And then, we could use the power shell script in task sequence to push the process. The hardware hash will be written to the specified CSV file, which you could then upload to Intune, either manually or using the Windows Autopilot Intune module's Import-Auto pilot CSV file. For more details, please refer to this excellent blog: https://oofhours.com/2020/09/28/export-all-your-hardware-hashes-from-configmgr/

Have a good day!

---

If the response is helpful, please click "Accept Answer" and upvote it. Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 5

Same problem here. The data from the CMPivot isn't digestible by the Autopilot importer.