Because of the way we had the devices domain-joined beforehand, and our plan to get them done as remotely as possible, we needed to make sure we could easily match up the domain-joined, pre-enrollment names with the device serial. 

The hardware hash for each in this case may only be necessary in certain situations — we had a customized script for our environment to pull that info. 

However, I’m always game to work on my reporting skills.

• Hardware Hash: v_GS_MDM_DEVDETAIL_EXT01 (DeviceHardwareData0)
• Serial Number: v_GS_SYSTEM_ENCLOSURE (SerialNumber0)
• Computer Name: v_GS_SYSTEM (Name0)

SELECT v_GS_SYSTEM.ResourceID AS [v_GS_SYSTEM ResourceID],v_GS_SYSTEM.Name0,v_GS_MDM_DEVDETAIL_EXT01.ResourceID AS [v_GS_MDM_DEVDETAIL_EXT01 ResourceID],v_GS_MDM_DEVDETAIL_EXT01.DeviceHardwareData0,v_GS_SYSTEM_ENCLOSURE.ResourceID AS [v_GS_SYSTEM_ENCLOSURE ResourceID],v_GS_SYSTEM_ENCLOSURE.SerialNumber0
FROM v_GS_SYSTEM
INNER JOIN v_GS_MDM_DEVDETAIL_EXT01
ON v_GS_SYSTEM.ResourceID = v_GS_MDM_DEVDETAIL_EXT01.ResourceID
INNER JOIN v_GS_SYSTEM_ENCLOSURE
ON v_GS_SYSTEM.ResourceID = v_GS_SYSTEM_ENCLOSURE.ResourceID
WHERE
(v_GS_SYSTEM.Name0 like 'LAPTOP%')

I whipped up a quick table in Report Builder for this. 

Because the hashes are so long, I didn’t want all of them listed in one big mess. So I left grouping on for the table.

This resulted in each computer being its own “group” in the table — I had to click the + icon next to each laptop to expand the row and show the serial and hash. 

This worked out well for the specific use of this report, but the report couldn’t be emailed to anyone because those + signs don’t show up in the report email — something to watch for if you were going to send a report in the email instead of sending the report URL.