I have the same issue. I use a mac at home and windows at work. I use dual monitors at the office. When I remote in to the office from home (using Microsoft Remote Desktop), I cannot view my remote session on dual monitors at home. I can only view the remote session on a one monitor and the second monitor shows my mac. I use two monitors at the office and am finding it difficult to work from home because I'm only able to use one monitor. It seems the Microsoft Remote Desktop session just can't be split between the dual monitors.
I had the same issue with a new set up on my Mac using ipad as second display. When you open the Microsoft Remote Desktop app on your Mac select the "pencil" icon next to the "Bin" icon for the PC you are remoting to. The Edit PC window opens and then select the Display tab and check "Use all monitor". This will allow you to use MRD across all monitors connect to the Mac.
Hi I'm having the same issue. Up until last week I was able to connect into my VPN at work via MS remote desktop and work across both my monitor and my Macbook screen quite happily, drag and drop etc... Now I'm not able to do this. I'm updated to the latest Apple OS and Apple Support indicate its a third party issue ie with MS.
I've tried settings on the Mac. I have tried switching off "Displays have seperate spaces" but this just gives me a black screen on the second desktop and I cannot interact with it in any way. There doesn't appear to be any settings on the MS remote desktop app (Ive tried right click) that do anything. Has anyone found a fix?
OK. I don't have a dual screen setup as a rule, but I've connected my M1 MacBook Air to an Apple TV as a second non-mirroring monitor, and I can access a Windows PC using Remote Desktop on one screen and then move the cursor across to interact with the Mac on the other one. I'm clearly not understanding what your issue is.
I am trying to utilize information from one display to enter into a database on the other display. Eliminating the need to flip back nd forth thru the windows Not to see two displays on the remote side
Is it possible to add support for several monitors on MacOS, as it is on Windows? I currently work on 3 monitors and I would like to have RDP on fullscreen on 2 monitors and use one of the monitors locally. On windows you can replace the .rdp file, but on MacOS it doesn't work. In addition, on the windows, when connecting the desktop remotely to the azura, there is an option to select screens.
Switch off or close down(in case of a laptop) the screens you don't want to login into the remote session and then sign in remotely using "Use all monitors".
After the login is complete, start the shut screens.
Unfortunately, you have to use spaces to gesture to the Mac desktop. Then you have to make sure you only use the one monitor for the Mac and not that monitor(s) for the Windows session. Not the best solution, but it is workable.
Same issue. If I unselect "use all monitors" I get normal resolution on a single monitor. When the (previously working) "use all monitors" option is selected, not only do I only get one monitor, it shows at a very low (unusable) resolution. (also on a 2021 MacBook Pro 14")
In this release we've addressed display configuration failures that occurred when using the 2021 MacBook Pro 14" and 16" models with multiple monitors. Specifically, we handled scenarios where external monitors were positioned above the MacBook display. In addition, we addressed a crash on early versions of macOS 12, and fixed customer-reported smart card and folder redirection issues.
Thanks a lot, guys! I can confirm a new beta is working with 2 monitors on MBP 14" 2021 with M1 again, I got back also a good resolution (previously it was working only on 1024x768 or something else what looked worked on retina than the screen on my historic calculator from primary school).
I have the same problem again as before like @gfpcp and @mpgny. MB Pro 14" 2021 with M1, RDP 10.7.7. When I have "Use all monitors" checked, it will open just on one monitor. When Resolution is setup to "Default for this display" it opens in small rectangle with resolution very similar to my old calculator :D .(640x480 or something similar)
This is happening on 16" MacBook Pro M1 Max, when connected to 2 extended monitors and starting a remote session to a Windows machine. The remote session will only use 1 monitor with low resolution. The only solution I have now is like @mpgny to remain on an old Beta version 10.7.1 . Would love to see it fixed in a newer release, so I can update the application.
My IT department had Microsoft Support observe my computer and took notes. We tried a horizontal arrangement of the screens and that worked. It was when one monitor was placed beneath the other two that causes the app to fail. They said they were aware of this particular bug and would be building it into a future release. Probably not 10.7.8 but after that.
Thanks @mpgny for helping out. As mentioned, developers are aware of this issue and working towards a fix (multiple Tech Community threads tracking it), I will re-open the ticket to signify this! @gfpcp
Currently, my work around is to close my mac lid before I start the remote session, so when the session starts, I only have 2 display side by side, so the bug won't trigger, and I get 2 extended monitor in the remote session with good resolution. After the session starts, I can open my lid, the built-in monitor won't be connected to the remote session, but the 2 extended monitor stay with the remote session in a good state.
Hi, I'm getting the same issue on a 2021 16-inch macbook pro, using remote desktop 10.9.5. It was working in a previous version but regressed at some point. Using @Sonny1201's workaround works for me, thankfully! My display arrangement is this, with my laptop at the bottom and 2 4k monitors side by side.
I'm seeing the same issue on a brand new Mac Mini M1.
The only things conncted is: Samsung 4k monitor U32J590U via HDMI, MS Surface keyboard wireless and Razer Deathadder V2 Pro via 2.4GHz.
I have tried both normal and beta RDP client, connecting to RemoteApp.
Also same issue on mac mini. RDP 8 worked great, until Big Sur, then it started crashing on startup.
V10 and the beta are both so delayed as to be very frustrating to use. Tried plugging mouse directly into , mac mini (avoid the usb hub), made no difference.
I using my MacBook connected to an external 4K display (Gigabyte M32U) via a single Thunderbolt 3 cable.
Mouse and keyboard are both connected to the hub in the monitor.
I'm also connected via RDP Gateway.
Microsoft Remote Desktop is so laggy, it's completely unusable. I don't have this problem with any other application, it's only in RDP.
When using the built-in trackpad and MacBook keyboard everything is ok (not as fast and fluid as on Windows, but it's usable).
I'm running an older Intel-based Mac Pro, and I can confirm the same issue. For me, I'm watching a video in Microsoft Stream to ensure a constant feed of data over the wifi connection, and it seems the wifi connection is the issue:
It doesn't work with my G Pro X Superlight. However, that's a bug in the Logitech software. It doesn't accept changing polling rate...
However, I don't think it's an acceptable solution to set your mouse back to year 1995 ... all modern mice use 500 or 1000hz ...
These polling rates work flawlessly on the Windows version of Remote Desktop (same gateway, same target host) but they cause complete chaos with the macOS version.
That's a bug in the macOS RDP client and nothing else ... It's a shame that Microsoft doesn't respond in any useful way to this issue.
This problem is not related to hardware accl, it's definitely a mouse polling problem. It might not even be related to Mac only. There is another thread in the MS forums reporting the same problem on Windows machines:
-us/answers/questions/466590/remote-app-poor-performance-due-to-high-polling-ra.html
Thanks Ozberk. I did as you suggested to uncheck the "hardware acceleration." But the connection would start to slow down after a few minutes. However, the actual fix from seeing your screenshot. I also set the Graphics Interpolation Level from "Automatic" to "High." This fixed the issue.
My connection starts fast at first, but after a few minutes of use, there is more and more lag. Eventually, the lag would become unbearable and I kept having to turn off RDP, then reestablish the connection to reduce the lag. But the solution below completely fixed the issue.
HERE IS THE FIX: Go to the "Settings" menu in Microsoft Remote Desktop. On General Screen Tab, uncheck "Use hardware acceleration when possible" AND also set "Graphics Interpolation Level" from "Automatic" to "High." This completely fixed the issue.
When I try to connect via RDP to my company's network (using an RDP gateway), it becomes unusable as soon as I connect an external display to a brand-new MacBook Air. Disconnecting the external display renders RDP fine again. So it works correctly only if just the integrated display is used. I also tried Microsoft Remote Desktop Beta (10.6.2, 1874) without success.
UPDATE 1 (2020-04-19): I use an external LG 4K monitor. I have tested it with a Sony 4K TV now (actually with an AVR that is connected to the TV) and it works fine. So it seems to be related to the actual monitor somehow?
UPDATE 2 (2020-04-20): I am using a USB-C hub through which I connect my mouse, keyboard and display. I have found out now, that the issue occurs only when the mouse (Logitech G402) is plugged-in. It doesn't even matter if there is another external monitor connected. Even by unplugging everything else from the hub (i.e. only connect the mouse; no keyboard or display), it does not work. I tried with another mouse and it works as expected. Is it possible that the RD gateway somehow dislikes the mouse? Or the polling rate or something like that? I also tried to connect the mouse directly to the USB-C port with another adapter, and it does not work correctly in RDP. So it's not the hub's fault.
d3342ee215