RD Connection Manager is a comprehensive remote connection management and publishing solution. It supports the world’s most popular remote desktop management protocols and provides comprehensive functionality to help users and system administrators organize their remote connections in various environments within any organization. Administration is simple with the ability to manage accounts, groups, and permissions. Sensitive data, such as user account settings, are encrypted with SSL. Strong connection security is supported. A single sign on system allows a user to establish multiple remote connections instantly after logging in. Supported protocols include RDP v.5, RDP v.6, VNC, and Citrix ICA.
|Tags||VNC Remote Access Desktop Virtualization Server Administration Server Management ICA remote desktop remote control remote authentication server monitoring rdp vdi|
|Operating Systems||Windows Unix Java Capable Linux|
|Implementation||C C++ Qt 4.5 Visual Studio|
Release Notes: This release fixes the “New Version Available” notification issue, removes the unnecessary network scanning prompt, fixed the network scan error when servers could not be found, and fixed the ‘wxAutomationObject::ConvertOleToVariant: Unknown variant value type’ notification issue.
Release Notes: This version added the ability to remotely enable RDP access using AD extensions if you are a domain administrator.
Release Notes: The “Fast connection” dialog was fixed so that when selecting a connection, the appropriate protocol is applied automatically. Translation errors were fixed. The crash that occurred when entering an incorrect IP or hostname at Windows RDP connection was fixed. Update notification was fixed. An installer error was fixed.
Release Notes: This release adds the ability to switch sessions, multilingual support, notification of new releases, RDP protocol support via freerdp, full screen mode, and the ability to take remote desktop screenshots. This release fixes a backend crash, VNC session frames overlapping, moving a connection between groups, a problem when VNC server is not running, a problem when displaying a remote desktop screen, a crash when pressing Alt+f when there is no active connection, UI problems with alignment and sizing, a problem in which the connection tree disappeared, disabling of keyboard input when switching to full-screen, a crash when the wrong server name is used, and a crash when playing music on the server side.
Release Notes: For the Windows version, the implementation faced some issues. For instance, the tightVNC code is very dependent on WinAPI. The code was also made as a completed product and was not designed for creating a separate library. For the Linux platform, challenges arose from the fact that tightVNC was made as a monolith and it’s hardly ported. The main problems occurred while working in a multithreaded application in a single thread; there were issues with multilayered windows of a user's session display.