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

# Gestione remota

La gestione remota in Devolutions Server esegue attività amministrative, come il riavvio dei server sui sistemi remoti, da una console centrale.

La gestione remota nella piattaforma Devolutions si riferisce all'esecuzione di attività amministrative su sistemi remoti da una console centrale invece di connettersi manualmente ogni volta. Le azioni tipiche includono il riavvio dei server, la gestione dei servizi, la distribuzione di script o la raccolta di dati di inventario tramite protocolli come PowerShell, WMI o SSH.

Devolutions Server archivia gli host e le credenziali utilizzati da questi strumenti, mentre Remote Desktop Manager o altri client eseguono le operazioni e restituiscono i risultati nei log. Questa combinazione riduce il lavoro ripetitivo, standardizza le attività amministrative e mantiene una traccia rintracciabile delle modifiche apportate all'infrastruttura critica.

#### Argomenti correlati

* [Report](/server/it/web-interface/utilities/reports.md)

#### Vedere anche

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