Older graphics cards restrict screen resolution. This is not a problem with the Microsoft Terminal Services client which uses a virtual driver and can display much higher resolutions.
A simple workaround until they can build a driver is for them build a function so we can RDP over the control connection.
Give us a rightclick and RDP button. This would allow users to set the resolution to what ever they want and would fix many other issues that same time.
When will this issue be addressed. This becoming a big problem. I pay good money to use this remote tool and not being able to connect to a new AMD laptop with the lid closed or a headless desktop is a big issue.
My single biggest complaint with SC is working with headless machine. Every other remote desktop software I have used handle this. With Control, I'm I suffer with low resolution on headless machines. Even worse, I now have 45 new Lenovo M715Q Tiny PCs to set up and they will not work with Control at all unless a monitor, kb, and mouse are connected. And yes, I've been through the "blank screen troubleshooting". This is such a glaring product deficiency. Please fix it!
Every other remote control tool seems to work to connect to headless but Screenconnect. I've used Teamviewer, LMI, Takecontrol, and even ANYDESK and they all work...why in the hell can Control not figure it out?
While working to solve this please have a look at another RDP feature request:
Adding my voice to this. It's understood that this is a remote support tool and thus the flexibility to remotely support nearly anything is a must.
That said, we have only seen this be a problem with discrete GPU's with Displayport right now. Most of the machines we support are onboard DP and do not have this problem.
Can't we just send a trigger to the OS / GPU to activate output? There must be a better solution than RDP or dummy plugs.....
Did you test the bridge extension already?
https://www.connectwise.com/blog/remote-support/tech-talk-bridge-in-connectwise-access