Administration

Example 2: Existing User Session
This example illustrates how session placement might occur for a farm that contains six RDS hosts when a
user session currently exists on one of the RDS hosts. An RDS host that contains a session in which a user
has previously run an application is always reused for the same application.
1 A user session already exists on RDS host 3. RDS host 3 has a load preference of MED. The remaining
RDS in the hosts in the farm (the spare list) have the following load preferences.
RDS Host Load Preference
1 MED
2 LOW
4 HIGH
5 LOW
6 BLOCK
2 View sorts the RDS hosts in the spare list into two buckets according to load preference. View discards
RDS host 6 because View Agent reported a load preference of BLOCK.
Bucket Load Preference RDS Host
1 HIGH
MED
4
1
2 LOW
LOW
2
5
3 View randomizes the bucket order.
Bucket Load Preference RDS Host
1 HIGH
MED
4
1
2 LOW
LOW
5
2
4 View adds the RDS host that contains the existing session to the top of the new bucket ordered list.
RDS Host Session Placement Order
3
4
1
5
2
Configure an Anti-Affinity Rule for an Application Pool
When you configure an anti-affinity rule for an application pool, View Connection Server attempts to launch
the application only on RDS hosts that have sufficient resources to run the application. This feature can be
useful for controlling applications that consume large amounts of CPU or memory resources.
An anti-affinity rule consists of an application matching pattern and a maximum count. For example, the
application matching pattern might be autocad.exe and the maximum count might be 2.
View Administration
170 VMware, Inc.