Book Image

Mastering VMware Horizon 7.8 - Third Edition

By : Peter von Oven, Barry Coombs
Book Image

Mastering VMware Horizon 7.8 - Third Edition

By: Peter von Oven, Barry Coombs

Overview of this book

Desktop virtualization can be tough, but VMware Horizon 7.8 changes all that. With a rich and adaptive UX, improved security,and a range of useful features for storage and networking optimization, there's plenty to love. But to properly fall in love with it, you need to know how to use it, and that means venturing deeper into the software and taking advantage of its extensive range of features, many of which are underused and underpromoted. This guide will take you through everything you need to know to not only successfully virtualize your desktop infrastructure, but also to maintain and optimize it to keep all your users happy. We'll show you how to assess and analyze your infrastructure, and how to use that analysis to design a solution that meets your organizational and user needs. Once you've done that, you'll find out how to build your virtualized environment, before deploying your virtualized solution. But more than that,we'll also make sure you know everything you need to know about the full range of features on offer, including the mobile cloud, so that you can use them to take full control of your virtualized infrastructure.
Table of Contents (21 chapters)
Free Chapter
Section 1: Installation and Configuration
Section 2: Building and Delivering the Virtual Desktop Experience
Section 3: Advanced Features, Troubleshooting, and Upgrading an Environment

Load-balancing published apps in Horizon View

The next thing we are going to cover is how the Connection Broker decides which of the RDS host servers in the farm that is running the requested application is actually going to deliver the application. There are two options for configuring load balancing.

For the first option, there is no real complicated science behind the load balancing from a Horizon View perspective. It is purely based on how many sessions are available on any given RDSH server. So, that means when a user logs in and launches a published application, the application is delivered from the server that has the highest amount of free sessions available; that is, the one that is least busy.

This is illustrated in the following diagram:

This first option works fine, but how does it know what each session is consuming in terms of resources? A particular host may well...