NIC Intel(R) Ethernet Connection I217-LM Deployment Driver

Intel(R) Ethernet Connection I217-LM Deployment problems

HP Zbook, Probook 650G1 (See below for full range info)


OS Deployment problems with Intel NIC i217-V (I217V) under Windows 7 64BIT and different Deployment Software Like Frontrange-Enteo, SCCM, Symantec and also with Windows Deployment.

Main problem is that the Windows PE 3.X that most Deployment solutions use accepts a less DEVICEID (A shorter). Also the NIC somehow seems to have timing problems and just behaves different than others during unattended setup.


Your Windows PE will work with any driver DeviceID:


But the Windows 7 Setup that your Deployment does need is more specific driver and checks behind that base DeviceID:

PCI\VEN_8086&DEV_153B&SUBSYS_00008086 (Sample)

06.09.2013, < GEHT NICHT
06.06.2014, < GEHT NICHT
31.07.2014, (
) < GEHT von HP Carepaq, sp68420



Screenshot shows Driver 12.8.33 from original HP factory setup W7 64BIT which DOES not work for Deployment.

The HP Factory NIC Setup shows following Device-ID (W7 64BIT) which does not work for deployment










Errors your will see in c:\windows\panther with wrong driver (No NIC in OS phase / Not Windows PE)


»¿2015-04-15 09:57:35, Error [DJOIN.EXE] Unattended Join: NetJoinDomain failed error code is [1355]

2015-04-15 09:57:35, Error [DJOIN.EXE] Unattended Join: DsGetDcName test failed: 0x54b, last error is 0x0, breaking if debugger attached...

2015-04-15 09:57:35, Error [DJOIN.EXE] Unattended Join: Unable to join; gdwError = 0x54b


DSJOIN error in Logfiles (C:\Windows\Panther\UnattendGC\UnattendedJoinDCLocator.etl)

2015-04-15 09:50:34, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...

2015-04-15 09:50:39, Warning [DJOIN.EXE] Unattended Join: DsGetDcName failed: 0x54b, last error is 0x0, will retry in 5 seconds...

2015-04-15 09:50:44, Warning [DJOIN.EXE



Working Driver, 07/31/2014,


You need the INF file with the three DeviceID:

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

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

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


Extract File: e1d62x64.inf (Working Driver which should work for the PHASE after Windows PE Format/Copies the Disk with your deployment. {Unattended phase}) (NOT Windows PE)


Signature = "$Windows NT$"

Class = Net

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

Provider = %Intel%

CatalogFile =

DriverVer = 07/31/2014,




%Intel% = Intel, NTamd64.6.1, NTamd64.6.1.1, NTamd64.6.2



ExcludeFromSelect = \







; DisplayName Section DeviceID

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

%E15A2NC.DeviceDesc% = E15A2.6.1.1, PCI\VEN_8086&DEV_15A2


Device ID from working I217V for Deployment Driver,, 2014, HP Softpaq68420

PCI\VEN_8086&DEV_153A;PCI\VEN_8086&DEV_153A&SUBSYS _00008086;PCI\VEN_8086&DEV_153A&SUBSYS_00011179;PC I\VEN_8086&DEV_153A&SUBSYS_1909103C;PCI\VEN_8086&D EV_153A&SUBSYS_190A103C;PCI\VEN_8086&DEV_153A&SUBS YS_2253103C;PCI\VEN_8086&DEV_153A&SUBSYS_2255103C; PCI\VEN_8086&DEV_153B;PCI\VEN_8086&DEV_153B&SUBSYS _00008086;PCI\VEN_8086&DEV_153B&SUBSYS_00011179;PC I\VEN_8086&DEV_1559;PCI\VEN_8086&DEV_1559&SUBSYS_0 0008086;PCI\VEN_8086&DEV_1559&SUBSYS_00011179;PCI\ VEN_8086&DEV_155A;PCI\VEN_8086&DEV_155A&SUBSYS_000 08086;PCI\VEN_8086&DEV_155A&SUBSYS_00011179;PCI\VE N_8086&DEV_155A&SUBSYS_198F103C;PCI\VEN_8086&DEV_1 55A&SUBSYS_1991103C;PCI\VEN_8086&DEV_155A&SUBSYS_1 993103C;PCI\VEN_8086&DEV_155A&SUBSYS_2101103C;PCI\ VEN_8086&DEV_155A&SUBSYS_213E103C;PCI\VEN_8086&DEV _15A0;PCI\VEN_8086&DEV_15A0&SUBSYS_00008086;PCI\VE N_8086&DEV_15A1;PCI\VEN_8086&DEV_15A1&SUBSYS_00008 086;PCI\VEN_8086&DEV_15A2;PCI\VEN_8086&DEV_15A2&SU BSYS_00008086;PCI\VEN_8086&DEV_15A2&SUBSYS_0001117 9;PCI\VEN_8086&DEV_15A2&SUBSYS_2216103C;PCI\VEN_80 86&DEV_15A2&SUBSYS_221B103C;PCI\VEN_8086&DEV_15A2& SUBSYS_225A103C;PCI\VEN_8086&DEV_15A2&SUBSYS_22701 03C;PCI\VEN_8086&DEV_15A2&SUBSYS_2271103C;PCI\VEN_ 8086&DEV_15A2&SUBSYS_22DA103C;PCI\VEN_8086&DEV_15A 2&SUBSYS_22FB103C;PCI\VEN_8086&DEV_15A3;PCI\VEN_80 86&DEV_15A3&SUBSYS_00008086;PCI\VEN_8086&DEV_15A3& SUBSYS_00011179



INF file HP CVA / Softpaq 68420 Infos

TITLE: Intel I217LM/V and I218LM Gigabit Ethernet Driver

This package contains the driver installation package for the Intel I217LM/V and
I218LM This build has post-beta drivers that are Intel-Signed Gigabit Ethernet
Controller in the supported notebook models and operating systems.

PURPOSE: Routine
SOFTPAQ MD5: a369c6b348bb54a453afae2435f988a3
EFFECTIVE DATE: August 26, 2014
CATEGORY: Driver-Network


HP ZBook 17 G2 Mobile Workstation
HP ZBook 17 Mobile Workstation
HP EliteBook Folio 9480m Notebook PC
HP EliteBook Folio 1040 G1 Notebook PC
HP EliteBook 840 G1 Notebook PC
HP ZBook 14 Mobile Workstation
HP EliteBook 740 G1 Notebook PC
HP EliteBook 850 G1 Notebook PC
HP EliteBook 750 G1 Notebook PC
HP ZBook 15 G2 Mobile Workstation
HP ProBook 640 G1 Notebook PC
HP ProBook 650 G1 Notebook PC
HP ZBook 15 Mobile Workstation







HP biosconfigutility.exe and password in BIOS options, error 10

HP this is absolue confusing! Not all syntax provided in the "Biosconfigutlity.exe" seem to work in a certain order!

Here is the correct syntax and a working example under Windows PE 3.X 32BIT boot media:

Biosconfigutlity.exe /cspwd:"youroldbiospassword" /cspws:"yournewbiospassword"

And an example to renew the existing BIOS password and write new BIOS Setting in one command:

BiosConfigUtility.exe /cspwd:"youroldbiospassword" /nspwd:"yournewbiospassword" /set:"%cd:~0,3%bios\6300\settings\6300.txt"

  • %cd:~0,3% = Current Drive letter your batch is on
  • bios\6300\settings\6300.txt (The config file with the new bios settings in some file Directory structure bios\modelltype\settings\modelltypeconfigfile.txt (Just an example)
  • Yes, you have to mention the "-chars (Quotation marks)
  •  "IF" you provider a existing password (cspwd), AND it does not match, it will be overseen and the NEW password written (cspws)
  • The exact syntax and ORDER of the options have to be followed

Make sure you don't mess UP with this tool. On certain newer laptops if you mess UP the BIOS password you "Can't" reset it with a jumper. There are two way (Send device to HP or buy a unlock key from russia for USD50). A cutomer from us has tried and did not understand the tool correct.

 If you don't want plain text passwords in your scripts you may have to use "HPQPswd.exe" which makes a password.BIN file from your entrys with the password encrypted.


Deployment Time HP 6560 all Major super OS-Deployment fail!

OS-Deployment Time:
HP 6560 all Major super OS-Deployment fail!

With our Deployment system Storage and nic driver intergation is very easy! ;-)
A short look in google show you that all those new fancy OS-Deployments did work a few months. But
now with new hardware and new Nic and mass stroage drivers they (as allways) fail and people have problems.
All the regualr non-deployemtn people who took OS Deployment for easy and thought they can do it theirself have problems.
The HP 5660 seems to fail with. Fails mean you will have to integrate a NIC and Mass Driver into the PE and maybe the WIndows 
XP SP3 silent setup if you still run Windows XP.
Even Windows 7 seems to have problems with the RIS. Back to the roots and hiring expensive Deployment people ;-)
·         WDS Windows Deployment
·         SCCM/SMS
·         Acronis 
·         Symantec Ghost und Deployment Suites wie Altiris


SCCM 2007R2 Links

VL Aktivierung MAK SCCM 2007

MDT Integration in Details AFTER SCCM 2007 install

Deploy SCCM 2007 SP2 RC on Windows Server 2008 R2

WINS Eintrag fuer SLP

SCCM 2007 R2 Automatic Site Code Discovery Was Unsuccessful

Faden Roger, WIN7 deployment, Techdays

Zuercher Blog, SCCM, MKS, MAK