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

# I canali virtuali di Remote Desktop Manager non sono consentiti in ambienti restrittivi

Risolva le restrizioni dei canali virtuali di Remote Desktop Manager negli ambienti bloccati inserendo nella whitelist i canali RDMJump, RDMCmd e RDMLog.

### Canali virtuali

I canali virtuali sono percorsi di comunicazione stabiliti tra un client e una sessione remota per facilitare la trasmissione dei dati. Remote Desktop Manager utilizza tre canali virtuali per le sessioni RDP per eseguire jump e comandi: ***RDMJump***, ***RDMCmd*** e ***RDMLog***.

Questi canali virtuali possono essere limitati negli ambienti in cui i canali virtuali non sono consentiti.

### Soluzione

È necessario creare eccezioni negli ambienti per inserire nella whitelist i canali virtuali di Remote Desktop Manager.


---

# 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/it/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.