Change Resolution Microsoft Remote Desktop Mac

1 view
Skip to first unread message
Message has been deleted

Sheron Norsworthy

unread,
Jul 18, 2024, 6:19:33 PM7/18/24
to guvitata

In macOS Ventura it's possible to disable menu bar auto-hide even in full-screen apps. Set System Preferences->Desktop and Dock->Menu bar->Automatically show and hide menu bar->Never, create a connection to Windows 10 or newer in Remote Desktop, enable "Start session in full screen" and "Update resolution on resize" and connect.

Windows defaults to 96 d.p.i. while macOS still assumes 72 d.p.i. You can change a Windows machine's resolution (though it doesn't look as good), but not a Mac's. All remote software runs on the same basic technology, so you could try different Mac clients to see if you can get a better result.

change resolution microsoft remote desktop mac


DESCARGAR --->>> https://lpoms.com/2yPBxs



If I have the remote desktop app in full screen on an external monitor and then reconnect when plugged in to a monitor with a different resolution, anything I click on will not match up to what is on screen. If I take the app our of full screen mode and then go back to full screen it resolves the issue. I feel like the app should recognize that the screen resolution has changed.

I use Microsoft Remote Desktop regularly on both Windows (Surface Laptop 5) and macOS (MacBook Pro M1 Pro), and the macOS client has some significant issues not present on the windows version. I was wondering if this is due to some misconfiguration on my end or the features just work better on windows. Here is a list of issues that I face in the macOS version of remote desktop but not on windows:

I also have issues with the client on macOS. On the windows client you can specify the resolution and color depth that you want to connect and have a wide range of options. This allows you to be able to use the client in low bandwidth situations.

The macOS client is unusable in low bandwidth situations since you have very limited options when it comes to setting the resolution and color depth. The resolution defaults to "default for this display" and it cannot be changed, which is 4K in my case. Lowest color depth is 16 bit which is too high.

I'm having similar issues with my new machine (MacBook Pro M3 Max) when multiple monitors are connected. Every 10-15 seconds, video and input for the RDP connection will freeze for a few seconds. No issues with my previous i9 MBP, and I've ruled out connectivity or other possible issues.

Hi, having similar issues when I have dual monitors connected. My mouse and keyboard that are connected through my docking station (same station that the monitors are plugged into) does not work when I have the Remote Desktop app opened across both screens. When I change the App to only be displayed on one screen the keyboard and mouse work.

I'm using the Microsoft Remote Desktop Connection tool with my MBP retina to connect to a Win7 system, but I can't get the resolution over 1440 x 900, even in full screen mode. Is this a limitation, or am I doing something wrong?

Buy 'Jump Desktop (Remote Desktop)' from the App Store. It solves the lag caused by the retina display...I had the same problem and it was doing my head in. It also makes the resolution look a lot better than the Windows RDC software.

I was able to force RDC to accept other resolutions. I already knew in advance that forcing the desktop to Macbook Pro's Retina 2800 x 1800 would cause problems if you weren't able to adjust the text and item size (some Terminal Server setups won't allow display changes - my client's doesn't)

Is Windows 7 using Boot Camp supported on the Retina display?
Yes. You will need to download and install the Windows Support Software using the Boot Camp Assistant to use the Retina display with Windows 7. For more information see this document.

So, I'm aware that generally the resolution is the resolution of the actual monitor, but I hit a new issue: I no longer have a monitor attached to a PC I'm connecting to, and hence, it's defaulting to the Basic Video Adapter at 800x600. For normal RDP, the resolution is set by the client connecting to the machine, but that's not an option with Pulseway Remote.

I have 2 large monitors on my remotePC but two smaller monitors on my home PC. I need a lower resolution in my Pulseway window (TeamViewer, RemotePC and Microsoft remote desktop manage to do this automatically), is there anyway I can change this -- I can see no setting or option for this :( Currently I have to keep scrolling side-ways and up and down, which is unsustainable.

I'm trying to adjust the resolution of my Windows Virtual Desktop machine (Spring 2020 release - Win 10 Enterprise 1909) as I have an app (QuoteWerks.exe) that is missing its icons in the ribbon bar within the app. The QuoteWerks support team asked that I adjust scaling. From their support: "This is usually caused by magnification or High DPI Scaling specified within Windows. Please adjust your Display Scaling or magnification back to a 100% setting and this should resolve the issue."

All of this seems rather tedious. Why not allow the setting of the resolution from the RDP client as can be done with the older mstsc client/other clients? When I attempt to adjust the resolution from within the windows session itself, I see the message that "The display settings can't be changed from a remote session."

@Neil McLoughlin Well, it took me a few to find the 10.3.11 client again. It's found by following the link here from the WVD documentation - -us/azure/virtual-desktop/connect-macos This then links you to the App Store and 10.3.11. Screen shots of release notes from 10.3.9 to .10 to .11 attached.

All that said, none of the releases 10.3.9, 10.3.10, 10.3.11 or even the new beta of 10.4.0 solve my original posted issues. My RDP sessions still go full screen regardless of the host pool's RDP settings and the scaling settings and icons are missing from my app's ribbon bar. I am sure there is something I am doing wrong/need to update. I appreciate the help!

I don't know much about Macs, but the resolution and scaling in WVD is taken from the local machine, so I'd recommend checking (assuming you haven't already!) if there is any increased scaling/text size set locally. I had a similar issue in WVD where an application was not showing fullly on the screen, it turned out the user had changed scaling on the local Win10 computer to 125% (changing it back to 100% and restarting the WVD session fixed the application not displaying correctly).

I have tried using the default scaling settings for my display on my Mac but I still have the same trouble. No icons showing. The Mac OS Remote Desktop app doesn't seem to have any settings to allow me to set the desktop size for a Workspace machine.

@TTMGT3Again I haven't used the mac client, but according to the docs there should be an option to change the resolution: -us/windows-server/remote/remote-desktop-services/clients/remote-deskto... Is this option not there?

In addition, it enables you to change the screen resolution easily, there are a lot of other options for you on the taskbar. You can change the image quality easily. You can also take quick operations, such as lock, restart, or shut down the computer easily.

After reading this post, we have known two ways to change the screen resolution of the remote computer while using Remote Desktop Connection? On the one hand, you can change it by editing the Display Configuration. On the other hand, you can change it by editing the screen resolution size within the RDP file.

Besides, you can also use AnyViewer, a free and easy-to-use remote access software. Unlike the complicated process of changing screen resolution on Remote Desktop, you can change the screen resolution during remote sessions easily With AnyViewer.

About your only hope is to DISCONNECT the session (leaving it running by closing the RDP session without logging out), and then reconnect using a different resolution. Of course this will all depend on the server remote session settings, etc. This works in 2003/2008. No idea if it will work in 2000. The screen scaling in the VMWare client (and the old McAfeee RDesktop32) was very nice.

No, not until you close that particular remote desktop connection. I think that the reason for this is becasue some older applications retrieve the colordepth and resolution on start and crash when they change suddenly.

It's not true that you have to sign out. If you are connecting to Windows 10 or Windows Server 2012 R2, the resolution automatically changes when you switch to fullscreen mode. And if you have on your PC two monitors with different resolutions, you can change the resolution of the RDP session by switching from one monitor to the other. Unfortunately, I do not know how to change the resolution to other size...

This is due to my new monitor at home with 4K resolution. When I connect to Windows 10 I have to choose "use client resolution option" otherwise if I choose "custom resolution" option Remmina makes screen smaller but does not change resolution.

Recent remmina versions can set RDP remote windows desktop scaling factor. From the global preferences menu -> RDP. But you need an updated remmina version and an OS (windows 8.1 or higher) that supports scaling factor. Upgrade remmina following instructions on the main website We provide a PPA for ubuntu 16.04.If you already enabled local scaling on your local PC, and usually this is the case when using a 4K monitor, you should also play with the remmina scaler function to neutralize the Xorg/Unity scaling, because remmina can't currently do to it.

If I turn on my computer with the monitor off, the TV remote resolution is stuck at 640x480. There are no other resolutions offered. All I have to do is turn on my monitor and the remote resolution instantly changes to 3840x2160 (what I want).. The behavior occurs with my Windows laptop, iPad and iPhone.

Good news. The behavior is exclusive to the display port. Last night, I connected an HDMI cable to the monitor (disconnected DP) and the problem is gone.Now, I can leave the monitor off, boot the computer and get 3840x2160 remotely. Would prefer to keep the display port connection, but this will work..

d3342ee215
Reply all
Reply to author
Forward
0 new messages