> 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-machine-enumeration.md).

# Local Machine Enumeration

Active Directory security notes for Local Machine Enumeration, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.

### Basic user and machine information

Show current user name:

```powershell
$env:Username
```

Show user domain:

```powershell
$env:UserDomain
```

Show machine name:

```powershell
$env:ComputerName
```

These commands quickly identify:

* which user we work with;
* what machine we are on;
* in which domain or workgroup you are connected.

### Enumeration of local groups

With PowerView:

```powershell
Get-NetLocalGroup
```

With native PowerShell:

```powershell
Get-LocalGroup
```

These commands display the machine's local groups, for example:

* `Administrators`
* `Users`
* `Remote Desktop Users`
* `Guests`

### View members of the Administrators group

With PowerView:

```powershell
Get-NetLocalGroupMember -Groupname Administrators | Select-Object MemberName, IsGroup, IsDomain
```

With native PowerShell:

```powershell
Get-LocalGroupMember -Group Administrators
```

This step is important to identify:

* local administrators;
* domain groups added locally;
* users with elevated privileges on the machine.

### See the groups a user belongs to

With PowerView:

```powershell
Get-NetGroup -UserName "user1" | select name
```

This allows you to know which groups a specific user is in.

Example of interest:

* check if `user1` belongs to a privileged group;
* identify interesting groups like `Administrators`, `RDPUsers`, `Executives`, etc.


---

# 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-machine-enumeration.md?ask=<question>&goal=<user_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.