That sounds like a basic network driver issue.
FWIW you can load drivers in WinPE using drvload and point to an INF file.
However, this just loads the driver. You still need to run wpeutil initializenetwork to tell WinPE to load the stack and grab an IP address from DHCP.
Once the wpeutil command runs, just type ipconfig /all and see if you pulled an IP address.
You can then add the drivers to your Landesk WinPE image.
I thought that too. I have tested this 2 different ways.
I have set the HP computer to "Legacy boot enabled, secure boot disabled" so that I can successful connect to the PXE server and load the boot.wim
When this fails to connect to the network, I cancel the command and use drvload to load one of the drivers that I have previously injected into LANDesk WinPE. The driver loads successfully. I use wpeutil /initializenetwork [driver] to load the stack. the computer does not get an IP and ipconfig does not list any network adapters.
In my Test 2:
I created a bootable USB driver from the winPE ISO i created on a windows 10 computer using Windows ADK. I performed the steps above, and the computer gets an IP address.
Go and get the Win8.1 32bit version of the drivers you need for those laptops, LD WinPE is based on Win8. Inject those drivers by going to OS Provisioning tool, "Manage drivers in WinPE Image", then redeploy pxe rep. Use legacy boot as uefi booting requires you using the 64bit WinPE and there's more steps to getting through that.
You're using an incorrect NIC driver. It may load but it's not correct for that version of WinPE.
Ironman said as much and sounds correct.
Are you positive you used 32bit Win10 NIC drivers?
Try downloading this file from hp and execute it with a "/?" switch and walk it through saving the files contained in the download. Go to where they are saved and add the one in the WIN10-32 folder to the winpe image. Redeploy pxe rep and test again.
The test #2 that you did appears to confirm that you have the correct driver for whatever version of WinPE you are using when built from the ADK and also that DHCP on that network is working with spare leases available etc.
To be certain of what version of WinPE you are loading, you can type "ver" from a command prompt in WinPE and also "SET" which will show you the variables for program files (x86) and programw6432 if WINPE 64 bit is loaded.
I did a quick internet search and apparently the following should work to set a static IP from within a command prompt in WinPE:
netsh int ipv4 set address "Ethernet0" static 10.10.10.2 255.255.255.0 10.10.10.1
The syntax for the IP info appears to be IP Address/Mask/Default Gateway.
If that doesn't work, it must be the driver and WINPE version combination.
For what it's worth, I have found the built in driver adding method to be clumsy and ineffective. Any time I'm adding new drivers to the boot wims, I mount them and inject the drivers with DISM. I get a lot better success rate in WinPE, especially with network and HID devices.
I ended up doing the same. Thanks for the info.