Forum Discussion
Password Complexity Error 2016281112(Remediation failed)
I was struggling with this too until my colleague very carefully read the tooltip on that setting, paying attention to the commas. What this setting affects is the PIN. If you put "alphanumeric" for PW type, the compliance policy will require a password, AND an alphanumeric PIN. Each setting requires a password actually, so the only difference is what style of PIN is required.
If you want a numeric only PIN, or if you do device default (which gives the option of an alphanumeric PIN but doesn't require it) - either way the Password Complexity switch disappears. The PW complexity setting is only relevant when the password type is set to alphanumeric, which forces the PIN to be alphanumeric.
My guess is that if you queried a few noncompliant users, you'd find that they are using numeric PINs, therefore they are noncompliant, regardless of what's going on with the PW.
Also confirmed here: https://learn.microsoft.com/en-us/mem/intune/protect/compliance-policy-create-windows
Even set to Device Default, we get the complexity errorJesseVaught
- DarrenH1580Oct 08, 2024Copper Contributor
DarrenH1580 Just fixed our issue... Turns out when we originally hired an outside source to help set up our Intune compliance policys, they set up a Windows compliance policy and applied it to several User groups. After I created a new test compliance policy (for Windows devices only) using the same configuration details but applying it to a test Device group only, all test devices showed as compliant.