CommandExecutionError in lgpo.set
due to bad zero value for LockoutDuration
#56406
Labels
Bug
broken, incorrect, or confusing behavior
fixed-pls-verify
fix is linked, bug author to confirm fix
P3
Priority 3
severity-medium
3rd level, incorrect or bad functionality, confusing and lacks a work around
ZRelease-Sodium
retired label
Milestone
Uh oh!
There was an error while loading. Please reload this page.
Steps to Reproduce Issue
On a Windows Server 2012R2 system, install salt and run the command below. Note that this issue only reproduces when
LockoutThreshold
is non-zero, seemingly due to some internal Windows API constraints.Explanation
This errors because
LockoutDuration
does not actually use0
as the zero value, but the lgpo module does not know that (yet). See the line in the output:Similar to the transform for
MaxPasswordAge
, the zero value forLockoutDuration
needs to be0xffffffff
. Then it magically works.Versions Report
The text was updated successfully, but these errors were encountered: