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

# Remote management

Control and monitor systems remotely in Remote Desktop Manager using dashboards for Active Directory, VMware, and Hyper-V, plus remote tools.

Remote management is the ability to control and monitor systems from a distance, enabling secure access without being on site.

In Remote Desktop Manager, remote management centralizes launch, monitoring, and troubleshooting. Use dashboards for Active Directory, VMware, and Hyper-V, and open remote tools such as Remote Task Manager, Remote Printer, and Remote Registry directly from entries. This streamlines routine administration, speeds diagnostics, and reduces context switching.

#### Related topics

* [WOL](/rdm/knowledge-base/knowledge-base-articles/wake-on-lan-wol.md)
* [VMware](/rdm/knowledge-base/troubleshooting-articles/vmware.md)

#### See also

* [Devolutions Academy - Managing Systems Remotely](https://academy.devolutions.net/student/path/1925039/activity/2667184)


---

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