The ADS Deployment Agent Builder Service does not correctly parse the latest .inf file formats

Article translations Article translations
Article ID: 830413 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

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.

CAUSE

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.

RESOLUTION

Hotfix information

A 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=support
Note 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.

Prerequisites

You must install this hotfix together with the hotfix that is described in Microsoft Knowledge Base article 829053 to resolve this problem.

Restart requirement

You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The 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

WORKAROUND

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:
  1. Use a text editor to open the vendor-supplied .inf file.

    Typically, this file is named Oemsetup.inf. The Oemsetup.inf file is located in the Deployment Agent Builder service repository on the computer that runs Network Boot Service. The location is:

    Drive:\Program Files\Microsoft ADS\Nbs\Repository\User\PreSystem (or PostSystem)
  2. Locate and then change the following text in the Oemsetup.inf file.

    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 similar.
    1. Locate the following text:
      [Manufacturer]
      %IBM%=IBM,NTx86.5.2
    2. Change the line to the following by removing the comma between "IBM" and "NT":
      [Manufacturer]
      %IBM%=IBMNTx86.5.2
  3. Change the value in the "Model" section that is associated with the value in the "Manufacturer" section of the file so that the model value matches the value in 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, search for IBMNTx86.5.2.
    1. In the "Model" section, locate the following text:
      [IBM.NTx86.5.2]
      
    2. Change the text to the following by removing the period between "IBM" and "NT":
      [IBMNTx86.5.2]
      
  4. Save the .inf file to the Deployment Agent Builder service repository.
  5. Restart the Deployment Agent Builder service, boot the device into the Deployment Agent, and then view the Deployment Agent Builder service log to see if a driver for the hardware device has been installed.

    In this step, device is the device that contains the hardware device that is associated with the vendor-supplied .inf file that you modified.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

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:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For additional information about Automated Deployment Services, visit the following Microsoft Web site:
http://www.microsoft.com/windowsserver2003/techinfo/overview/ads.mspx
For 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.

Properties

Article ID: 830413 - Last Review: November 15, 2007 - Revision: 6.8
APPLIES TO
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server Automated Deployment Services 1.0
  • Microsoft Windows Server Automated Deployment Services 1.1
Keywords: 
kbautohotfix kbhotfixserver kbwinservperf kbmgmtservices kbbug kbfix kbqfe kbwinserv2003presp1fix KB830413

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com