> 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/session-tools.md).

# Strumenti di sessione

Risolva l'errore Access is denied quando utilizza Gestione computer o altri strumenti di sessione in Remote Desktop Manager abilitando le credenziali predefinite.

Quando prova a utilizzare ***Computer Management***, riceve l'errore `Access is denied(5)`.

### Soluzione

Per far funzionare questa operazione, deve selezionare ***Use default credentials*** nella scheda ***Management Tools*** della sessione RDP.

Se questo non risolve il problema, è probabile che nella sua sessione siano abilitate le ***User-specific settings***.

Questo può essere utile quando utilizza strumenti come:

* Hyper-V
* Visualizzatore eventi
* Gestione computer
* Servizi di Windows

Se questa esigenza si presenta spesso, le consigliamo di modificare le ***Default Settings*** del tipo di voce. Con questa modifica, tutte le nuove sessioni utilizzeranno le credenziali specificate quando viene avviato uno strumento.


---

# 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/session-tools.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.