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 Select the global entitlement and click Edit.
4 To modify the name or description of the global entitlement, type a new name or description in the
Name or Description text box in the General pane.
The name can contain between 1 and 64 characters. The description can contain between 1 and 1024
characters.
5 To modify a global entitlement policy, select or deselect the policy in the Policy pane.
Policy Description
Scope
Specifies where to look for desktops that satisfy a desktop request from the
global entitlement. You can select only one scope policy.
n
All sites - View looks for desktops on any pod in the pod federation.
n
Within site - View looks for desktops only on pods in the same site as
the pod to which the user is connected.
n
Within pod - View looks for desktops only in the pod to which the
user is connected.
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.
Automatically clean up redundant
sessions
Logs off extra user sessions for the same entitlement.. This option is
available only for floating entitlements.
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.
Default display protocol
Specifies the default display protocol for desktops in the global
entitlement.
6 Click OK to save your changes.
Delete a Global Entitlement
You can use View Administrator to permanently delete a global entitlement. When you delete a global
entitlement, all of the users who are dependent on that global entitlement for desktops cannot access their
desktops. Existing desktop sessions remain connected.
You can also use the lmvutil command to delete a global entitlement. See “Deleting a Global Entitlement,”
on page 49.
Procedure
1 Log in to the View Administrator user interface for any View Connection Server instance in the pod
federation.
2 In View Administrator, select Catalog > Global Entitlements.
3 Click the global entitlement to delete and click Delete.
4 Click OK in the confirmation dialog box.
Chapter 4 Managing a Cloud Pod Architecture Environment
VMware, Inc. 33