I wrote a post back in 2012 on how to tattoo the registry with OSD information from Task Sequence variables and OS versions. https://ccmexec.com/2012/08/script-to-tattoo-the-client-registry-during-osd/
We can then inventory that information using Configuration Manager and create collections and create reports based on Task Sequence used, media type and originally installed Windows 10 build which can be useful in the future. I have added in this example OSD Duration so we really easy can see how long time the OS deployment took. It can be downloaded here: https://github.com/Ccmexec/MEMCM-OSD-Scripts
And the inventoried values will look like this in resource explorer. I used RegKeyToMof to extend the HW inventory,
I use the variable for OSD StartTime that we set in OSDBackground which I have blogged about here before: https://ccmexec.com/2016/10/configuration-manager-osdbackground/ and it can be downloaded from Onevinn – Scripts (schrewelius.it)
The name of the Registry key can be configured in the beginning of the script as shown here.
After adding changing the script with the name of the registry key, add it to a package and distribute it to your Distribution Point group. I run the script in the end of my Task Sequences like this.
hope this can be useful and spark ideas on what more to add to the registry during OSD that can be useful afterwards.