GPO - Local Users and Groups - Item level targeting - Security Group - Removed from security group and local group but it keeps coming back

Anonymous
2024-07-16T18:31:57+00:00

I have a GPO that adds a security group to the local Administrators group using item-level targeting (another security group with servers). I remove the server in question from the item-level target group and manually remove the group from Administrators. When I do a gpupdate, it adds the group back. The GPO is set to update (action).

That server is no longer in the item-level targeting group. Why is it adding the group back during a gpupdate after it has been removed?

Windows for business | Windows Server | Directory services | Active Directory

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} vote
Accepted answer
  1. Anonymous
    2024-07-17T03:23:47+00:00

    Hi TJCooperWhatever,

    Thank you for posting in the Microsoft Community Forums.

    Recheck GPO settings: Make sure that the GPO settings are correct and that no unnecessary groups are added to the local Administrators group.

    Running gpresult /h C:gpresult.html at the command prompt generates an HTML report detailing the policy settings applied to the computer. This helps you better understand which strategies are being applied.

    Relink or remove GPOs: If the problem persists, consider removing or relinking the GPOs from the OU that contains that server and check if the issue is resolved.

    Check the system event log for details about any errors that may have occurred during Group Policy processing.

    Best regards

    Neuvi Jiang

    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Anonymous
    2024-08-21T16:06:28+00:00

    I am unable to select a User Group for an Item level targeting in a file update. This file update is in the User Section of policy.

    0 comments No comments