1 of 1 people found this helpful
Have you reviewed the Hiiclient.log and dism.log to see which driver is being injected for your card. It is possible that you have one driver being applied from some other oem manufacturer that because it is a newer driver, it is seleected and does not work. The 82579LM is a very popular NIC and I have seen a lot of OEM drivers that don't work well. Try using the driver from Intel.
Thanks for the reply. I have checked them and it is pulling the appropriate driver. The issue is that within the driver INF there are references to both the 82579LM and 82579V NIC. When Windows attempts to load drivers at first startup, it tries to start the device as 82579LM and the device fails to start. It IS the correct driver INF, but fails to start the device. If I catch it in time, I can press Shift + F10 to open a CMD line and go into device manager, uninstall the NIC and let the system "reinstall" the device and it processes as 82579V and proceeds through as usual, getting an IP and joining the domain etc.
I'm looking forward to 9.5 SP1 and being able to assign specific drivers to specific hardware again, although I'm not sure if ti will fix this exact issue. It will, however, give me the ability to troubleshoot individual driver injection instead of toying with the whole library to get the right one added. That was a pain.