Show Check-Out Status inside Smart Folders in RDM
Hi everyone,
We use Remote Desktop Manager (RDM) together with Devolutions Server and rely heavily on shortcuts within RDM.
The background: for each customer we have linked VMs (jump hosts) that have all the necessary tools installed. On top of that, we make extensive use of the automatic check-out feature, so we can immediately see which jump hosts are already in use (occupied).
This generally works very well. However, due to the growing number of customers and jump hosts, we now have a very large number of entries, which is starting to have a negative impact on performance.
We've therefore been thinking about maintaining the VMs in only one central location in RDM and displaying them elsewhere using Smart Folders (or possibly something else that fits better). This works, but unfortunately the check-out status is not shown inside the Smart Folder (the red marking that indicates an entry is checked out, which for us means "occupied").
My questions:
- Would it be possible for future RDM versions to also display the check-out status within Smart Folders?
- Or are there better/alternative solutions to achieve this?
Thanks in advance for any suggestions.
Best regards
All Comments (2)
Hello,
To improve performance when working with a large number of entries, we generally recommend dividing them across multiple vaults for example, one vault per user or team, depending on how your environment is organized.
Regarding displaying the check-out status within Smart Folders, this functionality is not currently available and would be considered a feature request.
Would you like me to transfer this forum post to the Feature Request section so our development team can evaluate it?
Best regards,
Carl Marien
Hello,
Yes, of course we are aware that it would be better to split this across multiple vaults. However, we are facing the issue that entries such as our jump host credentials cannot be made available across multiple vaults, including visibility of the check-out status.
If there is no better solution for the topic mentioned above, I would kindly ask you to convert this into a feature request as suggested.
Best regards