ConfigMgr is a bit like a garage – you throw all kinds of stuff in there over the years, and then one day you decide to go through everything and chuck out the stuff you don’t need anymore. It’s a time-consuming process and sometimes there are difficult decisions to be made – do I / don’t I? What if it might come in useful 3 years from now?! By the time you’ve finished going through everything you’re so exhausted you start chucking out everything for fear of having to do this again one day! But once it’s done, it’s done. For now…
Recently I ran a housekeeping project for a ConfigMgr environment and ended up writing a bunch of SQL queries to help identify items that are good candidates for deletion based on various criteria. I decided to publish them on GitHub in case they might help others in their own spring-cleaning efforts.
I’d welcome any contributions as it’s challenging to identify legacy items that might exist in any environment. In the initial commit, the following queries are included:
- Active Applications not deployed or referenced in a Task Sequence
- Application deployments with 0 deployment results or targeted at 0 resources
- Boot images not referenced by a Task Sequence
- Collections with 0 members
- Compliance Baseline deployments with 0 deployment results or targeted to 0 resources
- Compliance Items not used in a Compliance Baseline
- Deployed Applications with no Last Enforcement Message in the last 180 days.
- Disabled Compliance Baselines
- Disabled Task Sequences
- Driver Packages not referenced in a Task Sequence
- Enabled Compliance Baselines not deployed
- OS Image Packages not referenced in a Task Sequence
- OS Upgrade Packages not referenced in a Task Sequence
- Retired Applications
- Software Update Deployment Packages not referenced by an Automatic Deployment Rule
- Software Update Groups not deployed
- Standard Package deployments with 0 deployment results or targeted to 0 resources
- Standard Packages not deployed or referenced in a Task Sequence
- Superseded Applications
- Task Sequence deployments with 0 deployment results or targeted to 0 resources
- Task Sequence deployments with no execution history in the last 180 days
- Task Sequences not deployed
There’s also a couple of PowerShell scripts to help identify orphaned content in your content source share, but use these with appropriate discretion.
