@vervoordeldonk What we are finding is the mainstream hardware vendors (dell, hp, lenovo, intel nuc so far) do an excellent job of making each system unique so coming up with an alternate method of identification isn’t a problem.

The issue is like the system below

System Manufacturer xxxxr System Product TMB-3010 System Version R0M0 System Serial Number To be filled by O.E.M. System Type Type: Notebook BIOS Vendor American Megatrends Inc. BIOS Version 1.00/636G00WPC76508 BIOS Date 05/06/2016 Motherboard Manufacturer xxxxr Motherboard Product Name WEB-889A/WEB-889AA Motherboard Version R0M0 Motherboard Serial Number To be filled by O.E.M. Motherboard Asset Tag To be filled by O.E.M. CPU Manufacturer Intel® Corporation CPU Version Intel® Core™ i5-3210M CPU @ 2.50GHz CPU Normal Speed Current Speed: 2500 MHz CPU Max Speed Max Speed: 3800 MHz Memory 3.74 GiB Hard Disk Model 2.5" SATA SSD 3ME3 Hard Disk Firmware S15A19 Hard Disk Serial Number xxxxxxxxxx000025 Chassis Manufacturer xxxr Chassis Version Chassis Serial To Be Filled By O.E.M. Chassis Asset

I put the lower case “x” in just to mask a few values, but as you can see there is nothing unique on this system from the next system from the same manufacturer other than the disk serial number. I have a few examples of other systems that are very similar. One solution is to go ahead and use the mac address as part of the mix for system identification. In that case we would be no worse off than we are today by only using just the mac address.

We also want to bring in the asset tag value so at the very least if FOG can’t identify the system the IT tech will need to populate that field to create a unique ID for that system. (sorry I’m a bit thinking out loud here)