Virtual Screen driver similar to that used by MSTSC to eliminate screen resolution limits

Avatar
  • updated
  • Under Review

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.

Avatar
0
brf

We've had issues with vendor provided drivers since 2019.2/2019.3. In our support conversations it's been indicated that this would mitigate/resolve this issue. Hopefully we can get more than "under review" soon.

Avatar
0
Mark Hodges

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?

 

Avatar
1
TwinHats

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! 

Avatar
0
Troy Thibo

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.  

Avatar
0
BC3

Lets get this done. I'm away from my office for 30 days and stuck at 800 x 600. I can't even believe this.

Avatar
1
Sean Keown

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. 

Avatar
2
Sean Keown

The bridge would probably work great for Control only users. Our staff uses Automate via the control plugin and because we have all our access permissions built in Automate the bridge won't work for us without a huge overhaul of the Control / Automate integration. 

  • If they integrated RDP like backstage then it could be permission based with a drop down under logon session.
  • Because the control agent is installed locally it would be able to access the registry and auto obtain the RDP port from the registry. 
  • It could be tunneled via the loopback address. (we do this at my company today with other technology)
  • The control agent could auto acquire your screen resolution and feed that into the RDP session. 


Then when users are in Automate they could select RDP that would tunnel over the control session. Making more users happy with one change. Then as control matures, they could implement some driver to adjust screen resolution.



At the moment this request was over 4 years ago and they don't seem very interested in building a driver to adjust the screen resolution. Maybe this would be a happy middle ground until it gets built. 

Just my 2¢. 

Avatar
0
Michael Kearney

With recent events - this thing has become more of an issue - to a point where we are looking for alternatives. I could never get the bridge service to run our account. I've installed and reinstalled it multiple times and I still can't enable it. It'll be really nice to just add RDP mode ala Backstage. 

Avatar
0
Tom Bolick

I assume everyone knows about the headless dongles.  We use them for adding a second monitor for remote users.  There are HDMI and DP styles.  Yes, they should fix this, but until they do, the dongles are cheap.



Top contributors

Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar