Windows Deployment Services–adding drivers to boot.wim

Currently I’m in a project where I have do a windows 7 operating system provisioning for a customer of mine. I’ve been gone all down the way starting with NT3.51, then NT4, then Win2000, then WinXP, Vista and now Win7 provisioning. I must say, Microsoft did a good job with the latest deployment mechanism.. Logo_winlogo

So this part is dedicated to one thing: Adding (OEM, but not only) Network Drivers to a boot.wim to successfully boot Windows PE, mount the Network Card and connect to a Windows Deployment Server (WDS).

I started building the base Windows 7 Image using vSphere and Virtual Machines. Then I tried to apply the image to a HP Compaq Elite 8100 Small Form Factor Machine and got this error message:

WDS_WinPE_WdsClient_An_Error_occured_while_starting_networking

WdsClient: An error occurred while starting networking: a matching network card driver was not found in this image. Please have your Administrator add the network driver for this machine to the Windows PE image on the Windows Deployment Services server.

Ok, the Administrator – that’s me .. so I was reading thru Technet and found (among thousand of other posts and articles) this article

as a resume – open WAIK Command Prompt  (assuming latest MDT2010 and WAIK is installed)

--- optional part ---
D:\RemoteInstall\Boot\x86\Images>dism /cleanup-wim

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Scanning drive C for stale files
Scanning drive D for stale files
The operation completed successfully.

--- mount the image ---

D:\RemoteInstall\Boot\x86\Images>dism /mount-wim /wimfile:d:\RemoteInstall\Boot\x86\Images\boot.wim /index:2 /mountdir:d:\mount

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Mounting image
[==========================100.0%==========================]
The operation completed successfully.


--- inject/add the desired/necessary drivers to the boot.wim ---
D:\RemoteInstall\Boot\x86\Images>dism /image:d:\mount /add-driver:"\\vmd.local\dfs\IT\DistributionSharePoint\Drivers\hp\8100SFF\NET\sp51785" /recurse

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image Version: 6.1.7601.17514

Searching for driver packages to install...
Found 9 driver package(s) to install.
Installing 1 of 9 - \\vmd.local\dfs\IT\DistributionSharePoint\Drivers\hp\8100SFF\NET\sp51785\e1e6232.INF: The driver package was successfully installed.
Installing 2 of 9 - \\vmd.local\dfs\IT\DistributionSharePoint\Drivers\hp\8100SFF\NET\sp51785\E1K6232.INF: The driver package was successfully installed.
Installing 3 of 9 - \\vmd.local\dfs\IT\DistributionSharePoint\Drivers\hp\8100SFF\NET\sp51785\E1Q6232.inf: The driver package was successfully installed.
Installing 4 of 9 - \\vmd.local\dfs\IT\DistributionSharePoint\Drivers\hp\8100SFF\NET\sp51785\e1r6232.inf: The driver package was successfully installed.
Installing 5 of 9 - \\vmd.local\dfs\IT\DistributionSharePoint\Drivers\hp\8100SFF\NET\sp51785\e1y6232.INF: The driver package was successfully installed.
Installing 6 of 9 - \\vmd.local\dfs\IT\DistributionSharePoint\Drivers\hp\8100SFF\NET\sp51785\Install\DRIVERS\ANSM2KXP.INF: The driver package was successfully installed.
Installing 7 of 9 - \\vmd.local\dfs\IT\DistributionSharePoint\Drivers\hp\8100SFF\NET\sp51785\Install\DRIVERS\ansmw60.inf: The driver package was successfully installed.
Installing 8 of 9 - \\vmd.local\dfs\IT\DistributionSharePoint\Drivers\hp\8100SFF\NET\sp51785\Install\DRIVERS\ANSP2KXP.INF: The driver package was successfully installed.
Installing 9 of 9 - \\vmd.local\dfs\IT\DistributionSharePoint\Drivers\hp\8100SFF\NET\sp51785\Install\DRIVERS\anspw60.inf: The driver package was successfully installed.
The operation completed successfully.

--- unmount the boot.wim and commit changes ---

D:\RemoteInstall\Boot\x86\Images>dism /unmount-wim /mountdir:d:\mount /commit

Deployment Image Servicing and Management tool
Version: 6.1.7600.16385

Image File : d:\RemoteInstall\Boot\x86\Images\boot.wim
Image Index : 2
Saving image
[==========================100.0%==========================]
Unmounting image
[==========================100.0%==========================]
The operation completed successfully.

--- open explorer ... ---
D:\RemoteInstall\Boot\x86\Images>start.

Now I usually restart the WDS Service (I don’t know if this is really necessary) and then reboot the client.

Links

 

CommandLine in Unattended.xml

Sample Unattend Files

Automating the Domain Join

Add and Remove Drivers Offline

TimeZone specifies the time zone of the computer.

Windows Deployment Services Getting Started Guide

Add Device Drivers by Using Windows Setup

How to Modify the BCD Store Using Bcdedit

Microsoft Deployment Toolkit (MDT) 2010 Update 1

Automated Installation to Upgrade to Windows 7: Step-by-Step Guide

Managing and Deploying Driver Packages

Deploying Windows 7 Using Windows Deployment Services (WDS): Step-by-Step – Part I

3 thoughts on “Windows Deployment Services–adding drivers to boot.wim

  1. SmartDeploy will integrate with WDS, and handle driver management for you both in the WinPE environment, and in the deployed images. Saves lots of time if you have to manage a wide variety of hardware types.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>