Troubleshooting administrator console issues

Some common administrator console issues are presented here along with information about how to resolve them.

Enabling user interface debug logging

If you customized the configuration XML but the XML is not correct, the actions in the user interface might not work properly.

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

MMC crash, exception, or Property Not Found errors occur 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 occurred during importation, or for some reason the WMI information is incorrect, the MMC might generate 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: Lenovo_DeploymentPack.

If the desired class does not exist, the custom action cannot appear in the menu. Use the installer to reinstall the site server files to correct the problem.

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 WMI Administrative Tools.