What's new 
We enabled LAPS in a Windows policy, but the policy stays in progress for a long time and does not complete. I tried splitting LAPS into a separate policy, but the behavior is the same. This has happened on more than one device and across different networks. I also do not want to manually scan, restart, and reassign policies for every newly enrolled device. What is the correct way to handle a Windows LAPS policy that is stuck in Hexnode?
21 Views
Replies (1)
Marked SolutionPending Review
Hexnode Expert
3 weeks ago
Jul 30, 2026
Marked SolutionPending Review
Hi @gnishilda,
For a Windows LAPS policy that remains in progress, first confirm whether the device is actively checking in with Hexnode and whether the action history shows the policy command being delivered.
A useful troubleshooting sequence is:
- Open the device in Hexnode and check the last check-in time.
- Go to the device action history and verify whether the LAPS policy action is pending, in progress, failed, or completed.
- Trigger a manual Scan Device action from the Actions menu.
- Restart the Windows device if the policy remains in progress after the scan.
- Re-deploy the policy by opening the policy, selecting Manage > Edit Policy, and saving it again without necessarily changing the configuration.
In this case, the policy completed successfully after the device was scanned and the same policy was saved again to trigger a fresh deployment.
If the policy is not failing and no conflict is shown, the delay is usually related to the Windows device processing queued MDM/CSP tasks and reporting the completed status back to Hexnode. During that period, Hexnode may continue to show the policy as In Progress until the device finishes processing and syncs the updated status.
Regards,
Sienna Carter
Hexnode UEM
Save