ConfigMgr 2007 Perf Threshold: MP Status Backlog > 10,000 over 3 hours Monitor

  • ID:  SMSv4_Perf_Threshold__MP_Status_Backlog__10000_over_3_hours_17_Rule.AdvancedAlertCriteriaMonitor
  • Description:   
  • Target:  ConfigMgr Server
  • Enabled:  Yes

Operational States

Name State Description
AlertLevelSuccess Success  
AlertLevelWarning Warning  
AlertLevelError Error  

Overridable Parameters

Parameter Name Default Value Description Override
ErrorThreshold 10000  
WarningThreshold 5000  

Alert Details

Monitor State Message Priority Severity Auto Resolution
  (Warning) ConfigMgr 2007 Perf Threshold: MP Status Backlog > 10,000 over 3 hours Medium Match Monitor Health Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The total number of queued management point status messages on the management point has exceeded the standard operational threshold. This condition will increase unless it is resolved. If the queued management point status message count keeps going beyond the threshold, the client status information in the Configuration Manager site database will not be accurate. For example, without accurate software distribution status you would not know which clients have received software packages or if any software installations have failed. You might also be unaware of problems with inventory or software metering.

Causes

The management point status messages can exceed the threshold because:

  • The SMS Agent Host service (CCMexec) is not running.

  • The management point status processing rate is slower than the incoming rate of status messages.

  • The management point has insufficient resources such as CPU, memory, or disk space.

Resolutions

To resolve this issue and lower the number of queued management point status messages:

  • Verify that the SMS Agent Host service (CCMexec) is running. If it is stopped, start it. If you encounter errors when starting it, make sure logging is enabled for the service and examine the CCMexec.log file.

  • Verify that the threshold for this alert is not too low and is beyond the standard operating threshold for this specific site.

  • Verify that the management point has sufficient resources. If necessary, add more memory or make more disk space available or do both. If the computer is too slow, upgrade to a more powerful processor or multiple processors.

  • Distribute software to collections with smaller membership. Software distribution creates a minimum of four status messages for each client, so distributing to smaller collections could vary the rate at which status messages are received.

External References

For more information about server sizing, see Planning and Deploying the Server Infrastructure for Configuration Manager 2007 at the Configuration Manager Product Documentation Web page.

For information about Configuration Manager Backup, see Planning for Backup and Recovery at the Configuration Manager Documentation Library Web page.

For more assistance, see a list of additional support options in the support section of Configuration Manager Web site at Support for Configuration Manager.

See Also for System Center Configuration Manager Management Pack


Downloads for System Center Configuration Manager Management Pack

AZURE OPTIMIZATION ASSESSMENT GET STARTED
MIGRATION TO AZURE GET STARTED
SYSTEM CENTER MIGRATION TO AZURE GET STARTED
MIGRATION TO AZURE FOR SQL AND WINDOWS 2008 GET STARTED