Everyone knows that performing SCCM maintenance frequently is the key to a healthy SCCM experience. A lot of authors refer to tuning up the SCCM maintenance within the SCCM console but I am referring here about the cleanup we oversight with our day to day creation of collections and applications that is needed. If ignored, over time you will notice that these stale objects accumulate and use valuable refresh and evaluation cycles that could have improved the overall system performance.

I definitely say hats off to all the administrators out there that have done it meticulously and categorized their collections over the years. Organizing collections and applications is the first step to knowing what each of these objects represents and their purpose but when you have too many administrators, this process may fall short. I have gone ahead and created 2 separate reports which permit the administrators to cleanup using a single pane of glass for analyzing the data which are:

1. SCCM applications with 0 Deployments Report

The SCCM applications with 0 Deployments Report can be downloaded here.

The report fields include:

  1. Application Name
  2. Author
  3. Date last madified
  4. Age of application
  5. If currently enabled
  6. Number of DT
  7. Number of Dependencies
  8. Dependent Deployments that use it
  9. Device count where application is currently installed
  10. Device count where application has experienced failure
2. SCCM Collections with 0 Deployments Report

The SCCM Collections with 0 Deployments Report can be downloaded here.

The report fields include:

  1. Collection ID
  2. Collection Name
  3. Collection Type(User/Device/Other)
  4. Member Count
  5. Refresh Type
  6. Last modified
  7. Last refresh
  8. Attached comments