TechShizz

When using Windows Deployment Server to roll out a new OS, if the driver of the NIC is not in the standard install.wim the installation will fail with this error.

"WdsClient: An error occurred while obtaining an IP address from DHCP server. Please check to ensure that there is an operational DHCP server on this network segment".

WDS comes with the option to add Drivers to the WIM through the GUI but seems to fail for all 57 variants of the drivers.

Here are the steps to setup for and inject the drivers into the boot.wim file with DISM.

Preparation

1.       Create the following folders on the root of the C drive:

C:\Mount
C:\Mount\Drivers
C:\Mount\BootWIM

2.       Copy the drivers you wish to inject into the C:\Mount\Drivers folder

3.       NB; the drivers need to be the INF files and not the EXE’s..

      then copy your original boot.wim to the C:\Mount folder.

         Execution

1.       Open the Deployment and Imaging Tools Environment command prompt, from the Windows Kits start menu folder, as Administrator.

2.       Navigate to "C:\Mount".

3.       Use the following DISM commands to mount the Boot.wim:

DISM /Mount-Wim /WimFile:C:\Mount\boot.wim /Index:2 /MountDir:C:\Mount\BootWIM

4.       Use the following DISM command to add the driver:

DISM /Image:C:\Mount\BootWIM /Add-Driver /Driver:C:\Mount\Drivers /recurse

5.       Use the following DISM command to unmount the Boot.wim:

DISM /Unmount-Wim /MountDir:C:\Mount\BootWIM /Commit

Once this is done you can add the amended boot.wim to your Boot Images in WDS