Integration
Table Of Contents
- View Integration
- Contents
- Introduction
- Integrating with the Event Database
- Using View PowerCLI
- Introduction to View PowerCLI
- View PowerCLI Cmdlets
- View Administrator, View PowerCLI Cmdlet, and vdmadmin Operations
- View PowerCLI Cmdlet Parameters
- Examples of Using View PowerCLI Cmdlets
- Displaying Information About a View Connection Server Instance
- Updating the Configuration of a View Connection Server Instance
- Managing the Configuration of vCenter Servers 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 Manual Unmanaged Desktop Pools
- Creating and Updating Desktops Provisioned by RDS Hosts
- Obtaining Information About Users and Groups from Active Directory
- Managing Desktop Entitlements
- Managing Remote Sessions
- Managing Virtual Machines
- Displaying Information About Physical Computers
- Updating the Ownership of Machines
- Displaying Information About Events
- Managing the Global Configuration of View
- Managing View Licenses
- Examples of Using View PowerCLI for Enhanced Functionality
- Assign Multiple Network Labels to a Desktop Pool
- Customizing LDAP Data
- Integrating with SCOM
- View Management Packs
- Name a View Connection Server Group
- Import the View MPs
- View Discovery Script
- Run the Discovery Script
- Display Discovered Objects
- Display Managed Objects
- Views and Monitors
- Enable a Proxy Agent on a Server
- Display Performance Data
- Display Information About an Alert
- Restart a Service
- Exclude a Domain from Connectivity Monitoring
- Close Alerts
- Class and Relationship Definitions
- Examining PCoIP Session Statistics
- Dynamically Setting Desktop Policies with Start Session Scripts
- Index
View Integration
66 VMware, Inc.
VMware.View.Library.mp contains class and relationship definitions for the managed objects in View.
See “Class and Relationship Definitions” on page 71.
VMware.View.Image.Library.mp contains the graphics that represent the classes that are defined in
VMware.View.Library.mp.
Name a View Connection Server Group
You can assign a name to a group of one or more View Connection Server hosts and security servers. The
Operations Manager console displays this name to help you identify the group within SCOM.
To name the View Connection Server group
On one of the View Connection Server hosts in the group, use the -C and -c options with the vdmadmin
command.
vdmadmin -C -c group_name
For example, set the name of a View Connection Server group to VCSG01.
vdmadmin -C -c VCSG01
Import the View MPs
When you install the View Connection Server software, the View MPs are also loaded onto the View
Connection Server instance or security server. You can copy the View MPs to a SCOM server and use the
Import Management Packs wizard from the Operations Manager console to import them.
To import the View MPs on a SCOM server
1 Copy the View MPs from their installation directory (usually C:\Program Files\VMware\VMware
View\Server\extras\ManagementPacks) on a View Connection Server instance or security server to
the SCOM server.
2 In the Operations Manager console, right click Administration\Management Packs, and select Import
Management Packs.
3 Use the Import Management Packs wizard to import the View MPs.
4 (Optional) Run the discovery script manually for the systems on which the View software is installed.
More more information, see “Run the Discovery Script” on page 67.
View Discovery Script
The VMware.View.Discovery MP contains a script that finds View installed systems. The discovery script
probes the registries of Windows servers for entries that indicate the version of the View software, the type of
server, and the name and ID of the View Connection Server group. If the script detects that a View server is
installed on a computer, it creates instances of the object classes that are defined in the VMware.View.Library
MP and establishes the relationships between these managed objects.
The script can only discover a Windows server if you have used the Operations Manager console to enable the
proxy agent for the server. See “Enable a Proxy Agent on a Server” on page 70.
The discovery script is scheduled to run once every hour. You can also perform the discovery manually from
the Operations Manager console. See “Run the Discovery Script” on page 67.
You can verify the objects that the discovery agent has created for a server by viewing them in the Operations
Manager console. See “Display Discovered Objects” on page 67.
The agent discovers the following managed objects for a Connection Server.
N
OTE There is a known problem with McAfee VirusScan Enterprise 8.0i blocking the operation of Visual Basic
scripts that are used by SCOM. For more information and details of the available patch, go to
http://support.microsoft.com/kb/890736/en-us.