Just over a month after the 7.3.1 release, VMware has released a minor version update, Horizon 7.3.2, which appears to primarily fix a 7.3.1 issue related to Instant Clones where the operations were failing in 7.3.x versions. Operations are now handled gracefully, according to the release notes. VMware appears to strongly recommend that customers running 7.3.x upgrade to 7.3.2.
Only the updates to Instant Clones and references to version 7.3.2 have changed. The rest of the updates appear to be identical to 7.3.1.
Just the clones. If you haven’t already updated to the 7.3 release, 7.3 also upgrades 7-Zip version incorporated into the Horizon Agent and Horizon Connection Server to 16.04 to resolve a security issue in 16.02 and earlier, CVE-2016-7804. The issue was an untrusted search path vulnerability in 7 Zip for Windows 16.02 and earlier allows remote attackers to gain privileges via a Trojan horse DLL in an unspecified directory.
It is also worth noting that if you plan on installing VMware View Composer you must upgrade the Microsoft .NET framework to version 4.6.1, otherwise the installation will fail. Also, VMware Tools interoperability Matrix should be referenced when installing a version other than the default provided with vSphere.
If upgrading from a prior release to 7.3.2, there are several issues and workarounds for 7.3 related to the following components: Horizon Persona Management, View Composer, Horizon Connection Server, Horizon Agent for Linux, Horizon Agent, Horizon GPO Bundle, Horizon Client. The list is environment dependent and too lengthy to summarize. It is advisable to refer to the release notes linked below.
Of the items to note, if you plan on migrating directly to 7.3.2, with the updates to Global Policy Objects, Computer-based Global Policy Objects that require a reboot to take effect are not applied on instant clones. If you are attempting to use computer-based policy settings on instant clones, you will want to make note of this shift and move to user-based GPO settings or follow the guidance in VMware KB article 2150495.