> For the complete documentation index, see [llms.txt](https://docs.parallels.com/landing/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.parallels.com/landing/ras-best-practices-guide/v19/remote-access-configuration/configure-remotefx/general-purpose-remotefx-settings/configure-remotefx-adaptive-graphics.md). # Configure RemoteFX Adaptive Graphics RemoteFX supports two Group Policy settings that give administrators the flexibility to manually choose the best configuration for their scenario. Both policies are under this path: Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Remote Session Environment. The first policy setting is **Configure image quality for RemoteFX Adaptive Graphics**. This policy setting specifies the graphics quality for a remote session. Administrators can use this option to balance network bandwidth usage with graphics quality delivered. The options are Medium (default), High, and Lossless. The Medium setting consumes the lowest amount of bandwidth, The High setting increases the image quality with a moderate increase in bandwidth consumption, while the Lossless setting uses lossless encoding, which preserves full color and resolution integrity but requires significant increase in bandwidth. The second policy setting is **Configure RemoteFX Adaptive Graphics**. This policy setting allows the administrator to choose the encoding configuration to be optimized for server scalability or bandwidth usage. If you enable this policy setting, the RemoteFX experience could be set to one of the following options: * Let the system choose the experience for the network condition * Optimize for experience (balanced) * Optimize to use minimum network bandwidth By default, the system will choose the best experience based on available network bandwidth. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.parallels.com/landing/ras-best-practices-guide/v19/remote-access-configuration/configure-remotefx/general-purpose-remotefx-settings/configure-remotefx-adaptive-graphics.md?ask=&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 `build a script that syncs our docs to a CMS` 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.