First published on CloudBlogs on Jul 13, 2018 by Enterprise Mobility + Security team
The Microsoft Remote Desktop 10 client for macOS with its redesigned user experience and new code base has been available in the App Store since last November and the feedback has been incredible, helping us continuously improve the client. As more and more customers have switched to the new client for their daily usage, we are now preparing to retire the older Microsoft Remote Desktop 8.0 version from the App Store. To that end, on September 1, 2018, version 8.0 will be retired and only version 10 will remain available for download. If you are one of our macOS customers, now is the time to download the new version, test all familiar scenarios, and give us feedback for any issues or concerns you might have before September. Submit your feedback through Help > Report an issue in the client or request additional functionality via our UserVoice Suggestion box . We look forward to your feedback, comments, and help in ensuring the new client meets all your needs.
Blog Post
48 Comments
Our use - in case it is useful
We use version 10 a lot on Win2012 and Win2016, always via an MS Gateway and aren't have the problems you mention. We have now stopped using Version 8. Over the 800+ RDP users on our system, perhaps 10-15 use Mac and I think all now are using V10.
Re the comment on Gateways
We use the Windows created RDP file as the basis of the configuration on the Mac, that uses our own servers MS Gateway install - not a cloud vendors. It would surprise me is AWS had anything that wasn't the MS version - but really I don't know as I have never used it The only change we make is to the monitor size once loaded. It now all seems to work for us.
Ooh for petessakes... keep the 8.0 client forever because every time I use the version 10, our 2016 Server hangs for good for about 8-10 minutes !!!!
And yes, any RD client, be it on Windows 10, Windows 7, will cause out 2016 Server to hang.
The RDP v10 client does not support AWS gateways. I have the exact same configuration in RDP v8, and I'm able to access the remote Windows machine. I have imported the RDP profile to both RDPv8 and RDPv10. Gateway configurations are also the same.
I have noticed however, that when editing the gateway configuration in RDPv10, it keeps defaulting the account back to the desktop selection, and not my configured Microsoft cloud account.
Has anybody else seen this problem? Does anybody else use a gateway to reach through to a Windows machine in AWS?
10.2.13 on Mojave 10.14.4 crashes at least twice per day for me, more often if I'm connected to more than one remote machine at once. "Crashes" means stops responding completely until it's killed with force quit. I don't have any problems with 8.0.44.
Please don't discontinue 8 until 10 works.
The one issue that is still not working is an RDP file using a secure connection broker and RDP farm. I can import and use the file in V8, but the V10 app cannot complete the connection.
kafelatte You can no longer run 10 on Sierra so I'm not sure how you would do that
That is NOT good news! I have to remain on Sierra for business needs. Still using MRD8 while the bugs are shaken out of 10. Anyone know if importing settings from 8 to 10 ruin the 8 setup? I can't lose access to work just to test 10 for the same issue.
Microsoft Remote Desktop 10 no longer works on my Mac Mini running Sierra (10.12.6). This happened after the most recent update. You can’t open the application “Microsoft Remote Desktop.app” because it is not supported on this type of Mac.
yep
I find it now compatible with Version 8 except in two areas.
1. When you install it, can it prompt you to delete old versions that includes the app that came with Office 2004 and 2008. Or at least make the new version the default app for RDP files.
2. The feature of moving between the remote session and the mac desktop breaks multi screen mode. If you click the green window button to make your window small, then click it again to re maximise, it goes back to one screen, but worse the other screen is still there, you just can't get to it. Thus at present you can only click out and log completely back in again.
