> 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/enterprise-deployment-of-remote-desktop-manager.md).

# Enterprise deployment of Remote Desktop Manager

Deploy Remote Desktop Manager enterprise wide using the custom installer service to replicate configuration into a distributable installer package.

The ***custom installer service***, offered through our Devolutions Portal services, replicates the configuration from a Remote Desktop Manager instance. This configuration is used to create an installer file (\*.rdi), which will be used to create the installation package intended for distribution.

{% hint style="info" %}
You can store and create up to 6 ***custom installer*** configuration file package in your Devolutions Account.
{% endhint %}

Once you have created the installation package with our [***custom installer service***](/rdm/getting-started/installation/client/custom-installer-service.md), deploy it and copy the **default.cfg** in the installation folder, which by default is under **%ProgramFiles(x86)%\Devolutions\RemoteDesktopManager**.


---

# 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/enterprise-deployment-of-remote-desktop-manager.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.