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
Table 5‑8. Options for Creating Global Entitlements (Continued)
Option Description
--multipleSessionAutoClean
(Optional) Logs off extra user sessions for the same entitlement. Multiple
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 desktop
entitlement. Valid values are RDP and PCOIP.
Applies only to global desktop entitlements.
--htmlAccess
(Optional) When you specify this option, users can use the HTML Access
feature to access resources in the global entitlement. With HTML Access,
end users can use a Web browser to access remote resources and are not
required to install any client software on their local systems.
Examples
lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" --createGlobalEntitlement
--entitlementName "Windows 8 Desktop" --scope LOCAL --isDedicated
lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" --
createGlobalApplicationEntitlement --entitlementName "Microsoft Office PowerPoint" --scope LOCAL
Modifying a Global Entitlement
To modify a global desktop entitlement, use the lmvutil command with the --updateGlobalEntitlement
option. To modify a global application entitlement, use the lmvutil command with the
--updateGlobalApplicationEntitlement option.
Syntax
lmvutil --updateGlobalEntitlement --entitlementName name [--scope scope] [--description text]
[--disabled] [--enabled] [--fromHome] [--disableFromHome] [--multipleSessionAutoClean]
[--disableMultipleSessionAutoClean][--requireHomeSite] [--disableRequireHomeSite]
[--defaultProtocol value] [--htmlAccess] [--disableHtmlAccess]
lmvutil --updateGlobalApplicationEntitlement --entitlementName name [--scope scope]
[--description text] [--disabled] [--enabled] [--fromHome] [--disableFromHome]
[--multipleSessionAutoClean] [--disableMultipleSessionAutoClean] [--requireHomeSite]
[--disableRequireHomeSite] [--htmlAccess] [--disableHtmlAccess] [--appVersion value]
[--appPublisher value] [--appPath value]
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 among all pods in the pod federation.
These commands return an error message if the global entitlement does not exist, the scope is invalid, the
Cloud Pod Architecture feature is not initialized, or the commands cannot update the global entitlement.
Administering View Cloud Pod Architecture
48 VMware, Inc.