RDM and Launcher | License management improvement

RDM and Launcher | License management improvement

1 vote

avatar

Good morning Devolutions

We have different users - business who are using Devolutions Launcher, and IT admins who are using RDM client. We are finding it difficult to manage licenses. At the moment, this is only possible per user. This is causing a lot of manual overhead, since we need to assign each user license manually (depending on their role).

Also, when the user is offboarded, cleanup is also manual.

We would ike to have possibility to use Active directory groups - to assign RDM and Launcher licenses separately. And also to remove license automatically once the user is no longer a member of the group.

All Comments (11)

avatar

Hi David,

Could you confirm which data source you are using? (SQL-Server, DVLS, Hub Business)

Have a good day!

Maxime Morin

avatar

Hi Maxime,

We are using DVLS 2024.3.4.0

avatar

Hello,

In DVLS, if you edit your license, you should be able to configure it to auto-assign to certain groups:


There are a few things to keep in mind:

  • A user will only be assigned a license when it connects through RDM or Launcher (so actually "using" the license). This means they will have to connect through Launcher first before seeing the "open with launcher" button in the web DVLS UI.
  • It's not currently possible for the unassignment to happen automatically if the user is removed from the AD group


We will open internal tickets to add the following:

  • Add a way to assign licenses to all members of a group directly through DVLS. This might take the form of an "assign to members of selected groups" button.
  • Add a way to automatically assign licenses to all members of a group. The DVLS scheduler could run periodically to automatically assign licenses to new members of the specified AD groups
  • Add a way to automatically unassign licenses when a user is disabled/deleted from AD. Similar to above, the DVLS scheduler would perform these actions automatically.


I think with these suggested changes, the workflow you're thinking of should be possible, and it would remove the limitation we currently have that necessitate the user to login through RDM/Launcher before getting the appropriate license assigned. We will also see if we can do this for Hub eventually.

Let me know if there's something I forgot or if I'm missing the point.

Regards,

Hubert Mireault

bb16561c-1618-433c-ae56-d8e266353395.png

avatar

Hi Hubert

That is exactly what we would need, thanks!

avatar

Hi Hubert, do you perhaps have a timeframe, when we could expect this to be implemented?

avatar

Hello,

Thank you for the confirmation. We will have to discuss this with the DVLS team. This is something we already had in mind as improvements but I don't think it's planned in a current roadmap.

Regards,

Hubert Mireault

avatar

Please push the request i need it

avatar

Hello,

Thank you for your interest. We are currently planning our next development cycle. I will try to add it to our roadmap. We will post back here once we have an update.

Best regards,

François Dubois

avatar

Hello @Maxime Morin,

I found that post and wanted to ask if there's a possibility to handle the exact same request when using RDM with "just" a MS SQL as a datasource?

Cheers,
Philipp

avatar

Hello Philipp,

Thank you for your interest. This product development is not currently planned for the MS SQL Server datasource. We're taking note of your feedback and will follow this topic to see if there's any additional interest or input from other users. We also want you to know that migrating to Devolutions Server is possible for free. It will allow you to use that feature in Devolutions Server.

Here are a few links:
Migration from SQL Server to Devolutions Server: https://www.youtube.com/watch?v=JmoEOMkp-QY
DVLS presentation: https://www.youtube.com/watch?v=3A7oA0WOxYI

Don't hesitate if you have questions; we will help you with pleasure.

Best regards,

François Dubois

avatar

Thx for the quick response on that Francois. I'll take a look at the proposed change.