Microsoft Secure Tech Accelerator
Apr 03 2024, 07:00 AM - 11:00 AM (PDT)
Microsoft Tech Community
Deprecation of the Remote Desktop 8.0 client for macOS
Published Sep 08 2018 11:20 AM 1.4M Views
Community Manager

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.

47 Comments
Copper Contributor

excelente aplicación mil gracias


@TechCommunityAPIAdmin wrote:

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.


 

Brass Contributor

Will version 8 be made available for download, once pulled from the app store, for users that still depend on V8 for authentication to RDS through 3rd party SSO provider - example: pgina fork:  http://mutonufoai.github.io/pgina/documentation/rdp.html

 

RDC for Mac V10 upto Version 10.2.1 (1143) continues to not work with pGina for Auth.  RDC for Mac V8 works fine.

 

Config:

RDS on 2012 R2 using pGina for external ldap authentication. 

Copper Contributor

Here are a few requests. PLEASE look at including these. 

 

1. Can you make it so that when you scale the content, you have an option to maintain aspect ratio? 

 

2. Can you make it so we can just reorder them any way we want? Alphabetical is an option, but not always preferred. 

 

3. If I have 40 machines all connecting to the same domain, with the same creds, why can't I just refer to the single credential instead of having to store them over and over as individual items?

Copper Contributor

If I have 90 machines all connecting to the same domain, with the same logins, why can't I just refer to the single credential instead of having to store them over and over as individual items?

CCNA Course in Pune

Copper Contributor

Hi, I cannot set up a remote session with the new App on my iMac. I use the exact the same credentials which I use in the old app. 

The new app states that my name and password did not work. With the old app, it works fine. All other settings are the same.

I've already submitted my feedback via Help > Report an issue but no reaction from Microsoft there.

 

Anyone a clue what could be wrong?

Kind regards, Ward

Copper Contributor

How do I install the all modifications by of Microsoft 365 in my MacBook air ?. 

Copper Contributor

This is causing us a lot of issues. We can not import our RemoteApp RDP files into the new Program and there is no configuration in the 10 client to auto launch apps. Our users do not need to have full remote desktop access to the server desktop presented to them.

 

On import we get the error message. We couldn't import any desktops. We couldn't import any of your desktops because all the files are invalid.

 

Screen Shot 2018-09-24 at 3.28.18 PM.jpg

Copper Contributor

hi do i have to change to this new remote desktop? as im not confident in moving the data off 8 to 10?

Copper Contributor

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.  

Copper Contributor

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.

Brass Contributor

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.   

Copper Contributor

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.

Copper Contributor

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!

Copper Contributor
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.
Copper Contributor

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

Copper Contributor

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.

Copper Contributor

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. 

Copper Contributor
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.
Copper Contributor

There is a dual screen bug in v10.  If you minimise using the green button a dual screen setup, the maximise dual screens don't come back.  You get one screen working and the other black.  On the black screen you apps/windows are still running.  Thus it is only display issue.  To fix, I close out (red button) and log in again, which is painful particularly when you have 2 factor authentication to go through.

 

Another issue

It is not very intuitive to go back to the local Mac either.  In earlier versions of 10 and in 8, on the Windows menu there was a way to completely minimise windows by choosing an option on the menu.  That has disappeared and as such I use the function above, which is flawed.

Deleted
Not applicable

the new Remote Desktop 10 won't let you open the window on MAC taskbar. It shows the icon but doesn't pop up.

Copper Contributor

Dear Microsoft,

 

The Microsoft Remote Desktop version 10 with limited work Windows Server is not allowing me to connect it to my Mac files if I want to upload files from Mac to Windows Server using the app. Windows Server by our employer is all locked and limited, we are only allowed to use only one app in the Windows Server and we cannot modify any settings in Windows Server we have. The good thing about old Microsoft Remote Desktop version 8 is when I open a feed it asks me which folder do I want to connect in Mac which is the best thing ever life-saving! This feature is necessary to have on version 10 otherwise it's a big problem. Please make version 10 to ask me which folder do I want to connect in Mac so my Windows Server can have access to Mac files easily without needing to setup myself in Windows Server which I can't its all blocked.

 

Thank you for taking this comment seriously, I really need the feature passed for generations. 

Copper Contributor

Thanks, @JanusTrans! I was about to update, but without that feature (accessing the Mac drive), it will be useless. I'll stay on 8 until our IT Dept comes back with an alternative to MRD10 in its current iteration. Long live version 8!

Deleted
Not applicable

"...and the feedback has been incredible"

 

but it really hasnt????? why write this?

Brass Contributor
 
 

@JanusTrans 

@Deleted 


I don't have any issues with bringing folders across MRD10 when I connect to my windows devices.  I manage all kinds of Windows servers and desktops daily, and at current MRDS10 feature/fix level I have switched over to using version 10 exclusively. The group feature is so useful.  Also you can run both V8 and V10 and beta 10 builds side by side.  No reason to delete V8. 

What OS version are you running?  Are you using AFS on the drive/folder you are trying to connect?

They did change menus around in V10:

Select the config you want to add local folder to.  Connections menu - Edit desktop.  Or right click (ctrl click) edit.  Select Folders. 

If you manage a ton of RDS configs, the groups feature is such a time saver. 


Microsoft

Thank you all for your feedback. Version 8 will not be available for download once it is pulled from the App Store. 

 

@JanusTrans / @kafelatte: You can select which folder to connect to in Preferences > General in V10. 

 

@Debra Hansen / @Robert Cox: We will investigate the display / resolution bugs you are experiencing. 

Copper Contributor

@briantaintor I have tried the Preferences > General in V10 it doesn't work as the administrator's Windows Service is disabled many features and options and limited me to use just a company software so with V10 there is no way for me to connect it to my Mac OSX Desktop but with V8 I am able to do that. It is sad V8 is no longer available so that means I am pretty much stuck and cannot use Microsoft Remote Desktop anymore. 

Copper Contributor

@briantaintor I have tested the new Version 10.2.9 (1575) it is working well so far I am able to upload files from my mac desktop.

 

There is another problem with the mac menu bar on the top ... when I want to close a window in Windows Server by moving my mouse to top-right corner to click red X box then suddenly mac menu bar drops down blocks me from closing the window ... very annoying. VMWare doesn't drop down the menu bar until 5 seconds later I think Microsoft Remote Desktop should have it same behavior to wait 5 seconds before dropping down the menu bar.

Copper Contributor

"the feedback has been incredible" <-- except it hasn't been.

 

I share the same thoughts as @Rickyspanish.  The feedback on the app store has been mixed at best, with some incredibly negative comments that are not infrequent.  Resolution issues, blurry text, overheated CPU, slow response are some of the things that are mentioned in reviews.

 

Has these issues been addressed sufficiently?

 

Edit: Tested the new version and lost my cursor while working in Outlook in the new client.  Blurry text issue is real.  Please do the community a favour and make it the great client that is a worthy successor to v8.

Copper Contributor

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.

Copper Contributor

yep

 

Copper Contributor

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.

Copper Contributor

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.

Copper Contributor

@kafelatte You can no longer run 10 on Sierra so I'm not sure how you would do that

Copper Contributor

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. 

Copper Contributor

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.

 

 

Copper Contributor

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?

Copper Contributor

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.

Copper Contributor

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.

Copper 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

 

Copper Contributor
The 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.
Copper Contributor

Remote Desktop V10 makes my Mac cpu fan run constantly, V8 does not. Why does V10 use so much more resources. 

Copper 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?

Copper 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,

Copper 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.

CCNA Claases in Pune

Copper Contributor

I love version 8.0

I will not upgrade.

Copper 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?

 

mwestermann_0-1605820192177.png

 

Copper 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.

 

Version history
Last update:
‎May 11 2021 02:06 PM
Updated by: