About two weeks ago (can't for the life of me figure out what changed to cause this), our HP ProBook 6460b laptops imaged with Windows 7 x64 Pro started failing to join the domain after OSD. All other machine models are working fine. I started looking closely at the setupact and setuperr logs and they basically say "Domain cannot be contacted". I've tried injecting several different drivers using HII and all have the same result.
After the image is laid down and HII injects drivers (correct drivers, I've double checked), the machine begins the Specialize pass. When it gets to "Setup is applying system settings", I Press Shift + F10 to open a CMD prompt and run devmgmt.msc. The Intel 82579LM Gig NIC is there, but states it cannot start. If I right click the computer name and kick off a "Scan for hardware changes", the NIC is all the sudden "found" as an Intel 82579V (what it actually is). The machine grabs an IP and adds to the domain with no issue.
Odd thing is, if I let the "Applying system settings" action time out and fail, the machine reboots and LOADS THE DRIVER CORRECTLY, finishing all its network-based installs. It just isn't installing the correct NIC during Specialize.
I've added this particular driver to the image, I've added/removed several different driver sets to the HII driver library. So far, none of these has fixed the issue. The 6460b does not install the NIC properly.
Has anyone else had issues like this? It's not 100% an HII issue as it is pulling an acceptable driver. Windows is just deciding to install the wrong hardware from the right driver during the Specialize pass.