there are several methods you can try to inject a network driver.
1. Install driver to the offline OS in Phase Post-OS "install"
check this link: Add and Remove Drivers Offline
2. You can modify your unattend.xml and define a local directory with all your necessary drivers:
check this link: Add Device Drivers During Windows Setup
3. you can use HII, if this doesnt work, check the HII log, there you should find some clues, why the injection didn't work.
4. if all these doesn't work, you also can inject your drivers into your install.wim or captured image. (This should be your wery worst case)
If your image makes it all the way to the System Configuration phase then we know that the NIC works (at least in WinPE). I assume that your prov. process makes it through the Pre-OS installation, OS Installation, and Post-OS Installation phases, correct? If so, there is absolutely no need to inject drivers into WinPE. Once the computer reboots into the Windows OOBE phase, WinPE is no longer being used.
The Intel 82579LM chip is pretty generic. Without even using HII, I'd be very surprised that a Win 7 64bit OS can't handle it .....with no driver update whatsoever.
So, if it's still not working then something is wrong with the image or something is wrong with HII. Assuming that the image is good, confirm the following:
1. You are adding 64bit Win 7 Drivers under HII driver management.
2. You are clicking the Built Library button in the HII Driver Management Toolset and receiving no errors.
3. The HII database located at ...LANDesk\ManagementSuite\landesk\files\drivers is updating after you Build the Library. Check the Data Modified of the file drivers.db3 on your core server. It should be the date and time that you clicked the Build Library button.
4. The drivers are located in this directory - LANDesk\ManagementSuite\landesk\files\drivers
5. The HII Action in your Post-OS Installation phase (before System Configuration) succeeds without failure.
If all of the above is correct, you're looking at a driver or image issue. Double check the drivers again (64bit Win 7) and update.
Exactly where does it fail? Does it make it all the way to the windows auto login? Or does it fail prior to that? Does it open the provisioning window after auto login?
I had a workaround. Apparently LDMS 2016.3 still can't assign drivers properly in HII. It downloaded multiple platforms of x86 and x64 drivers. I went in HII deleted everything except for Windows 7 x64. This sees to fix my issue.