I'd like to start out by saying the InjectMSD tool for the HII process is stellar!! The worst part about creating a HII is having to rebuild it everytime I want to add new mass storage controllers. (Sweet work Jan). Instead of building the image on the latest model like I used to I decided to make a Base Golden Image in Vmware and take a snapshot prior to launching sysprep. Now anytime I want to create a new HII I just revert the snapshot make the changes, Sysprep it and then Capture the Image using OSD. Of the 30 Dell Models we have here they all use the Intel storage controllers so I build those into the Sysprep mass storage section and for any new models we are going to use InjectMSD. For my exsiting OSD prcoess I just edited the InjectMSD Script to not toss an error if no arguments were passed which allowed for this funcationality to be added for new models.
Here is the issue we are expereincing. I tried to take my HII and drop it on a base VMware machine. ( Just a bare metal machine PXE booting ) Of course it blue screened because I did not have the Mass storage drivers. I added those into the Drivers Folder and the machine booted up into the sysprep process although instead of just detecting the PNP Drivers was prompted to browse for the location of the VMWare SCSI Drivers(LSI Logic). The Input box was pre-populated with c:\sysprep\i386. Is this becauseI have it as my "InstalledFilesPath" in the sysprep file?? If I Enter C:\Drivers\MSD The process continues fine.
Is there a perticular reason why these MSD Drivers were not detected by PNP?
Below is the unattended peice of my Sysprep file. I am using LDPrep as stated in the HII Document which should replace the contents of the DriversPath key in the registry. I didn't think the OEMDriversPath section was needed? I thought all that did was populate the Driverspath section during sysprep.
Driversigningpolicy = Ignore
UpdateInstalledDrivers = Yes
InstallFilesPath = "C:\sysprep\i386"
;OemDriverPath = c:\drivers
Thanks in advance.