The processor utilization for the SMS Executive service has increased to 95 percent over three hours. This condition will increase unless it is resolved or until the amount of activity on the computer decreases. If this threshold is consistently exceeded, performance will suffer.
The percent processor time can exceed the threshold because of insufficient processing capacity for the current load.
To resolve this issue and lower the percentage of page file utilization:
Add an additional processor.
Upgrade to a faster processor.
Reduce the load on the SMS Executive service by moving processes to another computer. Offload server roles like distribution points, client access points and management points to dedicated servers.
For more information about Microsoft Windows operating system performance:
See the Microsoft Windows 2000 Server Product Documentation Web page for Windows 2000 Server.
See the Microsoft Windows Server 2003 Product Documentation Web page.
For additional information about SMS performance:
See Scenarios and Procedures for Microsoft Systems Management Server 2003: Maintenance, Backup and Recovery at the Systems Management Server 2003 Product Documentation Web page.
See Scenarios and Procedures for Microsoft Systems Management Server 2003: Planning and Deployment at the Systems Management Server 2003 Product Documentation Web page.
For more assistance, a list of additional support options is available in the support section of the SMS Web site at Support for Systems Management Server.
If this alert is generating too many false positives, you can modify the threshold tab of the rule properties to designate values more appropriate for your environment.
% Processor Time is the percentage of elapsed time that all of the threads of this process used the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code that is executed to handle some hardware interrupts and trap conditions is included in this count. On multi-processor machines the maximum value of the counter is 100 percent times the number of processors.
This alert is best handled by SMS administrators.
| Target | Microsoft.SMS.2003.SMS_Server_Class | ||
| Parent Monitor | Performance | ||
| Category | StateCollection | ||
| Enabled | False | ||
| Alert Generate | True | ||
| Alert Severity | MatchMonitorHealth | ||
| Alert Priority | Normal | ||
| Alert Auto Resolve | True | ||
| Monitor Type | System.Mom.BackwardCompatibility.PerformanceThreshold.ThreeStateMonitorType | ||
| Remotable | True | ||
| Accessibility | Internal | ||
| Alert Message |
| ||
| RunAs | Default | ||
| Comment | Mom2005ID='{23077531-5CDF-4D35-8D85-3C84F65401C8}' |
Home
ENU <UnitMonitor ID="SMS_2003_Perf_Threshold__Process_____Processor_time__smsexec___95_over_3_hours_19_Rule.AdvancedAlertCriteriaMonitor" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.PerformanceThreshold.ThreeStateMonitorType" Accessibility="Internal" Target="Microsoft.SMS.2003.SMS_Server_Class" Enabled="false" ParentMonitorID="Performance" Comment="Mom2005ID='{23077531-5CDF-4D35-8D85-3C84F65401C8}'">
<Category>StateCollection</Category>
<AlertSettings AlertMessage="SMS_2003_Perf_Threshold__Process_____Processor_time__smsexec___95_over_3_hours_19_Rule.AdvancedAlertCriteriaMonitor.StringResource">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>MatchMonitorHealth</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/Name$</AlertParameter1>
<AlertParameter2>$Data/Context/Description$</AlertParameter2>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState HealthState="Success" MonitorTypeStateID="Success" ID="AlertLevelSuccess"/>
<OperationalState HealthState="Warning" MonitorTypeStateID="Warning" ID="AlertLevelWarning"/>
<OperationalState HealthState="Error" MonitorTypeStateID="Error" ID="AlertLevelError"/>
</OperationalStates>
<Configuration>
<ServerRole>SMS Server</ServerRole>
<Component>Performance</Component>
<ServerRoleInstance>$Target/Property[Type="Microsoft.SMS.2003.SMS_Server_Class"]/Name_1$</ServerRoleInstance>
<RuleId>$MPElement[Name="SMS_2003_Perf_Threshold__Process_____Processor_time__smsexec___95_over_3_hours_19_Rule"]$</RuleId>
<ErrorThreshold>95</ErrorThreshold>
<ErrorOperator>Greater</ErrorOperator>
<WarningThreshold>85</WarningThreshold>
<WarningOperator>Greater</WarningOperator>
</Configuration>
</UnitMonitor>