> 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/device-management-configuration-from-remote-desktop-manager-mobile.md).

# Device management configuration from Remote Desktop Manager mobile

Push Remote Desktop Manager mobile configuration files to other users iOS and Android devices using an MDM tool such as Workspace One.

{% tabs %}
{% tab title="iOS" %}
The Devolutions environment does not have a Mobile Device Management (MDM) tool to push the configuration to other user's iOS devices. But with the use of an application like Workspace One, it is possible to do so.

### Solution

1. Configure a Remote Desktop Manager iOS device.
2. Export the configuration in a MDM file. To do so, go to ***Settings – Advanced – Generate Managed App Configuration file (xml, plist)***.
3. In your MDM application, use the exported MDM file to push it to all devices.
   {% endtab %}

{% tab title="Android" %}
The Devolutions environment does not have a Mobile Device Management (MDM) tool to push the configuration to other user's Android devices. But with the use of an application like Workspace One, it is possible to do so.

### Solution

1. Configure a Remote Desktop Manager Android device.
2. Export the configuration in a MDM file. To do so, go to ***Settings – Generate Managed App Configuration file (xml, plist)***.
3. In your MDM application, use the exported MDM file to push it to all devices.
   {% endtab %}
   {% endtabs %}


---

# 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/device-management-configuration-from-remote-desktop-manager-mobile.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.