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

# Implementación empresarial de Remote Desktop Manager

Despliegue Remote Desktop Manager en toda la empresa utilizando el servicio de instalador personalizado para replicar la configuración en un paquete de instalación distribuible.

El ***servicio de instalador personalizado***, ofrecido a través de nuestros servicios de Devolutions Portal, replica la configuración de una instancia de Remote Desktop Manager. Esta configuración se utiliza para crear un fichero de instalación (\*.rdi), que servirá para crear el paquete de instalación destinado a la distribución.

{% hint style="info" %}
Puede almacenar y crear hasta 6 paquetes de ficheros de configuración del ***instalador personalizado*** en su Devolutions Account.
{% endhint %}

Una vez que haya creado el paquete de instalación con nuestro [***servicio de instalador personalizado***](https://docs.devolutions.net/rdm/es/getting-started/installation/client/custom-installer-service.md), despliéguelo y copie el fichero **default.cfg** en la carpeta de instalación, que por defecto se encuentra en **%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/es/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.
