Note that self-signed certificates are insecure and should be replaced by CA-signed certificates as soon as possible, and that SHA-1 certificates are no longer considered secure and should be replaced by SHA-2 certificates.ĭo not remove CA-signed certificates that were installed for production use, as recommended by VMware. The self-signed certificate in this release has a longer RSA key (2048 bits instead of 1024) and a stronger signature (SHA-256 with RSA instead of SHA-1 with RSA) than in pre-6.2 releases. Removing the old self-signed certificate ensures that a new certificate is installed. During an upgrade, the installer does not replace any existing certificate. Connections might not work if the existing self-signed certificates remain in place. If you intend to upgrade a pre-6.2 installation of Horizon 7, and the Connection Server, security server, or View Composer server uses the self-signed certificate that was installed by default, you must remove the existing self-signed certificate before you perform the upgrade. See the Horizon 7 Upgrades document for upgrade instructions. This Horizon 7 release includes new configuration requirements that differ from some earlier releases. If you want to install View Composer silently, see the VMware Knowledge Base (KB) article 2148204, Microsoft Windows Installer Command-Line Options for Horizon Composer.

To determine which VMware Tools versions are supported, go to the VMware Product Interoperability Matrix, select the solution VMware Horizon View and the version, then select VMware Tools (downloadable only). If you plan to install a version of VMware Tools downloaded from VMware Product Downloads, rather than the default version provided with vSphere, make sure that the VMware Tools version is supported. Important note about installing VMware Tools

If you plan to install or upgrade to View Composer 7.2 or later, you must upgrade the Microsoft. Important note about installing VMware View Composer

Vmware vdi client