> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/pam/knowledge-base/how-to-articles/elevate-management-tools-with-a-privileged-account.md).

# Elevate management tools with a privileged account

Elevate management tools with a privileged account using PowerShell Remote sessions configured to run as administrator in Remote Desktop Manager.

Discover how to manage tools with elevated privileges using the PowerShell Remote session type in Remote Desktop Manager. It establishes a connection to a remote host through ps-sessions with different credentials.

### Prerequisite

* [***WinRM HTTPS listener***](https://learn.microsoft.com/en-us/windows/win32/winrm/installation-and-configuration-for-windows-remote-management) is properly configured on the target workstation.
* A ***valid SSL certificate*** is used with an appropriate thumbprint.

#### Configuring a **PowerShell terminal (Remote) entry**

1. Open **Remote Desktop Manager.**
2. Click on **New entry** and search for **PowerShell terminal (Remote)**.
3. Select **PowerShell terminal (Remote)** as the session type.
4. Enter the name, the host and the credentials.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You can configure multiple hosts and select the destination at the startup of the session.</p></div>
5. The elevated credentials could be a custom one from AD, a privileged access management account, or any other credentials entry from Remote Desktop Manager.
6. To elevate permissions, the session must be configured to ***run as an administrator***.
7. Navigate to the **Run as** tab.
8. Enable the setting **Run as administrator**. Note that port 5986 - HTTPS (WinRM) is used when running the PowerShell entry as an administrator.
9. Click ***Add*** to save the PowerShell entry.
10. Execute the PowerShell entry.
11. To confirm that the session is running under a privileged account, use the following PowerShell commands:

* Check the current user

```powershell
whoami
```

* Verify elevated permissions

```powershell
$currentPrincipal = New-Object Security.Principal.WindowsPrincipal([Security.Principal.WindowsIdentity]::GetCurrent())
$currentPrincipal.IsInRole([Security.Principal.WindowsBuiltInRole]::Administrator)
```


---

# 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://docs.devolutions.net/pam/knowledge-base/how-to-articles/elevate-management-tools-with-a-privileged-account.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.