Administering View Cloud Pod Architecture

Entitling Users and Groups in the Pod Federation
In a traditional View environment, you use View Administrator to create entitlements. These local
entitlements entitle users and groups to a specific desktop or application pool on a View Connection Server
instance.
In a Cloud Pod Architecture environment, you create global entitlements to entitle users or groups to
multiple desktops and applications across multiple pods in the pod federation. When you use global
entitlements, you do not need to configure and manage local entitlements. Global entitlements simplify
administration, even in a pod federation that contains a single pod.
View stores global entitlements in the Global Data Layer. Because global entitlements are shared data,
global entitlement information is available on all View Connection Server instances in the pod federation.
You entitle users and groups to desktops by creating global desktop entitlements. Each global desktop
entitlement contains a list of member users or groups, a list of the desktop pools that can provide desktops
for entitled users, and a scope policy. The desktop pools in a global entitlement can be either floating or
dedicated pools. You specify whether a global entitlement is floating or dedicated during global entitlement
creation.
You entitle users and groups to applications by creating global application entitlements. Each global
application entitlement contains a list of the member users or groups, a list of the application pools that can
provide applications for entitled users, and a scope policy.
A global entitlement's scope policy specifies where View looks for desktops or applications when it allocates
desktops or applications to users in the global entitlement. It also determines whether View looks for
desktops or applications in any pod in the pod federation, in pods that reside in the same site, or only in the
pod to which the user is connected.
As a best practice, you should not configure local and global entitlements for the same desktop pool. For
example, if you create both local and global entitlements for the same desktop pool, the same desktop might
appear as a local and a global entitlement in the list of desktops and applications that Horizon Client shows
to an entitled user. Similarly, you should not configure both local and global entitlements for application
pools created from the same farm.
Finding and Allocating Desktops and Applications in the Pod
Federation
View Connection Server instances in a Cloud Pod Architecture environment use shared global entitlement
and topology configuration information from the Global Data Layer to determine where to search for and
how to allocate desktops and applications across the pod federation.
When a user requests a desktop or application from a global entitlement, View searches for an available
desktop or application in the pools that are associated with that global entitlement. By default, View gives
preference to the local pod, the local site, and pods in other sites, in that order.
For global desktop entitlements that contain dedicated desktop pools, View uses the default search behavior
only the first time a user requests a desktop. After View allocates a dedicated desktop, it returns the user
directly to the same desktop.
You can modify the search and allocation behavior for individual global entitlements by setting the scope
policy and configuring home sites.
Administering View Cloud Pod Architecture
10 VMware, Inc.