HvemVet
asked on
HP EliteBook 840 G2 - Driver Issue SCCM 2012R2 / OSD
System Center version: 2012 R2 SP1 CU2
Product Name: HP EliteBook 840 G2
Operating System: Microsoft Windows 7 (64-bit)
We have an System Center 2012 R2 environment with Elitebook 840 G1 working very well with Operating System Deployment. However our G2 models is not able to present the same Task Sequence as it reboots on the "Preparing Network Connection" part of the WinPE startup.
We have injected both the newest network driver from Drivers Download at hp.com and the even newer driver from intel.com (both drivers tried separately) to the boot image.
The driver is (although I am aware that the chip now is called 218, it still carries the 217 driver name):
Intel(R) Ethernet Connection I217-LM
versions tried:
12.12.80.1950
12.12.80.19
How can we resolve this?
Product Name: HP EliteBook 840 G2
Operating System: Microsoft Windows 7 (64-bit)
We have an System Center 2012 R2 environment with Elitebook 840 G1 working very well with Operating System Deployment. However our G2 models is not able to present the same Task Sequence as it reboots on the "Preparing Network Connection" part of the WinPE startup.
We have injected both the newest network driver from Drivers Download at hp.com and the even newer driver from intel.com (both drivers tried separately) to the boot image.
The driver is (although I am aware that the chip now is called 218, it still carries the 217 driver name):
Intel(R) Ethernet Connection I217-LM
versions tried:
12.12.80.1950
12.12.80.19
How can we resolve this?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
It is working.
Is that what I recommend that you do is to inject the drivers into your WinPE.
What I did was took note of all drivers that was part of my WinPE pxe boot and removed them all.
Then once removed I added just the drive that is needed I217-LM Drive ver 12.12.80.19.
Once confirmed that I was able to boot successfully to the Task Sequence I then added each one of my NIC drivers back and tested.