vCenter Operations Manager for View Integration Guide 1.0 - VMware

VMware vCenter Operations Manager 

for View Integration Guide 

vCenter Operations Manager for View v1.0 

This document supports the version of each product listed and 

supports all subsequent versions until the document is replaced 

by a new edition. To check for more recent editions of this 

document, see http://www.vmware.com/support/pubs. 

EN-000889-00

vCenter Operations Manager for View Integration Guide 

You can find the most up-to-date technical documentation on the VMware Web site at: 

http://www.vmware.com/support/ 

The VMware Web site also provides the latest product updates. 

If you have comments about this documentation, submit your feedback to: 

docfeedback@vmware.com 

Copyright © 2012 VMware, Inc. All rights reserved. This product is protected by U.S. and international copyright and 

intellectual property laws. VMware products are covered by one or more patents listed at 

http://www.vmware.com/go/patents. 

VMware is a registered trademark or trademark of VMware, Inc. in the United States and/or other jurisdictions. All other marks 

and names mentioned herein may be trademarks of their respective companies. 

VMware, Inc. 

3401 Hillview Ave. 

Palo Alto, CA 94304 

www.vmware.com 

2 VMware, Inc.

Contents 

About This Book 5 

1 Introducing vCenter Operations Manager for View 7 

Features of vCenter Operations Manager for View 7 

Customizing Dashboards and Widgets 7 

Health 7 

Architecture 8 

Steps to Set Up vCenter Operations Manager for View 9 

2 System Requirements 11 

Prerequisites before deploying vCenter Operations Manager for View 11 

Requirements for vCenter Operations Manager for View 12 

System Requirements for vCenter Operations Manager for View Adapter 12 

Support for up to 1000 desktop sessions 12 

Support for up to 2000 desktop sessions 12 

Download vCenter Operations Manager for View 12 

Support for Oracle databases that provide View Events 13 

3 Installing the vCenter Operations Manager for View Adapter 15 

Running the vCenter Operations Manager for View Windows Installer 15 

4 Configuring the vCenter Operations Manager for View Adapter 17 

Configuring the View Connection Server 17 

Configuring the vCenter Operations for View Adapter server 18 

Configuring View connection settings and credentials (View Settings tab) 18 

Default Port Settings for PowerShell 18 

Configuring vCenter Operations Manager Enterprise server settings and credentials (vCenter 

Operations Settings tab) 20 

Configuring desktop VM settings and credentials (Desktop Settings) 21 

Windows XP Firewall Exceptions 21 

Windows Vista Firewall Exceptions 21 

Configuring Advanced settings (Advanced Settings tab) 23 

5 Deploying and Using vCenter Operations Manager for View Dashboards 27 

Installing the Dashboards 27 

Connect to the vCenter Operations Manager Admin Console 27 

Deploy the vCenter Operations Manager for View Adapter PAK file 28 

Using the vCenter Operations Manager Enterprise User Interface 30 

Validating your installation 30 

Adding vCenter Operations Manager Enterprise User Accounts 30 

Using the Dashboards 31 

Overview of dashboards and widgets 31 

View Main dashboard 31 

View Users dashboard 34 

View Top Desktop VMs 37 

View Pools dashboard 38 

View Desktop Sessions dashboard 40 

VMware, Inc. 3


vSphere Infrastructure dashboard 42 

Appendix A, Important Metrics 45 


About This Book 

The vCenter Operations Manager for View Integration Guide describes how to install, configure, and use 

VMware ® vCenter Operations Manager for View an automated intelligence system for IT operations. 

Intended Audience 

This guide is intended for anyone who must install and configure vCenter Operations Manager for View or 

use it to manage and monitor a VDI Infrastructure. 

VMware Technical Publications Glossary 

VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitions 

of terms as they are used in VMware technical documentation go to http://www.vmware.com/support/pubs. 

Document Feedback 

VMware welcomes your suggestions for improving our documentation. If you have comments, send your 

feedback to docfeedback@vmware.com. 

VMware vCenter Operations Manager for View Documentation 

The documentation set for VMware vCenter Operations Manager for View consists of the following 

documents. 

� VMware vCenter Operations Manager Deployment and Configuration Guide. Contains conceptual and 

procedural information on using vCenter Operations Manager Enterprise. 

� vCenter Operations Manager Enterprise Getting Started Guide. Contains descriptions of VMWare vCenter 

Operations Manager Enterprise, its user interface, and key terms and concepts. It also describes how to 

set up dashboards and configure widgets. 

� vCenter Operations Manager for View Integration Guide, this document. 

Technical Support and Education Resources 

The following sections describe the technical support resources available to you. To access the current version 

of this book and other books, go to http://www.vmware.com/support/pubs. 

Online and Telephone Support 

To use online support to submit technical support requests, view your product and contract information, and 

register your products, go to http://www.vmware.com/support. 

Customers with appropriate support contracts should use telephone support for the fastest response on 

priority 1 issues. Go to http://www.vmware.com/support/phone_support. 



Support Offerings 

To find out how VMware support offerings can help meet your business needs, go to 

http://www.vmware.com/support/services. 

VMware Professional Services 

VMware Education Services courses offer extensive hands‐on labs, case study examples, and course materials 

designed to be used as on‐the‐job reference tools. Courses are available onsite, in the classroom, and live 

online. For onsite pilot programs and implementation best practices, VMware Consulting Services provides 

offerings to help you assess, plan, build, and manage your virtual environment. To access information about 

education classes, certification programs, and consulting services, go to http://www.vmware.com/services. 


1This 

Introducing vCenter Operations 

1 

Manager for View 

vCenter Operations Manager for View extends the functionality of vCenter Operations Manager Advanced 

and vCenter Operations Manager Enterprise to monitor and manage VMware® View environments. This is 

done through the vCenter Operations Manager for View Adapter which gets the topology from the VMware 

View environment, collects metrics and other types of information from managed desktops, and introduces 

this into vCenter Operations Manager Enterprise. 

Features of vCenter Operations Manager for View 

vCenter Operations Manager for View extends the functionality of vCenter Operations Manager Enterprise, 

and enables IT administrators and Help Desk specialists to monitor and manage the View VDI environments. 

vCenter Operations Manager for View is built on top of the vCenter Operations Manager Enterprise. 

Therefore, it includes the functionality of collecting performance data from monitored software and hardware 

resources in your enterprise and provides predictive analysis and real‐time information about problems in 

your VDI infrastructure. It presents data and analysis through alerts, in configurable dashboards, and 

predefined pages in the user interface. 

The View Adapter gets the topology from the View environment, and gets metrics and other types of 

information from the desktops, and passes the information into vCenter Operations Manager Enterprise. 

The typical users of vCenter Operations Manager for View are IT Admininistrators and Help Desk specialists. 

The IT Administrator typically would use vCenter Operations Manager for View to get a quick overview of 

how the View environment is behaving, and to view some of the important metrics associated with their View 

environment. A Helpdesk person may, in the process of assisting an end user with a VM or desktop issue, need 

to quickly see resources related to the end user’s session, and perform basic troubleshooting to view, analyze, 

and resolve the issues that exist. 

Customizing Dashboards and Widgets 

VMware View‐specific dashboards and resources are automatically configured when you install vCenter 

Operations Manager for View. These dashboards and resources added as part of the vCenter Operations 

Manager for View installation and deployment are preconfigured dashboards, resources, metrics, and alerts. 

As with vCenter Operations Manager Enterprise, you can customize your vCenter Operations Manager for 

View workspace. Depending on your access rights, you can add, delete, and arrange widgets on your 

dashboards, edit widget configuration options, and configure widget interactions. 

Widgets include configuration options that you can edit to customize them for your particular needs. The 

available configuration options vary depending on the widget type. For details on how to customize and 

configure dashboards and widgets in vCenter Operations Manager for View, see the vCenter Operations 

Manager Enterprise Getting Started Guide. 



Health 

vCenter Operations Manager for View incorporates the health ratings feature of vCenter Operations Manager 

Enterprise which gives you a quick overview of the current state of a resource in your VDI environment. 

vCenter Operations Manager Enterprise uses an internally‐generated metric instead of the Health badge used 

by vCenter Operations Manager Advanced. The vCenter Operations Manager Enterprise health score is 

calculated using resource metric anomalies and is best described as an indicator of how closely the resource is 

behaving to its “normal” observed behavior. If many resource metrics are outside their expected range, then 

this is reflected in a decreased Health score. 

For more details on understanding health ratings, see the vCenter Operations Manager Enterprise Getting Started 

Guide. 

Architecture 

vCenter Operations Manager for View is a solution built on top of the vCenter Operations Manager Enterprise 

platform which enables you to monitor your VMware View 5.0 VDI environment. 

The diagram below shows the relationship of vCenter Operations Manager Enterprise, the vCenter Operations 

Manager for View Adapter, and their relationships to other vCenter Operations Manager for View VDI 

components. 

Figure 1-1. vCenter Operations Manager for View Architecture 


Chapter 1 Introducing vCenter Operations Manager for View 

To use vCenter Operations Manager for View, there are two main components that you need to install: 

� vCenter Operations Manager Enterprise vApp v5.0.1 or higher 

For details on installing the vCenter Operations Manager Enterprise, see: 

https://www.vmware.com/pdf/vcops‐5‐installation‐guide.pdf 

� vCenter Operations Manager for View Adapter v1.0 

For information on installing the vCenter Operations Manager for View Adapter, see “Installing the 

vCenter Operations Manager for View Adapter” on page 15. 

You install the vCenter Operations Manager for View Adapter using an installation file on a separate Windows 

server VM. Installing and configuring these two components is described in the following chapters. 

Steps to Set Up vCenter Operations Manager for View 

The setup process for VMware vCenter Operations Manager for View is comprised of the following steps: 

1 Verify hardware/software requirements—see “System Requirements” on page 11 

2 Install and configure the vCenter Operations Manager Enterprise vApp. For information on how to do 

this, refer to the vCenter Operations Manager Enterprise documentation at the following URL: 

https://www.vmware.com/support/pubs/vcops‐pubs.html 

3 Install the vCenter Operations Manager for View adapter—“Installing the vCenter Operations Manager 

for View Adapter” on page 15. 

4 Run the EnableRemotePS.cmd script on the View Connection Server. See “Configuring the View 

Connection Server” on page 17. 

5 Configure the vCenter Operations Manager for View adapter on the View Adapter Windows server VM 

See “Configuring the vCenter Operations Manager for View Adapter” on page 17. 

6 Deploy dashboards—“Deploying and Using vCenter Operations Manager for View Dashboards” on 

page 27. 




2 

System Requirements 2 

The following sections describe the prerequisites, system requirements, and compatibilities for vCenter 

Operations Manager for View. 

This chapter includes the following topics: 

� “Prerequisites before deploying vCenter Operations Manager for View” on page 11 

� “Requirements for vCenter Operations Manager for View” on page 12 

� “Download vCenter Operations Manager for View” on page 12 

Prerequisites before deploying vCenter Operations Manager for View 

This is a list of prerequisites that must be performed before installing and deploying vCenter Operations 

Manager for View. 

� Obtain, download, install, and configure the vCenter Operations Manager Enterprise vApp. 

� vCenter Operations Manager for View v1.0 requires the vCenter Operations Manager Enterprise vApp, 

not the standalone version. 

NOTE Instructions in this guide assume that vCenter Operations Manager Enterprise vApp has already been 

installed and deployed. 

Refer to the vCenter Operations Manager Enterprise vApp documentation here: 

https://www.vmware.com/support/pubs/vcops‐pubs.html 

NOTE vCenter Operations Manager for View requires vCenter Operations Manager Enterprise vApp, version 

5.0.1 or higher. 

� You must install vCenter Operations Manager for View v1.0 into a View 5.0 or later VDI environment. 

Refer to the View documentation here: 

https://www.vmware.com/support/pubs/view‐pubs.html 

� The Windows Server 2008 R2 64‐bit operating system is the recommended server platform for the vCenter 

Operations Manager for View 1.0 Adapter installation. 

� Both SQL Server and Oracle database servers are supported for the View Events DB, but if you use Oracle 

database servers, you may need to update the client software. 

You may need to update the Oracle client libraries (ODAC) on the vCenter Operations for View Adapter 

server if View is configured with an Oracle Events database. For details, see “Support for Oracle databases 

that provide View Events” on page 13. 

� Before you install the vCenter Operations Manager for View Adapter, you must install the Microsoft .NET 

Framework version 3.5. 

NOTE Microsoft .NET version 3.5 ships with both Windows 2003 and Windows 2008 as an optional Windows 

component or feature, which you can enable from the Control Panel or Server Manager utilities. 



Requirements for vCenter Operations Manager for View 

The following lists system requirements for vCenter Operations Manager for View. 

NOTE vCenter Operations Manager for View supports up to 2000 concurrent desktop sessions (connected or 

disconnected). 

These requirements or recommendations include only logged‐on user sessions. Typically, only a portion of all 

VDI desktops are logged on at any given time. 

System Requirements for vCenter Operations Manager for View Adapter 

Support for up to 1000 desktop sessions 

� OS: Windows 2003 R2, Windows 2008 R2, 64‐bit OS 

� Processors: 2 cores, 2.8 Ghz or above 

� Memory: 6 GB 

� Disk Space: 30 GB 

Support for up to 2000 desktop sessions 

� OS: Windows 2003 R2, Windows 2008 R2, 64‐bit OS 

� Processors: 4 cores, 2.8 Ghz or above 

� Memory: 8 GB 

� Disk space: 30 GB 

NOTE The vCenter Operations Manager for View Adapter requires a 64‐bit Windows (Windows 2003 or 2008) 

VM. VMs that are 32‐bit based are not supported in this release. 

If the hardware and software environment has been set up properly, the complete vCenter Operations 

Manager for View installation and deployment process should take about 1 hour (excluding download times). 

Download vCenter Operations Manager for View 

This guide assumes that you have already purchased vCenter Operations Manager for View. If you have not 

purchased it yet, you can do so at the following URL: 

https://www.vmware.com/vmwarestore/datacenter‐products/buyoperations.html 

For permanent licensing keys go to the following URL: 

https://www.vmware.com/licensing/license.portal 

When downloading vCenter Operations Manager for View at the previous URL, You will see the following 

download: 

� View Adapter 64‐bit (encrypted zip) 

64‐bit: VMware-vcops-viewadapter-x86_64-1.0.0-XXXXXX.exe 

You will now have a Windows installation package containing an .exe file that you can install. 

The default installation folder is 

c:\Program Files\VMware\vCenter Operations\View Adapter 

� Oracle client libraries (ODAC) may need to be updated on the View Adapter server if View is configured 

with an Oracle Events database. 


Support for Oracle databases that provide View Events 

NOTE This may be required if you have a View installation using an Oracle Events DB. 

Chapter 2 System Requirements 

When adding support for Oracle View Events databases, the client libraries may need to be updated on the 

vCenter Operations for View adapter server, depending on the version of the Oracle DB server in use. 

You can download this update from the following link: 

NOTE This update is for 64‐bit systems only. 

http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html 

From this page, download the zip file from the 64‐bit ODAC 11.2 Release 4 (11.2.0.3.0) Xcopy for Windows 

x64 link and follow the instructions in the readme.html file included in the zip file. 




3 

Installing the vCenter Operations 

3 

Manager for View Adapter 

Installing vCenter Operations Manager for View consists of running an executable file, which starts an 

installation wizard. 

Prerequisites 

� Obtain and download vCenter Operations Manager for View from the following URL: 

https://www.vmware.com/vmwarestore/datacenter‐products/buyoperations.html 

NOTE The vCenter Operations Manager for View Adapter does not require license keys. However, license 

keys are required when installing the vCenter Operations Manager Enterprise vApp. 

On the VMWare download site, you will see the following: 

� View Adapter 64‐bit (encrypted zip) 

(64‐bit) VMware-vcops-viewadapter-x86_64-1.0.0.exe 

NOTE The vCenter Operations for View Adapter for 32‐bit systems is not supported. 

Running the vCenter Operations Manager for View Windows Installer 

After you have downloaded the installation package, you are ready to install the vCenter Operations Manager 

for View Adapter. 

After downloading the installation package, you will have an installer .exe file. 

Agree to the presented EULAs and follow the instructions presented by the installation wizard. 

After you install vCenter Operations Manager for View, the configuration utility will be launched by default. 

Proceed to “Configuring the vCenter Operations Manager for View Adapter” on page 17. 




4 

Configuring the vCenter Operations 

4 

Manager for View Adapter 

After installing vCenter Operations Manager for View you are ready to configure the vCenter Operations for 

View Adapter using the utility provided. 

Prerequisites 

NOTE Confirm that the vCenter Operations Manager Enterprise is installed and running before you start the 

vCenter Operations Manager for View adapter. 

The vCenter Operations Manager for View adapter needs access to a number of resources to collect 

information about the VMware View topology and metrics. Connection information and credentials are 

required for each resource, which you configure from the vCenter Operations View Adapter Settings utility. 

By default, the vCenter Operations View Adapter Settings utility is launched after installation completes. 

Additionally, you must configure the View Connection Server to allow remote PowerShell connections before 

the View Adapter service can be started. A script is included with the vCenter Operations Manager for View 

Installation package that you can use for this task, which is described in “Configuring the View Connection 

Server” on page 17. 

Configuring the View Connection Server 

Before starting the vCenter Operations Manager for View Adapter service, you must configure the View 

Connection Server. Configuration is necessary to enable remote PowerShell sessions and initialize View 

PowerShell extensions on the View Connection Server. 

1 Copy the PowerShell command EnableViewPS.cmd from the vCenter Operations Manager for View 

Adapter installation folder onto the VMware View Connection Server. 

The default installation folder for vCenter Operations Manager for View is: 

c:\Program Files\VMware\vCenter Operations\View Adapter 

2 On the View Connection Server, as administrator, run the following command: 

EnableViewPS.cmd 

The EnableViewPS.cmd script does the following: 

� Initializes the VMware View PowerCLI cmdlets. 

� Enable remote PowerShell sessions. 

� Open firewall ports needed for remote PowerShell sessions. 

NOTE In environments that have more than one View Connection Server, you only need to run the script on 

the one View Connection Server that you are configuring the vCenter Operations Manager for View Adapter 

for. You do not need to run the script on the other connection servers. 



Configuring the vCenter Operations for View Adapter server 

To configure the vCenter Operations for View adapter, you use the vCenter Operations for View Adapter 

Settings utility. By default, this utility is launched after the vCenter Operations for View Adapter installation 

completes. You can also start it from the Start Menu by using: 

Start Menu->VMware->vCenter Operations for View->View Adapter Settings 

When you initially run the View Adapter Settings utility, review each tab to fill in all appropriate credentials 

and connection settings. After installation, you can run the utility at any time from the Start menu to update 

the configuration. 

Each group of settings has a Test button that you can use to verify connection settings and credentials. After 

all settings are configured, click Apply to save the settings and start the vCenter Operations Manager for View 

Adapter service. 

IMPORTANT It is recommended that you click Test after configuring each group of settings on each 

configuration tab. This runs a test that the configuration is set up correctly so far. 

Configuring View connection settings and credentials (View Settings tab) 

You can configure View server connection settings and credentials on the View Settings tab. 

The username and password that you enter must have read access to the View Connection Server. (Typically, 

this account is included in the Local Admins group on the server). 

Default Port Settings for PowerShell 

The default ports for remote PowerShell are 

� 5985 (HTTP) 

� 5986 (HTTPS) 

Optionally, you can specify one or more View desktop pools that you want to monitor. If no pools are 

specified, then all pools will be monitored. 

Credentials for the View events database are optional but highly recommended. Additional View specific 

events, metrics, and alerts are collected when you provide access to the database (including desktop login and 

reconnection times). For details on how to set up the Events database, see “Support for Oracle databases that 

provide View Events” on page 13 and the vCenter Operations Manager Enterprise Administrator Guide. 


Figure 4-1. VMware View Settings tab 

Chapter 4 Configuring the vCenter Operations Manager for View Adapter 



Configuring vCenter Operations Manager Enterprise server settings and 

credentials (vCenter Operations Settings tab) 

Next, configure the vCenter Operations Manager Enterprise server settings and credentials on the vCenter 

Operations Settings tab. When using the vCenter Operations Manager Enterprise vApp, enter the name or 

IP address for the vCenter Operations Manager Enterprise UI VM, not the name or IP address for the Analytics 

VM. See Figure 4‐2. 

NOTE This information is specific to the vCenter Operations Manager Enterprise vApp, not the standalone 

version. 

By default, the vCenter Operations Manager for View vApp installation uses HTTPS and enables HTTP Post 

Adapter authentication. HTTP Post Adapter authentication requires that you provide additional credentials. 

NOTE The username and password specify a vCenter Operations Manager Enterprise user account rather 

than a domain account. 

Figure 4-2. vCenter Operations Manager Enterprise Settings tab 



Configuring desktop VM settings and credentials (Desktop Settings) 

You configure desktop VM settings and credentials on the Desktop Settings tab. It is highly recommended that 

you specify a desktop username and password. Without proper credentials, metric data will not be collected 

from desktop VMs and the connected VMware View clients will not be created. The credentials that you 

provide must specify a domain account, which is included in the Local Admins group on each desktop VM 

being monitored. 

Figure 4-3. vCenter Operations Manager for View Desktop Settings tab 

Each desktop VM must have the Remote Registry service and the Windows Management Instrumentation 

(WMI) service enabled and running for metric data to be collected for that VM. 

You must also configure the firewall settings on each desktop to allow inbound Remote Registry and WMI 

service requests. You can do this by either disabling the firewall or applying the following firewall exceptions 

or allowed programs, using the following information. 

Windows XP Firewall Exceptions 

� Remote Registry 

� File and Printer Sharing 

� WMI 

� Go to: http://support.microsoft.com/kb/875605 

Windows Vista Firewall Exceptions 



� WMI 

� Windows Management Instrumentation (WMI) 



Windows 7 Allowed Programs 



� WMI 

� Windows Management Instrumentation (WMI) 

Ideally, you should configure these settings in the desktop template or base image. You may also enable them 

through a Group Policy Object (GPO) or manually configure them for each desktop. 


Configuring Advanced settings (Advanced Settings tab) 

You can configure other settings on the Advanced tab. 


Log level defaults to 3–info. After an installation has been up and reliably running for several days, you can 

decrease this setting. You may need to increase it to 4‐verbose for short periods for debugging purposes. This 

log level directly affects the size of the log files. Note that log files older than 7 days will be automatically 

deleted. 

The collection interval specifies the time between View topography updates. In large VDI environments, 

topography updates can take a long time and add load to the View Connection Server, so less frequent updates 

may be desirable. Recommendations by number of desktop VMs are as follows: 

� up to 2000 desktops—5 minutes 

NOTE A collection interval of 5 minutes should work for up to 2000 desktops, based on recent testing results. 

The configuration utility has not yet been updated to reflect this new recommendation. 

It is recommended that you leave the collection threads at the default of 20. 

If a customer‐provided certificate is used, it may be desirable to increase the certificate policy to High. The 

default Medium setting works best if you are not using a custom certificate. 

NOTE You can also start and stop the View Adapter service on this tab. 

However, make sure that you save your configuration settings by clicking Apply before leaving this tab. 

IMPORTANT Before you start the vCenter Operations Manager for View adapter, make sure that the vCenter 

Operations Manager Enterprise vApp is installed and running. 



Figure 4-4. vCenter Operations Manager for View Advanced Settings 

It is recommended that you run connection tests after you apply each category of settings. 

The following status dialog displays when all settings and credentials have been configured properly. 






5 

Deploying and Using vCenter 

Operations Manager for View 

Dashboards 5 

For monitoring and troubleshooting your View VDI environment, seven dashboards are created 

out‐of‐the‐box. Installation of vCenter Operations Manager for View dashboards is automated by deploying 

a PAK file using the vCenter Operations Manager Enterprise update mechanism as described in “Installing the 

Dashboards” on page 27. The PAK file is included with the vCenter Operations for View adapter installation. 

Installing the Dashboards 

The process of installing dashboards is comprised of the following steps: 

1 Connect to the vCenter Operations Manager Admin Console. 

2 Deploy the vCenter Operations Manager for View Adapter PAK file: 

VMware-vcops-viewadapter.pak 

The PAK file is located in the default vCenter Operations Manager for View Installation folder: 

c:\Program Files\VMware\vCenter Operations\View 

Adapter\VMware-vcops-viewadapter.pak 

Connect to the vCenter Operations Manager Admin Console 

To connect to the vCenter Operations Manager Admin Console: 

1 Open the vCenter Operations Manager Admin Console using the following URL: 

https:///admin 

See the vCenter Operations Manager Admin Console in “vCenter Operations Manager Admin 

Console—Update package screen” on page 28. 



Figure 5-1. vCenter Operations Manager Administration Console 

2 Log onto the vCenter Operations Manager Admin Console using the admin account. 

Deploy the vCenter Operations Manager for View Adapter PAK file 

1 In the vCenter Operations Manager Admin Console, open the Update page shown in “vCenter 

Operations Manager Admin Console—Update package screen” on page 28. 

Figure 5-2. vCenter Operations Manager Admin Console—Update package screen 

2 Click the Browse button. Navigate to the vCenter Operations Manager for View Adapter installation 

folder (by default C:\Program Files\VMware\vCenter Operations\View Adapter) and select the 

VMware-vcops-adapter.pak file. 


Figure 5-3. vCenter Operations Manager for View Installation Folder with PAK File 

Chapter 5 Deploying and Using vCenter Operations Manager for View Dashboards 

3 Click the Update button and accept the End User License Agreement, which is shown in the following 

screen. 

Figure 5-4. vCenter Operations Manager Enterprise Admin Console--Update Package screen 

4 After you accept the End User License Agreement, the vCenter Operations Manager for View Adapter 

PAK file begins deploying to the vCenter Operations Manager Enterprise. This process can take several 

minutes to complete. After the deployment completes, the Admin Console shows the result of the 

deployment, which is shown in “vCenter Operations Manager Admin Console” on page 30. 



Figure 5-5. vCenter Operations Manager Admin Console 

Using the vCenter Operations Manager Enterprise User Interface 

vCenter Operations Manager for View uses the vCenter Operations Manager Enterprise web interface rather 

than the vCenter Operations Manager vSphere interface. You access this interface through a separate URL. 

https:///vcops-custom 

NOTE You can access the vSphere interface at the following URL: 

https:///vcops-vsphere 

You can find the Getting Started guide for the vCenter Operations Manager Enterprise web interface at the 

following URL: 

https://www.vmware.com/pdf/vcops-enterprise5-getting-started-guide.pdf 

Validating your installation 

To validate that the dashboards got installed and configured correctly, open the vCenter Operations Manager 

Enterprise UI and look for the seven dashboard tabs. See Figure 5‐6 for an example of the View Main 

dashboard, which is displayed by default. Click through each tab and confirm its content with the dashboard 

descriptions contained in the following sections. 

NOTE Some health and metric values may display in blue with a question mark (?). This is not a cause for 

concern; it just indicates that the corresponding data is not yet available for this metric. 

Adding vCenter Operations Manager Enterprise User Accounts 

It is recommended that you create one or more vCenter Operations Manager Enterprise user accounts with 

read‐only access to vCenter Operations Manager for View UI dashboards. Ideally, these users should have 

access privileges to view the dashboards but not modify them. Refer to the Configuring and Managing Users 

chapter in the following document for instructions on creating and managing vCenter Operations Manager 

user accounts: 

https://www.vmware.com/pdf/vcops-enterprise5-admin-guide.pdf 

After the dashboards are installed, you can proceed to “Using the Dashboards” on page 31. 


Using the Dashboards 


Seven View‐specific dashboards are created for you to use to monitor and troubleshoot your VDI 

environment. These dashboards are automatically installed when you deploy the PAK file in “Deploy the 

vCenter Operations Manager for View Adapter PAK file” on page 28. 

The following sections provide a high‐level overview of the seven vCenter Operations Manager for View 

dashboards. 

Overview of dashboards and widgets 

Dashboards present performance data from monitored software and hardware resources in your enterprise 

and provide predictive analysis and real‐time information about problems. Data and analysis is presented 

through alerts, in configurable dashboards, on predefined pages in the user interface. Depending on your 

access rights, you can add, delete, and arrange widgets on the dashboards, create new dashboards, and edit 

widgets and the configuration and interaction of widgets on your dashboards. 

Each section of a dashboard is a widget. Each widget shows a specific type of data in a specific format. Each 

widget has a button bar at the top containing a number of icon buttons which perform actions on the selected 

data or control how the data is displayed. 

Widgets include configuration options that you can edit to customize for your use. For example, you can select 

the metrics that the Alerts widget shows by editing its configuration. You can also configure widget 

interactions so that one widget, called a providing widget, provides information to another widget, called a 

receiving widget. For example, you can configure the Root Cause Ranking widget to receive data from the Tag 

Selector widget and the Health Status widget. 

For more details on how to customize and configure dashboards and widgets, see the vCenter Operations 

Manager Enterprise Getting Started Guide. 

View Main dashboard 

You use the View Main dashboard to visualize the end‐to‐end VDI environment, its underlying technology 

silos, and any alerts. The following screen is an example of the View Main dashboard. 



Figure 5-6. View Main dashboard 

The View Main dashboard gives you an overall status of the VDI environment. The View Main dashboard is 

broken down into four sections: 

� VDI Environment Indicators 

� VDI Alerts 

� VDI Health Tree 

� VDI Tier Health 

The VDI Health Tree is broken into six tiers, which represent the underlying technology silos supporting the 

VDI environment. Each tier is represented by an icon which you can double‐click to drill down into for more 

information about that tier and its applications. 

� View Infrastructure 

� User Sessions 

� Network 

� Storage 

� View Clients 

� vSphere Infrastructure 

For example, you can drill into View Infrastructure which contains the VMware View Connection Servers, 

VMware View Security servers, and View pools. You can also drill into a View pool to view and monitor the 

desktop VMs assigned to those pools. 



The VDI Environment Indicators on the left of the View Main dashboard indicate the health of your VDI 

environment, broken down into categories such as overall VDI capacity used, connected and disconnected 

sessions, and so forth. This gives you a quick overview of how your overall VDI environment is behaving. 

vCenter Operations Manager for View presents information based on what it learns, what problematic 

behavior is normal, and what is outside of the metric ranges, based on previous behavior. 

PCoIP Latency, Average PCoIP Packet Loss, PCoIP TX Bandwidth, and PCoIP Rx Bandwith give you 

information about the connection quality between the View client and the VMware View desktop VM, which 

is rolled up across the entire VDI environment. This gives you a better idea of client performance and how the 

user experience is affected. 

The VDI Tier Health area points the VI Administrator to problem silos in the VDI environment, such as the 

Storage Tier. The VI Administrator can examine the storage tiers in more detail by drilling into the datastores 

that are associated with the VMware View pools. If all the health indicators across the VDI Tier Health area 

are yellow or red, the health of the component data storage may affect the health of the entire tier, which the 

VI Administrator can see by quickly reviewing these icons. 

NOTE Note that the VDI Health Tree and VDI Tier Health is not necessarily an indication of behavior or 

current performance, but instead with respect to how it’s behaved in the past. vCenter Operations Manager 

for View collects all metrics and looks for trends and patterns. It learns what types of behavior to expect from 

each of the resources it is monitoring. 

Average Session Logon Time and Average Session Reconnect Time provide information that is averaged 

across all connections currently in your VMware View environment. 

At the bottom of the VDI Environment Indicators section, Recent Desktop Launch Errors and Recent Desktop 

Provisioning Errors give the number of errors over the last collection interval. 

At the upper right of the View Main dashboard, the active alerts associated with VMware View‐specific 

resources in your VDI environment display under VDI Alerts. For example, for a particular client, you may 

see a certain percentage of packet loss, and you may want to find where that client is connecting from, such as 

from the Internet or Intranet, and examine possible causes for the packet loss. You can double‐click on these 

icons to get more information, and drill into each alert condition to troubleshoot the issue further. 

For details on metrics, see Appendix A. 



View Users dashboard 

You use the View Users dashboard to visualize and troubleshoot user‐specific issues. For example, a VI 

Administrator or Helpdesk Specialist would typically use this dashboard when a user calls the 

Helpdesk/Desktop Specialist or IT Operations teams, or when there is a need to deep‐dive into a specific user 

issue when troubleshooting other problems. Figure 5‐7, “View Users dashboard (showing relationships for 

selected user in Health Tree),” on page 34 shows a typical View User dashboard. 

Figure 5-7. View Users dashboard (showing relationships for selected user in Health Tree) 

The View Users dashboard is especially useful for a Helpdesk specialist, who assists people that contact the 

Helpdesk with performance issues with their desktops or some similar reason. 

The End Users section on the upper left of the dashboard gives a list of users that are currently logged on, using 

the format 


If any desktop or any of its related objects has an alert, there will be a red triangle shown with that object’s icon. 

To view the alert, select the object in the tree and then click the Show Alerts icon in the button bar above the 

tree. All current alerts for the object will display in a popup window and you can navigate to the alert’s details 

by double‐clicking an alert in this list. 

For example, the alert may show a Waste badge, which may indicate that user’s provisioning may be a bit high. 

Drilling down on a desktop showing problems is a good way to get status information on objects associated 

with the user issue you are investigating. This may show out of normal ranges, based on historical trends, for 

things like datastore demand, or the provisioned disk space for that user may be a bit higher than normal. 

The Metric Selector shows all metrics collected for the object currently selected in the Health Tree. For any 

object, there may be as many as 50 or more metrics that are being monitored on the client, VM, desktop, and 

so forth. Any metrics that are currently exhibiting abnormal behavior, based on past history, are highlighted 

with a yellow icon and may need further investigation. 

NOTE vCenter Operations Manager for View and vCenter Operations Manager Enterprise are designed to 

collect data and evaluate it based on past behavior to determine what is normal vs. abnormal behavior. 

Determining abnormal behavior for a particular user, desktop, VM, or other infrastructure object requires 

investigation and evaluation by the Helpdesk specialist and/or VI Administrator to analyze and resolve the 

issue. 

Interesting Metrics show the current value and brief history of metrics that may be important for the currently 

selected object. Important Metrics are usually those that are outside their expected range, exceeding a 

threshold, or marked as a key indicator. 

When analyzing and interpreting interesting metrics, you may see a gray bar, which indicates the expected 

range for a particular group of metrics. Under Interesting Metrics you might see an anomaly or see that some 

metrics are above the dynamic thresholds for a particular desktop. You can pick other metrics for further 

analysis by selecting them in the Metric Selector and clicking the Move to Graph icon, and get historical 

graphs which are also shown in the list of Interesting Metrics. 

You can adjust the time range, from a range of values from the last hour, last 24 hours, and so forth, and the 

graphs rescale so you can see the behavior over a different range and see a different set of data. 

Root Cause Ranking shows a list of metrics that are currently out of their expected range for the selected object 

or its related objects. This list gives you a ranked order of metric anomalies you can use to start investigating 

an issue with the currently selected object. 

For descriptions of metrics, see Appendix A. 



Figure 5-8. View Top Sessions dashboard 

The View Top Sessions dashboard shows you a number of different metrics for pools or desktops, and which 

ones are exhibiting the longest times or have the worst performance.The metrics displayed are: 

� Pool Capacity Used ‐ Highest Last Month Average 

� Pool Logon Times (sec) ‐ Highest Last Hour Average 

� Pool Reconnection Times (sec) ‐ Highest Last Hour Average 

� Pool PCoIP Latency (ms) ‐ Highest Last Hour Average 

� Desktop Logon Time (sec) ‐ Highest Last Hour Average 

� Desktop Reconnection Time (sec) ‐ Highest Last Hour Average 

� Desktop PCoIP Round Trip Latency ‐ Highest Last Hour Average 

� Desktop PCoIP Packet Loss (%) ‐ Highest Last Hour Average 

� Desktop PCoIP Throughput (Kbit/sec) ‐ Highest Last Hour Average 

Each of these widgets give you the resources with the worst performance. For example, Desktop PCoIP Packet 

Loss gives you a ranking to get a quick view of how user desktops are performing in the area of PCoIP packet 

loss. You can drill down into a specific resource from this dashboard to the details page for that resource. 

The configuration of metrics on these dashboards in vCenter Operations Manager for View have been 

preconfigured for you, based on user feedback, however you can choose what types of metrics to display. 

There are a number of configurations you can choose from, if you want to change what type of information is 

displayed and how it’s displayed. For descriptions of metrics, see Appendix A. 


View Top Desktop VMs 


You can use this dashboard to view the list of the top desktop VM consumers for a number of important 

indicator metrics. On this dashboard, you can quickly see which desktop VMs have the lowest health scores, 

the highest workloads, and are using the most network bandwidth. 

Figure 5-9. View Top Desktop VMs dashboard 

The View Top Desktop VMs shows you a number of different metrics for desktop VMs, and which ones are 

exhibiting the longest times or have the worst performance. The categories of metrics displayed are: 

� VM Health (%) ‐ Lowest Last Hour Average 

� VM Critical Alerts (%) ‐ Highest Last Hour Average 

� VM Behavior (Anomaly Count) ‐ Highest Last Hour Average 

� VM CPU Contention (%) ‐ Highest Last Hour Average 

� VM CPU Workload (%) ‐ Highest Last Hour Average 

� VM Memory Workload (%) ‐ Highest Last Hour Average 

� VM Disk Workload (%) ‐ Highest Last Hour Average 

� VM Network Workload (%) ‐ Highest Last Hour Average 

� VM Network Throughput (Kbit/sec) ‐ Highest Last Hour Average 

Each of these widgets show you the resources with the worst performance. 

The View Top Desktop VMs dashboard collects similar information for the desktop VMs as the View Top 

Sessions dashboard. It collects metrics for CPU workload, critical alerts on the VMs, network workload, 

memory workload, and averages those usage indexes over a selected period of time. 

The configuration of metrics on these dashboards in vCenter Operations Manager for View has been 

preconfigured for you, based on user feedback; however you can choose what types of metrics to display. 


displayed and how it’s displayed. For descriptions of metrics, see Appendix A. 



View Pools dashboard 

You use the View Pools dashboard to assess the status of desktop VMs within View pools. To view statistics 

about the VMs and datastores contained in each View pool, select a configuration from the heat map in the 

upper left of the dashboard. You can use this dashboard to quickly identify and troubleshoot poorly 

performing VMs, VMs with high workload, or datastore capacity. 

Figure 5-10. View Pools dashboard 

Metrics are displayed in the following areas on the View Pools dashboard: 

� View Pool Statistics 

� Pool Alerts 

� Object Metrics 

� Object Tree 

View Pool Statistics uses a heatmap widget to show important information about the VMs and datastores used 

by View Pools. Heatmaps are an efficient way to show a large number of objects and quickly identify which 

objects may be experiencing problematic behavior. Each square in the View Pool Statistics heatmap represents 

a VM or a datastore and these squares are grouped by View Pools. The color of the square indicates the relative 

behavior of the corresponding object as chosen for the currently selected configuration. 

When moving the mouse over each square in the heatmap under View Pool Statistics, the object name and 

metric value is displayed. Selecting an object will fill other widgets on this dashboard with information 

pertaining to that object. 

The View Pool Statistics heatmap has a number of configurations showing the workload and health metrics 

for all desktops and datastores in View Pools. The VI Administrator can select from among the following pool 

statistics configurations: 

� VM Health 

� VM Behavior 


� VM Overall Workload 

� VM CPU Workload 

� VM Memory Workload 

� VM Disk Workload 

� VM Network Workload 

� Datastore Health 

� Datastore Overall Workload 

� Datastore IO Workload 

� Datastore Disk Space Available 

� Datastore Demand 

� Datastore Latency 


As with the other vCenter Operations Manager for View dashboards, configuration of metrics on these 

dashboards in vCenter Operations Manager for View have been preconfigured for you, based on user 

feedback. However, you can customize and configure what types of metrics you want to display. There are a 

number of configurations you can choose from, if you want to change the types of metrics that are displayed 

and how they are displayed. 

For descriptions of metrics, see “Appendix A” on page 57. 



View Desktop Sessions dashboard 

You use this dashboard to assess the PCoIP performance of VMware View clients connected to desktop VMs. 

To view PCoIP statistics related to View desktops and client network connections, select a configuration from 

the heat map in the upper left of the dashboard. Use this dashboard to quickly identify and troubleshoot poor 

View client connection issues. You can quickly find issues such as increase in latency, and other key 

measurements such as packet loss. 

Figure 5-11. View Desktop Sessions dashboard 

The default configuration for View Desktop Sessions is similar to that of the View Pools dashboard. 

The View Desktop Sessions dashboard shows the following sections of metrics information: 

� Active Desktop Statistics 

� Object Metrics 

� Alerts 

� Object Tree 

The Active Desktops Statistics heatmap has a number of configurations showing health, workload, and PCoIP 

statistics for all currently connected user desktop sessions. Select a configuration in Active Desktop Sessions 

to show different representations of the metrics data, by selecting from the following list: 

� Desktop Health 

� Desktop Workload 

� Desktop PCoIP Latency 

� Desktop PCoIP TX Bandwidth 

� Desktop PCoIP RX Bandwidth 

� Desktop PCoIP TX Packet Loss 

� Desktop PCoIP RX Packet Loss 

� Network PCoIP RX Latency 


� Network PCoIP TX Bandwidth 

� Network PCoIP RX Bandwidth 

� Network PCoIP TX Packet Loss 

� Network PCoIP RX Packet Loss 




feedback, however you can choose what types of metrics to display. 




vSphere Infrastructure dashboard 

Use the vSphere Infrastructure dashboard to assess the status of the underlying vCenter Operations Manager 

vSphere infrastructure that supports your View VDI environment. Use this dashboard to quickly identify 

problem components within the vSphere object hierarchy. See the default dashboard in Figure 5‐12. 

You can more thoroughly assess the vCenter Operations Manager vSphere infrastructure by using the vCenter 

Operations Manager vSphere web interface. To access this interface enter the following URL in your web 

browser: 

https:///vcops-vsphere 

The vCenter Operations Manager vSphere interface is described in detail in the following document: 

https://www.vmware.com/pdf/vcops-5-getting-started-guide.pdf 

Figure 5-12. vSphere Infrastructure dashboard 

You can view and drill down into the vSphere virtual objects in your vSphere environment. You can view an 

internal data store, internal network, and view the user currently attached to a particular VM. The vSphere 

Infrastructure dashboard is broken down into the following sections: 

� VC Relationship 

� World 

� vSphere Server Systems 

� Data Centers 

� Clusters 

� Hosts 

� VMs 

� vSphere Topology 

� vSphere Root Cause 



Under the VC Relationship section, you can view the overall health score of the vSphere environment, at 

different levels of the vSphere object hierarchy. 

The vSphere topology lets you view the topology of the vSphere object hierarchy, and drill down into an object 

such as a VM, datastore, disk store, etc. to further analyze an issue. The vSphere Root Cause area shows you 

more metric information which you can drill into for more details. The vSphere Infrastructure hierarchy shows 

at a high level your entire vSphere environment, and is a good place to start troubleshooting, as you drill down 

from the top level of the vSphere hierarchy. 

You can view anomalies that are outside the expected range of values, and use that as a starting point to do 

more troubleshooting. 



feedback, however you can choose what types of metrics to display. 


displayed and how it’s displayed. You can mix and match the widgets, and customize the way the data is 

displayed depending on your needs. 





Appendix A, Important Metrics 

Table A-1. 

This chapter contains a list of the vCenter Operations Manager for View metrics, how you access them in the 

vCenter Operations Manager for View UI, and descriptions. 

NOTE For descriptions of the vCenter Operations Manager Enterprise vApp metrics, refer to the vCenter 

Operations Manager Enterprise online help. 

NOTE All metrics marked with an asterisk (*) are non‐View Adapter metrics. 

Metric Name Dashboard UI Sequence Metric Description 

VDI Health* VDI Environment—vCenter 

Operations Generated | Self – 

Health Score 

VDI Capacity Used VDI Environment—Summary—VDI 

Capacity Used (Percent) 

Connected Sessions VDI 

Environment—Summary—Connect 

ed Sessions 

Disconnected Sessions VDI Environment—Summary— 

Disconnected Sessions 

Average PCoIP Latency View Client—PCoIP|Average 

PCoIP Latency (ms) 

Average PCoIP Packet 

Loss 

View Clients—PCoIP|Transmit 

Packet Loss Percent 

PCoIP TX Bandwidth View Clients—PCoIP|Transmit 

Bandwidth (kbit/sec) 

PCoIP RX Bandwidth View Clients—PCoIP|Receive 


Avg Session Login User Sessions—Remote Sessions | 

Average Logon Time (sec) 

Avg Session Reconnect User Sessions—Remote 

Sessions|Average Reconnect Time 

(sec) 

vCenter Operations Manager examines internally generated metrics 

and uses its proprietary analytics formulas to determine an overall 

health rating for a resource. The health rating, which ranges from 0 to 

100, gives you a quick overview of the current state of a resource. 

Percentage of the total VDI capacity (virtual desktops) that are 

currently logged on. 

The number of sessions where the user is actively logged on and 

connected to the desktop. 

The number of sessions where the user is logged on, but not currently 

connected to the desktop. 

Average round trip latency between the desktop and the client across 

all connected desktop sessions using the PCoIP protocol. 

Percentage of transmitted packets lost during the last sampling 

period across all connected desktop sessions using the PCoIP 

protocol. 

Overall bandwidth for outgoing PCoIP packets across all connected 

desktop sessions using the PCoIP protocol. 

Overall bandwidth for incoming PCoIP packets across all connected 

desktop sessions using the PCoIP protocol. 

Average logon time across all logged‐on desktop sessions. This value 

does not include desktops that have disconnected at some point 

during the session. 

Average reconnection time across all logged‐on desktop sessions. 

Reconnection time is the time it takes for a disconnected session to 

reconnect to the session. 



Table A-1. 

Metric Name Dashboard UI Sequence Metric Description 

Recent Desktop Launch 

Errors 

Recent Desktop 

Provisioning Errors 

View Infrastructure—Error 

Events|Desktop Launch—last 

interval 

View Infrastructure—Error Event | 

Desktop Provisioning—last interval 

1. BROKER_DESKTOP_LAUNCH_FAILURE 

2. BROKER_MACHINE_ASSIGNED_UNAVAILABLE 

3. BROKER_MACHINE_CANNOT_CONNECT 

4. BROKER_MACHINE_NOT_READY 

5. BROKER_MACHINE_PROTOCOL_UNAVAILABLE 

6. BROKER_MACHINE_REJECTED_SESSION 

7. BROKER_POOL_CANNOT_ASSIGN 

8. BROKER_POOL_EMPTY 

9. BROKER_POOL_NO_MACHINE_ASSIGNED 

10. BROKER_POOL_NO_RESPONSES 

11. BROKER_POOL_OVERLOADED 

12. BROKER_POOL_PROTOCOL_UNAVAILABLE 

1. BROKER_PROVISIONING_ERROR_CONFIG_SET 

2.BROKER_PROVISIONING_ERROR_DISK_LC_RESERVATION_S 

ET 

3. BROKER_PROVISIONING_ERROR_DISK_SET 

4.BROKER_PROVISIONING_ERROR_LICENCE_SET 

5. BROKER_PROVISIONING_ERROR_NETWORKING_SET 

6. BROKER_PROVISIONING_ERROR_RESOURCE_SET 

7.BROKER_PROVISIONING_ERROR_TIMEOUT_CUSTOMIZATIO 

N_SET 

8.BROKER_PROVISIONING_VERIFICATION_FAILED_VMNAME 

_IN_USE 


Table A-2. View Top Sessions dashboard metrics 

Metric Name Metric UI Sequence Metric Description 

Pool Capacity Used (%) View Pool‐>Desktop VMs|Pool 

Capacity Used (Percent) 

Pool Logon Times (sec) View Pool‐>Remote Sessions|Average 

Logon Time (sec) 

Pool Reconnection Times 

(sec) 

View Pool‐>Remote Sessions|Average 

Reconnection Time (sec) 

Pool PCoIP Latency (ms) View Pool‐>RemoteSessions|Average 

PCoIP Latency (ms) 

Desktop Logon Time (sec) User Desktop‐>Session | Logon Time 

(sec) 

Desktop Reconnection Time 

(sec) 

Desktop PCoIP Round Trip 

Latency (ms) 

Desktop PCoIP Packet Loss 

(%) 

Desktop PCoIP Throughput 

(kbit/sec) 

User Desktop‐>Session|Reconnection 

Time (sec) 

User Desktop‐>PCoIP|Round Trip 

Latency (ms) 

User Desktop‐>PCoIP|Transmit Packet 

Loss Percent 

User Desktop‐>PCoIP|Transmit 



Percentage of available VDI desktops that are currently in 

use (connected desktops + disconnected desktops) divided 

by the total number of desktops in the pool. 

Average logon time across all logged‐on desktop sessions 

that are running on VMs within this pool. This value does 

not include desktops that have disconnected at some point 

during the session. 

Average reconnection time across all logged‐on desktop 

sessions that are running on VMs within this pool. 

Reconnection time is the time it takes for a disconnected 

session to reconnect to the session. 

Average round trip latency between the desktop and the 

client across all connected desktop sessions running on VMs 

within this pool using the PCoIP protocol. 

Time elapsed between the broker desktop request event and 

the agent connected event in the View Events database. 

Time elapsed between the broker desktop request event and 

the agent reconnected event in the View Events database. 

Round trip latency between the desktop and the client. 

Percentage of transmitted packets lost during the sampling 

period. 

Overall bandwidth for outgoing PCoIP packets during the 

sampling period. 



Table A-3. View Top Desktop VMs dashboard metrics 


VM Health (%)* Virtual Machine—Badge | Health vCenter Operations Manager examines internally generated 

metrics and uses its proprietary analytics formulas to 

determine an overall health rating for a resource. The health 

rating, which ranges from 0 to 100, gives you a quick 

overview of the current state of a resource. 

VM Critical Alerts* Virtual Machine‐>Badge|Alert Count 

Critical 

VM Behavior (anomaly 

count)* 

This is the number of critical alerts that are open at the 

current time. 

Virtual Machine‐>Badge|Anomaly An anomaly is when an individual metric is outside the 

boundary that vC Ops has determined to be its normal 

range. The anomaly badge compares the current number of 

anomalies for a resource to the to the expected number of 

anomalies. 

VM CPU Contention (%)* Virtual Machine‐>CPU Usage|CPU 

Contention (%) 

VM CPU Workload (%)* Virtual Machine‐>CPU 

Usage|Workload (%) 

VM Memory Workload (%)* Virtual Machine‐>Memory|Overall 

Workload (%) 

Measures the difference between how much CPU the VM 

wants to use and how much CPU the VM gets 

CPU workload is an estimate of how much CPU a VM wants 

based on its actual usage plus its ìactiveî ready time. 

Memory workload is an estimate of how much memory the 

VM wants to actively use over its configured size. 

VM Disk Workload (%)* Virtual Machine—>Disk | Workload Disk workload is an estimate of how many iOPS the VM 

wants to use over the estimated capacity for iOPS. 

VM Network Workload (%)* Virtual Machine‐>Disk | Workload (%) Network workload is an estimate of how much of the 

network capacity the VM wants to use over the maximum 

observed capacity of the network. 

VM Network Throughput 

(KBps)* 

Virtual Machine‐>Network|Usage 

Rate (KBps) 


Table A-4. View Pools dashboard metrics 



VM Health (%)* Virtual Machine‐>Badge | Health vCenter Operations Manager examines internally generated 





VM Behavior (anomaly 

count)* 

Virtual Machine‐>Badge|Anomaly An anomaly is when an individual metric is outside the 

boundary that vCenter Operations Manager has 

determined to be its normal range. The anomaly badge 

compares the current number of anomalies for a resource to 

the to the expected number of anomalies. 

VM CPU Workload (%)* Virtual Machine‐>CPU Usage | 

Workload (%) 

VM Memory Workload (%)* Virtual Machine‐>Memory|Overall 

Workload (%) 

CPU workload is an estimate of how much CPU a VM wants 

based on its actual usage plus its ìactiveî ready time. 

Memory workload is an estimate of how much memory the 

VM wants to actively use over its configured size. 

VM Disk Workload (%)* Virtual Machine‐>Disk|Workload (%) Disk workload is an estimate of how many iOPS the VM 

wants to use over the estimated capacity for iOPS. 

VM Network Workload (%) * Virtual Machine‐>Network| 

Workload (%) 

Network workload is an estimate of how much of the 

network capacity the VM wants to use over the maximum 

observed capacity of the network. 

Datastore Health* Datastore‐>Badge|Health vCenter Operations Manager examines internally generated 





Datastore Overall Workload* Datastore‐>Badge|Workload (%) The overall workload for a Datastore is the maximum of the 

Disk workload and the Capacity workload. 

Datastore IO Workload* Datastore‐>Disk|Workload (%) Disk workload is an estimate of how many iOPS the VM 

wants to use over the estimated capacity for iOPS 

Datastore Disk Space 

Available* 

Datastore‐>Capacity|Workload (%) Capacity workload for a datastore is a measure of the used 

space compared to the total capacity of the datastore. 

Datastore Demand* Datastore‐>Datastore|Dem Demand is a calculation that looks at device latency for 

reads and writes, and also queue latency for reads and 

writes. 

Datastore Latency* Datastore‐>Datastore|Total Latency 

(ms)d 

This is the normalized latency on the datastore (combined 

read and write latency). 



Table A-5. View Desktop Sessions dashboard metrics 


Desktop Health* User Desktop‐>vCenter Operations 

Generated|Self —Health Score 

vCenter Operations Manager examines internally generated 





Desktop Workload User Desktop‐>Badge|Workload Individual workloads are calculated in the areas of CPU, 

Memory, Disk, and Network. The Desktop Workload is the 

maximum of these individual workloads. 

Desktop PCoIP Latency User Desktop‐>PCoIP|Round Trip 

Latency (ms) 

Desktop PCoIP TX 

Bandwidth 

Desktop PCoIP RX 

Bandwidth ‐ 

Desktop PCoIP TX Packet 

Loss 

Desktop PCoIP RX Packet 

Loss 

User Desktop‐>PCoIP|Transmit 


User Desktop‐>PCoIP|Receive 


User Desktop‐>PCoIP|Transmit Packet 

Loss Percent 

User Desktop‐>PCoIP|Receive Packet 

Loss Percent 

Network PCoIP Latency View Client 

Network‐>PCoIP|Average PCoIP 

Latency (ms) 

Network PCoIP TX 

Bandwidth 

Network PCoIP RX 

Bandwidth 

Network PCoIP TX Packet 

Loss 

Network PCoIP RX Packet 

Loss 

View Client Network‐>PCoIP|Total 

Transmit Bandwidth 

View Client Network‐>PCoIP|Total 

Receive Bandwidth 

View Client 

Network‐>PCoIP|Transmit Packet 

Loss Percent 

View Client Network‐>PCoIP|Receive 

Packet Loss Percent 

Round trip latency during the last sampling period between 

the desktop and the client 

Overall bandwidth for outgoing PCoIP packets during the 

last sampling period for this User Desktop. 

Overall bandwidth for incoming PCoIP packets during the 

last sampling period for this User Desktop. 

Percentage of transmitted packets lost during the last 

sampling period. 

Percentage of received packets lost during the last sampling 

period. 

Round trip latency between the desktop and the 

client across all connected desktop sessions using the 

same View Client Network. 

Overall bandwidth for outgoing PCoIP packets across all 

connected desktop sessions using the same View Client 

Network. 

Overall bandwidth for incoming PCoIP packets across all 

connected desktop sessions using the same View Client 

Network. 

Percentage of transmitted packets lost during the last 

sampling period across all connected desktop sessions 

using the same View Client Network 

Percentage of received packets lost during the last sampling 

period across all connected desktop sessions using the same 

View Client Network.

vCenter Operations Manager for View Integration Guide 1.0 - VMware

Create successful ePaper yourself

Delete template?

Save as template?