7.0
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
- Initialize the Cloud Pod Architecture Feature
- Join a Pod to the Pod Federation
- Create and Configure a Global Entitlement
- Create and Configure a Site
- Assign a Home Site to a User or Group
- Create a Home Site Override
- Test a Cloud Pod Architecture Configuration
- Example: Setting Up a Basic Cloud Pod Architecture Configuration
- 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
- Add a Pod to a Site
- Modifying Global Entitlements
- Managing Home Site Assignments
- 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
Options
You can specify these options when you modify a global entitlement. Some options apply only to global
desktop entitlements or only to global application entitlements.
Table 5‑9. Options for Modifying Global Entitlements
Option Description
--entitlementName
Name of the global entitlement to modify.
--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.
--description
(Optional) Description of the global entitlement. The description can
contain between 1 and 1024 characters.
--disabled
(Optional) Disables a previously enabled global entitlement.
--enabled
(Optional) Enables a previously disabled global entitlement.
--fromHome
(Optional) If the user has a home site, causes View to begin searching 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.
--disableFromHome (Optional) Disables the --fromHome option function if the --fromHome
option was previously specified for the global entitlement.
--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.
--disableMultipleSessionAutoClean (Optional) Disables the --multipleSessionAutoClean option function
if the --multipleSessionAutoClean option was previously specified
for the global entitlement.
--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.
--disableRequireHomeSite (Optional) Disables the --requireHomeSite option function if the
--requireHomeSite option was previously specified for the global
entitlement.
--defaultProtocol
(Optional) Default display protocol for desktops or applications in the
global entitlement. Valid values are RDP, PCOIP, and BLAST for global
desktop entitlements and PCOIP and BLAST for global application
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.
Chapter 5 lmvutil Command Reference
VMware, Inc. 49