Article ID: 830413 - View products that this article applies to.
When you add OEM drivers or other third-party drivers to the Microsoft Windows Server Automated Deployment Services (ADS) Deployment Agent Builder service repository, these vendor-supplied drivers may not be installed when the computer is booted into the Deployment Agent. This problem occurs even when you copy the vendor-supplied drivers to the correct location on the server that hosts the Deployment Agent Builder service, and you stop and restart the Deployment Agent Builder service.
Note This article only refers to hardware device drivers that are to be used under the Deployment Agent. For information about how to add drivers to your ADS images, see the Windows System Preparation Tool (Sysprep) documentation in the appropriate Microsoft Windows Resource Kit. For example, if you are deploying ADS images of Windows 2000, see the Microsoft Windows 2000 Server Resource Kit.
This problem occurs because the vendor-supplied setup information file (.inf file) is not parsed correctly. Generally, this issue occurs with small computer system interface (SCSI) hard disk controllers and with network adapters because a hard disk controller and a network adapter are required for the device to function in the Deployment Agent. An .inf file is used to install the driver for the SCSI hard disk controller, the network adapter, or other hardware device.
The Deployment Agent Builder service uses functionality that is similar to the functionality that is used by the Setupapi.dll file to install the hardware devices that are identified when the Deployment Agent image is being constructed. However, the Deployment Agent Builder service does not correctly read the vendor-supplied .inf file if the header of the file is not parsed correctly.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=supportNote The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesYou must install this hotfix together with the hotfix that is described in Microsoft Knowledge Base article 829053 to resolve this problem.
Restart requirementYou do not have to restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Date Time Version Size File name -------------------------------------------------------- 15-Dec-2003 16:01 5.2.3571.1001 113,152 Adsbuild.dll 15-Dec-2003 16:01 5.2.3571.1001 107,520 Wsocore.dll 15-Dec-2003 16:01 419 Nbsos.inf 15-Dec-2003 16:01 11,513 Ntbm.inf
You do not have to use this workaround if the hotfix that is described in the "Resolution" section is installed together with the hotfix from Microsoft Knowledge Base Article 829053. To work around this problem so that the Deployment Agent Builder service can correctly parse the vendor-supplied .inf file, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the terms that are used to describe software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684For additional information about Automated Deployment Services, visit the following Microsoft Web site:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
http://www.microsoft.com/windowsserver2003/techinfo/overview/ads.mspxFor information about how to turn on Deployment Agent Builder service logging if it is not already turned on, see Automated Deployment Services Help.
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Article ID: 830413 - Last Review: November 15, 2007 - Revision: 6.8