> 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/server/knowledge-base/how-to-articles/configure-remotefx-for-the-rdp-webclient.md).

# Configure RemoteFX for the RDP WebClient

Enable RemoteFX on remote Windows machines through Group Policy settings to improve RDP WebClient performance in Devolutions Server sessions.

By default, Windows does not enable RemoteFX to ensure backward compatibility. However, for optimal performance when using a WebClient RDP, it is recommended that you enable RemoteFX on the server machines that allow it.

To enable RemoteFX on a remote machine, a number of options must be enabled.

Here is the procedure to follow on the remote machine:

1. Launch the Windows run command <kbd>Windows</kbd>+<kbd>R</kbd>, and run `gpedit.msc`.
2. Enable ***Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment\RemoteFX for Windows Server 2008 R2\Configure RemoteFX***.
3. Enable ***Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment\Enable RemoteFX encoding for RemoteFX clients designed for Windows Server 2008 R2 SP1***.
4. Enable ***Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment\Limit maximum color depth***.
5. Restart the remote machine.


---

# 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/server/knowledge-base/how-to-articles/configure-remotefx-for-the-rdp-webclient.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.
