Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RDP window size does not adapt #2911

Open
sfwwslm opened this issue Nov 13, 2024 · 5 comments
Open

RDP window size does not adapt #2911

sfwwslm opened this issue Nov 13, 2024 · 5 comments

Comments

@sfwwslm
Copy link

sfwwslm commented Nov 13, 2024

Describe your issue:
After changing the primary monitor resolution from 1920x1080 to 2880x1800, the RDP window size in the secondary monitor does not adapt. The secondary monitor is 1600x900.

Steps to reproduce the issue:

NETworkManager version:
2024.11.11.0
2024.8.1.0

  • [√ ] Portable

Windows version (like 10.0.x.x):
Win11 23h2
版本 10.0.22631 版本 22631

.NET version (like 6.0.x):
8.0

Screenshots
微信截图_20241113105611

Eventlog (if application crashes)
@BornToBeRoot
Copy link
Owner

BornToBeRoot commented Nov 14, 2024

Hi @sfwwslm, you can set the display options global, per group and per host.

https://borntoberoot.net/NETworkManager/docs/application/remote-desktop#display

If you change this setting, you must re-establish the connection (open a new tab) for it to be applied.

Maybe the server itself has set a max display resolution. (e.g. https://admx.help/?Category=Windows_10_2016&Policy=Microsoft.Policies.TerminalServer::TS_MAXDISPLAYRES)
You could check this with the normal mstsc.exe.

Edit:

I just tried this, and it's working for me:

image

@sfwwslm
Copy link
Author

sfwwslm commented Nov 14, 2024

@BornToBeRoot Thanks, I used mstsc.exe and it showed normal. I tried custom resolution but it didn't work.

@sfwwslm
Copy link
Author

sfwwslm commented Nov 14, 2024

This is my laptop's display configuration

20241114175053

@BornToBeRoot
Copy link
Owner

Thanks for the infos. I try to reproduce that

@BornToBeRoot
Copy link
Owner

BornToBeRoot commented Nov 28, 2024

I was able to reproduce the problem. It's due to the display settings/scaling factor (150%, 200%, ...)

I'm not sure how to fix it, but I'll try to look into it when I have more time.

Edit: This also affects PuTTY, PowerShell, TigerVNC, AWS Session Manager

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants