Microsoft KB Archive/824891

= Vendor-Supplied Drivers That You Added to the ADS Deployment Agent Builder Service Repository Are Not Installed =

PSS ID Number: 824891

Article Last Modified on 12/18/2003

-

The information in this article applies to:


 * Microsoft Windows Server 2003, Datacenter Edition
 * Microsoft Windows Server 2003, Enterprise Edition

-



iBIG:10556



SYMPTOMS
When you add vendor-supplied drivers, such as Original Equipment Manufacturer (OEM) drivers or other third-party drivers, to the Automated Deployment Services (ADS) Deployment Agent Builder service repository, the vendor-supplied drivers may not be installed when you boot a device into the Deployment Agent (where device is a computer in the data center). This issue occurs even though you copied the vendor-supplied drivers to the correct location on the server that hosts the Deployment Agent Builder service and you stopped and then restarted the Deployment Agent Builder service.

Note This article refers only 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 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.



CAUSE
This issue occurs because the syntax of the vendor-supplied setup information file (.inf file) is not correct. Generally, this issue occurs with small computer system interface (SCSI) hard disk controllers and 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, network adapter, or other hardware device.

The Deployment Agent Builder service uses functionality that is similar to Setupapi 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 contains a syntax error. For example, the following excerpt from an .inf file contains a syntax error.

Note This example uses a sample vendor-supplied Oemsetup.inf file for an IBM ServeRAID-5i Controller. The .inf file that you use may have different values, but the syntax is basically the same.

[Manufacturer]

%IBM%=IBM,NTx86.5.2

The Model section in this sample Oemsetup.inf file contains the following value:

[IBM.NTx86.5.2]

In this example, the comma in the value &quot;IBM,NTx86.5.2&quot; in the [Manufacturer] section is incorrect. The Deployment Agent Builder service reads the [Manufacturer] section header, but the Deployment Agent Builder service cannot install the driver for the IBM ServeRAID-5i Controller in the Deployment Agent image.



RESOLUTION
To resolve this issue so that the Deployment Agent Builder service can correctly read the vendor-supplied .inf file, follow these steps:  Add all the vendor-supplied driver files. Even though some files, such as .cat files, are not processed, the .inf parsing may fail because a file may be missing. Therefore, add the .inf files, the .cat files, the .sys files, the Txtsetup.oem file, and so forth. Make the changes to the .inf file as specified.

Note Do not put any .pnf files in this folder. The builder service will compile the .inf files and build the .pnf files as needed. Use any text editor to open the vendor-supplied .inf file. (Typically, this file is Oemsetup.inf.) This file is located in the Deployment Agent Builder service repository on the computer that runs Network Boot Service (NBS). The location is:

\Program Files\Microsoft ADS\Nbs\Repository\User\PreSystem (or PostSystem)

 Locate and then change the following entry.

Note This step uses an example from the vendor-supplied Oemsetup.inf file for an IBM ServeRAID-5i Controller. The vendor-supplied .inf file that you use may have different values, but the syntax is basically the same.

Change the following lines from

[Manufacturer]

%IBM%=IBM,NTx86.5.2

to

[Manufacturer]

%IBM%=IBMNTx86.5.2

(Remove the comma between &quot;IBM&quot; and &quot;NT&quot;.) Change value in the associated Model section in the file so that the model value matches the [Manufacturer] section. To find the associated Model section, search for text that is similar to the text on the right side of the equal sign in the [Manufacturer] section (in this example, IBMNTx86.5.2). For example, change the following entry

[IBM.NTx86.5.2]

to

[IBMNTx86.5.2]

(Remove the period between &quot;IBM&quot; and &quot;NT&quot;.) Save the .inf file to the Deployment Agent Builder service repository. Restart the Deployment Agent Builder service.</li></ol>

Boot the device into the Deployment Agent (where device is the device that contains the hardware device that is associated with the vendor-supplied .inf file that you modified), and then view the Deployment Agent Builder service log to see if a driver for the hardware device has been installed.

For information about how to turn on Deployment Agent Builder service logging (if not already turned on), see ADS online Help.

<div class="moreinformation_section">

MORE INFORMATION
For additional information about ADS, visit the following Microsoft Web site:

http://www.microsoft.com/windowsserver2003/techinfo/overview/ads.mspx

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Keywords: kbADSv1 kbprb KB824891

Technology: kbWinServ2003Data kbWinServ2003DataSearch kbWinServ2003Ent kbWinServ2003EntSearch kbWinServ2003Search

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© 2004 Microsoft Corporation. All rights reserved.