Ah AH, encontrei, rapaz...
Tens que editar também o [OemBootFiles]...
Vê:
[MassStorageDrivers]
This section contains a list of small computer system interface (SCSI) drivers to be loaded by the Setup Loader and installed during text-mode Setup. If this section is missing or empty, Setup attempts to detect the SCSI devices on the computer and install the corresponding retail drivers.
mass_storage_driver_description
Value: Retail | OEM
Identifies the driver to be installed. mass_storage_driver_description must match one of the strings defined in the right-hand side of the [SCSI] section of TxtSetup.sif (for a retail driver) or TxtSetup.oem (for an OEM driver). You can specify multiple instances of mass_storage_driver_description.
Retail
Indicates that the driver is part of the retail Windows product.
OEM
Indicates that the driver is OEM-supplied. If the value is OEM, the driver must also be listed in the [OEMBootFiles] section of the Unattend.txt file.
E Depois:
[OEMBootFiles]
Specifies OEM-supplied boot files. This entry is valid only if OemPreinstall = Yes and the files listed here have been placed in the \$OEM$\Textmode folder of the OEM’s distribution share point.
This section is necessary if you are using ComputerType in either the [Unattended] or [MassStorageDrivers] sections of Unattend.txt.
HAL_file_name
Maps to a hardware abstraction layer (HAL) description that has been defined by the ComputerType entry in the [Unattended] section of the Unattend.txt file.
SCSI_driver_file_name
Maps to a mass-storage device driver description defined in the [MassStorageDrivers] section of the Unattend.txt file. There can be multiple instances of SCSI_driver_file_name listed in the [OEMBootFiles] section.
TxtSetup.oem
This file contains descriptions of all the OEM-supplied drivers listed in this section and includes instructions on how to install them. This file must exist if the Unattend.txt file contains an [OEMBootFiles] section.
If your mass-storage device is a Plug and Play device, verify that a Hardware Identification section and a reference to the catalog file for the driver (<Driver>.cat) exist in the Txtsetup.oem file.
If the Hardware Identification section does not exist, you must add [HardwareIds.scsi.yyyyy] to the Txtsetup.oem file and verify that the following information is included:
id = "xxxxx", "yyyyy"
where xxxxx represents the device ID, and yyyyy represents the service associated with the device.
Se tiveres mais dúvidas, post ou PM.
Este man pra Deployment é um espectáculo!...