> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/active-directory/enumeration/local-admin-access-discovery.md).
# Search for local administrator access
Active Directory security notes for Search for local administrator access, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
### Find machines where user is local admin
{% code overflow="wrap" %}
```powershell
Find-LocalAdminAccess -Verbose
```
{% endcode %}
This command tests on which machines the current user has local administrator rights.
This is a very useful command in the post-compromise enumeration phase in a lab.
### List local administrators on multiple machines
{% code overflow="wrap" %}
```powershell
Invoke-EnumerateLocalAdmin -Verbose
```
{% endcode %}
This command allows you to identify local administrators on multiple hosts in the domain.
### Find user sessions in a group
{% code overflow="wrap" %}
```powershell
Invoke-UserHunter -GroupName "RDPUsers"
```
{% endcode %}
This command searches for sessions established by users belonging to the `RDPUsers` group.
This command searches for sessions established by users belonging to the `RDPUsers` group.
This can help identify:
* on which machines a group is active;
* where some interesting users are connected;
* which machines deserve further analysis.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/active-directory/enumeration/local-admin-access-discovery.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)
.png?alt=media)