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

# Instalación del plugin de KeePass en un RDS

Instale el plugin de KeePass en un servicio de Escritorio remoto junto con Remote Desktop Manager y configure la ruta de instalación del plugin.

El uso de Remote Desktop Manager y KeePass en un servicio de Escritorio remoto requiere varios pasos.

### Requisitos

La instalación de Remote Desktop Manager sigue [Terminal Services / Remote Desktop Services](https://docs.devolutions.net/rdm/es/getting-started/installation/client/remote-desktop-services-terminal-services.md).

Asegúrese de que la instalación de KeePass se realizó correctamente y de que no está en una unidad de red.

### Plugin de KeePass

1. [Descargue el plugin de KeePass](https://keepass.info/download.html).
2. Descomprima los ficheros en la carpeta de instalación de KeePass (p. ej., `C:\Program Files (x86)\KeePass Password Safe 2`).
3. La ruta de instalación de KeePass (`File – Settings – Clipboard – Paths – Configure installation path`) debe configurarse en **default.cfg**, mencionado en [Terminal Services / Remote Desktop Services](https://docs.devolutions.net/rdm/es/getting-started/installation/client/remote-desktop-services-terminal-services.md).
4. Para editar manualmente **default.cfg**, ajuste la ruta y añada la línea en el contexto: `C:\Program Files (x86)\KeePass Password Safe 2`.

Cada vez que se inicia Remote Desktop Manager y detecta un nuevo fichero default.cfg, aparecerá una ventana de diálogo.

Al seleccionar Usar nueva configuración, la configuración del usuario simplemente se sobrescribe. Si solo desea actualizar la clave de licencia de Remote Desktop Manager tras una renovación, elija ***Retrieve new registration only***.


---

# 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/es/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.
