https://communities.vmware.com/wbsdv95928/tracker patricksarian Tracker Fri, 24 Nov 2023 05:59:56 GMT 2023-11-24T05:59:56Z https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-Agent-7-13-1-19067315-vs-7-13-1-18057992/m-p/2894373#M17413 <P>Similar issue here, and also newly provisioned vms are not powering on to go into 'Available' state.&nbsp; Regardless of how many spares are configured for the pool.&nbsp; Manually powering them on makes them available.</P><P>Connection servers are&nbsp;7.13.1-18057992 with Log4J workaround applied.</P><P>Agent version&nbsp;7.13.1-19067315 (VMtools 11365)</P><P>Is this mismatch the problem?&nbsp; &nbsp;If so, is it possible to do a build update on the servers without uninstalling?</P> Sat, 19 Feb 2022 00:44:11 GMT https://communities.vmware.com/t5/VMware-Horizon-Discussions/Horizon-Agent-7-13-1-19067315-vs-7-13-1-18057992/m-p/2894373#M17413 patricksarian 2022-02-19T00:44:11Z https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VM-with-Provisoned-Status/m-p/2894198#M96327 <P>Hi ChevUribe,</P><P>Did you ever get this resolved?&nbsp; I'm experiencing the same issue.&nbsp;</P><P class="">My view linked-clone pool has a bunch of vms in a provisioned state.&nbsp; They can only be made available if I power them on manually in VC.</P> Fri, 18 Feb 2022 00:51:34 GMT https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/VM-with-Provisoned-Status/m-p/2894198#M96327 patricksarian 2022-02-18T00:51:34Z