This content has been marked as final. Show 1 reply
To add additional drivers to your OSD setup, you have two options.
Insert the the driver files into the appropriate ZIP file's located in the source fileshare:
designates the relevant share for the operating system source files.
.zip designates the relevant zip file depending on the driver category.
According to Microsoft:
"Plug and Play device drivers that are not included on the Windows 2000 Professional operating system CD can easily be added by following the steps in this section. This method works for all Plug and Play device drivers. You can also use this method for updating drivers.
To add Plug and Play devices
In the \$OEM$ subfolder of the distribution folder, create a subfolder for any special Plug and Play drivers and their INF files, for example:
In the answer file, edit the [Unattend] key for Plug and Play, adding the path to the list of Plug and Play search drives, for example:
OEMPnPDriversPath = "PnPDrvrs"
To maintain the folders so that they can accommodate future device drivers, create subfolders for potential device drivers. By dividing the folders into subfolders, you can store device driver files by device type, rather than having all device driver files in one folder. Suggested subfolders types include Audio, Modem, Net, Print, Storage, Video, and Other. An Other folder can give you the flexibility to store new hardware devices that might not be currently known.
If the PnPDrvs folder contains the subfolders Audio, Modem, and Net, the answer file must contain the following line:
OEMPnPDriversPath = "PnPDrvs\Audio;PnPDrvs\Modem;PnPDrvs\Net"
Note The specified folder is created at the root of the system drive and remains there after setup is complete.
If you intend to use any updated drivers, you must first verify that they are properly signed. If they are not, those drivers might not be installed. To verify that drivers are properly signed, contact the vendor.
Driver Signing Policy
In the answer file, the DriverSigningPolicy key in the [Unattended] section specifies how nonsigned drivers are processed during installation.
Important Microsoft strongly advises against using DriverSigningPolicy = Ignore unless you have fully tested the device driver in your environment and are sure that it works properly. Using unsigned drivers increases the risk of device driver problems that can effect the performance or stability of your computer.
If you are using DriverSigningPolicy = Ignore and you attempt to install a newer, unsigned copy of a driver that is protected by Windows 2000 Professional, the policy level is automatically updated to Warn.
For more information about driver signing policy, see Unattend.doc in Support\Tools\Deploy.cab on the Windows 2000 Professional operating system CD."