Administering View Cloud Pod Architecture
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
Options
You can specify these options when you create a global entitlement.
Table 5‑8. Options for Creating Global Entitlements
Option Description
--entitlementName
Name of the global entitlement. 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.
--scope
Scope of the global entitlement. Valid values are as follows:
n
ANY. View looks for desktops on any pod in the pod federation.
n
SITE. View looks for desktops only on pods in the same site as the
pod to which the user is connected.
n
LOCAL. View looks for desktops only in the pod to which the user is
connected.
--isDedicated
Creates a dedicated entitlement. A dedicated entitlement can contain only
dedicated desktop pools. To create a floating entitlement, use the
--isFloating option. An entitlement can be either dedicated or floating.
You cannot specify the --isDedicated option with the
--multipleSessionAutoClean option.
--isFloating
Creates a floating entitlement. A floating entitlement can contain only
floating desktop pools. To create a dedicated entitlement, specify the
--isDedicated option. An entitlement can be either floating or
dedicated.
--disabled
(Optional) Creates the global entitlement in the disabled state.
--description
(Optional) Description of the global entitlement. The description can
contain between 1 and 1024 characters.
--fromHome
(Optional) If the user has a home site, causes View to look for desktops on
the user's home site. If the user does not have a home site, View begins
searching for desktops on the site to which the user is currently
connected.
--multipleSessionAutoClean
(Optional) Logs off extra user sessions for the same entitlement. 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 specify 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.
--requireHomeSite
(Optional) Causes the global entitlement to be available only if the user
has a home site. This option is applicable only when the --fromHome
option is also specified.
--defaultProtocol
(Optional) Default display protocol for desktops in the global entitlement.
Valid values are RDP and PCOIP.
Example
lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" --createGlobalEntitlement
--entitlementName "Agent Sales" --scope LOCAL
--isDedicated
Chapter 5 lmvutil Command Reference
VMware, Inc. 47