27-04-2026, 12:02 PM
Description:
I am submitting a feature request to implement a secure local caching mechanism (Offline Mode) for database-driven configurations in Rocket Remote Desktop.
Problem Statement:
Currently, Rocket Remote Desktop relies entirely on an active connection to the central database to retrieve and manage RDP desktop data. If this database becomes temporarily unavailable—whether due to network outages, VPN drops, server maintenance, or unexpected failure—users cannot log in to the application, view their resource lists, or initiate new connections. While currently active RDP sessions remain open and functional.
Unless there is an existing configuration setting that I am overlooking, this architecture introduces a critical single point of failure. In large enterprise environments, losing the ability to access the RDP infrastructure due to a backend database issue is an unacceptable operational risk that halts productivity and blocks IT administration capabilities.
Proposed Solution:
Implement an encrypted, local cache feature that periodically synchronizes with the central database during normal operation.
If the application detects that the central database is unreachable, it should automatically fall back to this local cache in a "Read-Only / Offline" mode. This would allow users to:
Business Value / Justification:
This is a critical functionality for enterprise deployments. I strongly request prioritizing the implementation of an offline caching mechanism to ensure the reliability and stability required in professional environments.
I am submitting a feature request to implement a secure local caching mechanism (Offline Mode) for database-driven configurations in Rocket Remote Desktop.
Problem Statement:
Currently, Rocket Remote Desktop relies entirely on an active connection to the central database to retrieve and manage RDP desktop data. If this database becomes temporarily unavailable—whether due to network outages, VPN drops, server maintenance, or unexpected failure—users cannot log in to the application, view their resource lists, or initiate new connections. While currently active RDP sessions remain open and functional.
Unless there is an existing configuration setting that I am overlooking, this architecture introduces a critical single point of failure. In large enterprise environments, losing the ability to access the RDP infrastructure due to a backend database issue is an unacceptable operational risk that halts productivity and blocks IT administration capabilities.
Proposed Solution:
Implement an encrypted, local cache feature that periodically synchronizes with the central database during normal operation.
If the application detects that the central database is unreachable, it should automatically fall back to this local cache in a "Read-Only / Offline" mode. This would allow users to:
- View their existing hierarchy of RDP connections.
- Initiate new RDP sessions using the most recently synchronized data and credentials.
- Maintain business continuity until the database connection is successfully re-established.
Business Value / Justification:
- Business Continuity: Ensures that critical infrastructure remains accessible to administrators and employees even during centralized database outages.
- Enterprise Readiness: Large-scale organizations demand high-availability tools. A strict dependency on a live database without an offline fallback limits the software's viability in strict corporate environments.
- Resilience: Provides a buffer against transient network instability, greatly improving the overall user experience.
This is a critical functionality for enterprise deployments. I strongly request prioritizing the implementation of an offline caching mechanism to ensure the reliability and stability required in professional environments.
