+21
Under review

Server 2019 VM not refreshing display unless the console is live

TheScottyQ 1 year ago updated by Bill Townsend 3 months ago 13

We have a 2019 Clustered HyperV environment where the guests do not show a live display unless the console is live from the HOST 

Keys and Mouse seem to be being passed through because if we send a CTRL+ALT+DEL to the guest and refresh the screenshot you can see it has been passed through to the guest, the display on the session just does not refresh for the host 

Screenconnect Version - 19.2.24707.7131 (not listed below) 

ConnectWise Control Version:
20.5
Server Affected:
Host Client Affected:
Guest Client Affected:

I can't belieeve this has been open for a month without any response. ConnectWise Control does not work with the latest version of Microsfot Server software and one of the most popular virtualisation environments and no update on this in a month!!!

This is happening to us too. Using ConnectwiseControl aka Screenconnect (cloud hosted, latest agent version 19.5.25995.7276 ) to connect to two Windows Server 2019 std virtual machines. (My DC01 and DC02). It worked fine for months until this morning. Now when I connect, I get only a grey screen. If I connect to the hypervisor and start a console session, the screenconnect session suddenly starts working. But screenconnect session will stop and go grey again if I end the hypervisor console session.This started happening to both machines this morning. They are the only 2019 servers in house. This issue is not happening to other servers or PCs.

I'm currently experiencing this on our 2 Windows Server 2019 guest VM's on a 2019 Windows Server hypervisor. If my Hyper-V connector is closed, when I connect to one of the guest VM's via ScreenConnect, I'm presented with a grey display. Say the VM I'm connected to is at the Windows welcome screen: If I send Ctrl+Alt+Del, nothing visible happens. If I then connect to the VM directly within the Hyper-V host, the ScreenConnect viewer is now live, displaying the login screen (resulting from sending Ctrl+Alt+Del).

I have experiencing this same issue on a fresh install of Server 2019 Standard running on HyperV 2016. CW Control version 19.6.26378.7317. 

+1

It has been MONTHS and there is no reply here from Connectwise.  Getting a strong feeling here that THEY DONT CARE.  Come on CW Support... throw us a bone.

+2

Had this issue on a brand new 2019 cluster with 2019 VM's.  The issue was resolved after I bumped the VM's to more than 1 virtual core.   

I am also having this issue connecting to Windows Server 2019 Host. Unable to input the password, even using on-screen keyboard.

+1

I just resolved this using one of the comments from above. I increased the virtual machines memory to 8192 and increased the number of virtual processors to two or more. Now I am able to screen connect in without having the console session up on the hypervisor.Thanks!!!

I have a Windows 2019 Hyper-V host, with Windows 2019 Standard VMs. I can confirm the fix was to increase the CPU from 1 to 2, then ScreenConnect worked without console. I did NOT have to increase memory.

I was experiencing the same thing on 2019 host with a new 2019 VM. I built the VM with 8 cores from the start, then installed Control. That's when I noticed the issue. Changed the cores down to 4 and didn't have the problem anymore. Changed back to 8, still no problem. May be that you just need to change the cores to something other than what they were when you installed Control, then you can change them back if you want.  ¯\_(ツ)_/¯  It's CW's new "Are you sure that was really how many procs you wanted, maybe you should check again" feature.

+1

Enable "Guest Services" in the Integration Services in Hyper-V Manager for the affected VMs. It should work after that.

Why would assigning two CPU to a VM also fix the issue?  I would think that if guest services is required that the number of CPU's would not matter.