We have recently purchased some new systems. These have a newer NIC card and driver in them than the ones currently in our boot.wim file.
I have extracted from the relevant systems and added to the drivers in WinPE in the LDMS. However when I PXE boot the new deivces and try to capture them WinPE fails to boot to the NIC and contact LD.
The WinPE process and driver list shows the new driver added but then just sits at the 'waiting for IP address.......' and has an IP of local loopback.
Also, the 'pending' task status just sits at the 'waiting' stage and does not go to 'pending' as I think it should.....
The task fails to run and the PXE boot attempt does not contact our Core to capture.
The reason I was trying to capture is to test and check the drivers so I can use HII. However the Provisioning / HII Task and a Capture Task both fail.
It was quite straight forward in SP2! :-(
instead of extracting the driver from one of your new system, did you try going out to the manufacturer and just download their supplied Win7 (x86) network driver. Might be possible that you are missing something.
What is the name of the nic card and the computer model of the new system?
Yes I first extracted from the system the driver(s) and related files. No joy. I then went to Lenovo website, downloaded and extracted. No joy.
I have added both those drivers via. the 'Manage the drivers in WinPE image'. Removed / redeployed the PXE Rep.
The Network card is an Intel 82579LM Gig
The system is a Lenovo T420s.
Did you have a look on intel website for your drivers ?
I don't know if it will work but you can try...
Go to lenovo site, search for your ThinkPad T420s
Download the 32-bit Network Driver. It should be:
Intel PRO/1000 LAN Adapter Software for 32-bit Windows
Launch the EXE to extract the drivers.
Point your WinPE to this folder PRO1000\Win32\NDIS62 and select the e1c6232 driver
I ran into the same issue a while back. I loaded the new drivers but didn't update the WinPE Image or redeploy the PXE Rep. Once I did that it seemed to fix the issue.
There's also the update script you can run.....