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

# Dismettere un'istanza di Devolutions Server

Dismetta un'istanza di Devolutions Server disinstallando Devolutions Gateway e lo scheduler, quindi rimuovendo i file di installazione residui e i binding IIS.

Questo articolo descrive come dismettere un Devolutions Server, ad esempio dopo aver migrato il server da una vecchia workstation a una nuova macchina.

1. Nella Devolutions Server Console, vada alla scheda ***Companions*** e selezioni ***Uninstall*** per Devolutions Gateway e lo scheduler.
2. Al termine, vada alla scheda ***Server*** e clicchi sul pulsante ***Explore***. Dovrebbe essere indirizzato alla cartella di installazione del Devolutions Server selezionato.
3. Poi, torni alla Devolutions Server Console e clicchi su ***Uninstall*** nella stessa scheda.
4. Rimuova le cartelle e i file rimasti nella finestra di Esplora file precedentemente aperta.
5. Facoltativamente, rimuova il binding o elimini il sito in 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 dynamically 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/it/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 `build a script that syncs our docs to a CMS` 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.