The following sections provide information for installation
issues with the HP ProLiant Server OS Deployment Toolkit for
Microsoft System Center Configuration Manager 2007 kit:
Enabling UI debug logging
MMC Crash, Exception, or "Property Not Found" errors when
loading custom action
Enabling UI debug
If you customized the configuration XML and have an incorrect
XML, the actions in the UI might not work properly. Turning on
debug logging on the Admin UI part of the custom action might
resolve this issue. Logging is enabled by setting the Debug Logging
key (DWORD value in the base registry key for the OEM) to a value
of 1. For example, HKLM\SOFTWARE\Microsoft\SMS\Deployment\HP\ProLiant\Debug
Logging to 1. The debug log file is saved within the OEM
installation directory within the \AdminUI directory.
MMC Crash, Exception, or
"Property Not Found" errors when loading custom action
Configuration Manager uses information stored in WMI to load the
custom action assemblies from disk. This WMI information is
imported into the site system WMI database during installation
through the use of MOF files. If an error occurs during importation
or if the WMI information is incorrect, the MMC might encounter an
exception when attempting to load the assembly, because the file
name or assembly name is not found. Verify that the appropriate WMI
class HP_ProLiantDeployment exists under root\SMS_<SiteCode>\SMS_TaskSequenceStep\SMS_TaskSequenceAction.
If the class does not exist, the custom action does not appear
in the menu. Re-install the site server files using the installer.
WMI CIM Studio, a useful tool for viewing and editing WMI
information, is available from the Microsoft website.