11 | december | 2015

What’s New in Release 2.10?

Windows 10 Support: Classic Windows 10 applications can be delivered through AppStacks to Windows 10 virtual desktops. End-users can install classic Windows applications on Writable Volumes when they are logged in to Windows 10 virtual desktops. Installation of universal applications is not supported on AppStacks and Writable Volumes. App Store applications are not supported.

Enabling vMotion: The AVM_PROTECT_VOLUMES=”1″ environment variable can be set on the App Volumes Manager to enable vMotion and to provide protection against accidental deletion of volumes when all ESX hosts are of version 6.0 Update 1a and 5.5 Update 4. vMotion of Storage is not supported.

vSphere 6 Update 1 support: This release of App Volumes includes support for vSphere 6 Update 1.

Horizon 6.2 support: This release of App Volumes supports Horizon 6.2.

Storage Group management: An option to mark a storage as Not Attachable is now available. App Volumes Manager will ignore this storage while mounting volumes.

Expand existing writable volumes: Size of an existing writable volume can be expanded through the App Volumes Manager. This change will take effect after the next user login.

App Volumes templates: All App Volumes templates are now created with the volume attribute set to NODEFAULTDRIVELETTER to ensure they are not automatically assigned a letter by the Windows MountVol utility.

What’s New in This Release of Horizon 6

VMware Horizon View 6.2.1 is a maintenance release. Some known issues from previous releases are resolved. For more information, see Resolved Issues.
To improve security, SSLv3 is no longer supported. By default, TLS 1.1 and TLS 1.2 are enabled. TLS 1.0 is enabled for outgoing connections to support vSphere 5.x, but disabled for incoming connections, including those from Horizon Clients. This will affect Horizon Clients 3.3 and earlier versions, which support only TLS 1.0. If the vSphere version is 6.x, it is recommended that TLS 1.0 be disabled for outgoing connections. To support Horizon Clients 3.3 and earlier, it is necessary to enable TLS 1.0. For instructions on configuring security protocols including TLS 1.0 on View servers, see Configuring Security Protocols and Cipher Suites on a View Connection Server Instance or on a Security Server in the View Security document.
By default, TLS 1.1 and TLS 1.2 are enabled and TLS 1.0 is disabled for PCoIP connections. Horizon Client 3.3 and earlier versions use only TLS 1.0. To support Horizon Client 3.3 and earlier versions, you can enable TLS 1.0 for PCoIP connections by following the instructions in KB 2130798, Configure security protocols for PCoIP for Horizon 6 version 6.2 and later, and Horizon Client 3.5 and later.
By default, TLS 1.1 and TLS 1.2 are enabled and TLS 1.0 is disabled for Blast Secure Gateway and the HTML Access agent. You can configure the security protocols and cipher suites for both components. See Configuring Security Protocols and Cipher Suites for Blast Secure Gateway in the View Security document and Configure Security Protocols and Cipher Suites for HTML Access Agent in the Horizon Client and View Agent Security document.
Linux desktops now support clipboard redirection, single sign-on, and smart card redirection. The Setting Up Horizon 6 for Linux Desktops guide also documents additional bulk-deployment scripts.