> 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/domain-computer-enumeration.md).
# Domain Computer Enumeration
Active Directory security notes for Domain Computer Enumeration, covering enumeration, Kerberos, credentials, ACL abuse, lateral movement, exploitation workflow, and validation steps.
### With the Active Directory module
List all computers:
{% code overflow="wrap" %}
```powershell
Get-ADComputer -Filter *
```
{% endcode %}
Filter the information:
{% code overflow="wrap" %}
```powershell
Get-ADComputer -Filter * | select DNSHostName, Name, SID
```
{% endcode %}
### With PowerView
{% code overflow="wrap" %}
```powershell
Get-NetComputer
```
{% endcode %}
This command allows you to retrieve information such as:
* the name of the machine;
* the operating system;
* the Windows version;
* the SAM account type;
* the date of the last machine password change.
### Check if the machines are turned on
{% code overflow="wrap" %}
```powershell
Get-NetComputer -Ping | select name,operatingsystem
```
{% endcode %}
This command allows you to identify the machines that can be reached on the network.
---
# 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/domain-computer-enumeration.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)
.png?alt=media)