The policy engine didn't attampt to configure the settings

Noyon Chandra Das 341 Reputation points
2022-09-19T05:51:04+00:00

Why this error comes up

242401-image.png

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2022-09-23T03:03:21.1+00:00

    Hello NoyonChandraDas-4493,

    Thank you for posting in our Q&A forum.

    The error may occur in the following situation:

    I assume this machine is in an OU container on a domain controller, and for the OU that the machine is in, you may have linked multiple GPOs (or multiple GPOs are inherited to the OU) to this OU, but for ONE gpo setting, maybe the same gpo setting value is configured in different GPOs OR maybe different gpo setting values are configured in different GPOs .

    And you can check by right clicking one setting and open its Properties and check Precedence tag.

    For example:
    244089-apo.png

    Here is a similar thread for your reference.

    https://learn.microsoft.com/en-us/answers/questions/76477/rsopmsc-shows-a-red-x-for-one-of-the-setting-which.html

    Hope the information above is helpful.

    Best Regards,
    Daisy Zhou

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Noyon Chandra Das 341 Reputation points
    2022-09-25T04:38:44.16+00:00

    244532-image.png

    Hello Daisy Zhou,
    Thanks for your reply. How can I solve it?


  2. Noyon Chandra Das 341 Reputation points
    2022-09-26T07:53:19.3+00:00

    Hi DaisyZhou-MSFT,
    Thanks for your reply. I have checked the workaround you recommend me.

    After Uncheck all services
    244639-image.png

    After reconfigure services
    244677-image.png

    Create New GPO
    244714-image.png


  3. Roberto Gacitua 0 Reputation points
    2024-10-30T18:48:18.3666667+00:00

    This may be too late, but it happens because you have enabled the "Force audit policy subcategory settings (Windows Vista or later) to override audit policy category settings" option in Computer Configuration\Policies\Windows Settings\Security Settings\LocalPolicies\Security Options

    User's image

    This setting causes the behavior you describe in the audit policy settings.

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.