When you run Sysprep on one platform and deploy the image to another platform, you would ordinarily expect Plug-and-Play to handle any hardware differences (assuming that the machines use the same version of Ntoskrnl.exe and Hal.dll). However, mass storage drivers represent a special case. The boot loader needs to load the mass storage devices prior to initializing the operating system, so there's no opportunity to let the Plug-and-Play Manager shuffle around drivers. For this reason, it's fairly common to get a "0x0000007b bugcheck" error following the deployment of a Sysprep image to a machine from a different vendor, or different models from the same vendor, even though you're using what appears to be a generic Integrated Drive Electronics (IDE) controller in both cases.
Ghost version 11.0.2.1573 Hardware: any
[Sysprep] BuildMassStorageSection=yes [SysprepMassStorage]
There will be no other graphical indication that the process has succeeded.
This is for those customers with the 11.0.2.1573 version of Ghost as there was no built in functionality for deploying image across various HALs. The one issue this method does not rectify is when the machine boots up for the first time, there will be no third party drivers loaded up. That can be handled by:
Unattended] DriverSigningPolicy=Ignore UpdateInstalledDrivers=Yes OemPNPDriversPath=drivers\hardware_cat\driver_dir\driver_inf;(repeat); [SysPrep] BuildMassStorageSection=Yes SysprepMassStorage]
In each of those folders, the specific driver bundles are placed with their driver inf files.
The last part would include the name of the .inf file.