We have a VM that we are using a PCOIP Thin Client to connect to. I installed View Agent and Direct Connect on the VM we created.
Once we do this all form of remote connections no longer work. Windows RDP takes forever to log in and when it opens I have a black screen. Web/Remote console in Vsphere has no mouse and keyboard however I can see the time changing so I know it's not frozen.
I've attempted this a couple of times. We have no firewall settings between the locations on these networks. We have tried connecting from multiple locations and still the same issue. Before we installed this software RDP was working fine.
I found that you need to change this SVGA dma setting to true so we've done that already.
Any ideas on what could be causing this?
try this kb
even if it says via rdp it works...
I'd want some info:
horizon agent version?
do you use UAG?
The PCoIP VDI connection is ok?
Model of Thin Client and OS?
Verify the resolution and the number of monitor in Thin client (must be the same of the desktop pool Config)
We only have license for horizon 6 so i'm using the newest builds of that
We are not using the horizon server or anything like that since these are just two machines. The reason why we even have a license to 6 is an abandoned project from the last IT crew that no longer works here and we rebuilt everything, including the domain, from scratch.
We have no firewall or anything. Nothing should be blocking traffic the only chance of data not reaching either destination is routing. This is on a 'offline' network.
When I first got here I actually got this working, we just dismantled that network and management had me tackle things they had in priority. All I did was install agent+direct-connection software and it worked. However we were using software builds of what they had and out of date hardware on a network with no group policy. We had this working with that direct connect without a horizon server or anything like that installed. Just these two client softwares. A coworker claimed you can't do that anymore so I kind of am wondering what's the case.
horizon agent version: 184.108.40.20695838
thinos - 9.1.2101 (pcoip version)
Windows 10 20h2
VM's compatibility is set to 6.7 or later esxi idk if that's a problem given the version numbering. Next thing i'll try is to build a VM with earlier version compatibility and see if that works.
After the weekend I try it this morning and it no longer gives an error. Just says it's connecting then the dialogue disappears with no error message or anything.
It's just weird that I can't use the vmware remote console or web console to control this. I have never had that problem before. At my last job we had a proper full horizon setup and never that issue. From what i'm reading in this KB article and all that I shouldn't be having that problem.
There is this article: https://kb.vmware.com/s/article/77199?lang=en_US&queryTerm=direct+connection
Which references that you must have a connection server with 7.0 and higher. Wondering if that has trickled down. Seems this isn't intended to use in a "production" environment but we are strictly using these as admin consoles from a remote location.
I meet all the requirements according to this https://docs.vmware.com/en/VMware-Horizon-6/6.2/view-agent-62-direct-connection-plugin-administratio...
but I am going through it again following it exactly. I'll post if this is the resolution.
This bit right here I may not have done correctly:
Verify that View Agent is installed. If your environment does not include View Connection Server,
install View Agent from the command line and specify a parameter that tells View Agent not to register
with View Connection Server. See “Install View Agent for HTML Access,” on page 19.
But idk how that would explain mouse/keyboard not working in vmware console.
edit: Rebuilt the vm, installed VMware tools, followed that pdf and put in the command line argument for no horizon server. I didn't even install direct connection yet and I get no mouse/keyboard in web/remote console. Only video.
Considering no version of 6 is supported anymore, and I don't think has been for awhile, there is very likely something in 20h2 causing a problem, can you try an older verrsion of windows, at least 1803 probably earlier.