7.0
Table Of Contents
- View Integration
- Contents
- View Integration
- Introduction to View Integration
- Integrating View with the Event Database
- Using View PowerCLI
- Getting Started with View PowerCLI
- View Administrator, PowerCLI Cmdlets, and View Command-Line Interfaces Compared
- View PowerCLI cmdlet Reference
- View PowerCLI cmdlet Parameters
- Examples of Using View PowerCLI cmdlets
- Managing View Connection Server Instances
- Managing vCenter Server Instances in View
- Managing Desktop Pools
- Creating and Updating Automatically Provisioned Desktop Pools
- Creating and Updating Linked-Clone Desktop Pools
- Creating and Updating Manually Provisioned Desktop Pools
- Creating and Updating Manual Unmanaged Desktop Pools
- Displaying Information About Users and Groups
- Managing Desktop Entitlements
- Managing Remote Sessions
- Managing Virtual Machines
- Displaying Information About Physical Machines
- Updating Virtual Machine Ownership
- Displaying Event Reports
- Displaying and Updating Global Settings
- Displaying and Adding License Keys
- Examples of Using View PowerCLI to Perform Advanced Tasks
- Assigning Multiple Network Labels to a Desktop Pool
- Network Label Configuration File Format
- Example Network Label Configuration File
- Obtain and Export NIC and Network Label Information
- Verify and Edit a Network Label Configuration File
- Deploy a Desktop Pool That Uses Multiple Network Labels
- Displaying Network Label Assignments for a Pool
- Displaying Network Label Assignments for a Virtual Machine
- Displaying vCenter Server Network Label Assignments for a Virtual Machine
- Disable Automatic Network Label Assignments
- Customizing LDAP Data
- Integrating View with Microsoft SCOM
- Setting Up a SCOM Integration
- Assign a Name to the View Connection Server Group
- View Management Packs
- Import the View Management Packs on the SCOM Server
- Enable a Proxy Agent on a View Connection Server Host or Security Server
- Run the Discovery Script in the Operations Manager Console
- View Connection Server and Security Server Managed Objects
- View Object Classes and Relationships
- Monitoring View in the Operations Manager Console
- Setting Up a SCOM Integration
- Examining PCoIP Session Statistics with WMI
- Setting Desktop Policies with Start Session Scripts
- Index
Using View PowerCLI 3
View PowerCLI provides an easy-to-use PowerShell interface to View. You can use View PowerCLI cmdlets
to perform various administration tasks on View components.
This chapter includes the following topics:
n
“Getting Started with View PowerCLI,” on page 27
n
“View Administrator, PowerCLI Cmdlets, and View Command-Line Interfaces Compared,” on
page 30
n
“View PowerCLI cmdlet Reference,” on page 34
n
“View PowerCLI cmdlet Parameters,” on page 36
n
“Examples of Using View PowerCLI cmdlets,” on page 40
n
“Examples of Using View PowerCLI to Perform Advanced Tasks,” on page 46
n
“Assigning Multiple Network Labels to a Desktop Pool,” on page 52
Getting Started with View PowerCLI
PowerShell is a command line and scripting environment designed for Microsoft Windows. PowerShell uses
the .NET object model and provides administrators with management and automation capabilities. You
work with PowerShell by running commands, which are called cmdlets in PowerShell. The command line
syntax for View PowerCLI cmdlets is the same as generic PowerShell syntax.
The View PowerCLI cmdlets are defined in the PowershellServiceCmdlets.dll file, which is installed in the
C:\Program Files\VMware\VMware View\Server\bin directory. The PowershellServiceCmdlets.dll file
constitutes the VMware.View.Broker snapin.
You can edit and extend the View PowerCLI cmdlets script configuration file, InitViewCmdlets.ps1, to
define cmdlet aliases, configure the environment, and set startup actions. InitViewCmdlets.ps1 is in the
Extras folder in the View installation directory.
You can use View PowerCLI cmdlets in conjunction with vSphere PowerCLI cmdlets. vSphere PowerCLI
cmdlets provide an administrative interface to VMware vSphere. If vSphere PowerCLI is installed on a View
Connection Server instance, the vSphere PowerCLI cmdlets load when you launch View PowerCLI.
You can refer to virtual machines and vCenter Server instances by ID in View PowerCLI, but you cannot
pass these entities as objects. For other vSphere objects, such as resource pools and folders, you must
provide a full path. You can use View PowerCLI cmdlets to examine the configuration of vCenter Server
instances within View.
For general information about using PowerShell, see the Microsoft documentation.
VMware, Inc.
27