HP ProLiant SCVMM 2012 Integration Kit (v 2013.02.0) User Guide

6 Troubleshooting
Deployment fails with a blue screen
When using a host profile that filters drivers matching PnP IDs, the target server might blue screen
during the first production boot.
To resolve this issue:
Use a host profile that filters driver matching the appropriate HP supplied tag, e.g.
hpproliant-ws2008r2-x64.
Deployment fails on some new servers under certain upgrade conditions
After upgrading from 2012.02.0 to 2012.06.0 and rebuilding the WinPE boot image using the
Microsoft Powershell script with a custom tag, some new servers are not supported
The additional WinPE tag specified during the 2012.02.0 install was not recorded and applied
to the new drivers, so those drivers were not selected by the Powershell script.
To resolve this issue:
1. Apply your tag to the elxfc, hpsa2, ixn62x64, and ql40xx drivers either in the console or in
the Powershell command prompt.
2. In the HKLM\SOFTWARE\Microsoft\Microsoft System Center Virtual Machine Manager
Administrator Console\HP\ProLiant registry key, create a string value of UserWinPETag =
your tag.
Unable to uninstall kit in certain HA configuration situations
When the kit is installed on the primary node, the uninstaller is added to its Program and Features.
There is nothing installed on the secondary node. If the primary node fails and has to be rebuilt,
it will be missing that entry and the secondary node won't have it.
To resolve this issue:
1. Reinstall the kit on the secondary node. The drivers will be reinstalled and the uninstaller will
be added to Program and Features.
2. Execute the uninstaller.
Deployment fails with a blue screen 11