Integration

Table Of Contents
VMware, Inc. 75
6
You can use Windows Management Instrumentation (WMI) to examine performance statistics for a PCoIP
session by using any of the supported programming interfaces, including C#, C++, PowerShell, VBScript,
VB .NET, and Windows Management Instrumentation Command-line (WMIC). You can also use the Microsoft
WMI Code Creator tool to generate VBScript, C#, and VB .NET code that accesses the PCoIP performance
counters. For more information about WMI, WMIC, and the WMI Code Creator tool, go to
http://technet.microsoft.com/en-us/library/bb742610.aspx and
http://www.microsoft.com/downloads/en/details.aspx?familyid=2cc30a64-ea15-4661-8da4-55bbc145c30e&dis
playlang=en.
This chapter includes the following topics:
“Usage Notes for Recorded Statistics” on page 75
“General Session Statistics” on page 76
Audio Statistics” on page 76
“Imaging Statistics” on page 77
“Network Statistics” on page 78
“USB Statistics” on page 79
Usage Notes for Recorded Statistics
The WMI namespace for the PCoIP session statistics is root\CIMV2.
Administrator privileges are required to access the performance counters remotely.
The names of the statistics are suffixed with (Server)or (Client), according to whether the statistic is
recorded on the PCoIP server or on the PCoIP client.
You can use Windows Performance Monitor (PerfMon) with the counters to calculate averages over a specified
sampling period.
All statistics are reset to 0 when a PCoIP session is closed. If the WMI property SessionDurationSeconds is
a non-zero value and stays constant, the PCoIP server was forcefully ended or crashed. If the
SessionDurationSeconds property changes from a non-zero value to 0, the PCoIP session is closed.
To avoid a division-by-zero error, verify that the denominator in the expressions for calculating bandwidth or
packet-loss percentage does not evaluate to zero.
USB statistics are recorded for zero clients, but not for thin clients or software clients.
Examining PCoIP Session Statistics
6