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
Deprecation of the Remote Desktop 8.0 client for macOS
48 Comments
- Fabian1835Copper Contributor
I can´t install the new version because of the macOS High Sierra my computer has. And I can´t update to a new macOS 12, due to requirements. Any solution?
- millercombinationcom330Copper Contributor
RDP 8 quit working on my mac (Big Sur). Too bad because V10 and the beta V10.7.1 have so much latency in them that they are near useless. I have been working on a Mac mini, RDP to Windows 2016 server in the same room. It takes 2 seconds to position the cursor over a button due to the delay.
Regrettably, this product follows the general rule that every piece of new software is inferior to what it replaced:(
I will have to put a head on the server, at which point may as well move my environment to Windows and quit using the Mac. What a shame.
- mwestermannCopper Contributor
It's astounding to me how little MS seems to be paying attention to the Gateway auth problems for Mac users. Trying to troubleshoot this issue for my users is maddening. Only *some* mac users get the apparently common "Unable to connect" error. I don't have a problem either on my Mac or my Win10 vm, no other windows users at our company do, but I've got frustrated subset of Mac users that can't connect to the systems I support. I've had to set up regular RDS via a single host for them to be able to get onto systems. Search this error online and you'll find a lot of complaining and no support from MS. It appears it must be a Mac RDP Client 10 bug. Is there any plan to address this?
- berkeleykhanCopper Contributor
I love version 8.0
I will not upgrade.
- Karishma11Copper Contributor
Amazing article sir. A great information given by you in this blog. It really informative and very helpful. Keep posting will be waiting for your next blog.Thank you.
- RobertCoxCopper Contributor
I can now answer my own question. There is a bug in Apple Microsoft Remote Desktop 10 when storing the username only.
If you store your username only, under "user account:" where it normally says "ask when required" then when using DUO 2FA is asks for authentication twice (I tried 2 different forms of DUOs 2FA). If you remove it [the stored username], put it back to "ask when required" it goes back to asking once, but then I have to type my username into the field when logging on. I hope two things:
1. A Microsoft person will picks this up and resolves - I am happy to test if you wish - easily repeatable
2. It helps someone who has this problem
Regards,
- RobertCoxCopper Contributor
We recently implement DUO 2FA on our firms Remote Desktop Server (Windows2016). We setup DUO so that my home's IP Address is the second factor to allow me to work from home without being asked for the one-time number from the DUO App. After we did this the following always occurs.
I am asked twice for my password (noting around 40 times to date - thus "I know" I am not typing my password wrongly the first time everytime!).
* The first time, Remote Desktop software (password entry dialog) says incorrect password
* the second time it works. - logs me in cleanly.
I have also tried this with two test accounts on our system - same issue occurs - it is 100% reproduceable. Duo logs (according to my techs) say there was only ever one connection logged - almost like Remote Desktop didn't send the first one!
I am organising for a test Mac and a bunch of other options to test with moving forward.
But before I start that - has anyone else seen this problem?
- jwyattCopper Contributor
Remote Desktop V10 makes my Mac cpu fan run constantly, V8 does not. Why does V10 use so much more resources.
- eoportovitechCopper ContributorThe v8 client has cli capability if you call "/Applications/Microsoft Remote Desktop.app/Contents/MacOS/Microsoft Remote Desktop" but this does not seem to the the case for Microsoft Remote Desktop Beta.app. The v10 client also does not provide a means to quick connect to an IP with a default set of options, instead requiring you to go through the steps of adding a system.
- adelaraCopper Contributor
Thanks Robert.
I will consider and mention a RD Gateway to the IT mgmt over here as we can't afford the problems we have right now.
-Alex