A practical SCCM health-check sequence
A repeatable order for checking site systems, clients, content, deployments, and patching before deep troubleshooting begins.
KNOWLEDGE BASE
Clear notes for
real operations.
Practical guidance focused on decisions, evidence, failure modes, and safe ways of working—not filler.
FIELD NOTE · SCCM
A practical SCCM health-check sequence
A repeatable order for checking site systems, clients, content, deployments, and patching before deep troubleshooting begins.
8 min read · Updated 2026-08-01Read featured guide →
10 guides found
Designing safer Intune remediations
How to design detection, remediation, logging, rollout, and recovery so a useful script does not become a fleet-wide incident.
Turning an admin script into an operational tool
The engineering details that separate a useful one-off script from automation a team can schedule, support, and improve.
Guardrails for high-scale Tanium actions
A practical control set for targeting, impact review, approvals, monitoring, and evidence when an action can reach thousands of endpoints.
Where Python fits in endpoint operations
Use cases where Python adds value alongside PowerShell: APIs, data shaping, validation, reporting, packaging, and integrations.
Technical handover that survives the project
A reusable handover structure covering architecture, dependencies, controls, operations, recovery, and ownership.
Trace an SCCM application deployment end to end
A disciplined troubleshooting path from requirement rules and policy to content location, execution, detection, and final state reporting.
Build Win32 app detection rules you can support
How to choose stable evidence, distinguish versions, handle architecture, and test Intune detection without creating reinstall loops.
Use one result schema across PowerShell automation
A small object contract that makes console output, CSV reports, scheduled jobs, and support evidence easier to consume.
Score an automation idea before you build it
A practical intake scorecard for value, repeatability, data quality, permissions, blast radius, recovery, and long-term ownership.
EDITORIAL PRINCIPLES
Every guide starts with what to observe and how to prove the current state.
Automation advice includes targeting, validation, failure handling, and rollback.
Documentation focuses on ownership, monitoring, support, and continued improvement.