Copy all of the appropriate files for a 32-bit or 64-bit Windows installation out of the version folders on the Tools and Drivers DVD to the appropriate folder structure on a network share.
Identify the appropriate version files.
The following examples are from the Tools and Drivers DVD. In the examples below, cdromdrive is the driver letter of the CD/DVD drive that contains the Tools and Drivers DVD:
Tools and Drivers DVD Windows Vista Ultimate 32-bit files:
cdromdrive:\drivers\windows\Chipset ...\SAS\driver\32bit ...\sata\32bit ...\TPM\driver\32bit ...\audio\Vista ...\nic\pro1000\win32
Tools and Drivers DVD Windows Vista Ultimate 64-bit files:
cdromdrive:\drivers\windows\Chipset ...\SAS\driver\64bit ...\sata\64bit ...\TPM\driver\64bit ...\audio\vista64 ...\nic\pro1000\winx64
Tools and Drivers DVD Windows Server 2008 32-bit files:
cdromdrive:\drivers\windows\Chipset ...\SAS\driver\32bit ...\sata\32bit ...\TPM\driver\32bit ...\nic\pro1000\win32
Tools and Drivers DVD Windows Server 2008 64-bit files:
cdromdrive:\drivers\windows\Chipset ...\SAS\driver\64bit ...\sata\64bit ...\TPM\driver\64bit ...\nic\pro1000\winx64
Copy the files identified in Step a out of their version folders and into the appropriate folder structure on your network share.
In the examples below, \\yourshare\share is the share path you have set up on the network, DriverPack\x64 is for 64-bit Windows, and DriverPack\x86 is for 32-bit Windows. All files must reside directly under the x64 or x86 folder or component subfolder (there should be no version subfolders as found on the Tools and Drivers DVD). See examples below:
Windows Vista Ultimate 32-bit WIM folder structure:
\\yourshare\share\DriverPack\x86\Chipset ...\SAS ...\sata ...\TPM ...\audio ...\nic
Windows Vista Ultimate 64-bit WIM folder structure:
\\yourshare\share\DriverPack\x64\Chipset ...\SAS ...\sata ...\TPM ...\audio ...\nic
Windows Server 2008 32-bit WIM folder structure:
\\yourshare\share\DriverPack\x86\Chipset ...\SAS ...\sata ...\TPM ...\nic
Windows Server 2008 64-bit WIM folder structure:
\\yourshare\share\DriverPack\x64\Chipset ...\SAS ...\sata ...\TPM ...\nic
Select the service image to update and export the image.
Mount the Windows image you just exported. For example,
imagex /mountrw C:\windows_distribution\sources\install.wim 1 C:\win_mount
The first Windows image in the Install.wim file is mounted to C:\wim_mount
Use Windows System Image Manager (Windows SIM, available in Windows AIK) to create an answer file that contains the paths to the device drivers that you intend to install. See the Microsoft documentation for the Windows Automated Installation Kit for the details of starting the Windows SIM application.
Add the Microsoft-Windows-PnpCustomizationsNonWinPE component to your answer file in the offlineServicing pass.
Expand the Microsoft-Windows-PnpCustomizationsNonWinPE node in the answer file. Right-click DevicePaths, and then select Insert New PathAndCredentials.
A new PathAndCredentials list item appears.
In the Microsoft-Windows-PnpCustomizationsNonWinPE component, specify the path to the architecture folder in the DriverPack folder on the network share, and the credentials used to access the network share.
For example, the path and credentials for a 64-bit image might be:
<Path>\\yourshare\share\DriverPack\x64</Path> <Credentials> <Domain>MyDomain</Domain> <Username>MyUserName</Username> <Password>MyPassword</Password> </Credentials>
Save the answer file and exit Windows SIM. The answer file must be similar to the following sample. The sample assumes the architecture is 64-bit (for the processorArchitecture component ID parameter, supported values are x86 for 32-bit Windows, or amd64 for 64-bit Windows).
<?xml version="1.0" ?> <unattend xmlns="urn:schemas-microsoft-com:asm.v3" xmlns:wcm= "http://schemas.microsoft.com/WMIConfig/2002/State"> <settings pass="offlineServicing"> <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"> <DriverPaths> <PathAndCredentials wcm:keyValue="1"> <Path>\\yourshare\share\DriverPack\x64</Path> <Credentials> <Domain>MyDomain</Domain> <Username>MyUserName</Username> <Password>MyPassword</Password> </Credentials> </PathAndCredentials> </DriverPaths> </component> </settings> </unattend>
Use Package Manager to apply the unattended installation answer file to the mounted Windows image. Specify a location for the log file to create. For more information about using Package Manager, see the Microsoft Windows AIK documentation. For example,
pkgmgr /o:"C:\wim_mount\;C:\wim_mount\Windows" /n:"C:\unattend.xml" /l:"C:\pkgmgrlogs\logfile.txt"
The .inf files referenced in the path in the answer file are added to the Windows image. A log file is created in the directory C:\Pkgmgrlogs\.
Review the contents of the %WINDIR%\Inf\ directory in the mounted Windows image to ensure that the .inf files were installed. Drivers added to the Windows image are named oem*.inf. This is to ensure unique naming for new drivers added to the computer. For example, the files MyDriver1.inf and MyDriver2.inf are renamed oem0.inf and oem1.inf.
Unmount the .wim file and commit the changes. For example:
imagex /unmount /commit C:\wim_mount
Replace the service image and enable the updated image, as follows:
If the Windows Deployment Services snap-in is not running, click Start, click Administrative Tools, and then click Windows Deployment Services.
Find the image to service. Right-click the image and then click Replace Image. Use the wizard to replace the service image with the Windows image that was updated.
Right-click the service image and then click Enable.
The service image is now available and all the workstation-specific drivers are added to the image.