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

# Remote-Verwaltung

Die Remoteverwaltung in Devolutions Server führt administrative Aufgaben wie das Neustarten von Servern auf Remotesystemen von einer zentralen Konsole aus.

Die Remoteverwaltung in der Devolutions-Plattform bezeichnet das Ausführen administrativer Aufgaben auf Remotesystemen von einer zentralen Konsole aus, anstatt sich jedes Mal manuell zu verbinden. Typische Aktionen sind das Neustarten von Servern, das Verwalten von Diensten, das Bereitstellen von Skripten oder das Sammeln von Inventardaten über Protokolle wie PowerShell, WMI oder SSH.

Devolutions Server speichert die Hosts und Anmeldeinformationen, die diese Werkzeuge verwenden, während Remote Desktop Manager oder andere Clients die Vorgänge ausführen und die Ergebnisse zurück in Protokolle einspeisen. Diese Kombination reduziert wiederkehrende Arbeit, standardisiert Administrationsaufgaben und bewahrt eine nachvollziehbare Aufzeichnung von Änderungen an kritischer Infrastruktur.

#### Verwandte Themen

* [Berichte](/server/de/web-interface/utilities/reports.md)

#### Siehe auch

* [Remoteverwaltung](https://docs.devolutions.net/rdm/de/concepts/intermediate-concepts/remote-management)


---

# 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/server/de/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.