> 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/da/knowledge-base/how-to-articles/elevate-management-tools-with-a-privileged-account.md).

# Ophøj administrationsværktøjer med en privilegeret konto

Ophøj administrationsværktøjer med en privilegeret konto ved hjælp af PowerShell Remote-sessioner, der er konfigureret til at køre som administrator i Remote Desktop Manager.

Se, hvordan De administrerer værktøjer med ophøjede privilegier ved hjælp af sessionstypen PowerShell Remote i Remote Desktop Manager. Den opretter en forbindelse til en fjernvært gennem ps-sessioner med andre legitimationsoplysninger.

### Forudsætning

* [***WinRM HTTPS-lytter***](https://learn.microsoft.com/en-us/windows/win32/winrm/installation-and-configuration-for-windows-remote-management) er korrekt konfigureret på målarbejdsstationen.
* Der bruges et ***gyldigt SSL-certifikat*** med et passende tommelfingeraftryk.

#### Konfiguration af en **PowerShell terminal (Remote)-post**

1. Åbn **Remote Desktop Manager.**
2. Klik på **Ny post**, og søg efter **PowerShell terminal (Remote)**.
3. Vælg **PowerShell terminal (Remote)** som sessionstype.
4. Angiv navnet, værten og legitimationsoplysningerne.

   <div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>De kan konfigurere flere værter og vælge destinationen ved sessionens start.</p></div>
5. De ophøjede legitimationsoplysninger kan være brugerdefinerede fra AD, en konto til administration af privilegeret adgang eller en hvilken som helst anden post med legitimationsoplysninger fra Remote Desktop Manager.
6. For at ophøje tilladelser skal sessionen konfigureres til at ***køre som administrator***.
7. Gå til fanen **Kør som**.
8. Aktivér indstillingen **Kør som administrator**. Bemærk, at port 5986 - HTTPS (WinRM) bruges, når PowerShell-posten køres som administrator.
9. Klik på ***Tilføj*** for at gemme PowerShell-posten.
10. Kør PowerShell-posten.
11. For at bekræfte at sessionen kører under en privilegeret konto, skal De bruge følgende PowerShell-kommandoer:

* Kontrollér den aktuelle bruger

```powershell
whoami
```

* Bekræft ophøjede tilladelser

```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/da/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.