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

7 Troubleshooting
Install fails immediately after a reboot
To resolve this issue, wait approximately 15 minutes, then retry.
Some drivers fail to be injected into the boot image
One of the reasons this might occur is when 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 your environment, remove the driver from
the boot image’s driver list and then manually re-inject the remaining drivers.
The Create HP ProLiant Deployment Task Sequence wizard listboxes are
empty
There are several possible causes:
• The logged in user doesn't have SCCM permissions to view the various required packages.
• On 2012.08.0, the logged in user doesn't have permission to enumerate the
HKLM\Software\Microsoft\ComponentStudio registry key.
To resolve this issue:
• Verify the user's SCCM privileges.
• Give the user Full Control to the HKLM\Software\Microsoft\ComponentStudio registry key.
The target server boots to WinPE but the task sequence doesn’t start
There are several possible causes:
• There is no network connection because the network adapter is unsupported
• There is no network connection because the boot image does not contain the necessary network
driver
• SCCM doesn’t recognize the target server
• One or more of the packages referenced by the task sequence are not available
To resolve this issue:
• Install a supported network adapter and set it as the PXE NIC.
• Use the appropriate HP ProLiant boot image.
• Ensure that the target server was imported with the correct identification information.
• Ensure that all referenced packages have been copied to a distribution point.
Updated or new hardware configuration input files were not used
To resolve this issue, update the HP ProLiant Hardware Configuration package to the appropriate
distribution points
Install fails immediately after a reboot 17