"Probably". There's a bunch of "special needs" hardware boxes out there, who need to have their drivers baked in hard into the WIM(s) to behave sensibly.
If you could get an actual IP (even not DHCP'ed) it would be a 169.x.x.x of some sort ... so ... odd.
You can try shoving the driver into the WIM & see if that helps you.
Listing the hardware / model type may have other folks go "Aha - I had the same thing" (hopefully) and give you their information. on how they handled it.
You may run into similar problems around USB3 potentially as well (again - down to the hardware / model).
It's one of those wonderful "misbehaving hardware model" shenanigans that ends up needing to be worked around.
It's a Dell Optiplex 5040
I concur with Phoffmann, you may want to bake in into the WIM. Check this How To Mount Modify and Unmount a (.WIM) Image to Add, Edit, and Delete Files/Folders by ImageX - YouTube It sounds like you need to update your Manage WinPE drivers as well. If you are on 9.6, you will need to include Win7 & Win8 NIC drivers for the models you need. For 2016, you will need to also include Win10 NIC drivers.
I used LANDesk to put in network drivers for this pc model... I tried many (Win 10, Win 7, Win Vista, Win PE specific), and every time I get nothing. The computer is acting as if there is no network card whatsoever... ipconfig comes up blank, and ipconfig /renew comes back with "no adapter is in a state permissible...". I can see it successfully loading the network drivers that I am loading in to the boot.wim image, but it still acts like there is no NIC.
What is the model who are trying to add? I have also experienced the hardship of finding that right driver, try the Intel 218-LM NIC and Intel 219-LM NIC
The network device according to the data sheet for the dell optiplex 5040 is an Intel i219-V Ethernet LAN 10/100/1000. I went to Intel's website and downloaded the WinPE driver for it, and still nothing.
Wanted to add to what the others have recommended.
When I have had stubborn models that didn't take the driver in the wim, rather than:
- Adding new driver to wim
- Redeploying pxe
- re-pxe booting
I find it easier (provided you're at the box) to load the drivers onto a usb stick and use this docs instructions to try a driver manually and verify it works.
As far as getting hold of a driver for the device, I've got a couple thoughts.
If you have another model of this device already setup, try booting it into Windows and extract the NIC driver it is using, so you can go try it in winpe as outlined above.
My recommended method for extracting the driver is a 3rd party tool called Double Driver.
It is portable, so you can download the zip and run it without installing.
Choose to backup the nic driver into a structured folder and then take the folder, go try it in winpe.
If you have a device setup but missing the nic driver, you can go manually look up the hardware id of the NIC and then search that hardware id online to find a matching device.
I also wanted to add that I worked with one device a while back that also would not take any windows driver I could find for it... until I found one labeled by the vendor as applicable for 'Windows Blue'... that one worked. No clue why.
Thanks for the info. Unfortunately we are not getting an error when loading the drivers... the network driver loads just fine, the computer just never gets an IP address after that. I suspect we might have better luck if we were to use the 64 bit boot.wim, but I can't figure out how to make winpe use the 64 bit version... it always uses the 32 bit version even on 64 bit machines. But I will make a new topic for that question.
1 of 1 people found this helpful
@ DuboisKing You need to apply the WinPE drivers from Dell to the boot.wim .
For Landesk version 9.6 : http://en.community.dell.com/techcenter/enterprise-client/w/wiki/5029.winpe-5-0-driver-cab
For Landesk version 2016: http://en.community.dell.com/techcenter/enterprise-client/w/wiki/11530.winpe-10-driver-pack
For the computer to boot in 64bit, you need to either schedule a template for this computer or boot from USB
Thank you! It's finally getting an IP! This has been an issue for weeks for me, and we have had to build several machines by hand because we couldn't get this to work. Thank you so much!