2016281112 Remediation failed

Von Bandel, Kai 0 Reputation points
2024-03-19T14:16:33.0233333+00:00

Hello everyone,

I have the problem, that only a few of our companies devices get marked as noncompliant with a "2016281112 (Remediation failed)" for the system account. It's only for the minimum password length as well.

User's imageUser's image

Most other devices work and we set the password for the only active local account with LAPS. The local security policies are all correct as well and the password set by LAPS is working.

I'm completely out of idea as this is seemingly completely random behaviour...

Does anyone have a fix for this without resetting the whole system?

Thank you all in advance!

Microsoft Intune Compliance
Microsoft Intune Compliance
Microsoft Intune: A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.Compliance: Adhering to rules, standards, policies, and laws.
142 questions
Microsoft Intune
Microsoft Intune
A Microsoft cloud-based management solution that offers mobile device management, mobile application management, and PC management capabilities.
4,462 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Fiona Matu 86 Reputation points Microsoft Employee
    2024-05-02T09:00:57.1766667+00:00

    The error code "2016281112 Remediation failed" you're encountering typically means that the Intune service tried to remediate a settings violation, but it failed. This is often due to the device being offline, or the user not being signed in.

    However, in your case, it seems to be related to Local Administrator Password Solution (LAPS) and the minimum password length policy.

    Please double-check the following:

    1. Ensure that the local security policy on the devices does not conflict with the domain policy.
    2. Check the Event Viewer on the affected devices for any additional error messages or warnings related to LAPS or password policy. These will give you a better idea on where the issue could be emanating from.
    3. Make sure the devices are online and users are signed in when the policies are being applied.
    4. Verify that the LAPS extension is installed and functioning correctly on the devices showing the error.
    0 comments No comments