> 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/powershell/da/remote-desktop-manager-powershell/powershell-scripting/custom-powershell-commands.md).

# Custom PowerShell commands

Kør en Brugerdefineret PowerShell kommando på poster valgt i Remote Desktop Manager navigation pane til edit flere sessioner på én gang.

Brugerdefineret Powershell kommando vil act på i øjeblikket valgt poster i Deres ***navigation pane***. Brug click og <kbd>Ctrl</kbd>+click til build op Deres liste, eller en [avanceret søgning](https://docs.devolutions.net/rdm/ribbon-menu-bar/view/search/advanced-search) at vælge en great tal af poster. Efter Deres valg er done, kommandoen er tilgængelig ved hjælp af enten:

1. Rettighed-click posten eller poster, derefter select ***Edit – Edit (særlig handlinger)***.
2. Én gang der, select ***Brugerdefineret PowerShell kommando***.
3. Et vindue appears i som De kan write en kodestykke af code. Note at er sidste linje skal altid være `$RDM.Save();`.
4. Upon pressing ***Ok***, en oversigt dialog appears til at angive fuldført eller fejl.


---

# 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/powershell/da/remote-desktop-manager-powershell/powershell-scripting/custom-powershell-commands.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.