A useful SCCM health check is an evidence trail, not a collection of green icons. Start with the platform dependencies, move through site processing, then validate the client and workload paths that users actually depend on.
1. Establish the operating baseline
Record the Configuration Manager version, hierarchy, site roles, SQL placement, boundary design, content topology, client population, maintenance windows, and current change activity. Without this baseline, an apparent fault may simply be an undocumented design decision.
Confirm backups, restore expectations, service accounts, certificate dependencies, and monitoring ownership before investigating individual components.
2. Follow the platform dependency chain
Validate host capacity, storage, SQL health, name resolution, certificates, and connectivity before focusing on component messages. Review site status, component status, replication, inbox backlogs, and role-specific logs as one connected story.
A warning matters when it affects processing, remains unexplained, or repeats. Document the evidence and the user-facing impact instead of clearing status messages to make a console look healthy.
3. Test the client and content journey
Sample clients from different locations and management paths. Confirm policy retrieval, inventory, state messaging, content location, boundary behavior, cache health, and the ability to evaluate and install a controlled deployment.
Test distribution from source to distribution point to client. Content validation should include package state, boundary selection, transfer behavior, and evidence on the endpoint—not only a successful distribution status.
4. Validate business workloads
Review software update synchronization, ADR output, deployments, maintenance windows, scan state, compliance calculation, and representative failures. Apply the same end-to-end approach to applications, task sequences, and reporting.
Finish with prioritized findings: immediate risk, recurring reliability issue, design improvement, documentation gap, and monitoring opportunity. Assign an owner and a verification step to every action.
OPERATIONAL CHECKLIST
Take this into the work.
- ✓Document hierarchy and role ownership
- ✓Verify backups and recovery assumptions
- ✓Review component, replication, and inbox evidence
- ✓Sample client health across locations
- ✓Trace one content item end to end
- ✓Validate update and application workflows
- ✓Prioritize findings with owners and proof of closure
PRIMARY REFERENCES
Check the platform documentation.
Product behavior and requirements change. Validate this guidance against the current vendor documentation and your own environment.
NEED HELP APPLYING THIS?