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

# KeePass plugin installation on a RDS

Install the KeePass plugin on a Remote Desktop Service alongside Remote Desktop Manager and configure the plugin installation path.

Using Remote Desktop Manager and KeePass on a Remote Desktop Service require multiple steps.

### Requirements

The installation of Remote Desktop Manager follows [Terminal Services / Remote Desktop Services](/rdm/getting-started/installation/client/remote-desktop-services-terminal-services.md).

Make sure that the installation of KeePass was successful and is not on a network drive.

### KeePass plugin

1. [Download the KeePass plugin](https://keepass.info/download.html).
2. Unzip the files in the installation folder of KeePass (e.g., `C:\Program Files (x86)\KeePass Password Safe 2`).
3. KeePass installation path (`File – Settings – Clipboard – Paths – Configure installation path`), has to be configured in **default.cfg** refereed in [Terminal Services / Remote Desktop Services](/rdm/getting-started/installation/client/remote-desktop-services-terminal-services.md).
4. To manually edit **default.cfg**, adjust the path and add the line in context: `C:\Program Files (x86)\KeePass Password Safe 2`.

Whenever Remote Desktop Manager is started and it detects a new default.cfg file, a dialog window will appear.

By selecting Use new configuration, the user's configuration is simply overwritten. If you only wish to update the Remote Desktop Manager license key after a renewal, choose ***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/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.