topic Horizon Agent 7.13.1-19067315 vs. 7.13.1-18057992 in VMware Horizon Discussions

Horizon Agent 7.13.1-19067315 vs. 7.13.1-18057992

nschlip — Wed, 09 Feb 2022 22:52:06 GMT

Hello,

Since we've installed 7.13.1-19067315 (to address the log4j vulnerability) we've encountered random issues with VMs suddently dropping sessions. When this happens, the VM displays a status of "agent unreachable" in Horizon. It takes several minutes for the agent to communicate with Horizon again, and sometimes not at all, where we have to restart the VM from vSphere.

Is anyone else running agent 7.13.1-19067315, and encountered any issues?

Re: Horizon Agent 7.13.1-19067315 vs. 7.13.1-18057992

patricksarian — Sat, 19 Feb 2022 00:44:11 GMT

Similar issue here, and also newly provisioned vms are not powering on to go into 'Available' state. Regardless of how many spares are configured for the pool. Manually powering them on makes them available.

Connection servers are 7.13.1-18057992 with Log4J workaround applied.

Agent version 7.13.1-19067315 (VMtools 11365)

Is this mismatch the problem? If so, is it possible to do a build update on the servers without uninstalling?

Re: Horizon Agent 7.13.1-19067315 vs. 7.13.1-18057992

ibeerens1 — Wed, 23 Feb 2022 14:02:42 GMT

Did you try to upgrade to the latest Horizon Agent (7.13.1-19251283)?

Re: Horizon Agent 7.13.1-19067315 vs. 7.13.1-18057992

nschlip — Wed, 23 Feb 2022 16:17:27 GMT

I have not, since that version only very recently released, and I made this post long before. That said, will give it a try on some test VMs and see how it goes.