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

  • ID:  SMSv4_Perf_Threshold__MP_FileCollection_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 FileCollection Backlog > 10,000 over 3 hours Medium Match Monitor Health Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary

The total number of collected files queued on the management point has exceeded the standard operational threshold. This condition increases unless it is resolved. If the queued management point file collection count continues beyond the threshold, the files stored on the management point do not reflect the current files on the client computer.

Causes

The collected files can exceed the threshold because:

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

  • The management point file processing rate is slower than the incoming rate of files.

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

  • The software inventory rules have been modified to collect large files or a large number of files, and the resulting larger inventory file requires increased processing time.

  • The file collection properties of the software inventory client agent have been modified to collect files that change frequently. Software inventory collects a file only if it has been modified since the last software inventory collection. Files that change frequently can be collected during every software inventory cycle.

Resolutions

To resolve this issue and decrease the number of queued files:

  • 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 Configuration Manager site.

  • Determine whether the increased load is due to an infrequent influx of newly collected files, or whether the file load remains relatively constant. If the load is constant, update the Configuration Manager infrastructure to achieve zero processing backlogs. If the load is due to a large number of newly collected files, the issue can resolve itself if there are sufficient resources to process pending collected files in addition to the standard load.

  • Adjust the frequency of inventory collection to allow for a longer interval for files to be processed.

  • Modify the software inventory client agent file collection properties to collect smaller files or fewer files.

  • Modify the software inventory rules to collect files that do not change frequently.

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 more assistance, see a list of additional support options in the support section of the Configuration Manager Web site at Support for Configuration Manager 2007.

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