After a long time, I came across the RDP protocol again: I thought no one used it anymore. But instead, I discovered that it’s alive and well. Here’s how to use it from macOS, without spending a penny — yes, because there is also a paid version. It’s much quicker and easier than expected.
Why Should I Use the RDP Protocol?
You shouldn’t. Or rather, I know more reliable methods for communicating between operating systems for the same reason, but recently I found myself unable to avoid it. I was taking a course (see Workload Manager Validation for SQL Server) on Google Cloud Platform that required me to use it.
Chrome for Windows natively supports the URL handler for the protocol, so you don’t need to download anything to use it. The problem arises if you use macOS or Linux: do not confuse this feature with Chrome Remote Desktop, available on all operating systems, which uses a proprietary protocol to do the same thing.
Apple provides a paid application on the Mac App Store that is sold in Italy for €89.99, but it does not support the RDP protocol. This is not the solution I will recommend you use in this article. I almost fainted when I saw the price, fearing that it was the only possible solution.
Install Windows App From the Mac App Store
Previously Microsoft Remote Desktop, Windows App is a free application that allows you to control your computer remotely. It includes a number of features, among which the graphical interface for the RDP protocol stands out, representing the primary function of the application.
The app recognizes files with the .rdp extension that can be imported to obtain a preconfigured connection. Typically, these configuration files load default credentials to which others can be added. In my case, I had to set a new password directly from GCP, because the instance was a virtual machine in the cloud.
My use was related to GCP’s Compute Engine, so I connected to a virtual machine instead of a physical computer. In any case, Windows App allows you to connect to any instance of the operating system, regardless of where it is installed. Let’s take a look at how to configure the application and use it wisely.
Configure and Save Connection Settings
Remote desktop connection requests are saved as connections: they can be to PCs or workstations. There are many ways to add a new connection. In my case, I had no choice and had to opt for importing an .rdp file. Once you have added a connection, you can also export it to an .rdp file to add it elsewhere later.
Otherwise, simply specify an IP address or hostname. You must have a username and password for an account that already exists and is authorized in the system in order to establish a connection. Years ago, I used the RDP protocol to control my desktop remotely: it’s a different use case from SSH.
It is no coincidence that we are using a graphical interface that allows access to the common functions of the operating system. In the past, but I believe still today, the RDP protocol was used for remote customer support sessions. Not exactly something closely related to software development as we would expect.
Run a Remote Session From Your Mac
By default, the session opens in full screen mode: it’s not something I’m crazy about. I discovered that I could avoid this in the settings, where you can also specify the resolution and color depth between 16 and 32 bits. Windows App also supports optimization for Retina Displays.
Just like when we virtualize an operating system, we can choose to share devices that are physically connected to the Mac with the remote connection. Options include the ability to share printers, smart cards, webcams, and microphones. The first two are selected by default.
Two other interesting features concern file and folder sharing and clipboard sharing. I must admit, however, that running programs and command prompts remotely is not very fast. Obviously, it also depends on my internet connection, but there must be a bottleneck somewhere.
The RDP Protocol Is Not the Best Solution
I know I’m repeating myself, but I wouldn’t use this solution if I didn’t have to. I wouldn’t use Windows at all. However, contrary to what I would have expected, I was able to use the remote desktop with relative ease. I just had a few too many slowdowns that caused me to lose precious minutes.
The workshop I was participating in was time-limited, and I was afraid I wouldn’t make it. Apart from that, without time limits, I would not have complained about the response speed of the remote operating system. I’ve had worse problems with locally run applications.
It’s more the concept that I don’t like. I mean, as a developer, it’s very rare that I need to access the graphical interface of a remote computer: working from SSH is more than enough for me. This was just a fun exercise that I wanted to share. Maybe it will be more useful to you than it was to me.
If you like, follow me on Bluesky and/or GitHub for more contents. I enjoy networking.
Top comments (0)