> 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/getting-started/installation/devolutions-server-upgrade.md). # Devolutions Server upgrade [Install the proper version of the Devolutions Server Console](https://devolutions.net/server/download/) before upgrading the Devolutions Server web application. The following steps are intended for single-server setups or basic [topologies](https://docs.devolutions.net/server/overview/topologies/). If the environment differs from these configurations, please [contact us](mailto:service@devolutions.net) for guidance with the Devolutions Server upgrade. ### Workflow Recommendations and steps to follow before proceeding with the upgrade: * We strongly recommend testing the upgrade process in a [staging or test environment](https://docs.devolutions.net/server/kb/how-to-articles/create-server-staging-instance/) before upgrading the production instance. If a staging environment is not available, consider a limited roll-out to ensure that the workflow functions as expected before impacting the entire team. * Make sure you have a local Devolutions Server administrator account exempted from MFA in case the primary authentication fails. * [Enable the emergency login](https://docs.devolutions.net/server/kb/how-to-articles/enable-emergency-login-code-authentication/) for your administrator accounts. * Remove any password set on the Devolutions Server Console for the upgrade. Passwords can be reset afterwards. * The upgrade process will be performed with the Devolutions Server Console. Be sure to upgrade to the latest version compatible with the target Devolutions Server version planned for installation. * When Integrated Security is used for database connections, the upgrade must be performed with a Windows user account that has full rights to the database, such as [VaultDBOwner](https://docs.devolutions.net/server/kb/knowledge-base/pre-deployment-account-survey/#domain-based-operation-integrated-security-option). Ensure that the IIS Application Pool Identity and Scheduler accounts have adequate privileges on the database. You may have to manually apply the permissions on the database. See the [Generate script for database permissions](broken://pages/7a5ff4068d2fb353d10987f3d74738500a04f76f) article for more information. * For instances of Devolutions Server version 2019.2.9.0 or earlier with a configured [security provider](https://docs.devolutions.net/server/kb/how-to-articles/remove-security-provider/), specific operations must be performed prior to the upgrade. [Contact us](mailto:service@devolutions.net) for further details. * We recommend to back up the encryption keys before any operations that could modify database information or before upgrading Devolutions Server. The encryption key file should be securely stored to prevent data loss in the event that Devolutions Server needs to be restored. #### Preparation 1. Perform a full backup of the database, and ensure that measures are in place to prevent the backup file from being deleted by a maintenance plan. * The backup folder contains configuration details of the Devolutions Server instance prior to the upgrade. After a successful upgrade, ensure that the contents are either moved to a secure location or deleted. * Administrators who independently upgrade their copies of Remote Desktop Manager may trigger schema updates required for new features. This can prevent other users from accessing the system. It is strongly recommended to set both the maximal and minimal versions allowed to connect to the instance. * If Integrated Security is used for database connections, as configured in the [database](https://docs.devolutions.net/server/devolutions-server-console/devolutions-server-settings/database/) tab, ensure that the IIS Application Pool Identity and Scheduler accounts have sufficient privileges on the database. 2. Archive the contents of the web application folder containing the Devolutions Server instance, and store it in a secure location. 3. Install the appropriate version of the Devolutions Server Console. The required client version for each Devolutions Server version can be found in the corresponding sub-topics. 4. Go to the ***Support*** tab and click ***Check for updates.*** ![](https://cdnweb.devolutions.net/docs/DVLS6033_2025_1.png) 5. Install the necessary updates, if any. 6. Click and run the ***IIS diagnostic***. ![](https://cdnweb.devolutions.net/docs/DVLS6034_2025_1.png) 7. Click the ***Install prerequisites*** button if any are missing. ![](https://cdnweb.devolutions.net/docs/DVLS6035_2025_1.png) 8. Run the Devolutions Server Console with elevated privileges. #### Upgrade 1. Open the [Devolutions Server Console](https://docs.devolutions.net/server/devolutions-server-console/). 2. Select the instance to be upgraded. 3. Set the instance to ***Offline mode*** with the ***Go offline*** button. In a high availability / load balancing topology, all instances must be set to ***Offline mode*** before initiating the upgrade process. ![](https://cdnweb.devolutions.net/docs/DVLSCONSOLE2004_2024_1.png) 4. Click ***Update***. ![](https://cdnweb.devolutions.net/docs/DVLSCONSOLE2000_2024_1.png) 5. Select the upgrade source. Either choose the latest or extended maintenance release available online, or specify the path to a downloaded ZIP file. This option is typically used for beta releases or earlier versions. ![](https://cdnweb.devolutions.net/docs/DVLSCONSOLE2001_2024_1.png) 6. Click ***Next***. 7. Review the summary and click ***Update*** once details have been confirmed. ![](https://cdnweb.devolutions.net/docs/DVLSCONSOLE2002_2024_1.png) The process will begin, and upon completion, a confirmation message will indicate that the operation was successful. ![](https://cdnweb.devolutions.net/docs/DVLSCONSOLE2003_2024_1.png) #### Validation * Have a user upgrade their workstation with the version of Remote Desktop Manager supported by the Devolutions Server version and test connectivity with the server instance. * Ensure that computers running PowerShell scripts update the Devolutions.PowerShell module to the version supported by the Devolutions Server version, and verify the script results. * Once testing is complete and satisfactory, instruct the rest of the staff to upgrade to the same version of Remote Desktop Manager. * Update the maximal and minimal version of Remote Desktop Manager in ***Administration – System settings – Version management***. #### See also * [Devolutions Academy – Updating Devolutions Server](https://academy.devolutions.net/student/path/2942210/activity/4493539) --- # 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 current page URL with the `ask` query parameter: ``` GET https://docs.devolutions.net/server/getting-started/installation/devolutions-server-upgrade.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.