DSC Local Configuration Manager Stuck in Busy State

Question

DSC Local Configuration Manager Stuck in Busy State

Advait Mohammad 40

Hi,

We pushed a DSC configuration to a batch of Windows Servers, but the deployment was interrupted on several nodes. Since then, any attempt to apply a new configuration fails because the Local Configuration Manager (LCM) reports that it is still busy.

There are no active DSC jobs that we can see, so it looks like the LCM state was never properly released after the failed push.

What's the supported way to reset the LCM state and clean up any pending DSC configurations without having to reboot the affected servers?

0 comments

1 answer

Your answer

Answer 1

Hello,

When the Local Configuration Manager (LCM) gets stuck in a “busy” state after an interrupted DSC push, the supported way to clear it without rebooting is to explicitly reset the LCM job queue and remove any pending or partially applied configurations. You can do this directly from the console using PowerShell.

First, check the current DSC job state with Get-DscConfigurationStatus. If it shows a job in progress but never completes, you can force a reset by stopping the DSC engine:

Code

Stop-DscConfiguration -Force

This command clears any active or orphaned DSC job handles. Once that’s done, you should also remove any pending or corrupted configuration documents from the LCM store. Run:

Code

Remove-DscConfigurationDocument -Stage Pending -Force
Remove-DscConfigurationDocument -Stage Current -Force
Remove-DscConfigurationDocument -Stage Previous -Force

This wipes out the stuck configuration documents from all stages. After that, reinitialize the LCM by reapplying a clean meta-configuration if needed:

Code

Set-DscLocalConfigurationManager -Path <path_to_meta_config>

At this point, the LCM state machine is reset, the “busy” flag is cleared, and you can safely push a new DSC configuration without rebooting the server. This is the Microsoft-supported method for recovering from interrupted DSC deployments, and it avoids having to restart the node or reset unrelated system settings.

I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!

Domic Vo.