Online Help > Installation

Upgrading Devolutions Password Server




The Devolutions Password Server Console is now offered as a stand alone application. It is now available on the Download page.


It is highly recommended as a best practice to first deploy the new version of Devolutions Password Server to a staging instance and verify its stability before deploying it to your whole organization. If you do not have a staging instance we then recommend a limited roll-out to ensure the work flow is supported to your satisfaction prior to impacting your whole team.


New releases may require additional steps. Please consult the topics below, as required.


Upgrading to 3.2.2

Upgrading to 4.0.7

Upgrading to 4.5

Upgrading to 4.7.1

Upgrading to 5.1.0

Upgrading to 6.0



These steps are intended to be achieved on a single server or a basic topology. If your environment differs from these topologies, please contact us and we will guide you on how to upgrade Devolutions Password Server.





We highly recommend to test the upgrade process in a staging/test environment before upgrading your production instance.



The upgrade steps will be performed with Devolutions Password Server Console. You will need to upgrade your copy to the latest version that is matched with the target version of Devolutions Password Server that you are preparing to install. Please follow the steps carefully.



If you have elected to use Integrated Security for connecting to the database, you must perform the upgrade using a Windows user account that has full rights on the database.



If you have set the Security Provider Passphrase v1 on your current Devolutions Password Server, specific operations will need to be done before the upgrade. Please contact us for further details.



We recommend doing a backup of the Encryption Keys before any operation that could modify the information of the database or before the upgrade of Devolutions Password Server. Protect the Encryption Key in a safe to avoid data loss if Devolutions Password Server has to be restored.


Preparation phase

Ensure that the instance users have the offline mode enabled and that they all perform a full refresh of the cache (CTRL+F5)

Have your team switch to the offline mode, allowing them to work while the system is down

Update the Maximal version of Remote Desktop Manager in Administration - Data Source Settings - Version Management - Maximal version, if this option was set before the upgrade.


Phase 1

Perform a full backup of the database, take precautions against that backup file being deleted by a maintenance plan.

Archive the content of the folder containing the Devolutions Password Server instance, move to a safe place.

Install the proper version of Devolutions Password Server Console. In each of the sub-topics related to a specific version of Devolutions Password Server you will find the version of the client that you need.

Devolutions Password Server Console must be run with elevated privileges.


Phase 2

1.Open the Devolutions Server Console.

2.Select the instance that you wish to upgrade.

3.Set the instance in Offline Mode with the Go Offline button.

4.Click the Upgrade Server button.


Devolutions Password Server Console

Devolutions Password Server Console


5.Select upgrade source. You can either use the latest General Availability release that is available online automatically, or specify the path to a zip file that you have downloaded yourself.  Use this for beta releases or for earlier versions.


Devolutions Password Server Upgrade Wizard

Devolutions Password Server Upgrade Wizard


6.Press Next.

7.Review the summary and press Upgrade if you are satisfied.



Upgrade successful

Upgrade successful


8.Since Devolutions Password Server version, it is possible to access the Backup Folder, the Installation Folder or View Installation Log from the More Options button in the lower left corner of the Devolutions Password Server Upgrade Wizard dialog.




Final phase


The Backup Folder contains information about the configuration of the Devolutions Password Server instance prior to the upgrade. After a successful upgrade, you must ensure the content is either moved to a safe place, or deleted.



Our support department gets more and more urgent requests for assistance because of a rogue admin upgrading his own copy of Remote Desktop Manager and introducing a schema update for some new feature. This may prevent other users from using the system. We strongly recommend setting both the Maximal and Minimal versions allowed to connect to your instance.


Have a user upgrade his workstation with the version of Remote Desktop Manager supported by the Devolutions Password Server version and test connectivity with the server instance.

When you are satisfied with your tests, have the rest of the staff upgrade to the same version of Remote Desktop Manager.

Update the Maximal/Minimal version of Remote Desktop Manager in Administration - Data Source Settings - Version Management

Move or delete the backup folder, it is located in the %TMP%\DVLS folder of the current user profile. Newer versions of Remote Desktop Manager add a suffix to indicate a sequence.