+11
Pending Review

Support for connecting to a headless endpoint (windows computer without a monitor plugged in).

joelcrburgess 3 years ago updated by Zanthexter 3 months ago 9

Currently there is no support for connecting to a headless endpoint (windows computer without a monitor plugged in). This is a big problem, as we are in the middle of moving from Bomgar to Control and now we realize that we can't support many of our client's servers or even Win10 computers who are headless. Even though the client has no monitor connected, we should still be able to see the Explorer GUI, other remote support apps certainly can do this. This is a HUGE feature-lack.

Available in Version:

Hi joelcrburgess, 

Wanted to pass along our troubleshooting guide for blank screens. We are continuing to investigate fixes for these blank screen issues. Can you please provide relevant information about your servers, version number, etc.? 

Thanks, 

Caitlin 

Many of the servers (and some desktops) we support have no monitor or KVM plugged into them and we don't have this problem.  Your problem probably lies elsewhere - such a video card driver or some other cause of blank screen.  To troubleshoot - try changing a computer to the MS basic video adaptor driver, then reboot and see if it's resolved.

Hi, got exactly the same issue with Win 10 headless, latest version (released 10/2/19 US date format), self hosted server. We dont have this issue with Server 2012 r2, 2016 or 2019. 


We've tried blanking guest monitor, makes no difference.

Tried rebooting into safe mode, makes no difference

Just ran into a problem again where I cannot remotely control a headless machine. It's connected to a TV. That is turned off.

I had to download and install TeamViewer to get my work done. Which was a challenge given that half the screen elements wouldn't display.

You guys are pestering me to renew my subscription but you seem uninterested in addressing problems with headless access which is EXTREMELY common.

This is basic functionality. I shouldn't have to use a competitors product because yours hasn't seen significant updates in years.

I'm tired of dealing with it. 

I'm not renewing.

Old post, but had this issue and thought I'd give some insight. Turns out, no graphics card installed/onboard = no joy. Headless in this case means not only no monitor, but no graphics card either. You don't have to plug a monitor into the card, but one has to be in the machine for Connect Control to show a screen. So, those running headless saying they don't have an issue are either machines with onboard graphics, or a card inside.

Having trouble with a Precision Workstation with a Quadro 960 card in it. Pull the monitor and the remote session just craps on itself. This is really ridiculous in this day in time.

+1

Yes. They don't care, and apparently won't be fixing it. It's a very old problem at this point.


I stopped renewing my self hosted maintenance because of it. Well, that and the terrible mobile app interface.

Here's a hardware work around. You can search for various resolutions and pack sizes - https://smile.amazon.com/fit-Headless-Emulator-FUERAN-Resolution-Adapter1920x1080/dp/B093Q2DPKW

Just started running into this issue with a number of Windows 11 Desktop PC's ..well similar ... if the monitor (or monitors) plugged into the Desktop PC is turned OFF - I get a grey screen when I connect via ScreenConnect ... and it's clickable, i.e. I can actually click the desktop elements of the client PC, just not getting the desktop showing to me on my end.

Reboot - doesn't fix it
Blank Guest monitor, then unblank it again - doesn't fix it
Re-installed video card (including my own nVidia 2060 at home!) - doesn't fix it
Ask someone to run over and physically turn the attached monitor on and BAM! ScreenConnect works fine. 

This is getting a tad annoying

ConnectWise hasn't invested any effort into improving ScreenConnect since they've bought it. Well, that customers want anyway. They've spent money pushing their subscription and looking for ways to upcharge.

You're going to have to switch products if you want a working remote support solution. This issue has long since been addressed by TeamViewer, Splashtop, and others. (Splasthop has a "virtual monitor" driver, etc.)

I still keep my ScreenConnect server running as a backup method to connect. But I gave up and switched away. I just saw no reason to keep paying for maintenance when they were refusing to maintain the damn thing anymore.