Microsoft Remote Desktop Connection review: Free, native remote control

Microsoft Remote Desktop Connection : Free with Windows Pro or Enterprise

While Microsoft's Remote Desktop Connection (RDC from here on out) is free and excellent for basic remote control and file transfer, it doesn't ship with the more common Home version of Windows. Yes, you'll need to upgrade your PC to Pro or better if you want to remotely control it using RDC. (See our tips for getting Windows for cheap or free.)

If you do have an upper-tier version, Microsoft provides clients for Windows, the Mac, iOS, and Android so you can use just about any device to do the controlling. Yup, you can use and iPhone/iPad to control Redmond's pride and joy on their dime!

Microsoft Remote Desktop Connection: Setup

For users with computer chops, setup and use of RDC is no big deal—remote desktop control isn't rocket science. But it's a big deal if you're helping someone without said chops—RDC is isn't always the easiest thing to explain over the phone.

Given the proper version of Windows, you'll find the RDC settings under te.

Where programs such as TeamViewer or GoToMyPC only require installation, then receiving and entering a code, RDC requires enabling the feature plus finding information that less knowledgeable users must be coached through locating. In Windows 11, as shown above, enabling RDC is easy. It's less salient on other versions, though typing remote desktop into the search field will locate it easily enough.

At that point, on a local network you can simply connect via the local IP (e.g. 192.168.1.103). It's relatively easy to explain how to find this in the networking center. If you're connecting across the web, you'll need the public IP (e.g., 75.112.104.140). You can find these addresses in various locations, but the easiest for helpees is simply to browse to whatismyip.net/org/com (I prefer .net). It will be at the top of the page or someplace obvious.

If you can't connect by entering the public IP, you may need to unblock, or forward the port that RDC uses (3389 by default) to the computer you want to access. This varies by router, but is almost always labeled port forwarding. It's not difficult, but it is a pain to explain. You may also need to exempt the port in the Windows Defender Firewall.

The entire process gets even harder to explain when there are multiple computers on the home network. No lie, I often use TeamViewer or Chrome Remote Desktop to set up RDC for someone. It's quicker, especially as I change the RDC port to throw hackers off the scent.

This what you see when you launch Remote Desktop Connection under Windows. Click on More… under the Local Resources tab and you can transfer files between the remote and local machines.

Note that not all Home versions of Windows (7 and 8 for instance), were labeled as such. If you don't have Pro or Enterprise, you'll likely not find RDC.

Caveat: If you use direct-connect remote control software such as RDC, it's essential that you use a very strong password. As the default port is well-known, and open to the world. Password security is basically your only defense against hacking.

Microsoft Remote Desktop Connection: Features

RDC offers basic remote desktop control and very good scaling of the remote interface. As mentioned up top, there are clients for just about all operating systems and devices, though they don't generally offer file transfer. For that, I suggest an online storage service such as Dropbox or the like.

With Windows-to-Windows connections, file transfer is possible, even if the method is not immediately obvious. You must specify (click on More… as shown in the image above) that your local drives (on the controlling computer) show up in Windows Explorer on the remote PC. You can then transfer files using normal Windows copy/cut/paste methods. Even the network shares on the controlling computer will be available. Sweet.

Shown above is Windows Explorer on the remote computer display drives from the local, controlling computer. You can transfer files back and forth using normal Windows methods.

Beyond that, there aren't any bells and whistles such as chat. Note that in the pre-chat days, we simply opened a text file on the computer being controlled and used that for messaging if there was a reason a more efficient voice call wasn't possible. Cell plans weren't always unlimited if you remember.

RDC does have some unique Microsoft-centric capabilities such as audio and video integration when used with Teams. There's also further console oversight if used in conjunction with Azure Desktop, but that's only available to, yes, Azure users.

RDC also lets you save configurations into RDP files, which you can then use to connect from other devices. It's handier and less prone to mistakes than writing everything down. Especially if you're configuring multiple machines.

Microsoft Remote Desktop Connection: Performance

Across a local network RDC is extremely fast, especially between two Windows installations. That said, performance was still excellent when I used the macOS client, and passable when I used the iOS and Android clients. The main issue with the latter is all the scrolling required. I'm not complaining—that you can do it at all is fantastic.

This is Windows 11 being remote controlled using the macOS Windows Remote client for that operating system. iOS and Android are also supported.

Across the internet, nothing beats the direct connection offered by RDC. It's very agile, depending of course upon the speed of the connection. These days, that's generally pretty good.

Microsoft Remote Desktop Connection: Final thoughts

If the computer you want to control has the required grade of Windows, Remote Desktop Connection is a natural first choice for most users. If you're not willing to upgrade from Home, solutions such as Chrome Remote Desktop, TeamViewer (light/personal use), or VNC Connect are viable free alternatives.