Microsoft Remote Desktop Mac Extend Screen
Oleta Blaylock
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
Users in the financial sector and healthcare -- among many other industries -- are especially used to multiple monitor configurations, putting pressure on IT to adjust the settings to meet user needs. The challenge is getting remote desktops to detect and interact with local hardware when the desktop isn't running locally. Further, multiple monitors are turned off by default for remote desktops.
A key factor here is that enabling multiple monitors in Microsoft Remote Desktop Protocol (RDP) is an option the end user needs to enable on their Windows or Mac device. As an administrator, it is not something you can configure on the server side. As such, it might be a good idea to write up a good user instruction manual -- feel free to base it off these instructions.
Before IT embarks on this process, it's important to keep the limitations of multiple monitor RDP in mind. While it will be more than enough to have two medium resolution monitors, RDP users are limited to a maximum of 16 displays with a maximum resolution of 8192 x 8192. IT can also connect via RDP to a virtual desktop on a virtual server with multiple monitors. This will simply create a virtual desktop on the end user's monitors.
First, click on the search icon in the Windows start bar and search for "MSTSC/ MULTIMON." This will start up the RDP client in a multi-monitor configuration. From here, you can enter the server address, and it will automatically connect to the server full screen on all your monitors.
You can save the connection setting of the RDP session in the general tab of the RDP client. These settings will then be saved in an RDP file. You can edit this file within the client, or simply with the Notepad app.
After opening the RDP file in Notepad, you can change multiple options. But the one that configures multiple monitors is called use multimon:i:1. The number 1 means the option is enabled and 0 means the option is not enabled (Figure 2).
For macOS, there are two ways to enable multiple monitor support. The first way is to edit the RDP file with Text Editor in the same way as editing the RDP file on Windows. For macOS, the same setting for multiple monitor support is called usemultimon:i:1, where 1 means enabled and 0 means disabled.
The other way to enable the option in macOS is in the options of the RDP connection in the Microsoft RDP client. In the Display options, there is an option to enable Use all monitors (Figure 3).
It's also good to mention how to enable multiple monitor support on RDP within Igel OS. Igel OS is one of the most popular thin client OSes next to Windows. Within Igel OS, when setting up an RDP session, there is an option called True Multimonitor support. Enabling this option will allow multiple monitor support within Igel OS (Figure 4).
An RDP session will automatically detect the setting to use multiple monitors and run all available monitors. However, this may not be the best user experience in certain situations. Consider an example where you have three monitors and want to use local apps on monitor one and use monitors two and three for an RDP session. This can be configured with the selected monitor's option.
Published applications are applications that are loaded from an RDP session, but instead of showing the full remote desktop, the end user will only see the image of the chosen application. This should automatically work on multiple monitor setups. In addition, the end user can drag and drop the application screen to any connected monitor they like.
Using published apps also gives more freedom of use on the end user's device because it will appear that the remote applications are running exactly the same as any local applications making switching between these applications feel natural and normal. This is an excellent alternative for users who only need hosted applications and can run a native desktop for work. The method is especially helpful if the end user connects from a capable Windows device that also hosts local applications.
The symptom: the connection error occurs after authentication (filled still in the client app) and passing all the security checks phases. When the RDP screen is to be rendered (it is created but still all black), it gives the error.
I ran into the same issue today with one of my Server 2022 nodes. In my case I found it was because I disabled the Microsoft Remote Display Adapter while trying to clear my cluster validation report to zero warnings. Once the adapter is disabled it doesn't seem to be able to be re-enabled via the gui. (I have an OOB management connection so I can still get to the gui)
I had the same problem today, looking at the Event Log i can see it was the video driver! Microsoft installed automatically "Intel(R) Q35 Express Chipset Family (Microsoft Corporation - WDDM 1.0)" driver which caused a conflict with Microsoft Remote Display Adapter. What I had to do was revert to the previous controller in the the Display Settings in Devices Manager, and it reverted to Microsoft Basic Display Adapter. Problem solved!
I was still able to use PSREMOTING into the server. So I disabled Sophos AV from the cli and it started working again. I'm going to re-install Sophos Endpoint, and try to open a ticket with them to see if they can figure it out. The endpoint logs showed no entries, but it is Sophos, so who knows.
On a new harddisk on windows server "localhost\users" (on a domaincontroller domain\users) has read access. If you remove the read access for "users" on the systemdrive (C:) you can't access the server via RDP.
I had this issue as well. I caused the problem myself by removing the local users group (SERVERNAME\Users) from access to the c drive in the security permissions section. of the Remote Desktop server. Once I put that back in place the issue went away.
in my case it's been reason 0x3 and extended 0xf (15). The cause was:Group Policy (gpedit.msc) > Computer Configuration > Administrative Templates > System > Device Installation > Restrictions > Block installation of interchangeable devicesbeing activated. I set this back to default (not configured) and it's working again. Windows 11.
Although the varied answers here shows it's a fairly generic error, the issue in our case was connecting from a PC with a HighDPI Screen (2K Resolution) to a PC with an older Graphics Chipset (Intel G33);
I'm not sure if it's that chipset's maximum resolution or the fact it only had a WDDM 1.0 driver running it was the root cause, but putting the client PC down to HD Resolution (1080p) let it connect without issue, proving that was the problem. Client PC is getting replaced with something better, now.
He is using the Microsoft Remote Desktop Client app from a Dell Wyse thin client. Another user had used the computer before so the virtual desktop subscription wasn't using the same account (email address).
I often have this or similar RDC errors after installing OS updates. The reason is that not all services which startup mode are "Automatic" or "Automatic (Delayed Start)" are started, without any clues in EventLog.
I was able of setting up an iPad as a second screen in Mirror mode, by following this tutorial. It uses the new Remote desktop feature, inside Settings -> Sharing -> Remote Desktop. I can visualize my desktop on my iPad by connecting through a remote desktop client (in my case it is Microsoft Remote Desktop for Mobile). But when I try to change the settings of my new second virtual screen, I do not find it in the Displays menu, in the Settings app on Ubuntu.
Yesterday I tried following this tutorial and at first I had similar luck to you, although in my case the connection cease immediately after trying to connect. Then this morning i finally get it to work. this are some of the things that you may have wrong (at least things i did wrong).Make sure you are in Gnome 42 or later, you will find it on the settings/ about
d3342ee215