> 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/rdm/it/knowledge-base/how-to-articles/keepass-plugin-installation-on-a-rds.md).

# Installazione del plugin KeePass su un RDS

Installi il plugin KeePass su un Remote Desktop Service insieme a Remote Desktop Manager e configuri il percorso di installazione del plugin.

L'utilizzo di Remote Desktop Manager e KeePass su un Remote Desktop Service richiede più passaggi.

### Requisiti

L'installazione di Remote Desktop Manager segue [Terminal Services / Remote Desktop Services](/rdm/it/getting-started/installation/client/remote-desktop-services-terminal-services.md).

Si assicuri che l'installazione di KeePass sia andata a buon fine e che non si trovi su un'unità di rete.

### Plugin KeePass

1. [Scarichi il plugin KeePass](https://keepass.info/download.html).
2. Decomprima i file nella cartella di installazione di KeePass (ad esempio, `C:\Program Files (x86)\KeePass Password Safe 2`).
3. Il percorso di installazione di KeePass (`File – Settings – Clipboard – Paths – Configure installation path`) deve essere configurato in **default.cfg**, a cui si fa riferimento in [Terminal Services / Remote Desktop Services](/rdm/it/getting-started/installation/client/remote-desktop-services-terminal-services.md).
4. Per modificare manualmente **default.cfg**, adatti il percorso e aggiunga la riga nel contesto: `C:\Program Files (x86)\KeePass Password Safe 2`.

Ogni volta che Remote Desktop Manager viene avviato e rileva un nuovo file default.cfg, verrà visualizzata una finestra di dialogo.

Selezionando Usa nuova configurazione, la configurazione dell'utente viene semplicemente sovrascritta. Se desidera solo aggiornare la chiave di licenza di Remote Desktop Manager dopo un rinnovo, scelga ***Recupera solo la nuova registrazione***.


---

# 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/rdm/it/knowledge-base/how-to-articles/keepass-plugin-installation-on-a-rds.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.