[music]
Welcome to the VMware Horizon 7.6 and Client 4.9 Technical What's New Overview.
My name is Hilko Lantinga and I'm a Senior End-User Computing Architect at VMware. FIrst we will look at what's new with VMware Horizon 7.6 on the server,
and then the agent, and finally on the 4.9 Client.
Let's have a look at Horizon server 7.6. Previously, for subscription-based licenses, Workspace ONE mode was required to be enabled.
Now a cloud connection replaces that requirement with licenses from the cloud. These license types are available in either apps edition or VDI edition.
After installation or when performing a switch from perpetual licenses means the customer can deploy both default on a sponsor's and
doesn't have to offer a licensed Horizon administrator.
Licenses are validated every 10 days and renewal reminders are shown when entering the console.
ACTPS are customers for cloud only, and customers have the option to unplug the connector and to propetualize the Horizon administrator.
Cloud Connector will manage subscription license, and there is no change to Horizon 7 and to deploy and manage Horizon. Also note change in how end users connect to the desktops.
After the deployment, you log in to the Connector with a My VMware account. Then you provide your Connection Server SPDN,
credentials, and then
you provide information to identify the bulk later.
After that, the Connector will be configured
and Horizon is licensed. With VMware Cloud on Amazon Web Services (AWS), the full, software-defined data center, vSphere, and NSX, is delivered as a cloud services on bare metal Amazon hardware.
In this cloud data center, you can deploy any application, including Horizon 7 v7.6 without the need to worry about
maintaining vSphere components. The combination of Horizon 7 v7.6 and VMC 1.5 has Elastic DRS and cluster nodes, vSAN encryption and stretched cluster
and cluster support and the same limitations as on-premises supply.
Support for virtualization-based security and virtual TPM.
On the Horizon 7v7.6 suite, the following Enterprise features are now available: User Environment Manager, and the private beta from App Volumes and instant clone, which will be
available from a beta site. With Instant Clones, the power of non-persistent virtual machines are brought to VMware Cloud on AWS.
Instant clones allow simplified management, follow-up supervisioning, and consume less space than Full Clone.
Elastic DRS is able to automatically scale up or down, plus the resources based on amount. To facilitate growing or shrinking of the cluster,
or just as satisfy the SLAs, the customer can set minimum and maximum thresholds.
These threshholds are used in automatic scaling, up or down a cluster.
Combining this with our of automatically reduced costs. When an instance of VMware Cloud on AWS is created, two resource pools exist.
A management resource pool with reservations that contain vCenter and MSX, which is managed by VMware,
and the compute resource, which is managed by the customer. The resource pool is a logical obstruction for flexible management of resources.
As the management components of Horizon 7 v 7.6 are shared with all users, no single user should be able to influence a performance and as such, the
management component should be deployed in a separate resource pool with reservations when separate clusters are not used.
As physical memory cannot be shared between virtual machines, and swapping or ballooning should be avoided at all costs, all memory should be reserved for all of Horizon virtual machines.
This includes management components, virtual desktops, and remote desktop session hosts.
CPU reservations are shared when not being used, and reservations specifies the guarantee minimum allocation for virtual machines,
which for the management components should be the amount of CPU usage times CPU frequency, which currently is 2300 for VMware Cloud on AWS.
Any amount of CPU not actively used for the management components will still be available
for virtual desktops and remote desktop session hosts when they are not deployed to a separate cluster.
As a remote desktop session hosts can facilitate more users per virtual CPU than virtual desktops, the higher share should be given to them.
As an example, if a remote desktop session host with 8 virtual CPUs facilitates 28 users, and a
virtual desktop with 2 CPUs facilitates a single user, the remote desktop session host that is
facilitating 7 times the amount of virtual users per CPU, and as such would also desktops have a default share of
1000, the remote desktop session hosts should have a CPU share of 7000, when not deployed to a separate cluster.
This number should also be adjusted to require the amount of resources and could be different between a virtual desktop session and a remote desktop session.
Besides a reservation on the resource pool, a reservation on the virtual machine should be set. This ensures that extra actual virtual machines
added to the resource pool later can't consume any required resources
and that the reservation is kept at the HA failover time. This virtual machine-level reservations
do not remove the requirement for reservations on the resource pool. As virtual machines-level reservations are only taken into account when the virtual machine is powered on.
So the reservation could be taken by other virtual machines when they are powered off temporarily.
Besides the features listed earlier, now there is also support for vSphere 6.5 update 2.
With RDSH in the cloud pod federation, per-device and mixed licenses are supported.
And there is support for all role-based action control files in the new Administrator Console which also has improved performance.
Let's have a look at what's new with BLAST. In 7.5, IPv6 support was added, but now UDP or the Network Intelligent Profiles and Adaptive Transport are available too.
With BLAST Extreme a beta for H.265 or HEVC is available. Part of the changes for HEVC include the
comparison and larger difference coding areas improved by block size implementation, improved prediction, and improved motion handling.
Effective use of these improvements requires much more signal processing capacity for compressing the video and has less impact on the
amount of computation needed for decompression. Which is why, at least in this beta, solicit is required.
It also requires a separate build of Windows-only agent and clients. You can now establish and differentiate a service points the assume
from 0-263 and BLAST traffic to specify the quality as specified by the various individual settings for
each network hub. On the right, we see the DSCDs between PLO. Here, you can enable the marking and then set optional decimal values for any hub.
As an example, a short forwarding 144 would be the number value 38, and high-priority forwarding would be 46.
Windows 10 1809 will be on the pilot, and offered as a Tech Preview from VMware until it is fully supported.
As with all new OS releases, VMware supports them within 30 days. Once Microsoft declares releases as broad. Both can take 3 to 4 months
post pilot. Ubuntu 1804 is now supported as a guest operating system with single sign-on. RedHat 7.4 and 7.5 are supported with
single sign-on. Instant clones are now available for RedHat at 7.1 and higher. As a beta available for accessing physical machines running Windows 10
1803 with support for CPU acceleration, real time audio/video, ThinPrint, Skype for Business, Client Drive, Redirection,
MMR, Flash, and a single five redirection. Now in this beta, there is no support for the other types of redirection, nor for seamlessly Windows, Wakeup on LAN,
LDP, DPI synch, or session collaboration. Both HTTP Live Streaming and Dynamic Adaptive Streaming over HTTP are adaptive bitrate streaming formats.
In general, AVR streams provide multiple versions of the same content with different quality
and allows the player application to dynamically switch between these streams, depending on available resources.
To use this feature, you add the site of the group policy settings for an HTML5 redirections, install the browser plug-in, and then you can see that the
functions work in the arc as shown in the browser bar. vDGA and vGPU or MxGPU support has been added for videos high-compute P100 and V100 card.
Plus for AMDs Radion Pro V340, which is not supported for Blast hardware yet.
Client GPS redirection is available for Internet Explorer, a plug-in logs a script in HTML5 Geolocation API calls and forwards them to the clients redirection, if the site is white-listed.
Displaying Client Drive Redirection and network location got added in 7.5, to enable the Drive to be used
in applications like body. Now it is the only available option by default. If you want a list of all the others again too, you can set this drive redirection.
Improvements have been made to the speed of small files as well. Unmanaged desktop support for 7.6.
For example, you could run vGPU links, VDI desktops with connection
service to Unified Access Gateway (UAG), vCR in a non-vDR-based on EC2. RedHat/CentOS with clipboard and audio out are supported.
To allow other 32-bit-only plug-ins to be used in the virtualization pack, it is now possible to install a 32-bit version on a 64-bit VM.
It already used the Windows Proxy settings before, but now they are used for multiple endpoint calls as well.
Now let's take a look at what's new in the clients. For Windows clients, there is a GPO to enable clipboard actions in the Windows Event Log.
And another GPO to configure displaced scaling. There is a command-line option to minimize the client's connection to the broker. In the client,
there is an option to configure keyboard shortcut to alter monitor selection.
On the iOS, background applications terminate after being idle for 20 minutes or so. The client now automatically reconnects if the time limit has not been exceeded.
Just as with Android, it is now possible to push the Connection Server list through AirWatch. MacOS support has been updated to the latest release, and now supports 4:4:4 Chroma subsampling, keyboard language synchronization, and IPv6.
RDP is no longer available, and support for a 3rd-party Windows manager called Moom is added. With Linux Client, Ubuntu 18.04 is now supported,
DPI sync and scaling, and 4:4:4 Chroma subsamples. The client toolbar is hidden by default, and seamless Windows are enabled by default.
There are client options to override the defaults. The Chrome native client
ChromeOS 67 and 68 are supported, just as multi-touch and Smartcard without single sign-on, which is a platform limitation.
Internationalization support for Chinese, Japanese, Korean, French, German, and Spanish has been added.
The Android client version 9, or Pie, and IPv6 are now supported. Unity has been added to support System Tray redirection as well.
For more information, go to techzone.vmware.com.
[music]