HP ProLiant SCCM 2012 Integration Kit (v 2014.02.0) User Guide

7 Troubleshooting
Some drivers fail to be injected into the boot image
One of the reasons this might occur is that a driver is signed with a newer driver signing method
than what DISM and the operating system support. In that case, the driver is treated as an unsigned
driver and is not injected into the boot image. For example, when running SCCM 2012 SP1 on
Windows Server 2008 R2, some Windows Server 2012 drivers cannot be injected into an x64
boot image. If the driver in question is not required for the environment, remove the driver from
the boot image’s driver list and then retry updating the boot image to the distribution point.
Reinstall, upgrade, or uninstall fails
Some possible causes are:
• A driver package's data source folder has been deleted, but the driver package still exists in
the console.
• One of the data source folders is locked.
To resolve this issue:
• Manually delete the driver package in the console.
• Reboot the server to remove the lock on the folder.
14 Troubleshooting