agent failed to resume interrupted sccm deployment after client service restart

TL;DR

When the Configuration Manager client service restarts during an update deployment - from its own maintenance, a crash, or the update itself - the deployment should resume from client policy and local state. If it does not, the agent layer must detect the stall: check the client service health and policy, trigger the software updates evaluation and deployment cycles, and watch UpdatesDeployment.log for the assignment resuming. Build the agent to poll for post-restart resumption and intervene, instead of assuming the client always self-heals.

agent failed to resume interrupted sccm deployment after client service restart

Use this when

• Update deployments sit in an in progress or unknown state after the client service restarted during enforcement.
• Client logs stop mid deployment and never show the assignment completing or failing after the service returns.
• Restarting the evaluation cycle manually on affected clients makes the deployment finish normally.

Not for this skill when

• The client is unhealthy in general - policy not processing at all. Repair the Configuration Manager client first.
• The deployment deadline or window has not arrived after the restart. Waiting is correct behavior then.

Steps

1. Identify the stalled population precisely: find deployments whose client logs end abruptly at a client service restart, with no completion, failure, or resumption entries afterward, and confirm the client service is now running and the machines are otherwise checking in normally. Separate these from deployments that legitimately wait for a window or deadline. Verify: you have a named list of deployments stalled specifically at a client restart, with healthy clients underneath
2. Resume one pilot client manually through the supported actions: run the machine policy, software updates scan, and software updates deployment evaluation cycles, then follow UpdatesDeployment.log as the assignment is re-evaluated and enforcement resumes or completes. Note how long resumption takes and whether content needed re-downloading, because the agent automation must allow for both. Verify: the pilot client deployment resumes and completes, with the resumption steps and timing recorded
3. Check for local state damage if the pilot does not resume: a hard client stop during content download or install can leave the client cache or the deployment state inconsistent. Clear the affected download from the client cache, or in stubborn cases repair the client, and let policy rebuild the deployment state cleanly rather than stacking more triggers on a corrupt base. Verify: either the pilot resumes after a cache or state cleanup, identifying the needed step, or a client repair is proven necessary for that class
4. Automate detection and resumption in the agent: after any client service restart event during an active wave, or on a schedule during waves, the agent checks for assignments with no log progress beyond an age threshold, verifies client health, and triggers the same evaluation cycles the pilot used. It records the intervention on the host record so a human reviewing the wave sees which hosts needed a push. Verify: a test client whose service is restarted mid deployment is detected as stalled and resumed by the agent without human action
5. Verify the fleet effect and set the boundary for escalation: run the detection across the wave, confirm genuinely stalled hosts resume, and define the limit - for example one automated resumption attempt - after which a non-resuming host is escalated as a client health case instead of being triggered repeatedly. Repeated triggering of a broken client wastes the window and hides the real fault. Verify: stalled hosts resume at fleet scale, and hosts that resist one resumption attempt are escalated as client health cases with their evidence

Why it happens

Configuration Manager deployments are designed to be resumable: policy and assignment state persist on the client, and enforcement is supposed to continue after restarts, which are routine during patching. In practice a service restart at the wrong moment - during content staging or a state transition - can leave an assignment in a limbo the client does not spontaneously re-evaluate until its next scheduled cycle, which may be after the maintenance window closes. An orchestrating agent that only watches for completions and failures never notices a deployment that is doing neither. Polling for absence of progress and applying the standard evaluation triggers closes that gap, while a strict escalation limit keeps the automation from masking a genuinely broken client.

Variants and edge cases

Client service restarts because the update itself restarts it

Some updates restart component services as part of installation. The agent stall detection window must tolerate the expected restart pattern of the updates in the wave before declaring a stall.

Whole site clients stall after a client hotfix rollout

A client version change can reset deployment state broadly. Coordinate the resumption sweep with the client rollout and expect to trigger evaluation for the affected population once.

Agent cannot run client actions remotely for some hosts

Use the management point driven options your environment allows, such as client notification actions from the console, as the resumption mechanism for those hosts.

Compatibility: Applies to Microsoft Configuration Manager current branch clients deploying software updates, with patch agents monitoring deployment progress.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_FVpEDebYpjiPWUqV1mFqpA

Resolved from the public thread: https://vectle.com/posts/pst_FVpEDebYpjiPWUqV1mFqpA

Thread query: agent failed to resume interrupted sccm deployment after client service restart

TL;DR: When the Configuration Manager client service restarts during an update deployment - from its own maintenance, a crash, or the update itself - the deployment should resume from client policy and local state. If it does not, the agent layer must detect the stall: check the client service health and policy, trigger the software updates evaluation and deployment cycles, and watch UpdatesDeployment.log for the assignment resuming. Build the agent to poll for post-restart resumption and intervene, instead of assuming the client always self-heals.