This article was previously published under Q133385
This article has been archived. It is offered "as is" and will no longer be updated.
Because the Systems Management Server Executive is a wrapper containing theactual Systems Management Server services for many functions in the Site,they are run as threads and are, therefore, not subject to many of theconvenient Performance Monitor (PERFMON.EXE) features available to process-level statistics.
This article describes how to monitor each thread for certain counters andhow to isolate performance issues within the Executive.
To use Performance Monitor and the Windows NT Registry Editor to monitorand isolate Systems Management Server Executive performance issues tocertain threads:
WARNING: Using Registry Editor incorrectly can cause serious, system-wideproblems that may require you to reinstall Windows NT to correct them.Microsoft cannot guarantee that any problems resulting from the use ofRegistry Editor can be solved. Use this tool at your own risk.
Run Performance Monitor, and for the Object Thread, select %Processor Time, ID Thread, and all SMS_EXEC instances.
Monitor each thread's %Processor Time and identify the instance number in Performance Monitor for the thread that takes the most processor time.
Find the ID Thread item that has the same instance number as the thread you identified in step 2 and select this ID Thread with the mouse. Note that its Last and Average status indicators have the same value. This value is the decimal thread ID.
Convert the decimal thread ID to a hexadecimal (hex) number to get the Windows NT thread ID for that SMS Component thread of the Executive.
Start Registry Editor (REGEDT32.EXE).
From the HKEY_LOCAL_MACHINE subtree, go to the following subkey:
Compare the thread ID of each component to the hex number from step 4.
If they match, you have found the SMS Executive thread component responsible for the %Processor Time usage identified in Perfmon.
More Troubleshooting Tips
To watch each task the identified thread component performs and theassociated %Processer Time usage, use the SMSTrace tool and monitor thecomponent log file beside the Performance Monitor window. When the log filegoes idle, expect the %Processer Time usage of the component's thread to goidle also.
To learn about other statistics of the thread, look at additional counters,for example, %User Time, etc.