I recently started deploying around a dozen NUC's and I am running into an issue. Due to asset and imaging requirements, we require the SMBIOS to be filled out with the serial number, manufacture and internal asset tag. Before you say you have to use tha ITK to push this data in.. I know.
You can see in the image above I have configured the SMBIOS settings the way we need them to be configured. Once this was complete I deployed our image and notice the drivers' injection script was very fast. So I logged into the machine once the image was deployed and noticed that I was unable to get the information required from the command prompt.
I have since reflashed the bios and even reset the SMBIOS settings and I am still unable to get this to work on 4 of my devices, some were working on previous BIOS version and are no longer on the latest.
I have about 5x NUC6i3SYK's and 8x NUC7i3BNK's ALL on their respective latest bios firmware. Some work some don't in both types. Most are imaged to UEFI windows 10 64bit using the same base image. We have 3 with a Windows 7 Image (Same Base)
You can see from he above I have 3 stuck at the top and then the 3rd one in the second section I made a type and I am unable to correct it in the model number field.
Any help would be greatly appreciated.
I did some more digging and it looks like the SMBIOS is locked with the latest firmware's no matter what I do I am unable to change the SMBIOS on any of the 4 noted before.
From UEFI running ITK6.efi -s -t -p the output is what I configured and correct however when I reboot and check the bios nothing is showing up. Reboot back into UEFI and its there. Something is weird with the latest firmware I think.
I tried this on a BN i3 NUC with BIOS 0060 and 0064 and was able to write to the System and Chassis fields and was able to see the data in the Windows System Information app. Are you using the built-in EFI Shell? Do you have Secure Boot enabled? I am using a copy of EFI Shell from a USB flash drive and had Secure Boot disabled on both BIOS.
Thanks for your reply.
The system is not using safe boot and I was using the internal UEFI shell to run the commands.
I just attempted this in a bootable USB environment. I created a bootable UEFI USB and deleted all of the fields that were filled out in the SMBIOS. I then rebooted and verified that the visual bios was still blank. Then rebooted into the USB shell and filled out the system manufacturer rebooted and checked the visual bios and it was still blank.
I was hoping this was going to work but it appears to behave the same as the internal shell interface on the nuc.
I have also reflashed the BIOS to the latest version in case there was some corruption I have not tried to load an older version but I can.
I have also set bios to defaults rebooted and then tried again - no change.
Thank you for contacting us.
I understand that you are having issues with our Intel® Integrator Toolkit
Based on the brief description of your case, and the post from MrMitch, we would like you to test the previous versions of the BIOS for your machines, so we can create a report between the old and le tatest versions.
Here are the direct download links:
Please let us know the outcome.
I hope this helps.
Strange. I had BIOS 0060 on an i3 BN NUC and F7 flashed to 0064 and was still able to modify the System and Chassis SMBIOS fields from both the built-in and an external EFI shell. Only other thing to try other than an older BIOS is to do a Jumper Recovery. This allows a complete flash of the ME FW and BIOS.
https://www.intel.com/content/www/us/en/support/articles/000005532/mini-pcs.html BIOS Recovery Update Instructions for Intel® NUC
Ok, I did some more testing today.
The BNK system is in production and I was unable to perform any test, however, I have 3x SYK's in my lab and I did the following.
I performed BIOS recovery all the way back to 63, 62 fails to recover to a Managment Engin error and anything older than 61 just says its incompatible.
While on BIOS 66, 65, 63 they all are having the same effects. ITK shows the SMBIOS information while the Visual BIOS is blank.
Thank you for your response.
Have you tried the recovery method through the jumper to the versions that do not fail (66, 65, 63) as advised by MrMitch before?
If you have any doubts, please go ahead an access the following link:
As well let me know, the .BIO file that you created, did you use it for all the units that share the same model? Or did you create a .bio file for each machine individually?
I used the jumper method and tried that with 66 and 65 no change. I did not try the jumper recovery with 63.
The only BIO file I have used is from the Intel support page. I used the following from the intel support pages for all of the devices with the same model numbers.
I hope this helps
Thank you for your response.
I have sent you a private message, please take a look at your inbox.
I hope this helps.
We just wanted to double check if you still need further assistance.
Please do not hesitate on contacting us back.