Deploying Windows Server 2012 R2 to Intel NUC devices using MDT 2013

The Intel NUC  devices have turned out to be a great machine for a small but efficient Hyper-V host. The challenge is that Intel doesn't get that, and in fact block their network adapter device drivers for Windows Server 2012 R2 (with some exceptions). In this post you learn how to fix this properly:

When it comes to solving the Windows Server 2012 R2 network drivers issues for the Intel NUC device, you have three options:

  1. By one of the few (well two) Intel NUC models that actually does have a network driver for Windows Server 2012 R2.
  2. Fix the driver yourself and sign it like a boss
  3. Fix the driver yourself, go cheap, disable driver enforcement in Windows Server 2012 R2, install the driver (semi-manually), and enable driver enforcement again.

This post is focusing on the real deal, doing what you should be doing, for a real world production environment. e.g. Option 2 🙂

Option 1 – Buy the special Intel NUC models

Not much to say about, buy one of the DC53427HYE or NUC5i5MYHE Intel NUC kits, download the LAN_Server2012R2_64_19.5.exe driver, and import as usual into MDT 2013.

Option 2 – Sign the Driver Like a Boss!

This is where you want to be, and for this you need get a real driver certificate that is cross-signed with Microsoft. I ended up buying Kernel-Mode Code Signing Certificates from Digicert for 223 USD (1 year) but I have seen deals as low as 178 USD / year. I just happen to like Digicert because they are awesome. Here are the steps for fixing and signing the Intel network drivers for Windows Server 2012 R2. In these steps I assume you have bought a certificate:

  1. Download the Intel NUC network driver for Windows 8.1 (LAN_Win8.1_64_19.5.exe) from and extract to a folder. 
  2. The driver you want to modify is in the lan_win8.1_64_19.5PRO1000Winx64NDIS64 folder. In this guide I created a new folder, C:DriversIntelNUC, and copied the copied the NDIS64 folder to it.

    The NDIS64 folder copied from lan_win8.1_64_19.5PRO1000Winx64.

  3. Modify the e1d64x64.inf file per Jay-R Barrios instructions in his post: Intel NUC D54250WYKH: Installing LAN Driver on Windows Hyper-V Server 2012 R2
  4. Download and install Windows Driver Kit 8.1 Update 1 from . Don't worry about the notes saying you must have Visual Studio 2013 installed, because you don't.

    Installing Windows Driver Kit 8.1 Update 1.

  5. Since you modified the e1d64x64.inf file you have broken the signing. To fix this you generate new catalog files, and sign them with your certificate.
  6. Generate the new CAT files by starting an elevated command prompt and run the following commands:

    Cd "C:\Program Files (x86)\Windows Kits\8.1\bin\x86"

    inf2cat.exe /driver:"C:\Drivers\IntelNUC\NDIS64" /os:Server6_3_X64

    Generating the catalog files.

  7. Next up is to sign the catalog files, you can either do that using the Signtool.exe utility, or if you are using Digicert, you can use digicert util to do this. If you are doing the command line route, download the "DigiCert High Assurance EV Root CA.crt" from digicert to the folder where you have signtool.exe, and run the following command:

    signtool.exe sign /v /ac "DigiCert High Assurance EV Root CA.crt" /s My /n "Deployment Artist AB" /t /sha1 12210EDE21C48E90511476F35B18671665EEC14A ""

    Note: You need to replace the above command with your certificate name and SHA1 value (If you only have once certificate with that name you can skip the /sha1 switch).

  8. If you use the DigiCert utility, just add the CAT files to sign, don't forget to check "Kernel Mode Signing", and click Sign.
  9. Now the drivers are signed and you simply add them to MDT 2013. The Intel NUC tested with this guide was D54250WY, and since I always use the Total Control approach (click for details), I have that logical folder in my Deployment Workbench as well.

    "Fixed" network driver added to the workbench.

  10. You are Done!  MDT 2013 will no happily inject the driver into the driver store during deployment! During deployment, during the WinPE phase you can verify the injection into the driver store by pressing F8, and open the X:WindowsLogsDISMDism.log file.

    Dism.log file showing successful install of the modified driver.

Option 3 – Go cheap and trick the system

If you want to cheap, and don't mind having a manual task in the deployment (brr), you can disable driver enforcement in Windows Server 2012 R2, install the driver, and enable driver enforcement again. This post by Jay-R Barrios show you how: Intel NUC D54250WYKH: Installing LAN Driver on Windows Hyper-V Server 2012 R2

Happy Deployment

/ Johan

About the author

Johan Arwidmark

0 0 votes
Article Rating
Notify of
Oldest Most Voted
Inline Feedbacks
View all comments
9 years ago

Technically sure, we use these signed drivers throughout the company.

However, I'm not sure Intel would like you to distribute custom signed drivers publicly though 🙂

/ Johan

9 years ago

Hi Johan, great post.
I went for option 3 since I use the NUCS in my personal environment at home. Out of curiosity, if one were to sign the drivers using option 2, in theory could I then share the signed drivers with the world?