Troubleshooting administrator console issues

You can troubleshoot some common administrator console issues.

Enabling user interface debug logging

If you customized the configuration XML, but did not get the XML right, the actions in the user interface might not work properly.

Turn on debug logging on the admin console part of the custom action. Set the Debug Logging key, which is the DWORD value in the base registry key for the IBM Deployment Pack to a value of 1.

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 there was an error during importation, or for some reason the WMI information is incorrect, the MMC might hit an exception when trying to load the assembly, likely because the file name or assembly name is not found.

Check WMI under root\SMS_site_code\SMS_TaskSequenceStep\SMS_TaskSequenceAction for the appropriate WMI class for the product installed, such as: IBM_DeploymentPack.

If the desired class does not exist, the custom action cannot appear in the menu. Try reinstalling the site server files using the installer.

If you are already familiar with the contents of the WMI classes, you can modify the class as appropriate to correct the error. A good tool for viewing and editing WMI information is WMI CIM Studio, which is part of the Microsoft Download Center: WMI Administrative Tools.