The SCCM client that was running, registered, and ignoring every deployment
Why a GPO and a script on a fileshare quietly underperforms, and what to replace it with
A machine stops getting deployments. The console says Active. CcmExec is running. It registered this morning. Every check you would think to run comes back clean, and the machine has not installed anything in two months. Most shops end up with the same answer: a GPO and a remediation script on a fileshare. It half works, nobody entirely trusts it, and the manual triage never actually goes away. This is about why that happens and what to do instead.