Horizon view 7.8 Stuck in waiting for Agent

[max_nel]

Hello.

We upgrade vcenter&esxi to 6.7U1 and horizon from 6.2.0 to 7.8 and have problem: VM stuck in waiting for agent with Agent 7.8, but work correctly with 6.2

We read and attempt all methods: delete/install clean infrastructure of Horizon and agent on clean Windows, regenerated keys and other.

PLEASE, help us

Errors from agent, on connection server mirrored error.

2019-07-12T10:44:46.024+03:00 INFO (124C-1720) <Thread-2> [AgentJmsConfig] Attempting to securely pair agent for JMS communication

2019-07-12T10:44:46.087+03:00 WARN (124C-1720) <Thread-2> [JMSMessageSecurity] Failed to sign message: Cannot sign message

2019-07-12T10:45:16.102+03:00 WARN (124C-1720) <Thread-2> [JMSMessageSecurity] Failed to sign message: Cannot sign message

2019-07-12T10:45:46.117+03:00 WARN (124C-1720) <Thread-2> [JMSMessageSecurity] Failed to sign message: Cannot sign message

2019-07-12T10:46:16.147+03:00 WARN (124C-1720) <Thread-2> [JMSMessageSecurity] Failed to sign message: Cannot sign message

2019-07-12T10:46:41.989+03:00 ERROR (124C-0EB8) <Main Thread> [wsnm_jms] JavaBridge reader thread init: timed out

2019-07-12T10:46:42.052+03:00 INFO (04E4-1054) <JavaBridge> [wsnm_jmsbridge] wsnm_jms died, restarting in a minute

2019-07-12T10:47:42.111+03:00 INFO (13E0-1318) <Main Thread> [MessageFrameWork] Program 'wsnm_jms - VMware Horizon View Framework JMS Bridge' started, version=7.0.1 build-3988955, pid=0x13E0, buildtype=release, usethread=1, closeafterwrite=0, sessionId=0

2019-07-12T10:47:42.126+03:00 INFO (13E0-1318) <Main Thread> [wsnm_jms] Registered for address change notifications

[max_nel]

On test windows server 2016 work correctly, I think...production Connection working on 2008R2, but in Windows noboby turned on TLS1.2...

Does Connection server  use the Windows encryption library?

Wrong way.

Create same test enviromen, all work perfectly. Attempt reinstall COnnection server

[jmatz135]

Is this a persistent VM?  If so can you remove it from Horizon View shut it down and re-add it to Horizon View and let Horizon View power it on.

[max_nel]

Find. I have in pae-MSGSecOption keySize=2048, but with this params horiozn 7.8 in Trace Agent show error, even in clean new installion

The security strength of SHA-1 digest algorithm is not sufficient for this key size

and questions for VmWare: Why in 2019 you are using SHA-1 for new client, and you write, that in enhanced recomended keySize=2048, but with this options agent not working.

Horizon Messaging

After I on test server change keySize to 1024, do resetkey, agent connecting to Server