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 and Applications 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 and Application 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
- lmvutil Command Use
- Initializing the Cloud Pod Architecture Feature
- Disabling the Cloud Pod Architecture Feature
- Managing Pod Federations
- Managing Sites
- Managing Global Entitlements
- Managing Home Sites
- Viewing a Cloud Pod Architecture Configuration
- Listing Global Entitlements
- Listing the Pools in a Global Entitlement
- Listing the Users or Groups in a Global Entitlement
- Listing the Home Sites for a User or Group
- Listing the Effective Home Site for a User
- Listing Dedicated Desktop Pool Assignments
- Listing the Pods or Sites in a Cloud Pod Architecture Topology
- Managing SSL Certificates
- Index
Syntax
lmvutil --createGlobalEntitlement --entitlementName name --scope scope
{--isDedicated | --isFloating} [--description text] [--disabled]
[--fromHome] [--multipleSessionAutoClean] [--requireHomeSite] [--defaultProtocol value]
[--htmlAccess]
lmvutil --createGlobalApplicationEntitlement --entitlementName name --scope scope
[--description text] [--disabled] [--fromHome] [--multipleSessionAutoClean]
[--requireHomeSite] [--htmlAccess]
Usage Notes
You can use these commands on any View Connection Server instance in a pod federation. View stores new
data in the Global Data Layer and replicates that data in all pods in the pod federation.
These commands return an error message if the global entitlement already exists, the scope is invalid, the
Cloud Pod Architecture feature is not initialized, or the commands cannot create the global entitlement.
Options
You can specify these options when you create a global entitlement. Some options apply only to global
desktop entitlements.
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 desktops and
applications list in Horizon Client for entitled users.
--scope
Scope of the global entitlement. Valid values are as follows:
n
ANY. View looks for resources on any pod in the pod federation.
n
SITE. View looks for resources only on pods in the same site as the
pod to which the user is connected.
n
LOCAL. View looks for resources only in the pod to which the user is
connected.
--isDedicated
Creates a dedicated desktop entitlement. A dedicated desktop entitlement
can contain only dedicated desktop pools. To create a floating desktop
entitlement, use the --isFloating option. A global desktop entitlement
can be either dedicated or floating. You cannot specify the
--isDedicated option with the --multipleSessionAutoClean option.
Applies only to global desktop entitlements.
--isFloating
Creates a floating desktop entitlement. A floating desktop entitlement can
contain only floating desktop pools. To create a dedicated desktop
entitlement, specify the --isDedicated option. A global desktop
entitlement can be either floating or dedicated.
Applies only to global desktop entitlements.
--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 resources
on the user's home site. If the user does not have a home site, View begins
searching for resources on the site to which the user is currently
connected.
Chapter 5 lmvutil Command Reference
VMware, Inc. 47