> 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/cloud/es/concepts/intermediate-concepts/remote-management.md).

# Gestión remota

La gestión remota de Devolutions Cloud centraliza las sesiones de Active Directory, VMware y Hyper-V iniciadas mediante Remote Desktop Manager y Devolutions Gateway.

La gestión remota es la capacidad de controlar y supervisar sistemas a distancia, utilizando herramientas seguras en lugar de estar físicamente en el sitio. En Remote Desktop Manager, la gestión remota centraliza el inicio, la supervisión y la resolución de problemas de tecnologías como Active Directory, VMware y Hyper V.

Cuando las entradas se almacenan en Devolutions Cloud, la bóveda se convierte en el inventario de referencia, mientras que las sesiones remotas se inician desde la interfaz web de Devolutions Cloud o desde Remote Desktop Manager y Devolutions Password Manager. Combinado con Devolutions Gateway, esto permite un acceso remoto justo a tiempo a los recursos internos sin exponerlos directamente a Internet.

#### Temas relacionados

* [Gestión remota](https://docs.devolutions.net/rdm/es/concepts/intermediate-concepts/remote-management)
* [Interfaz web](/cloud/es/web-interface.md)


---

# 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 dynamically 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/cloud/es/concepts/intermediate-concepts/remote-management.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 `build a script that syncs our docs to a CMS` 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.