Alcedo RDP is a free remote desktop client for Mac and Linux by Terminalworks. It connects to Windows PCs and servers over the Remote Desktop Protocol (RDP), and to Azure Virtual Desktop, Windows 365 Cloud PCs and on-premises Remote Desktop Services. TSPrint, TSScan and TSWebCam are built in, so you can print, scan and use your webcam in the remote session.

Yes. Alcedo RDP is free on the Mac App Store, and the Linux packages (.deb, .rpm and AppImage) are free on the Alcedo RDP download page. TSPrint, TSScan and TSWebCam on the server are licensed separately, and each has a free trial.

Yes. The Mac guide and the Linux guide cover setup, every connection setting, cloud workspaces, keyboard shortcuts and troubleshooting. In the app, the same help is under the ? button in the sidebar.

For a remote desktop session, nothing extra: Alcedo RDP connects to Windows desktops and RemoteApp programs over RDP like any other client.

Printing, scanning and webcam need the matching Terminalworks product on the server: TSPrint 3.2.4.34, TSScan 3.5.5.6 or TSWebCam 1.0.9.10 or later. Earlier versions are not supported.

Edit the connection and turn on TSPrint, TSScan or TSWebCam on its Resources tab. For an Azure Virtual Desktop or Windows 365 resource, use Session Settings on its card. Everything on the Resources tab is off by default except the clipboard, so turn on only what you need.

1. The TSPrint, TSScan or TSWebCam server component is installed on the remote computer, in a supported version (see What do I need on the server?).
2. It is turned on for the connection, on the Resources tab or in Session Settings.
3. Your computer lets Alcedo RDP use the device: on Mac, allow the camera in System Settings › Privacy & Security; on Linux, see My scanner or camera isn't found.

Yes. Sign in with your work or school account (Microsoft Entra ID), and your Azure Virtual Desktop workspaces and Windows 365 Cloud PCs are listed next to your own connections.

For on-premises Remote Desktop Services, add the RD Web Access feed URL from your administrator; it usually ends in /RDWeb/Feed/webfeed.aspx.

Yes. RemoteApp programs from Azure Virtual Desktop workspaces and Remote Desktop Services feeds open as individual windows on your computer, not inside a full desktop.

Yes. Alcedo RDP imports the .rdp files that Microsoft Remote Desktop saves, and connections exported from Alcedo RDP on Mac or Linux. You can export your connections the same way, as .rdp files or one JSON file. On Linux, exports never contain passwords.

On Mac, in your macOS Keychain, when you turn on Save password in Keychain. On Linux, in your desktop's keyring (GNOME Keyring or KDE Wallet). Passwords are never written to disk in plain text.

The error message (“We couldn't connect to the remote PC” on Mac, “Connection failed” on Linux) names the cause. The common ones:

• Wrong address or port: check the host name or IP address, and that port 3389 (or your custom port) is reachable. A firewall or VPN may block it.
• Remote access is off: on the Windows PC, Settings › System › Remote Desktop must be on and your account allowed to connect.
• Sign-in failed: re-enter the password and add the domain. For a local account on the PC, type .\ before the user name.

Windows Server needs Remote Desktop licensing (RDS CALs) after its 120-day grace period. If the server can't reach a license server or has no licenses left, it refuses the session. Only the server administrator can fix this; Windows 10 and 11 Pro PCs never need these licenses.

Windows allows one active connection per user session. When you, or someone using the same account, connects from another computer, that computer takes the session over. Reconnect from the computer you want to use, and the session moves back.

On the first connection to a server with a self-signed or otherwise untrusted certificate, Alcedo RDP shows the certificate and asks whether to trust it. If the certificate of a server you use every day suddenly changes, check with your administrator before you accept it.

Use Report an Issue in Alcedo RDP, or email [email protected]. Include the error message or code, the Windows version of the remote computer, and your macOS version or Linux distribution.

macOS 12.4 or later, on a Mac with Apple M1 chip or later.

No. Alcedo RDP needs a Mac with Apple M1 chip or later. If you use TSPrint or TSScan, their original clients for Intel-based Macs are on the TSPrint and TSScan download pages.

Download it for free from the Mac App Store. Updates come through the Mac App Store as well.

Alcedo RDP runs in the macOS App Sandbox. Add folders through the connection's Folders list (Add Folder), which gives Alcedo RDP access to them.

The camera and microphone need the permission macOS asks for on first use; if you declined it, allow it in System Settings › Privacy & Security.

Use Session › Send Ctrl+Alt+Delete (⌥⌘⌫), or Send Windows Key in the same menu. In key combinations, ⌘ acts as the Windows key: ⌘+E opens File Explorer and ⌘+L locks the remote PC.

Match Window (Settings › Display) resizes the remote desktop to fit your window, but it needs Windows 8.1 or Windows Server 2012 R2 or newer. Older servers keep the resolution set in the connection, and the window scales the picture instead. After a resize, the remote desktop may take a second to follow.

Very old servers may not support the security levels Alcedo RDP offers. Ask your administrator whether the server allows TLS and Network Level Authentication.

• x86_64: Ubuntu 22.04, Debian 12, Linux Mint 21, Fedora 40 or later. Other distributions with the AppImage and glibc 2.35 or later.
• ARM64: Ubuntu 24.04, Debian 13, Fedora 40 or later. Other distributions with the AppImage and glibc 2.39 or later.

It runs on Wayland or X11, with GNOME, KDE Plasma, Cinnamon and other desktops.

The .deb package for Ubuntu, Debian, Linux Mint, Pop!_OS and Zorin OS, the .rpm package for Fedora, and the AppImage for any other distribution. Most PCs need x86_64. If you are not sure, run uname -m in a terminal: aarch64 means ARM64.

Download the package from the Alcedo RDP download page, then install it from a terminal:

• .deb: sudo apt install ~/Downloads/<file>.deb
• .rpm: sudo dnf install ~/Downloads/<file>.rpm
• AppImage: chmod +x ~/Downloads/<file>.AppImage, then run the file. It adds itself to your app menu the first time it runs.

The download page shows the command with the exact file name. Double-clicking an .rdp file then opens it in Alcedo RDP.

The AppImage needs FUSE 2. Install libfuse2t64 on Ubuntu 24.04 and later, libfuse2 on older Ubuntu and Debian, or fuse-libs on Fedora.

To update, install the new version the same way; your connections are kept. To remove Alcedo RDP, run sudo apt remove alcedo-rdp or sudo dnf remove alcedo-rdp, or delete the AppImage file.

The server, or a firewall that inspects TLS in front of it, rejects the modern handshake this client offers. Click Retry with legacy TLS on the error screen to connect once. To keep it for that connection, turn on Legacy TLS compatibility on its Gateway tab.

It is a small security downgrade, so use it only where needed; the real fix is a certificate or TLS update on the server.

Passwords are kept in your desktop's keyring. Without one (a minimal window manager without GNOME Keyring or KDE Wallet, or a locked keyring), saving fails and Alcedo RDP asks for the password every time. Start or unlock your keyring, or install gnome-keyring.

Your user needs access to the devices: usually membership of the scanner and video groups, or the udev rules your distribution installs with SANE. Alcedo RDP lists the scanners SANE finds (what scanimage -L shows) and the cameras your system provides through Video4Linux.

Alcedo RDP prints through CUPS to the printers set up on your computer. Printing to the TSPrint printer in the session opens Alcedo RDP's Print dialog, where you choose the printer, paper and tray.

TSPrint Server must be installed on the remote computer. If a job never arrives, send us the TSPrint log (see How do I collect logs for support?).

Some desktop environments catch these shortcuts before Alcedo RDP sees them. Use the session in full screen, or change the shortcut in your desktop's keyboard settings.

No. Text and images are copied both ways while the clipboard is on for the connection, but copying and pasting files is not supported. To move files, share a local folder with the session (Local folder share on the Resources tab).

Every launch writes alcedo-app.log and alcedo-freerdp.log to /tmp. For printing, scanning or webcam problems:

1. Turn on Developer mode in Settings › General.
2. Turn on the log for TSPrint, TSScan or TSWebCam in the connection's Logging tab.
3. Connect, reproduce the problem, and attach tsprint_debug.log, tsscan_debug.log or tswebcam_debug.log from /tmp to your email to support.