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
- We are experiencing an issue with CredSSP and untrusted certificates enterprise wide affecting 100+ admins. First we had to run "defaults write com.microsoft.rdc.macos ClientSettings.EnforceCredSSPSupport 0" in terminal to resolve the NLA login issue. Which affected since it ignores the value of the parameter EnableCredSspSupport. then later we found our one of our RDS instances was using the self-signed cert to secure RDP traffic. Any windows client works just fine, but all the Macs broke that were on v10.2.x. We had to use Version 8 to allow RDP and remote apps. It may be a security hole of some sort but it would be nice to be able to choose if you trust the certificate being presented. We added the cert to test Macs to no avail but the v8 client will allow you to connect and choose to trust the endpoint. In v10.2.x it never prompts for the cert. Please help resolve the v10 issue before you get rid of the v8 client.
I am having the same issue as Ward and Thomas, using all my same credentials that worked fine to login using RD8, RD10 tells me I don't have access and won't let me log in. This is an issue as I use my iMac to create content for company servers which are Windows based. Along with other basic usability issues people are expressing (which I haven't been able to experience because I am unable to even log in), not being able to log in using RD10 and RD8 no longer functioning has made my work impossible, and I would like to see a solution to this major issue soon. Thank you.
Version 10.2.2 (1291) resolved all my outstanding problems with earlier releases of 10.x Loggin out from RDP when using gateways, hanging on sleep, adding new (additional) configuration files.
There is only one outstanding function point.
On a 2 screen setup, I want to use one in full screen mode and still view (and use) the other screen's contents (e.g. view a webpage or youtube video). Then allow a mouse click to switch back and forth activiating what ever is on the screen/window/app you choose. I do this on a PC all the time.
Instead, if you don't select "use all monitors" and you go into full screen more, the second monitor/screen is just black. This was the same behaviour in version 8.x as well.
I am not sure this is possible, but if it is - it would be helpful.
The new Remote Desktop for Mac stalls when accessing a remote computer. I can log in and access a file system and then the cursor doesn't respond. Only after I log out and log in again can I continue. This does not happen with the old version
- User experience is critical... So the very first thing that someone does when they launch version 10 is expect it to automatically retrieve all of the RDP sessions they have created in version 8. They are probably all stored in the registry (a horrible idea, btw) and so.... why did this not happen. I am loath to go rebuild all of these RDP sessions. How do I import them and why did it not happen automatically. Instead of providing a product I can immediately use, you obsolete the old one, tell me I must use the new one and then prevent me from using it. Did anybody in QA actually test this, because if they did they need to be fired.
How to use RD10 with connected additional monitor?
Previously with RD8 I used to use three-finger swipes to switch between screens on remote machines as well.
Now I cannot do it at all. I can drag RD session to second monitor but when I maximise it there I get small picture with identical size(not resolution) as my Macbook's screen.
Resolutions are almost the same 2560x1600 and 2560x1440(monitor)
When it can be fixed at least how we had it with RD8?
Thank you!
Using Microsoft Remote Desktop 10, the resolution of my 1920x1080 remote desktop is UNREADABLE, when remoting from my MacBook Pro 13-inch screen. Using Microsoft Remote Desktop 8, the resolution was perfectly clear. Therefore, version 10 is completely unusable for me. I will continue to use version 8. Thank you.
So far I have found I can copy the RDC for Mac version 8 from the Apps folder - compress it and save it off for new workstations, since it will eventually be removed from the app store. So far I found this works to manually just copy V8 on the new Mac, decompress and then copy into the Applications folder. Test with: 10.11; 10.13; 10.14 (release build). So backup your V8 RDC if you need it going forward.
I also found 3rd party Jump Desktop works when RDC 10 is not working, but in Jump Desktop I needed to disable the client side Network Level Authentication to connect to my resources. Jump Desktop is not free, but it works when RDC V10 is not working.In my case, version 10 has a new interface, but it has several issues.
1. It doesn't handle multi screens (if you choose 1 monitor, the other monitor goes black and is not useable. Typically you have a web browser on the other with instructions on what to do, you google around on the one to try and solve the problem, whilst applying the suggestions to the remote desktop session.
2. It poorly handles the system going to sleep. It never wakes up.
3. It poorly handles logging out, it just hangs
4. If you download an RDP file and double click on it, it doesn't give you the option to save it - it just disappears never held in the nice interface that someone has designed.
I don't see anything better from version 8 at present.
I'm having the same issue as Ward from above - can login np using Version 8 with login credentials/pw - but won't let me login to version 10 - says password is a problem. Real real real big pain in the neck.
