Server Products
Data Center Products including boards, integrated systems, Intel® Xeon® Processors, RAID Storage, and Intel® Xeon® Processors
4762 Discussions

D54250WYKH NIC not supported on Windows Server 2012 R2

ADalh
Beginner
4,516 Views

So my great idea was to bulid a NUC LAB based on 3-4 D54250WYKH nodes <-- since these seem to support most Hyper-V features.

However I was very dissapointed to find out that no drivers was available for Windows Server 2012 R2. There are drivers for Windows 8.1 (straight out of the box). As far as I can see Intel has made an explicit effort in not supporting microsoft server editions.

I found a way to circumvent this: http://foxdeploy.com/2013/09/12/hacking-an-intel-network-card-to-work-on-server-2012-r2/ FoxDeploy.com | Hacking an Intel network card to work on Server 2012 R2

but to be frank it's a little dirty and hard to implement if you want to do an bare metal installation. I would much prefer to have the signed driver availble.

So dear Intel - why is it so?

0 Kudos
16 Replies
Silvia_L_Intel1
Employee
2,093 Views

AJDalholm, I would need to inform you that this specific NUC supports Windows 7, Windows 8 and 8.1 only.

http://www.intel.com/support/motherboards/desktop/sb/CS-034034.htm http://www.intel.com/support/motherboards/desktop/sb/CS-034034.htm

Intel® Desktop Boards or NUCs do not currently support Microsoft Windows Server 2003, 2008, or 2012*. There are no plans for making drivers available for these operating systems.

 

I really apologize for the inconvenience.

ADalh
Beginner
2,093 Views

Sylvia - that is a non-answer! In my post I already acknowledged that no drivers are available for Server OS.

My question was why there is no support NIC drivers for Server OS on the NUC.

I can however take great comfort in knowing that "There are no plans for making drivers available for these operating systems" - I'm one happy little customer..

0 Kudos
Silvia_L_Intel1
Employee
2,093 Views

This is a marketing decision, NUCs were meant to be used as Desktop systems, not servers systems.

0 Kudos
RMore8
Beginner
2,093 Views

Hi Sylvia,

 

I wonder if Intel could re-evaluate their stance on Not supporting a NUC for Windows Server 2012,

I work for a government organisation, where we have a number of mobile vehicles with satellite connectivity, at the moment we are using laptops acting as servers,

a NUC would be ideal firstly from a cost point of view, secondly it's small, and thirdly if can operate on 12V,

If I could integrate an Edison to a NUC that would be even better

0 Kudos
IUman
Honored Contributor II
2,093 Views

At the following link you can see the Intel® NUCs that support Windows Server 2012.

http://www.intel.com/content/www/us/en/support/boards-and-kits/intel-nuc-boards/000005628.html?wapkw=supported+operating+systems+for+boards+and+kits Intel® NUC Supported Operating Systems

I can see that the only ones that support Windows Server 2012 are the Intel® NUC Kit DC53427HYE and the Intel® NUC Kit NUC5i5MYHE.

The Intel® NUC Kit NUC5i5MYHE operates either at 12V or 19 V and the Intel® NUC Kit DC53427HYE operates at 19V.

Best wishes,

Ivan

0 Kudos
RMore8
Beginner
2,093 Views

Thank you Ivan, that's just what I was looking for!

Many thanks

Riccardo

0 Kudos
IUman
Honored Contributor II
2,093 Views
0 Kudos
MVeen
Beginner
2,093 Views

Hi AJDalholm,

It is not so difficult to make windows server 2012 R2 to work. I've done it in 15 min. Good luck, i've installed windows 2012 R2 with Hyper-V and it works like a charm.

  1. Download this LAN driver for Windows 8 x64 for the NUC
  2. Extract package and open \PRO1000\Winx64\NDIS64\e1d64x64.inf in notepad, edit it so it looks like below "e1d64x64.inf"
  3. Run as admin: bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
  4. Run as admin: bcdedit -set TESTSIGNING ON
  5. Reboot
  6. Install driver by executing \APPS\PROSETDX\Winx64\DxSysChk.exe
  7. Run as admin: bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
  8. Run as admin: bcdedit -set TESTSIGNING OFF
  9. Reboot
  10. Then the network card works and is has this Intel(R) Ethernet Connection I218-V

e1d64x64.inf remake:

Version]

Signature = "$Windows NT$"

Class = Net

ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}

Provider = %Intel%

CatalogFile = e1d64x64.cat

DriverVer = 03/14/2014,12.11.96.1

[Manufacturer]

%Intel% = Intel, NTamd64.6.3, NTamd64.6.3.1

[ControlFlags]

[Intel]

[Intel.NTamd64.6.3.1]

; DisplayName Section DeviceID

; ----------- ------- --------

%E153ANC.DeviceDesc% = E153A.6.3.1, PCI\VEN_8086&DEV_153A

%E153ANC.DeviceDesc% = E153A.6.3.1, PCI\VEN_8086&DEV_153A&SUBSYS_00008086

%E153ANC.DeviceDesc% = E153A.6.3.1, PCI\VEN_8086&DEV_153A&SUBSYS_00011179

%E153BNC.DeviceDesc% = E153B.6.3.1, PCI\VEN_8086&DEV_153B

%E153BNC.DeviceDesc% = E153B.6.3.1, PCI\VEN_8086&DEV_153B&SUBSYS_00008086

%E153BNC.DeviceDesc% = E153B.6.3.1, PCI\VEN_8086&DEV_153B&SUBSYS_00011179

%E155ANC.DeviceDesc% = E155A.6.3.1, PCI\VEN_8086&DEV_155A

%E155ANC.DeviceDesc% = E155A.6.3.1, PCI\VEN_8086&DEV_155A&SUBSYS_00008086

%E155ANC.DeviceDesc% = E155A.6.3.1, PCI\VEN_8086&DEV_155A&SUBSYS_00011179

%E155ANC.DeviceDesc% = E155A.6.3.1, PCI\VEN_8086&DEV_155A&SUBSYS_90BA104D

%E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559

%E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_00008086

%E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_00011179

%E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_90BA104D

%E15A0NC.DeviceDesc% = E15A0.6.3.1, PCI\VEN_8086&DEV_15A0

%E15A0NC.DeviceDesc% = E15A0.6.3.1, PCI\VEN_8086&DEV_15A0&SUBSYS_00008086

%E15A1NC.DeviceDesc% = E15A1.6.3.1, PCI\VEN_8086&DEV_15A1

%E15A1NC.DeviceDesc% = E15A1.6.3.1, PCI\VEN_8086&DEV_15A1&SUBSYS_00008086

[Intel.NTamd64.6.3]

; DisplayName Section DeviceID

; ----------- ------- --------

%E153ANC.DeviceDesc% = E153A, PCI\VEN_8086&DEV_153A

%E153ANC.DeviceDesc% = E153A, PCI\VEN_8086&DEV_153A&SUBSYS_00008086

%E153ANC.DeviceDesc% = E153A, PCI\VEN_8086&DEV_153A&SUBSYS_00011179

%E155ANC.DeviceDesc% = E155A, PCI\VEN_8086&DEV_155A

%E155ANC.DeviceDesc% = E155A, PCI\VEN_8086&DEV_155A&SUBSYS_00008086

%E155ANC.DeviceDesc% = E155A, PCI\VEN_8086&DEV_155A&SUBSYS_00011179

%E15A0NC.DeviceDesc% = E15A0, PCI\VEN_8086&DEV_15A0

%E15A0NC.DeviceDesc% = E15A0, PCI\VEN_8086&DEV_15A0&SUBSYS_00008086

%E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559

%E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_00008086

%E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_00011179

%E1559NC.DeviceDesc% = E1559.6.3.1, PCI\VEN_8086&DEV_1559&SUBSYS_90BA104D

%E15A0NC.DeviceDesc% = E15A0.6.3.1, PCI\VEN_8086&DEV_15A0

%E15A0NC.DeviceDesc% = E15A0.6.3.1, PCI\VEN_8086&DEV_15A0&SUBSYS_00008086

%E15A1NC.DeviceDesc% = E15A1.6.3.1, PCI\VEN_8086&DEV_15A1

%E15A1NC.DeviceDesc% = E15A1.6.3.1, PCI\VEN_8086&DEV_15A1&SUBSYS_00008086

ADalh
Beginner
2,093 Views

Not to sound unappreciative - but I know this.. I included a link to this in my first post... It's a workaround - not a solution.

Disabling integrity check and enabling testsigning... not exactly my preferred path. However a signed driver from Intel for the Server OS would be. This would also be far easier to use in unattended deployments.

0 Kudos
idata
Employee
2,093 Views

will this same procedure also apply to 2008 R2? i am considering this device to run a server.

0 Kudos
DMagn
Beginner
2,093 Views

Thanks MichelV! Great info!

I've hit an issue running through these steps on Hyper-V 2012 R2 (Hyper-V core). I get to the part where the intel installation starts but then, after hitting next a couple times and waiting a minute, I get an info notification from the installer that says there are no supported devices at which point the installation ends. I've also tried installing the modified .inf using pnputil. It says successfully installed but after a reboot still no network adapter.

Any advise? TIA!

0 Kudos
RSpoo
Beginner
2,093 Views

I don't see what business is it of Intel's what I do or do not do with a PC I have purchased. What right do you have to dictate what I can use my PC for? The fact that you designed it to be best used for one specific purpose, doesn't mean that you are fair in artificially and intentionally blocking installation of a server class operating system.

NUC's are ideal as home servers, and many enthusiasts make use of server class operating systems. Why can't you see beyond your arrogance and recognise that?

Regardless of your "marketing decision", I shall be using my PC how I CHOOSE to use it, and I will make this work accordingly.

rspeak, I'll let you know shortly on your question as I've just installed Server 2008 R2.

0 Kudos
RLobk
Beginner
2,093 Views

I do not agree with your view Ryster.

Intel does not block installation of server class operating systems per se. They chose not to address any issues regarding Server operating systems and not to implement anything regarding Servers. They probably also do not support running Android. You may choose to try and run it but you will have to address any issues yourself.

If they truly, intentionally and artificially would block things then they could have also disabled support for Hyper-V all together.

Nobody "dictates what you can use your PC for". Should Intel also provide drivers for MS-DOS? Seems fair by your reasoning. Who are Intel to dictate what I can use my PC for?

Just be glad that Hyper-V is less picky about NIC's. You could just as easily have chosen ESXi as a hypervisor. I bet that would not work out of the box as well. Should Intel also fix that for you?

RSpoo
Beginner
2,093 Views

You're perfectly entitled to disagree, but you're also missing the point. The NIC and Drivers are fully supportive of Windows Server 2012 R2... it is after all just Windows 8.1 underneath all the server stuff.

In addition, I'm not asking them to support anything extra like Android nor MS-DOS, and it;s silly to suggest that I was. Their driver already supports Windows 8.1 and by extension Server 2012 R2 (I know this because I have made it work already by editing the inf file). The issue is that they have artificially blocked the installation on the server operating system. As such, they are dictating that you cannot use this PC as a server.

As it happen though, I have worked around this artificial limitation and am using my PC how I have decided to use it.

0 Kudos
VSkah
Beginner
2,093 Views

just as a FYI - ESXi 5.5 works fine on the NUC but you 'do' need to manually modify the downloaded installer image to add the NIC and SATA drivers to it. Not a big deal modifying the installer image via ESX Customizer, but greater than zero work to do and a little more mental stress than I'd hoped. Note that I consider this a ESXi issue, not an Intel issue. It's up to the os provider (ESXi) which drivers to include. The fact that Intel drivers are available is goodness to me.

I have not tried to get the matching Intel bluetooth/wifi card to work under ESXi so I don't know if drivers for that are available.

0 Kudos
idata
Employee
2,093 Views

hi. but i am way ahead of you. already been running 2008R2 perfectly on 4 NUCS since July. mission accomplished!

0 Kudos
Reply