User Guide
RDPlenty is an RDP client for macOS designed around simplicity, predictable behavior, privacy, and easy integration into larger workflows.
Rather than exposing every feature the RDP protocol can provide, it focuses on the parts that work well in normal Mac-to-Windows use, simplifies a few common annoyances, and adds automation features that are often missing from other RDP clients.
Designed for Mac users
A few behaviors are intentionally different from those of more traditional RDP clients.
The remote desktop is always scaled proportionally to fit the application window. If the remote resolution is larger or smaller than the window, the display is stretched or reduced as needed rather than surrounded by scrollbars.
The keyboard mapping is designed so that Mac keyboard habits continue to work naturally inside Windows. The left
⌘key acts as Ctrl by default, so ordinary Mac shortcuts such as⌘Sfor Save,⌘Ffor Find,⌘Afor Select All,⌘Cfor Copy, and⌘Vfor Paste all behave as expected. This is not limited to the usual special-casing of Copy and Paste.Clipboard sharing is either enabled in both directions or disabled entirely. There are no separate Mac-to-Windows and Windows-to-Mac modes to configure or accidentally leave mismatched.
Privacy
RDPlenty does not require an account or any cloud service, and it does not collect user data or track how you use the application.
In particular, the application does not collect telemetry.
The trade-off is that the developers do not automatically learn about crashes, connection failures, or other problems you encounter. If something goes wrong, it will only become known if you report it yourself. The application logs can be useful when diagnosing or reporting an issue.
Workflow integration
RDPlenty can do more than simply open a saved connection.
A pre-connect script can run locally before a connection is opened. This can be used to wake a sleeping machine, start a virtual machine, establish a VPN, or perform any other preparation required before RDP becomes available.
Connections can be started from the bundled command-line interface, through URLs or AppleScript, or from the graphical application itself. These interfaces make it possible to integrate RDPlenty into scripts, launchers, automation tools, and other workflows.
Features intentionally not supported
Some RDP features are deliberately omitted because they tend to work well enough in simple cases to appear reliable, but become inefficient or troublesome with larger or more demanding workloads.
File redirection and clipboard file transfer are not supported. Small transfers may appear to work perfectly, which makes it easy to assume that the mechanism is suitable for general file transfer. In practice, large files or directory trees can perform poorly, stall, or leave the application tied up while the transfer completes or fails. SMB,
scp, or cloud storage are better suited to moving files between Mac and Windows.Printer redirection is not supported. Cross-platform printer redirection depends on matching printer capabilities and drivers between Windows and macOS, and frequently works poorly as a result. It is usually simpler to print to PDF or transfer the document to the Mac and print it locally.
Other features not currently implemented
The following features are not currently supported. They may be considered in future versions if there is sufficient demand.
RDP Gateway
Smart card redirection
Microphone redirection
Camera redirection
Organizing saved connections into folders
Using this guide
Most of the application is intended to be straightforward to use without documentation. The pages in this guide cover behavior that is less obvious, configurable, or useful when integrating RDPlenty into other workflows.
Use the navigation sidebar to browse the available topics.
This documentation uses content from open source software packages.