> 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/concepts/intermediate-concepts/extended-maintenance.md). # Extended maintenance Learn how the extended maintenance release channel in Remote Desktop Manager delivers security and major bug fixes without frequent feature upgrades. Extended maintenance is a release channel in Remote Desktop Manager for organizations that want stability and fewer upgrades while still getting security fixes. Instead of moving to each new release as soon as it is available, an installation on this channel stays on the previous release and receives only security fixes and major bug fixes. Remote Desktop Manager offers three release channels: * ***Current*** (default): The most recent version, with all the latest features, improvements, security fixes, and bug fixes. * ***Beta***: Pre-release versions for testing upcoming features before they reach the current channel. This channel is not available on Linux. * ***Extended maintenance***: The previous release, maintained with security fixes and major bug fixes only. No new features are added. ### Select the release channel The release channel is available in Remote Desktop Manager on Windows, macOS, and Linux. Select it in ***File*** – ***Settings*** – ***Application*** – ***Application startup***, in the ***Auto-update*** section, with the ***Release channel*** setting. On macOS, the setting is in ***File*** – ***Settings*** – ***General*** – ***Application startup***. On macOS, when the installed version is the current extended maintenance release and the release channel was never changed, Remote Desktop Manager switches the release channel to ***Extended maintenance*** automatically. On Linux, the extended maintenance version can also be installed directly with [Flatpak](/rdm/getting-started/installation/client.md). ### Enforce the release channel Administrators can enforce the release channel across an organization with the [Enforce auto-update release channel](/rdm/knowledge-base/how-to-articles/apply-policies-gpos.md#enforce-auto-update-release-channel) policy. When the policy is set, the ***Release channel*** setting cannot be changed in the application. On Windows, the policy is deployed as a group policy (GPO). On macOS, it is deployed with a configuration profile from an MDM solution. This policy is not applied on Linux. #### Related topics * [Update](/rdm/getting-started/installation/update.md) * [General (macOS)](/rdm/ribbon-menu-bar/file/settings/general-macos.md) * [Apply policies (GPOs)](/rdm/knowledge-base/how-to-articles/apply-policies-gpos.md) * [Prevent issues by matching major and minor versions](https://docs.devolutions.net/resources/other-resources/prevent-issues-by-matching-major-and-minor-versions) * [Version management](/rdm/ribbon-menu-bar/administration/system-settings/application/version-management.md) * [Devolutions security advisories](https://devolutions.net/security/advisories/) --- # 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/concepts/intermediate-concepts/extended-maintenance.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 `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.