Add Drivers to ADS

  • Article
Cc526832.chm_head_left(en-us,TechNet.10).gif Cc526832.chm_head_middle(en-us,TechNet.10).gif Cc526832.chm_head_right(en-us,TechNet.10).gif

Add Drivers to ADS

The ADS Deployment Agent Builder system repository is populated with device drivers-.inf and .sys files- from the Windows Server CD and the Automated Deployment System (ADS) CD. However, OEMs and independent hardware vendors periodically release software to customers that is not included in Windows-for example, a third-party redundant array of independent disks (RAID) controller driver. You can supplement the system repository with this software not included on the Windows CD so that the Deployment Agent Builder service produces Deployment Agent images that support the additional hardware. Administrators should not modify the repository. Instead, they should copy the drivers to one of the following directories in the repository:

  • systemdrive\Program Files\Microsoft ADS\nbs\repository\User\PreSystem
  • systemdrive\Program Files\Microsoft ADS\nbs\repository\User\PostSystem

Adding drivers this way enables a system to boot properly to the Deployment Agent. The Sysprep image that you deploy must also contain the same drivers. Be sure to capture a master image that contains the required drivers for the device hardware.

As new Windows service packs are released, you can update the systemdrive\Program Files\Microsoft ADS\WindowsCD\i386 directory, which ensures that the Deployment Agent Builder service creates Deployment Agent images using the latest drivers.

Note

Some administrators have succeeded in creating or updating images that work across multiple hardware configurations that use the same hardware abstraction layer (HAL). However, this is a complex task that, among other things, requires modifying .inf files with the correct Plug and Play ID values. If this is the case, you may want to contact a product support specialist for assistance or consult the Microsoft Knowledge Base.

Cc526832.arrowblueright(en-us,TechNet.10).gif Troubleshooting installation of vendor-supplied drivers
If vendor-supplied drivers are not being installed when a device is booted to the Deployment Agent, review Microsoft Knowledge Base Article 82905:Vendor-supplied drivers that you add to the ADS Deployment Agent Builder service repository are not installed.
Cc526832.arrowblueright(en-us,TechNet.10).gif More about the Deployment Agent Builder service and drivers

The Deployment Agent Builder service searches the \PreSystem directory before searching the system repository, and it searches the \PostSystem directory after searching the system repository.

The Deployment Agent Builder service uses the first .inf file or device driver it finds that is appropriate for the hardware. Therefore, if you add an .inf file or device driver to the \PreSystem directory, the Deployment Agent Builder service will use that .inf file or device driver instead of the one provided with Windows Server 2003, Enterprise Edition. The \PostSystem directory is typically used for .inf files and device drivers that should be applied after the Windows files have been added to the Deployment Agent image.

See the online ADS documentation topic Deployment Agent Builder service for more information.