Resolved

Structure best practices

avatar

Hello,

Currently, I use this structure.

|- Folder "Customer"
|-- Folder "Credentials"
|--- Password list entry
|-- Folder "Software"
|--- Software entries
|-- Folder "Sessions"
|--- VPN Session
|--- Folder "Device" (ex. ESX-01)
|---- Web session entry
|---- SSH session entry
-and so on...

I'd like to reorganize my sessions, maybe with host entries and also add some informations like purchase date, password expiration date, MAC address, devices configurations, contacts... but what would be the best practices for that?

I see there are lots of entries. What's the difference between "Company" in Folder or "Company" entry in Contact ?

Thank you,

All Comments (4)

avatar

Hello,

Thank you for reaching out to us regarding this,

  • Could you please specify the version of RDM you are currently using?
  • What type of data source are you using?


That being said, regarding your first point, it is possible to use the Assets section directly in the entry Properties for this type of information.

For your second point, I would recommend you create these entry types to see the difference, The Folder type is used to store entries, for example, RDP or SSH Session relating to this company, while the Contact Type has many additional fields that may be useful.

Of course, you could also use a regular folder without any issues,

Let me know if this helps,

Best regards,

Samuel Dery

avatar

Hello,

Thank you for your answer.

I am using version 2024.1.18.0 64-bit with Devolution Hub Personal.

Folders also have Asset properties, that's a bit confusing for me since you can create Asset entries.
I checked both entries, but I wasn't sure if there was a best practice of a "good organization" like for example, it's kind of better to use VPN session by inheritance to optimize the structure.

Regards,

avatar

Hello,
In discussing best practices for structuring in Remote Desktop Manager, it's important to note that there isn't a one-size-fits-all approach due to the versatile scenarios RDM can accommodate. However, a key principle to follow is to streamline your structure as efficiently as possible. Here are some refined strategies and recommendations:

  • Simplification: Aim to keep your structure straightforward. The complexity of your setup should be minimized to enhance manageability and clarity.


  • Using Folder Assets: Consider leveraging Folder Assets to organize multiple sessions. This method facilitates a structured approach and allows for the effective use of parent variables, which can significantly streamline management and inheritance of settings.


  • IT Assets and Hosts: While you can utilize IT Assets or Hosts with subconnections for organization, it's important to note that these do not support the creation of a nested substructure. This limitation is crucial when planning how to categorize and access your connections.


  • Reusing VPN Entries and Credentials: We strongly advise reusing VPN entries and linking credentials across your RDM environment. Treat credentials not just as mere access keys (like a website's username/password) but as comprehensive accounts. This approach enhances security and simplifies credential management.


  • Handling Contacts: Currently, RDM does not support linking a Contact Folder directly to existing entries. If managing sensitive information is not a significant concern, consider using the System Vault. This feature enables you to create and share entities such as Companies, Contacts, and Employees across different vaults, facilitating a more integrated and accessible system.


By adhering to these refined practices, you can optimize your Remote Desktop Manager setup for better efficiency, security, and usability. It's all about finding the right balance that suits your organizational needs while keeping the system as clean and straightforward as possible.

Regards

David Hervieux

avatar

Hello,

Thank you for this information, I see things more clearly now.

Regards,