> 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/es/knowledge-base/troubleshooting-articles/session-tools.md).

# Herramientas de sesión

Corrija el error Acceso denegado al utilizar Administración de equipos u otras herramientas de sesión en Remote Desktop Manager habilitando las credenciales predeterminadas.

Cuando intenta utilizar ***Administración de equipos***, recibe el error `Access is denied(5)`.

### Solución

Para que esto funcione, debe seleccionar ***Usar credenciales predeterminadas*** en la pestaña ***Herramientas de administración*** de la sesión RDP.

Si esto no resuelve su problema, es probable que su sesión tenga habilitada la opción ***Configuración específica del usuario***.

Esto puede resultar útil cuando utiliza herramientas como:

* Hyper-V
* Visor de eventos
* Administración de equipos
* Servicios de Windows

Si necesita esto con frecuencia, le recomendamos cambiar la ***Configuración predeterminada*** del tipo de entrada. Con esta modificación, todas sus nuevas sesiones utilizarán las credenciales especificadas cuando se inicie una herramienta.


---

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