> 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/rdm/ribbon-menu-bar/tools/powershell-rdm-cmdlet.md).

# PowerShell (RDM CmdLet)

Open the embedded PowerShell (RDM CmdLet) window in Remote Desktop Manager to automate session creation, editing, and management through cmdlets.

The ***PowerShell (RDM CmLet)*** automatically opens an embedded PowerShell window. Remote Desktop Manager snap-in allows for quick and robust automation of actions such as add/edit/open of sessions, the possibilities are endless.

Since its release, this highly-requested feature has become very useful in solving user requests. A quick search through our forum reveals many usages of the cmdlets, such as automating the creation of Windows Start Menu shortcuts for every Remote Desktop Manager session.

To learn more, you can find full Remote Desktop Manager cmdlet documentation available in [PowerShell scripting](https://docs.devolutions.net/powershell/remote-desktop-manager-powershell/powershell-scripting) or directly in PowerShell using the Get-Help cmdlet.

### Settings

You will find on [GitHub](https://github.com/Devolutions/DevoSample-ps) multiple PowerShell script to import edit or interact with the Remote Desktop Manager data.


---

# 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/rdm/ribbon-menu-bar/tools/powershell-rdm-cmdlet.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.