Devolutions Remote Desktop Manager
By Devolutions
Typical implementation process for Devolutions Remote Desktop Manager (RDM) and estimated time:
Define Requirements: Decide edition (Free or Team), data source type (local, Devolutions Server, SQL, etc.), and security policies.
Prerequisites: Ensure OS compatibility, .NET Framework, and admin rights for installation.
Download Installer: From the Devolutions site.
Install Client: Run MSI (Windows) or DMG (macOS) with elevated privileges; can be silent or manual.
Enterprise Deployment: Use a custom installer service or PowerShell scripts for bulk installs.
Time:
Choose Data Source: Local (SQLite), Devolutions Server, or cloud (Hub).
Set Up Team Folder & Vaults: For shared environments, configure permissions and roles.
Enable Role-Based Access Control & MFA.
Validate Connections & Permissions.
Devolutions Remote Desktop Manager (RDM) can be customized to fit a wide range of business needs. Key customization areas include:
1. User Interface:
Adjustable layouts (Ribbon or Classic view).
Customizable dashboards and widgets.
Editable keyboard shortcuts and UI themes.
2. Entries and Templates:
Custom entry types and templates.
Add custom fields and metadata to session entries.
Use “Template Groups” to standardize structures.
3. Vaults and Data Sources:
Flexible data sources (SQL Server, SQL Azure, etc.).
“Business Units” feature to group vaults per division or client.
Vaults can be restricted by content type.
4. Security and Permissions:
Role-based access control and permission sets.
Custom security policies and two-factor authentication.
Audit logs and sealed entries for controlled access.
5. Integrations and Automation:
Integrates with password managers (KeePass, Bitwarden, etc.).
Supports many protocols (RDP, SSH, VNC, ICA).
Global macro/script tools for automation.
6. Reporting and Monitoring:
Customizable audit and usage reports.
Free online training via Devolutions Academy: courses for beginner to advanced users, on-demand, covering RDM setup, features, integrations, workflows.
Documentation and help system: detailed user guides, step-by-step articles, in-app Help menu including an onboarding wizard.
Video tutorials and how-to series (e.g., “getting started” videos) for new users.
A forum community where users can ask questions, share best practices, and learn from peers.
Technical support via email ([email protected]), phone, email, and chat.
Support hours for standard support: Monday to Friday, 7:30 a.m. to 6:00 p.m. EDT in English, French, and German.
The security measures implemented by Remote Desktop Manager (RDM) from Devolutions to protect data:
All passwords stored in data sources are encrypted; the algorithm used is XChaCha20-Poly1305 for sensitive data, and AES (for FIPS mode) for local storage.
Local data (when stored locally) uses Windows Credential Manager on Windows – credentials cannot be viewed in plain text.
Data at rest in shared/multi-user environments can use “Security Providers” (shared passphrase, certificate, keyfile) to encrypt the database/file system so that both the database and the encryption key must be compromised to expose data.
Encryption in transit (TLS/HTTPS) is supported and strongly recommended, especially for cloud services or on-premises setups where remote clients connect to the data source.
Role-based access control (RBAC): granular permissions for who can view/edit/manage vaults, entries, and sessions.
Two-factor authentication (2FA) support: multiple options including YubiKey, Google Authenticator, Duo, etc.
Account brokering: credentials can be injected at session launch so the user never sees plaintext credentials, reducing the risk of credential exposure.
Offline mode and client access: administrators can disable offline mode to reduce local cache risk.
Audit logs, activity logs: records who did what, when, for which session; real-time connection monitoring is available.
Security Dashboard: built-in tool to assess security posture (e.g., password policies, master key usage, TLS usage) and guide hardening steps.
Integration with enterprise solutions (e.g., directory services) to meet regulatory/compliance requirements.
For maximum security, use advanced data sources (e.g., SQL Server/SQL Azure) and enforce encrypted communication to the database.
Use of master key, certificate-based encryption, and application password for local configuration files is recommended.
The official release notes page shows frequent version changes: for example, versions 2025.2.25.0, 2025.1.27.0, 2024.3.19.0, 2024.2.10.0, etc.
The verbiage “frequently offers new updates to release new features, improvements, as well as fixes” is used in their documentation.
From the historical data: major releases (e.g., “2024.1”, “2023.2”, “2022.3”) appear roughly every few months with minor updates in between.
Conclusion: Updates are released on a multiple-times-per-year basis (major versions every few months, interim patches/fixes more often).
RDM has a built-in “Check for update at startup” and “Enable check for updates” setting. Users can enable automatic checking.
Administrators can enforce minimal and maximal version policies for clients, from “System Settings → Version Management”.
Release notes detail breaking changes and dependencies (for example, requiring newer data source versions, .NET versions). Before installing, you should check the prerequisites.
Devolutions states that for certain cloud services (e.g., Devolutions Hub Business) they operate under a “zero‑knowledge” encryption model, meaning Devolutions (nor any third party) cannot access customer‑owned data.
For RDM installations where the data source is self‑hosted (e.g., SQL Server, local vault), the customer retains control of the data source. Devolutions does not claim ownership of the customer’s data.
In the “Deleting your data” page, they clarify that deleting the Devolutions account will not necessarily delete all data stored in external data sources of RDM. They recommend exporting data before deletion to retain access.
RDM supports export and import of entries and data sources. For example: you can export your data source (or entries) from one instance and import them into another.
Specifically, the documentation “Import and export a data source” notes you can export the data‑source configuration, then import it elsewhere. Note: the configuration export does not include the actual content of the data source; for full content you may need export of entries.
The “Import & export” page details that you can export entries in formats such as .CSV, .JSON, or native RDM (.rdm) to move between data sources or back‑up.
There is support for transferring the entire database when using a self‑hosted RDBMS (e.g., SQL Server) by using the RDBMS tools (outside of RDM) to move the database.
For Devolutions account data (cloud services), when you request deletion: data from product databases is deleted “within a 30‑day period” and backups are erased after 12 months.
Renewal Terms
Licenses (for many products) are renewed via the Devolutions Portal. You log in with the account that purchased the previous license, go to “Licenses”, find the license and click “Renew now”
At renewal, you may adjust the term (for example, 1 year or 3 years,) but cannot change the product(s) or number of users via that renewal path. To change users or products, you must contact Sales.
The subscription-based model (especially for the “Enterprise Subscription” version) states: if you do not renew when the subscription ends, “access to your data will be limited.”
Although some licenses are perpetual (you may continue using the version you have), software maintenance (updates, new features & support) requires renewal of the maintenance agreement.
Devolutions may amend the “Software License and Subscription Agreement” terms. Renewing or continuing to use the software after amendment constitutes acceptance of the new terms.
Cancellation / Termination Terms
Termination is addressed in the standard license agreements: upon expiry of the subscription period (or update period) or if the customer fails to renew, the agreement ends, or rights are limited.
If you terminate the Subscription Agreement in accordance with its terms, you may be eligible for a pro-rated refund of prepaid fees covering the remainder of the Subscription Period. If you terminate “for any reason or no reason” outside those terms, you will not be entitled to a refund of prepaid fees.
The EULA states that upon termination, you must immediately stop using the software and destroy all copies.
Other Relevant Points
The renewal/maintenance plan concept: maintaining a current subscription gives benefits like continuous updates, new features, and faster support.
The vendor, Devolutions Inc., is ISO/IEC 27001:2013 certified for its information-security management system.
Devolutions has also achieved ISO/IEC 27701:2019 certification (as of June 4, 2024) for its privacy-information-management system.
The company holds a renewed SOC 2 Type II report covering security, availability, processing integrity, confidentiality, and privacy controls.
RDM is compliant with the HIPAA Security Rule (for administrative, physical, and technical safeguards) when configured appropriately.
