I've created a new task sequence, and with it a new boot image. I built the new task sequence to include drivers for a new computer model, and the new boot image because I wanted to migrate from using a 32-bit boot image to 64-bit (I've already switched from a mixed environment to all 64-bit Windows). On the new model, it all works. On the very first older model I decided to test, it fails miserably.
The system boots to boot media, deploys the OS, and installs drivers. After restarting, the NIC does not get a DHCP address. If I press F8 to open a command prompt, I can run ipconfig /all and see my NIC, so it looks like it's not a driver issue (Intel(R) Ethernet Connection I218-LM if it matters), but I don't have a valid IP address.
The new task sequence does include updated drivers for the new model - It's a Dell Latitude E7240. The previous task sequence included the A03 drivers. The new one includes the A05 drivers. I deploy the drivers using an Apply Driver Package step.
This is totally confusing me:
New boot media/boot image > New task sequence = FAIL
New boot media/boot image > Old task sequence = FAIL
Old boot media/boot image > New task sequence = FAIL
Old boot media/boot image > Old task sequence = SUCCESS
Could this be a driver issue? The above results shoot down every one of my theories. Any suggestions?