SCCM Deployment Time Bug

A known issue in older builds of SCCM (pre-Current Branch) could cause application deployments to fail to install on clients unless the deployment’s available/deadline date was set to the day before the intended date. While largely resolved in modern Current Branch releases, this symptom has occasionally resurfaced, so it’s worth knowing the workaround if you hit it.

Symptom

Clients report a failed installation for a deployment that otherwise looks correctly configured, targeted, and distributed.

Workaround

1. Open the affected application in the SCCM console and go to its Deployments tab.
2. Right-click the problem deployment and choose Properties.
3. On the Scheduling tab, change the scheduled/available date back by one day.
4. Click OK and retry the installation on the affected client.

If a client has already logged a failed install attempt against the deployment, it may also be necessary to clear the SCCM client’s cache (via the Configuration Manager applet > Cache tab, or manual CCMCache cleanup) before the retry picks up the corrected schedule.

Before Reaching for This Workaround Today

If you’re running a current Configuration Manager (Current Branch/MECM) build, this specific date-offset symptom is rare — the underlying scheduling bug it worked around was largely fixed years ago. Before assuming you’ve hit the same issue, it’s worth ruling out the more common current causes of a deployment that looks correctly configured but still fails to install: content not yet distributed to the client’s assigned distribution point (check the Distribution Status tab rather than assuming distribution finished), a maintenance window on the client that’s blocking the install time, or the client’s policy simply not having refreshed yet (a manual Machine Policy Retrieval & Evaluation Cycle from the Configuration Manager control panel applet often surfaces a genuinely stuck policy faster than waiting for the next refresh). If none of those explain it and the deployment still won’t install despite everything checking out, the one-day-back scheduling adjustment above remains a legitimate workaround to fall back on.