Devo latest updates
Hello,
We currently have server at 2023.2 and clients at 2023.2. But a few of our admin staff are on client 2023.3 and have reduced functionality. what is the most ideal way to update to cause as little disruption to our end users? If we update to 2023.3 on the server side will end users be forced to update to 2023.3 to even use the application?
All Comments (1)
Hello Ross,
If there is a mismatch of the major version (2023.3 vs 2023.2) between RDM and Devolutions Server, RDM will be in read-only mode. This is the behavior your admin staff is currently experiencing. If you upgrade your Devolutions Server, the users on the 2023.2 version will have the same experience.
To that end, we recommend configuring the version management; it will prevent this problem. Just make sure to enable the "Disable check for update option": https://docs.devolutions.net/server/web-interface/administration/configuration/system-settings/version-management/
To enforce it even more, you could configure GPOs to disable the check for updates - https://docs.devolutions.net/kb/remote-desktop-manager/how-to-articles/group-policies/
Best regards,
Richard Boisvert