Windows Deployment Services: Boot.wim fails to Load Network Card Driver, Even After the Drive has been injected.

Foreward:  Credit to this solution goes to Braxus on This Site, I just wanted to repost as I don't want to forget this and think it should be posted various places!
_________________________________________________________________________________

Windows Deployment Services - Boot.wim fails to load Network (NIC) Card driver, even though it was injected into the boot.wim file without any issues...

Scenario:

You've injected your Network Card Drivers into your boot.wim  You've done everything right or so you thought.  Correct NIC drivers are been injected into your wim file, PXE boot gets and IP and you successfully get to the Windows Deployment Boot options menu, however, once Windows Setup starts you see this:

wdsclient an error occurred while obtaining an ip address from the dhcp server

You probably got to the point where you recreated the boot.wim file from scratch, and searched the web for hours looking for alternative drivers.

Quick side note:  This issue effected my Dell Optiplex 7060's that have Intel 1219-LM Cards, using the driver set E1D65X64

The solution to this issue, in the end, a simple fix that only takes a few minutes.

1. Launch the Deployment and Imaging command prompt, and execute the following command (replace my info with yours)

Command:

dism /get-wiminfo /wimfile:"E:\Operating Systems\Wim Images\Windows 10\171134\boot.wim"

Here is the result in my case:

Notice that the boot.wim file has 2 Indexes, and not just one.  In the past I have always mounted Index:1 as I understood it to be the "default" index using by WDS, however the is apparently not always the case...

At the point you've probably figured out the fix, simply go back and mount your boot.wim again, using (in my case) Index 2:

2. Run the DISM mount command:

DISM /Mount-Wim /WimFile:"E:\Operating Systems\Wim Images\Windows 10\171134\boot.wim" /Index:2 /MountDir:"E:\Operating Systems\Mount_Folder\Mount\171134"

Note:  I have seen reports online of boot.wim files have more than two indexes, if this is your case, I would mount each index number that you have and save the boot.wim again with the /commit argument.

3. Inject the drivers into this index:

Command:

DISM /Image:"E:\Operating Systems\Mount_Folder\Mount\171134" /Add-Driver /Driver:"E:\Operating Systems\Drivers\Windows 10\Dell Optiplex 7060\Extracted for Image Injection\Intel_12xx-825xx-Gigabit_Ethernet\production\Windows10-x64" /recurse

4. Commit Changes:

Command:

DISM /Unmount-Wim /MountDir:"E:\Operating Systems\Mount_Folder\Mount\171134" /Commit

5: Repeat if your boot.wim contains more Indexes.

6. Add updated boot.wim to WDS via the WDS Console

7. Boot up your client computer and see what happens, in my case:

(WDS Boot Menu)

Now Connected to WDS Server and Ready to Image!