Update order DVLS and RDM
We are using DVLS (with PAM), Gateway, and RDM. The RDM client runs in a VDI session. According to the release notes [1], RDM 2025.2.x requires DVLS 2025.2.x, which also includes a database update.
Additionally, the compatibility list [2] shows that DVLS 2025.2 is not compatible with RDM 2025.1 and vice versa.
It’s challenging to update all components at the same time. Is there an upgrade scenario where, for example, we can update RDM first to 2025.2 and update DVLS a day later?
[1] https://devolutions.net/remote-desktop-manager/release-notes/
[2] https://docs.devolutions.net/rdm/kb/knowledge-base/version-schema-compatibility-rdm-server/
All Comments (5)
Hello Freddy,
Thank you for reaching out on our forum.
Just to clarify the dependency between RDM and Devolutions Server (DVLS) versions typically relates to the features available in the DVLS version. For example, DVLS 2025.2 includes more recently implemented features compared to versions like 2025.1 or 2024.3.
While it’s recommended to use RDM 2025.2 alongside DVLS 2025.2 to take full advantage of all features, RDM 2025.1 will still work properly with DVLS 2025.2 the core functionality remains compatible.
If your goal is to enforce version consistency across your users, I suggest using the Version Management feature in Devolutions Server. You can find it under:
Administration > System Settings
There, you can define minimum and maximum supported RDM versions to ensure all users are aligned with your environment requirements.
Let me know if you need further clarification or have any additional questions I’ll be happy to assist.
Best regards,
Michel Audi
Hi,
when we update RDM the first the datasource in DVLS is going into read-only mode. I understand it to keep the database consistent. Basically this means that you have to update the DVLS right after the client update or visa versa. 
8bbd2bce-555c-4b20-a88f-9dcac01a81f5.png
Hi,
The recommended update sequence is to first update your Devolutions Server, followed by Remote Desktop Manager. As I mentioned in my previous message, using DVLS 2025.2 with RDM 2025.1 should still work; however, some features introduced in DVLS 2025.2 may not be fully supported by RDM 2025.1.
I also just received confirmation from a colleague that the yellow warning message you're seeing is a known bug. Our development team is currently working on a fix. So even if you're running RDM 2025.2 with DVLS 2025.1, you should still be able to work normally despite the Read-Only prompt.
Could you please confirm if that's the case on your end?
Best regards,
Michel Audi
Hi,
the problem we had was that we can checkout a account in PAM but can't select a extra right such as DomainAdmin.
We have now update the client and the server so the problem is gone.
The next time we first update the server and after that the client
Hello Freddy,
Thank you for your feedback glad to hear it's working now.
Feel free to reach out anytime if you need assistance.
Best regards,
Michel Audi