> 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/send-rdp-logs-to-our-customer-support-team-from-remote-desktop-manager-ios.md).

# Send RDP logs to our customer support team from Remote Desktop Manager iOS

Enable and send RDP session logs from Remote Desktop Manager iOS to customer support to troubleshoot connection issues.

Follow these steps to send sessions logs to our customer support team from Remote Desktop Manager iOS when encountering an issue with RDP.

1. On the main application screen, press ***More*** in the toolbar and select ***Settings***.
2. Tap ***Sessions***.
3. Under ***Sessions*** press ***RDP***, to open the RDP settings screen, and ***Enable logging***.
4. ***Launch*** the RDP session to reproduce the issue.
5. On the main screen, press ***More*** in the toolbar and select ***Tools***.
6. In the ***File Repository***, you should see a file named RPD\_LOG.log. Press on the information icon and select ***Preview***.
7. Press on the icon at the top-rignt corner of the screen and select your preferred email application.
8. Enter <service@devolutions.net> for the recipient and send the email.


---

# 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/send-rdp-logs-to-our-customer-support-team-from-remote-desktop-manager-ios.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.