Remove Local Administrators on Windows not working

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Remove Local Administrators on Windows not working

L3 Networker

I have been testing this default policy to lock down the local administrators group. But when I set the policy extension "Protect Windows administrative groups from changes" to "From all Users and Programs" I am still able to add users to this group in an elevated mmc with Computer Management.

 

Anyone has experience with this?

11 REPLIES 11

L5 Sessionator

LSASS there's a registry key that may need to be disabled essentially users can add themselves using NET USER cmds and powershell to add themselves back to the local admin, so basically by having this enabled it prevents the cyberark from injecting itself into the process - : Configure added LSA protection | Microsoft Learn I would obviously confirm with Cyberark as your issue might be different to one I came across

L4 Transporter

LSASS there's a registry key that may need to be disabled essentially users can add themselves using NET USER cmds and powershell to add themselves back to the local admin, so basically by having this enabled it prevents the cyberark from injecting itself into the process - : Configure added LSA protection | Microsoft Learn I would obviously confirm with Cyberark as your issue might be different to one I came across

L4 Transporter

This functionality works correctly for me... we've been using it for years. As @Touseef-ur rehman​ indicated in his answer, it would be best to reach out to CyberArk Support so they can walk through all aspects of this and how you have it configured to make sure all is well.

L1 Bithead

Try going to Advanced>Agent Configuration>Extended Protection. Turn that setting to "Set from all user and programs" Click save and see if that works.

Thanks for your reply. I already tried that and didn't help.

@John Gordijn​ 

So as rwn suggested, It’s a good idea to contact CyberArk Support to review your configuration and ensure everything is set up correctly.

 

 

To create a support ticket for your organization from the main page of the Technical Community, please use the "Services Hub" tab. Within, click on the "Open a Case" button on the lower left side of the screen.

 

Note:

 

  • If you do not have access to raise support tickets, please reach out to one of your team members who has access to support to raise a ticket on your behalf. 

 

  • If you are working with a partner, you should request that they raise a ticket for your issue. 

 

  • If you are not sure whether or not you should raise a support ticket yourself or via a partner, you can email '[email protected],' and they should be able to point you in the right direction. 

 

Lastly, if you require additional means of contacting CyberArk support or similar required services, please visit the CyberArk official website:https://www.cyberark.com/services-support/technical-support-contact/

 

Thanks,

Niv

Out of interest the users adding themselves to local admin only happening on W365 out of interest?

Out of interest the users adding themselves to local admin only happening on W365 out of interest?

No, this is a normal physical W11 workstation.

Looks like windows defender ASR rules also protect LSASS. which could break the epm agent to, so worth checking there ? Inaddition def worth confirming the below key is disabled as a test to see if it resolves the issue!

  • Indeed, LSA protection prevents EPM protection of the local admin group as it blocks injections to the LSASS process. This root cause is external to the EPM agent and can be addressed using the instructions in the specified document.
  •  

 

 

Looks like windows defender ASR rules also protect LSASS. which could break the epm agent to, so worth checking there ? Inaddition def worth confirming the below key is disabled as a test to see if it resolves the issue!

  • Indeed, LSA protection prevents EPM protection of the local admin group as it blocks injections to the LSASS process. This root cause is external to the EPM agent and can be addressed using the instructions in the specified document.
  •  

 

 

  • 45 Views
  • 11 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!