6.1
Table Of Contents
- Administering View Cloud Pod Architecture
- Contents
- Administering View Cloud Pod Architecture
- Introduction to Cloud Pod Architecture
- Designing a Cloud Pod Architecture Topology
- Creating Cloud Pod Architecture Sites
- Entitling Users and Groups in the Pod Federation
- Finding and Allocating Desktops in the Pod Federation
- Global Entitlement Example
- Cloud Pod Architecture Topology Limits
- Cloud Pod Architecture Port Requirements
- Security Considerations for Cloud Pod Architecture Topologies
- Setting Up a Cloud Pod Architecture Environment
- Managing a Cloud Pod Architecture Environment
- View a Cloud Pod Architecture Configuration
- View Pod Federation Health in View Administrator
- View Desktop Sessions in the Pod Federation
- Determine the Effective Home Site for a User
- Add a Pod to a Site
- Modifying Global Entitlements
- Remove a Home Site Association
- Remove a Pod From the Pod Federation
- Uninitialize the Cloud Pod Architecture Feature
- lmvutil Command Reference
- Index
3 Define the global entitlement.
a Type a name for the global entitlement in the Name text box.
The name can contain between 1 and 64 characters. The global entitlement name appears in the list
of available entitlements for the user in Horizon Client.
b (Optional) Type a description of the global entitlement in the Description text box.
The description can contain between 1 and 1024 characters. The global entitlement name appears in
the list of available entitlements for the user in Horizon Client.
c Select a user assignment policy for the global entitlement.
The user assignment policy specifies the type of desktop pool that the global entitlement can
contain. You can select only one user assignment policy.
Option Description
Floating
Creates a floating entitlement. A floating entitlement can contain only
floating desktop pools.
Dedicated
Creates a dedicated entitlement. A dedicated entitlement can contain
only dedicated desktop pools.
d Select a scope policy for the global entitlement.
The scope policy specifies where to look for desktops to satisfy a desktop request from the global
entitlement. You can select only one scope policy.
Option Description
All sites
View looks for desktops on any pod in the pod federation.
Within site
View looks for desktops only on pods in the same site as the pod to
which the user is connected.
Within pod
View looks for desktops only in the pod to which the user is connected.
e (Optional) If users have home sites, configure a home site policy for the global entitlement.
Option Description
Use home site
Causes View to look for desktops in the user's home site. If the user
does not have a home site and the Entitled user must have home site
option is not selected, the site to which the user is currently connected
is assumed to be the home site.
Entitled user must have home site
Causes the global entitlement to be available only if the user has a
home site. This option is available only when the Use home site option
is selected.
f (Optional) If you are creating a floating entitlement, use the Automatically clean up redundant
sessions option to specify whether to automatically clean up redundant sessions.
Multiple floating desktop sessions can occur when a pod that contains a session goes offline, the
user logs in again and starts another session, and the problem pod comes back online with the
original session. When multiple sessions occur, Horizon Client prompts the user to select a session.
This option determines what happens to sessions that the user does not select. If you do not select
this option, users must manually end their own extra sessions, either by logging off in
Horizon Client or by launching the sessions and logging them off.
g Select the default display protocol for desktops in the global entitlement and specify whether to
allow users to override the default display protocol.
h Select whether to allow users to reset desktops in the global entitlement.
Administering View Cloud Pod Architecture
18 VMware, Inc.