· Only Windows XP Professional, Windows XP Tablet Edition, and Windows Server 2003 are supported for this process.
· For a full explanation of the steps that MDT performs, see the Microsoft Support article, HOW TO: Create an Unattended Installation of Third-Party Mass Storage Drivers in Windows Server 2003.
· Files referenced in the TxtSetup.oem file that do not have the extensions .sys, .cat, or .inf are automatically copied to \$OEM$\$$\OEMDIR before calling Windows Setup (Winnt.exe), and then they are placed in the %WinDir%\System32 directory when the process is complete.
· By default, MDT skips installation of any integrated development environment storage drivers (devices with a PCI\CC_0101 Plug and Play ID), because these devices are covered by in-box drivers.
· MDT only injects drivers that have been imported into the Deployment Workbench.
· MDT injects only drivers that have matching devices on the local computer.
· If there is more than one matching driver for a computer, MDT injects both drivers on the local system. Unless identical, the *.sys, *.inf, and *.cat files must have globally unique file names (no other file with the same name can exist in any other package installed on the computer). The display name listed in the [scsi] section of TxtSetup.oem must be globally unique across each TxtSetup.oem file. A warning dialog box is displayed if duplicates are found.
· If driver packages conflict with other driver packages, typically the best thing to do is to identify the primary driver package, add it to a driver group, and add the group name to the StorageDriverGroup list item. Other storage drivers, not represented by groups defined in StorageDriverGroup, will not be installed.
· If the property list StorageDriverGroup is defined, only drivers associated with groups explicitly listed in this property are installed—for example:
· StorageDriverGroup001 = AccountingStorageDriverGroup
· StorageDriverGroup002 = SalesStorageDriverGroup