When you connect to a server the screen resolution can be quite small and there is no way to change the default window size, having the ability to change or set a default connection resolution size or control it in the session would be very helpful, it is very frustrating when you are viewing a sever at 800x600 when you have 1920 x 1080 monitor.
It seems that if the HDMI connector isn't connected or there is no monitor plugged in when I connect from Screenconnect it was giving me a small black square and it wasn't working at all. Then I changed the drivers to use Microsoft Basic Adapter and I am limited to 800x600 or 640x480.
I really can't use that remote PC on a 800x600. Is there a way to get higher resolution with ScreenConnect? Maybe you have a special monitor driver i could install or anything else? When I connect via RDP, it uses a special video driver that allow me to be on 1920x1080.
I have Screenconnect installed on a virtual machine, this computer is not conencted to a monitor or anything, so its just using the windows default display adapter, with a resolution of 1024x768.
It would be nice if there was a screenconnect display driver of sorts, so i can set a "virtual resolution" with the VM.
I'd like the ability to temporarily change the resolution of the targeted machine to match the controlling machine. For example, I often connect to customers that have large 27" 4K displays from my 15" laptop with 1366x768 res. This results in seeing their full screen on mine and everything is very small. I can change the zoom, but that makes it difficult. The only solution i have right now is to change the resolution on the target machine and hope i remember to change it back b efore i disconnect.I'd like the ability to set a pre-determined resolution and have it change to that when i connect and change it back to what it was before after i disconnect.
I use a combination of powershell and procexp to accomplish this in backstage.
In powershell,
Install-Module -Name DisplaySettingsSet-DisplayResolution -Width 1920 -Height 1080
This will set the screen resolution.
The backstage shell will be incorrectly sized, so launch procexp from the toolbox and find Screenconnect.WindowsBackstageShell and rightclick, Restart. This will re-launch the WindowsBackstageShell at the current resolution.
Not sure if I should post this hear or start a new topic / file a bug report:
So - this is really a neat feature but the monitor preview is causing me some grief. We use Control to remotely access a fleet of digital signage endpoints, and this new monitor preview doesn't play nice with portrait - it winds up being way too large and hiding the the quality, zoom, and session options unless you resize the window - and in some configurations its impossible to resize it enough to see them:
Also - for similar reasons / for our use case - being able to see and set the resolution like this is both very powerful and a bit dangerous - would *love* to have some kind of "are you sure" prompt (ideally one that can be toggled on or off).
I'm using the following solution to set the resolution of the backstage
Copy setres.exe and setres.exe.mui from a windows server to a shared location or a location on the computer. The setres.exe.mui must be in a sub folder EN-US. EN-US must be in the same folder setres.exe is in. You could copy the file to c:\windows\system32 if you wanted. Another option would be to copy the file from somewhere using the cmd file below
In my screen connect toolbox I have setbackstageresolution.cmd with the following in it. It will set the resolution and then stop/restart the screen connect service to resize the screen. Works great. To use it, I just click on this cmd file from the toolbox and the magic happens!
@echo off
setlocal enabledelayedexpansion
REM === 1) Set resolution ===
\\<Shared path or local path>\setres.exe -width 1920 -height 1080 -f
REM === 2) Find the ScreenConnect Client service (first match) ===
set "svc="
for /f "tokens=2 delims=:" %%A in ('
sc query state^= all ^| findstr /I /C:"SERVICE_NAME: ScreenConnect Client ("
') do (
set "svc=%%A"
goto :found
)
echo ERROR: ScreenConnect Client service not found.
exit /b 1
:found
set "svc=%svc:~1%"
echo Target service: "%svc%"
REM === 3) Fire a detached helper that stops/starts and waits for states ===
REM - Runs outside Backstage lifetime (new process)
REM - Waits up to 30s for STOPPED, 60s for RUNNING
start "" /min powershell.exe -NoLogo -NoProfile -WindowStyle Hidden -Command ^
"$name = '%svc%';" ^
"Write-Output ('Restarting ' + $name);" ^
"try {" ^
" Stop-Service -Name $name -Force -ErrorAction SilentlyContinue;" ^
" (Get-Service -Name $name).WaitForStatus([System.ServiceProcess.ServiceControllerStatus]::Stopped, [TimeSpan]'00:00:30');" ^
" Start-Service -Name $name;" ^
" (Get-Service -Name $name).WaitForStatus([System.ServiceProcess.ServiceControllerStatus]::Running, [TimeSpan]'00:01:00');" ^
" Write-Output ('SUCCESS: ' + $name + ' restarted.')" ^
"} catch { Write-Output ('ERROR restarting ' + $name + ': ' + $_.Exception.Message) }"
echo Launched detached restart helper. Backstage can close; the restart will continue.
exit /b 0
Partner has a high resolution monitor and is connecting into a session where the console output is a lower resolution. He is able to stretch the session to make it larger, but it becomes pixellated and grainy. Please update the client to improve handling of this situation.
CW#7691899