Keep RDM license when switching DVLS data sources with different users?

Keep RDM license when switching DVLS data sources with different users?

avatar

Hi!

We have our RDP licenses assigned through DVLS. A few users have a second account with admin privileges on DVLS.



Right now we need to assign both accounts a RDM license, because otherwise you get a "Invalid license" error when you try to log in from RDM. You can still log in to DVLS web without a RDM license.


So it appears the RDM license is checked server-side in DVLS, and you can't log in even though the user has a DVLS license and RDM is licensed through another account.

Would it be possible to keep using the license of the previously logged-on user when temporarily switching to a named admin account?

Thanks!

870ab541-7f1a-415f-9c8a-3ed82b2727ff.png

545b6249-4be8-4576-8dcf-6d9769d84877.png

All Comments (4)

avatar

Hello Daniel,

It is now possible in the latest 2023.2 version to bind two accounts to the same RDM license. Please see this blog article about it.
https://blog.devolutions.net/2023/06/whats-new-in-devolutions-server-20232/#new-link-two-user-accounts-to-a-single-license

Let us know if you have further questions about this.

Best regards,

Érica Poirier

avatar

Thank you! I'll try that after the update

avatar

Hi!

Update is done! So when I link the two accounts, they share a license, but does it have any other impact? In the KB it says

The Linked Account feature allows users to associate another account under the same user profile. [...] The primary purpose of Linked Account is to enhance user convenience and streamline account management.


I don't quite understand this. What exactly is a user profile? What will be more convenient for the user?

I just want to make sure it doesn't change the permissions or settings when working with the unprivileged account.

avatar

Hello,

Thank you for your feedback.

This feature is reserved for sharing a license. There is no impact on the other features like the permissions.

I will verify with our documentation team to rephrase this sentence to avoid any confusion.

Best regards,

Érica Poirier