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

# Fjernadministration

Fjernadministration i Devolutions Server kører administrative opgaver som genstart af servere på fjernsystemer fra en central konsol.

Fjernadministration på Devolutions-platformen betyder, at administrative opgaver køres på fjernsystemer fra en central konsol i stedet for at oprette forbindelse manuelt hver gang. Typiske handlinger omfatter genstart af servere, administration af tjenester, udrulning af scripts eller indsamling af inventardata via protokoller som PowerShell, WMI eller SSH.

Devolutions Server gemmer de værter og legitimationsoplysninger, som disse værktøjer bruger, mens Remote Desktop Manager eller andre klienter udfører handlingerne og sender resultaterne tilbage til loggene. Denne kombination mindsker gentaget arbejde, standardiserer administratoropgaver og bevarer en sporbar registrering af ændringer i kritisk infrastruktur.

#### Relaterede emner

* [Rapporter](/server/da/web-interface/utilities/reports.md)

#### Se også

* [Fjernadministration](https://docs.devolutions.net/rdm/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/da/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.