Subsequent pods use the deployment options that were set in the first. Note: This option is available only when setting up a new pod. Oracle Cloud (the Oracle Cloud on VMware Engine).Google Cloud (the Google Cloud on VMware Engine).Azure (the Azure VMware Solution solution).Dell EMC (the VMware Cloud on Dell EMC solution).AWS (either VMware Cloud on AWS, or EC2 Native).The following deployment environments are supported, and help you determine how the installation will be completed: You can now choose your deployment environment when you set up a new pod, during the connection server installation process. Note that now HTML is on by default for desktop pools and RDSH farms.

False memory alarm for IC Parents on vSphere 7.0 can be removed.

Up to 32 GB of cache in CBRC 2.0 is now supported, up significantly from 2 GB in CBRC 1.0.

If another host in a local or global pod is in an inconsistent state, the installer is blocked. Note that this applies to a maximum of 3 pods at a time in parallel. Horizon 2006 now supports parallel upgrades of Connection Servers. This new format applies to product installations and Horizon Console as well. We’ve moved to the YYMM-style format to version the Horizon Server, Horizon Client and Horizon Agent.

Here are some of the most notable new enhancements and updates to the platform:

Vmware horizon client latest version