File renaming

Some driver vendors supply files that are named differently, depending on the operating system they apply to (for example, driver_w2k.sys, driver_w2k3.sys, and driver_w2k3_64.sys apply to Windows® 2000, Windows Server® 2003, and Windows Server 2003 x64 Edition). The installation program renames the files to its base names before installing the driver, such as renaming to driver.sys.. If the installation program renames files prior to installation, then the driver injection into the WinPE image fails, because the correct file names are not present.

Modifying a boot image

During the installation of the deployment kit, you might have to modify WinPE boot image to insert drivers and other changes, which enable the OEM toolkit utilities to function. By default, the installation program makes a copy of the Configuration Manager default boot image (boot.wim) and then mounts the file, makes changes, and then unmounts the file.

The modified boot.wim file contains the base set of changes needed by the toolkit. Network and storage drivers must be added so that boot devices (such as array controllers) function and that the machine has the appropriate network drivers to communicate with the network in WinPE. These drivers must be added through the driver catalog within the OS Deployment node of the Configuration Manager Administrator Console. HP has integrated drivers from the latest SmartStart Scripting Toolkit into the HP ProLiant Server OS Deployment kit. However, drivers required for newer ProLiant servers must be added manually to ensure access to the newer devices. For latest supported SmartStart Toolkit version, see the HP Server Integrations with Microsoft System Center Products Support Matrix.

Configuration Manager stores two boot images that help to distribute for machines booting to PXE. The boot.wim file is the base boot image, which contains no Configuration Manager specific files. When you add drivers to a boot image and then update the boot image on a distribution point, Configuration Manager takes the base boot.wim file. Configuration Manager then adds the drivers from the driver catalog, along with other Configuration Manager files, and creates a new WIM file, named boot.<packageID>.wim. For example, boot.SMS00001.wim, this new WIM file is then distributed to the assigned PXE distribution points for your site.

Drivers import, but fail when updating the WinPE boot image

Drivers might be loaded together in a common directory and contain a TXTSETUP.OEM file. This can also occur with only one driver in a directory. By default, Configuration Manager chooses the TXTSETUP.OEM file for its source of import information for the drivers and, if this file is present, does not display any associated INF files. This might cause issues, so load the drivers individually, using their own respective INF files. To prevent issues, rename any TXTSETUP.OEM files in the driver directory so that you can select the INF files and import the drivers individually.