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
lmvutil Command Authentication
To use the lmvutil command to configure and manage a Cloud Pod Architecture environment, you must
run the command as a user who has the Administrators role.
You can use View Administrator to assign the Administrators role to a user. See the View Administration
document.
The lmvutil command includes options to specify the user name, domain, and password to use for
authentication.
Table 5‑1. lmvutil Command Authentication Options
Option Description
--authAs
Name of a View administrator user. Do not use domain\username or user principal
name (UPN) format.
--authDomain
Fully qualified domain name for the View administrator user specified in the
--authAs option.
--authPassword Password for the View administrator user specified in the --authAs option. Entering
"*" instead of a password causes the lmvutil command to prompt for the password
and does not leave sensitive passwords in the command history on the command
line.
For example, the following lmvutil command logs in the user domainEast\adminEast and initializes the
Cloud Pod Architecture feature.
lmvutil --authAs adminEast --authDomain domainEast --authPassword "*" --initialize
You must use the authentication options with all lmvutil command options except for --help and
--verbose.
lmvutil Command Output
The lmvutil command returns 0 when an operation succeeds and a failure-specific non-zero code when an
operation fails.
The lmvutil command writes error messages to standard error. When an operation produces output, or
when verbose logging is enabled by using the --verbose option, the lmvutil command writes output to
standard output.
The lmvutil command produces only US English output.
lmvutil Command Options
You use the command options of the lmvutil command to specify the operation to perform. All options are
preceded by two hyphens (--).
For lmvutil command authentication options, see “lmvutil Command Authentication,” on page 38.
Table 5‑2. lmvutil Command Options
Option Description
--activatePendingCertificate
Activates a pending SSL certificate. See “Activating a
Pending Certificate,” on page 60.
--addGroupEntitlement
Associates a user group with a global entitlement. See
“Adding a User or Group to a Global Entitlement,” on
page 52.
Administering View Cloud Pod Architecture
38 VMware, Inc.