Skip Ribbon Commands
Skip to main content

Distribution

:

Infrastructure Configuration: Driver Repository

Documentation and logs for UVM OS and application distribution methodologies
Production "PnP" Drivers:
On the volume containing the BDD Distribution share, create a "Staging" directory.
 
Under "Staging", create a "Drivers" directory.  This will contain the following subfolders:
  • x86 (for 32-bit drivers)
  • x64 (for 64-bit drivers)

Each subfolder will contin the following structures:

  • Network:
    • [VendorFolder] (One for each NIC vendor)
  • Video
    • [VendorFolder] (One for each Video vendor)
  • Storage
    • [DriverFolder] (One for each Storage driver)
  • Other
    • [DriverFolder] (One for each additional driver)

When importing drivers into BDD, import all drivers in the root "Drivers" directory

When building a WinPE image, import only the "Network" directory.

Production XP "Mass Storage" Drivers:

Mass Storage drivers are staged in the same was as PnP drivers.  But in addition to importing these drivers into the BDD "Out of Box Drivers" using the GUI, these drivers also need to be copied into the \\[Server]\[DistributionShare]\$OEM$\Textmode directory.

Copy all driver files except for the txtsetup.oem file into the "Textmode" directory.  Merge the contents of the new driver's txtsetup.oem file into the txtsetup.oem in the "textmode" directory.

You will need to add information to the sysprep.inf file of any build that you wish to use this driver, and you will need to inject the drivers into the any image that you want to deploy using this sysprep.inf.  The format of the [SysprepMassStorage] section of the sysprep.inf is somewhat cryptic, but you should be able to derive the format of the "PCI\" segment of each driver entry by looking at the txtsetup.oem file for that driver.

You will need to add information to the unattend.txt file of any build that you wish to use this driver.  The operant sections are [MassStorageDrivers] and [OEMBootFiles].  [MassStorageDrivers] will contain a list of Driver labels from txtsetup.oem, and [OEMBootFiles] will contain a list of files located in the $OEM$\Textmode directory that are to be loaded at setup time.

Driver Archive:

On the volume containing the BDD Distribution share, create a "Archive" directory.

Under "Archive", create a "Drivers" directory.  This will contain the following subfolders:

  • x86 (for 32-bit drivers)
  • x64 (for 64-bit drivers)

Each subfolder will contin the following structures:

  • Network
  • Video
  • Storage
  • Other

Whenever an update to a driver in the production staging directory is performed, copy the replaced driver to the "archive" tree in a new subfolder structure with the following naming convention:
<INF_Name>
     <CreationDate in YYYY-MM-DD format>

For example, if you up update the B57.inf driver set from version 5.18.12.1 to 5.21.18.2, you would copy the replaced driver to:
<volume> -> Archive -> Drivers -> Network -> B57 -> 2005-08-12