<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Can't command line upgrade the Horizon Agent? in Horizon Desktops and Apps</title>
    <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Can-t-command-line-upgrade-the-Horizon-Agent/m-p/2887297#M95917</link>
    <description>&lt;P&gt;I seem to be having an issue with command line &lt;STRONG&gt;upgrade&lt;/STRONG&gt; of the Horizon Agent on some persistent desktops. I'm doing this as I have a number to do, and I would rather not have to log into each of them to do the upgrade manually.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've found that if upgrading the version of the client from something older (e.g. 7.12), the upgrade process will work just fine when launched (for example) using the following syntax:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;VMware-Horizon-Agent-x86_64-7.13.1-19067315.exe /S /V"/qn VDM_VC_MANAGED_AGENT=1 ADDLOCAL=Core,SVIAgent,RTAV,ClientDriveRedirection,VmwVaudio,VmwVidd,BlastUDP"&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;However executing the exact same command line syntax on a guest with either 7.13.0 or the log4j vulnerable version of 7.13.1 on it, the process appears to run but doesn't seem to complete. The log output located in C:\ProgramData\VMware\logs seems to suggest it did the upgrade however it doesn't reboot, and even after a reboot you can see in the Connection Server that the version of the agent is still the existing version.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else encountered this problem? Is the only solution to, basically, uninstall the existing version of the agent and reinstall from fresh?&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 10 Jan 2022 13:49:38 GMT</pubDate>
    <dc:creator>ChicaneUK</dc:creator>
    <dc:date>2022-01-10T13:49:38Z</dc:date>
    <item>
      <title>Can't command line upgrade the Horizon Agent?</title>
      <link>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Can-t-command-line-upgrade-the-Horizon-Agent/m-p/2887297#M95917</link>
      <description>&lt;P&gt;I seem to be having an issue with command line &lt;STRONG&gt;upgrade&lt;/STRONG&gt; of the Horizon Agent on some persistent desktops. I'm doing this as I have a number to do, and I would rather not have to log into each of them to do the upgrade manually.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've found that if upgrading the version of the client from something older (e.g. 7.12), the upgrade process will work just fine when launched (for example) using the following syntax:&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;FONT size="2"&gt;&lt;STRONG&gt;&lt;FONT face="courier new,courier"&gt;VMware-Horizon-Agent-x86_64-7.13.1-19067315.exe /S /V"/qn VDM_VC_MANAGED_AGENT=1 ADDLOCAL=Core,SVIAgent,RTAV,ClientDriveRedirection,VmwVaudio,VmwVidd,BlastUDP"&lt;/FONT&gt;&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;However executing the exact same command line syntax on a guest with either 7.13.0 or the log4j vulnerable version of 7.13.1 on it, the process appears to run but doesn't seem to complete. The log output located in C:\ProgramData\VMware\logs seems to suggest it did the upgrade however it doesn't reboot, and even after a reboot you can see in the Connection Server that the version of the agent is still the existing version.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else encountered this problem? Is the only solution to, basically, uninstall the existing version of the agent and reinstall from fresh?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jan 2022 13:49:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/Can-t-command-line-upgrade-the-Horizon-Agent/m-p/2887297#M95917</guid>
      <dc:creator>ChicaneUK</dc:creator>
      <dc:date>2022-01-10T13:49:38Z</dc:date>
    </item>
  </channel>
</rss>

