Sysprep may fail if mass storage drivers are not signed. This problem occurs even if the sysprep.inf file is configured with DriverSigningPolicy=Ignore. This is a known problem with some versions of LSI SAS drivers (1.30.02.00) used on IBM blades. The driver available from LSI's website is not correctly signed. The same version is available from IBM's website and is correctly signed. It can be downloaded from:
(Critical update) IBM and LSI Basic or Integrated RAID SAS driver v1.30.02.00 for Microsoft Windows Server 2008 and Windows Server 2003 - IBM BladeCenter and System x
Open C:\Windows\setupapi.log. Look for lines containing "An unsigned or incorrectly signed file":
|
[2009/10/21 10:52:43 1912.7 Driver Install] |
The preferred method is to obtain a signed driver. If a signed driver cannot be located, try configuring the local computer policy to allow unsigned drivers:
Restart the image capture.