> 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/resources/da/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-windows-life-cycle-policy.md).

# Livscykluspolitik for Remote Desktop Manager Windows

Livscykluspolitikken for Remote Desktop Manager Windows følger alle Windows-udgivelser, som Microsoft understøtter i øjeblikket, herunder serverudgaver.

Devolutions sikrer, at Remote Desktop Manager Windows er kompatibel med alle versioner af Windows-operativsystemet, som Microsoft understøtter i øjeblikket, f.eks. Windows 10/11 og Windows Server 2016, 2019 og 2022.

Det er brugerens ansvar at sikre, at enheden kører en version af Windows, som Microsoft understøtter i øjeblikket, og dermed også Remote Desktop Manager.

Kompatibilitet med versioner af Windows, som Microsoft ikke længere understøtter garanteres ikke og kan medføre nedsat funktionalitet eller manglende funktion. Devolutions hæfter ikke for fejl, manglende funktion eller ydelsesproblemer i Remote Desktop Manager, der skyldes brug på ikke-understøttede eller forældede versioner af Windows, og forbeholder sig retten til efter eget skøn at fastsætte slutdatoen for support af disse.


---

# 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/resources/da/other-resources/life-cycle-policies/remote-desktop-manager/remote-desktop-manager-windows-life-cycle-policy.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.