Upgrade Process Bullet List

Upgrading an instance of Devolutions Server

Please visit the Upgrading Devolutions Server page for informational steps of the upgrade procedure.

Devolutions Server upgrades are not overly complicated, but certain steps must be planned carefully.

Please contact us at service@devolutions.net to book a session where we'll help out.

Devolutions Server is used by teams, this means that other users must be taken into account before starting with the upgrade.


Confirm that all minimum requirements are installed and dependencies reach the supported versions according to the System Requirements page.

The following bullet list describe each steps a support technician will follow to assist a customer to upgrade the Devolutions Server instance.

  1. Ensure that the Domain functional level is at least at version Windows Server 2012R2.
  2. Confirm for database and web application folder backups. Ensure that the Copy only backup option is enabled in SQL Server Management Studio to get a stand alone backup that is not part from a backup set.
  3. Make sure everyone is in offline mode in Remote Desktop Manager if properly configured or disconnected from the Devolutions Server web interface.
  4. Modify the Maximal version in the Administration - System Settings if configured.
  5. Confirm to stop the instance with the Go Offline button on the Devolutions Server Console If more than one Devolutions Server instance (High Availability or Load Balancing), switch all instances to Offline mode before the upgrade.
  6. For version older than 2020.1.x, check if a Passphrase Security Provider is set on the Devolutions Server instance. If so, remove the security provider before the upgrade and then set the new Encryption at REST after the upgrade. A database backup following each steps will avoid going back at the beginning of the process if something wrong happens.
  7. Confirm for 2FA settings.
  8. Confirm for Integrated Security enabled or disabled in Database tab.
    1. If so, confirm that the connected user on the Windows machine has enough permissions to do database upgrades. To be sure, look in the Application pool identity.
    2. After the upgrade, verify that the application pool identity has the proper permissions on the tables. You may have to provide the proper SQL statement.
  9. Make sure that no antivirus is currently running or scanning the web application and Devolutions Server Console installation folders.
  10. Open the Devolutions Server Console and tell the user to upgrade through the console.
  11. Install Prerequisites for Devolutions Server if required.
  12. Upgrade the Devolutions Server instance with the Update button on the Devolutions Server Console
  13. Check if Devolutions Server is back Online in the console.
  14. If the Integrated Security option is enabled, check the new database permissions and update them if required.
  15. Test web page login directly on the server with the Navigate to Website button on the Devolutions Server Console
  16. Reset the Devolutions Server cache and/or IIS reset.
  17. If required, install the latest Remote Desktop Manager version that belongs to the Devolutions Server version.
  18. Test connectivity from Remote Desktop Manager to the Devolutions Server data source.
  19. If required, update Devolutions Gateway.
  20. Make sure that the encryption keys will be exported and put in a safe place for security measure. These encryption keys are required for disaster recovery
  21. Ensure that the Remote Desktop Manager and the Devolutions Server licenses match.