Forum Discussion
Lucas_Ayre
Oct 31, 2023Copper Contributor
Password Complexity Error 2016281112(Remediation failed)
Hello, I've been having an issue with Intune device compliance. The main issue stems from the fact that the devices have a Microsoft account as the device profile, this means that users use the...
Lucas_Ayre
Nov 07, 2023Copper Contributor
Hi, MattR345
I actually found a crude way of fixing this, by going to the individual computer and going to the Local Security Policy settings (win+r "secpol.msc") > account policies > password policy and changing password must meet complexity requirements to "Enabled". However I don't fully understand how this is working as my Intune settings shouldn't require it at all, also this wouldn't be a good solution for 100+ endpoints, so I'm not claiming its a proper solution.
I actually found a crude way of fixing this, by going to the individual computer and going to the Local Security Policy settings (win+r "secpol.msc") > account policies > password policy and changing password must meet complexity requirements to "Enabled". However I don't fully understand how this is working as my Intune settings shouldn't require it at all, also this wouldn't be a good solution for 100+ endpoints, so I'm not claiming its a proper solution.
MattR345
Nov 07, 2023Copper Contributor
Hi Lucas_Ayre
Thanks for the reply. I appreciate the info, but just as you said, the crude fix really isn't viable for the number of devices we have failing for this error.
I've been digging through the MS docs to find more info on this, such as code setting criteria, but I'm coming up short. Please let me know if you find anything useful in your quest.
Thanks again
- Tracy HisomDec 04, 2023Copper Contributor
We are having the same issue and the user has reset their password but this error still remains, any luck with a solution MattR345 ?
- MattR345Dec 20, 2023Copper ContributorUnfortunately, no. I have a premier ticket with MS on this. I've been going back and forth with the support engineer; it has since been escalated higher up the chain.
We now have over 5k devices with this error. Something changed on the Microsoft side as another division of our company didn't have this issue for years, now suddenly thousands of them do and nothing was changed on our end.