I have been deploying the small and cool Intel NUC’s for a long time, they just have one problem, it is a small problem, but….
There is no Make/Model, actually, the entire SMBBios is empty, now that makes it a bit hard to figure what model we are deploying and therefore it is hard to determine what drivers that needs to be deployed. On some older NUC’s there could be settings.
This is what we get from PowerShell – Win32_ComputerSystem,Win32_ComputerSystemProduct,Win32_BIOS and Win32_BaseBoard
As you can see Make and Model are kind of “nothing”, but SMBIOSBIOSVersion is RYBDWi35.86A.0350.2015.0812.1722 and that is basically the name of the motherboard, but slightly better, why don’t we use the Win32_BaseBoard and grab product, that seems just to be the perfect match here. And hold it… Win32_BaseBoard is already inventoried by the ZTIGather process, so the only thing we need to do is to set ModelAlias to Product, that seems pretty easy…
The “old” AliasUserExit to the rescue (once more)
The AliasUserExit script runs as a part of the ZTIGather process in MDT/ConfigMgr. This script has a section for Models where either Make is “Intel” or “”, in that case we grab the Product from the gather process and store that in %ModelAlias%.
Script can be found here: http://1drv.ms/1OdlmnW and inside the VBscript it explains how to use it
Verify that it works:
| Running cscript ZTIGather.wsf /inifile:Customsettings.ini we get this on a DN2820FYK. Note: In this case someone manually added/modified the SMBios using the Intel Toolkit to say that the Model is DN2820FYKH, but it is actually DN2820FYK |
 |
| Running cscript ZTIGather.wsf /inifile:Customsettings.ini we get this on a NUC5i7RYB. Note: In this case the BIOS is “normal”, that is it is totally blank |
 |
| Running cscript ZTIGather.wsf /inifile:Customsettings.ini we get this on a D53427RKE. Note: In this case the BIOS does contain vales, older NUC’s could have them set.. |
 |
