Mac RDP Client Wishlist

There seem to be quite a few IT professionals out there that have chosen Mac OS X as their primary computing platform. While some of them may have environments that are predominantly UNIX or Linux-based—Macs seem to be particularly common in heavy Solaris environments—I would hazard to guess that a larger majority of them have Windows-based environments that they must support. As a result, a good Remote Desktop client for connecting to Windows-based servers is a valuable piece of software to have.

In search of that ideal Remote Desktop client, I’ve been through a pretty fair number of Remote Desktop clients and related software. While each of these clients has their own strengths and weaknesses, I have yet to find a Remote Desktop client that has what I’d really like to see.

Here’s my “wish list” for the perfect Remote Desktop Connection client:

  • It’s an Aqua-native application with a Universal binary. Hey, I still have some old PowerPC-based Macs at home.
  • It doesn’t interfere with Quicksilver.
  • It supports multiple sessions in such a way that I can switch between these sessions as easily as I could switch between multiple browser windows, multiple Finder windows, or multiple Word documents. That means it should play well with the Dock (single icon on the dock with a pop-up listing all the windows/connections), Expose (Application Windows, or F10, should show all connections/windows, like it would for Safari, Mail, or Finder), and Spaces, if running on Leopard.
  • Full Leopard compatibility, of course.
  • Support for Mac OS shortcuts in the Windows session, so that I don’t have to remember Cmd-C in Mac OS versus Ctrl-C in Windows.

So far, I’ve tried just about every Remote Desktop client out there: Microsoft’s Remote Desktop Connection (including the new beta version), TSClientX, and CoRD. Am I missing any significant contenders?

If anyone would like to suggest a Remote Desktop client, feel free to cast your votes and voice your support in the comments below. Thanks!

Tags: , ,

  1. Derek Morr’s avatar

    I agree with everything on your list. MS’s RDP 2.0 client is close, but not quiet there yet. One thing I’d like to see that isn’t on your list is IPv6 support.

  2. Ausmith1’s avatar

    I’d like to have console session support for 2003 and 2008 servers, if it’s in the new MS RDP beta client, I sure can’t find it…

  3. slowe’s avatar

    The old Microsoft client allowed you to push Option (or Command, I can’t recall) to connect to the Console session for Windows Server 2003. I don’t have a Windows Server machine handy right now to test the new version, but I’m guessing that behavior didn’t make it?

  4. wing figgles’s avatar

    in Server 2008 you can publish apps natively via RDP so cmd or powershell can be easily accessed via the web. Just like Citrix PS does today.

  5. Greg’s avatar

    @wing figgles

    Windows 2008 Terminal Services RemoteApp requires the ActiveX control only available via the Remote Desktop Connection client version 6.1. Only Windows 2008, Vista SP1 and XP SP3 have this client. Not to mention that ActiveX will never work natively on a Mac anyway…

  6. Michael’s avatar

    Try CORD out. It does most of the things you want.

  7. Scott’s avatar

    I use a solution of X11, rdesktop, and Applescript. First I installed X11 from system discs or from X11 website, then downloaded and setup rdesktop (instructions on rdesktop’s website). Then I wrote a basic Applescript to execute the Terminal commands for rdesktop. I duplicated the script and have one for each server I connect to so I can call the script from Quicksilver quickly.

    One tip though, when writing the terminal command make sure to end it with “;exit” so that the Applescript session will stay open until you exit the X11 window. Otherwise the Applescript will immediately exit your X11 session. If you want I can send you the full script I am using, just shoot me an email.