> 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/knowledge-base/how-to-articles/decommission-a-devolutions-server-instance.md).

# Nedluk en Devolutions Server-instans

Nedluk en Devolutions Server-instans ved at afinstallere Devolutions Gateway og planlægningstjenesten og derefter fjerne resterende installationsfiler og IIS-bindinger.

Denne artikel beskriver, hvordan en Devolutions Server nedlukkes, for eksempel efter migrering af serveren fra en gammel arbejdsstation til en ny maskine.

1. I Devolutions Server Console skal De gå til fanen ***Ledsagere*** og ***Afinstaller*** Devolutions Gateway og planlægningstjenesten.
2. Når det er gjort, skal De gå til fanen ***Server*** og klikke på knappen ***Udforsk***. De føres til installationsmappen for den valgte Devolutions Server.
3. Gå derefter tilbage til Devolutions Server Console, og klik på ***Afinstaller*** på samme fane.
4. Fjern eventuelle mapper og filer, der er tilbage i det tidligere åbnede Stifinder-vindue.
5. Fjern eventuelt bindingen, eller slet webstedet i IIS Manager.


---

# 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/knowledge-base/how-to-articles/decommission-a-devolutions-server-instance.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.