To be filled by O.E.M.

Intel NUC

I own a Intel NUC and am currently using it as a VMware vSphere server. One thing that has been a thorn in the eye is the stupid way Intel decided to fill the DMI (Desktop Management Interface) for the model i own.

Software that is listing system information (like the dashboard of vSphere), wmi (Windows Management Interface) or management / inventory software like SCCM and many others shows a. nothing or b. To be filled by O.E.M. So it’s pretty useless when not even the model, product number or serial number are filled.

Intel has a tool for system administrators to fix this and set the information manually (which is also ridicules). It is called the Intel® Integrator Toolkit (ITK). But the story won’t finish with this. 🙂 When trying to download the software from the Intel website you would get a Page Not Found on any link you could find.

As it turns out Intel ended the support for ITK and it was removed from the download section a few months later. Well that’s a shame, but as you known once on the internet, always on the internet. A quick google search found a mirror that has the latest version of the software and i downloaded it. Jeeej?

No 😦 , the software was signed with an expired certificate and it was even issued from a revoked authority lol 🙂 I tried a few minutes to find a way to run the software even if the certificate was invalid, turns out that is more challenging then you might think. I gave up on fixing the DMI strings on my old NUC.

And last week i came across the ITK 6.1.2 for Intel® NUC or Intel® Compute Stick product. Yess, finely! I downloaded it, read the manual as it is a UEFI command line tool and powered down my vSphere server, moved it to a monitor (yes i moved the server to a monitor instead of attaching a monitor to a server, it was lighter this way :D) and got started. According the instructions you need to boot into the internal UEFI shell.. the what?! Damn you Intel 😡 ! There is no internal UEFI shell on my DC3217IYE!

Creating a UEFI bootstick is not that difficult. Microsoft uses \EFI\BOOT\BOOTX64.EFI on their operating system dvd’s so i copied that one along with the Intel .efi file. And guess what… That also didn’t work 😦 It crashed as fast as it loaded. Microsoft’s EFI boot isn’t good for many other things then loading their own installer. I don’t think its possible to load something other than the Windows Setup.

I ended up using EDK II from the project. Taniocore is community site surrounding the open source components of Intel’s implementation of UEFI. I used the file Shell_Full.efi

You need to rename the Shell_Full.efi to BOOTX64.EFI and place it in the \EFI\BOOT\ folder on your boot device. Yes, just 1 file. It will boot fine if your system support UEFI. place the ITK6.efi file on the root of the boot device.

Once the EFI shell is loaded you might need to change the active folder to the one with the ITK6.efi file. Type in map, this will show a list of devices found. The USB stick is probably the last one. Type fsX: to change to the X: device. Note replace X: with the drive you found using the map command. Type ls to verify you have chosen the right drive and you should see the ITK6.efi file. Once you have located it the hard part is over.

Type the following to show the current values (there won’t be many values ;))

ITK6.efi –s –p

I used the following commands to fill my NUC.

ITK6.efi –s –t system –f manufacturer –v Intel
ITK6.efi –s –t system –f product –v  DC3117IYE
ITK6.efi –s –t system –f version –v something on my sticker on the back side
ITK6.efi –s –t system –f serial –v also on the sticker on the back side



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s