> 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/de/knowledge-base/troubleshooting-articles/remote-desktop-manager-virtual-channels-are-not-allowed-in-restrictive-environments.md).

# Virtuelle Kanäle von Remote Desktop Manager sind in restriktiven Umgebungen nicht zulässig

Beheben Sie Einschränkungen virtueller Kanäle in Remote Desktop Manager in abgesicherten Umgebungen, indem Sie die Kanäle RDMJump, RDMCmd und RDMLog auf die Whitelist setzen.

### Virtuelle Kanäle

Virtuelle Kanäle sind Kommunikationswege, die zwischen einem Client und einer Remote-Sitzung eingerichtet werden, um die Datenübertragung zu ermöglichen. Remote Desktop Manager verwendet drei virtuelle Kanäle für RDP-Sitzungen, um zu springen und Befehle auszuführen: ***RDMJump***, ***RDMCmd*** und ***RDMLog***.

Diese virtuellen Kanäle können in Umgebungen, in denen virtuelle Kanäle nicht zugelassen sind, eingeschränkt werden.

### Lösung

In den Umgebungen müssen Ausnahmen erstellt werden, um die virtuellen Kanäle von Remote Desktop Manager auf die Whitelist zu setzen.


---

# 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/de/knowledge-base/troubleshooting-articles/remote-desktop-manager-virtual-channels-are-not-allowed-in-restrictive-environments.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.