Category Archives: NUC

Add a Serial Number to your NUC

As an Intel NUC owner, you might have noticed that your NUC doesn’t come with the serial number hard-coded into the BIOS:

NUC with no Serial Number

NUC with no Serial Number

You can actually do this yourself with the Intel Integrator Toolkit.  The site says support ended for it and it would be taken down in 2015, but here we are mid 2016 and it’s still available :).  You get a list of client OS’s that support it but I installed it on Server 2016 TP 5 with no issues.

When you launch the application, you get a dialog box giving you some options.  As you can see, you could run this from another PC entirely (but don’t – you need to be present to accept the config changes).  If you’re running it from your NUC however, you can walk the wizard below to customize the BIOS and get right to it. (NOTE: You must have an active internet connection!)

Menu showing configuration options when you launch the tool.

Since I’ve picked to customize locally, the toolkit gives me a lot of options as you can see below.

Intel Integrator Toolkit

Lots of customization options!

In the SMBIOS menu, I simply input a value.  I had the Serial Number from an old HP laptop I happened to have written down handy so I input that as the value . Just kidding, I picked Beaker.  The toolkit allows you to paste in values, so you could create your own custom Serial Numbers and import them.

When you’ve finished your customization, you simply select “Save BIOS” from the ribbon.  This will install the BIOS and add all your custom configurations.

Save BIOSTime to make it happen!

YOU CANNOT DO THIS REMOTE – YOU NEED TO HAVE A KEYBOARD ATTACHED TO ACCEPT THE CONFIGURATION CHANGE (and a monitor to read the message, or just remember to press 9 on the keyboard).  Don’t say I didn’t warn you 🙂

Be ready to press 9 to accept the change

Be ready to press 9 to accept the change

When the configuration is complete and you sign in again, you’re greeted with a dialog box from the toolkit letting you know your change was successful.

Woohoo, you did it!

Woohoo, you did it!

And of course, you can validate in PowerShell too!

PowerShell is King! And your Intel NUC has a Serial Number!

PowerShell is King! And your Intel NUC has a Serial Number!

 

BONUS FOR READING THIS FAR!

Another important feature to customize is the display image.  I opted for a picture of Beaker because he’s my hero.

changing images

 

Save

Save

Save

Save

Enabling Wireless on the 6th gen NUC using Server 2016 TP4

This one is pretty straight forward.  Download the wireless driver for NUC from here.

In an admin PowerShell prompt type:

Import-Module ServerManager
Add-WindowsFeature -Name Wireless-Networking

You’ll be prompted that a restart is required which you can do from the same window by typing:
Restart-Computer

Then, when you’re back up and running you can install the driver.

Hacking the network driver for 6th gen NUC

Let’s say you buy a machine or have a machine that’s only supported for every OS on the planet except for the one you intend to use.  You can accept your fate – that you really don’t live with as much freedom as you want, or you can change your fate and hack drivers to get exactly what you want.  This post will show you how to do option 2 (which by the way is the correct option to pick).

Since everybody loves the NUC, we are going to hack the crap out of the 6th gen net driver to install the very unsupported Server OS.

What you need:

  • NUC net driver (I grabbed the Win10x64 one)
  • Windows 10 Driver Kit (scroll down, the actual download is about halfway down the page – and for what it’s worth, I installed it using all the default settings)
  • 7-zip (7-zip is king!)
It’s going to be really helpful to find the Device ID because you will need it for the specific driver you’re trying to hack.  The DeviceID for the network adapter on the 6th gen NUC is PCI\VEN_8086&DEV_1570&SUBSYS_20648086&REV_21 *but* you only need to match the first part – so in this case  PCI\VEN_8086&DEV_1570.  Using this info, I found the driver I wanted to hack was in the NDIS64 folder (specifically e1d64x64.inf) once I extracted the exe with 7-zip.  This is the only .inf with the matching hardware ID so I know for sure this is the file I need to edit and eventually import into my deployment workbench.Capture
To do the actual hacking, I copied the ID from this section: Capture1
and then pasted it into this one – it’s directly below where I got it from and literally the only other spot where something like this would belong – so if you’re new to this don’t be afraid!
Capture2

I kept it in the correct order as it was listed above

 

Once I did my copy paste magic, all I needed to do was save the file and then  move the NDIS64 folder away from where I extracted the LAN exe (my downloads folder) because it’s all that’s needed for the import when the time comes.
Now the driver is ready to be imported into your deployment workbench.  Since MDT doesn’t require driver signing, you’re good to go.
/NOTE: This same driver will work for Server 2016 – some of you will want to grab and edit in the NDIS65 folder but it’s just not necessary.