Loading...
View Integration
Modified on 4 JAN 2018
VMware Horizon 7 7.4
View Integration
You can find the most up-to-date technical documentation on the VMware website at: https://docs.vmware.com/
If you have comments about this documentation, submit your feedback to docfeedback@vmware.com
VMware, Inc.
3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com
Copyright © 2016–2018 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc. |
2 |
Contents
|
View Integration |
4 |
|
|
|
|
|
|
1 Introduction to View Integration |
5 |
|
||||||
|
View Components |
5 |
|
|
|
|
|
|
|
Integration Interfaces to View |
6 |
|
|
|
|||
2 Integrating View with the Event Database |
7 |
|||||||
|
Event Database Tables and Schemas |
7 |
|
|||||
|
Connection Broker Events |
10 |
|
|
|
|
||
|
Horizon Agent Events |
16 |
|
|
|
|
|
|
|
View Administrator Events |
16 |
|
|
|
|
||
|
Event Message Attributes |
25 |
|
|
|
|
||
|
Sample Database Queries and Views |
26 |
|
|||||
3 |
Customizing LDAP Data |
29 |
|
|
|
|||
|
Introduction to LDAP Configuration Data 29 |
|
||||||
|
Modifying LDAP Configuration Data |
|
30 |
|
||||
4 |
Examining PCoIP Session Statistics with WMI 36 |
|||||||
|
Using PCoIP Session Statistics |
36 |
|
|
||||
|
General PCoIP Session Statistics |
37 |
|
|||||
|
PCoIP Audio Statistics |
38 |
|
|
|
|
||
|
PCoIP Imaging Statistics |
39 |
|
|
|
|
||
|
PCoIP Network Statistics |
40 |
|
|
|
|
||
|
PCoIP USB Statistics |
41 |
|
|
|
|
|
|
|
Examples of Using PowerShell cmdlets to Examine PCoIP Statistics 42 |
|||||||
5 |
Setting Desktop Policies with Start Session Scripts 43 |
|||||||
|
Obtaining Input Data for a Start Session Script |
43 |
||||||
|
Best Practices for Using Start Session Scripts |
43 |
||||||
|
Preparing a View Desktop to Use a Start Session Script 44 |
|||||||
|
Sample Start Session Scripts |
47 |
|
|
|
|||
VMware, Inc. |
3 |
View Integration
The View Integration document describes how to integrate View™ software with third-party software such as Windows PowerShell, business intelligence reporting engines, and Microsoft System Center Operations Manager (SCOM).
Intended Audience
This document is intended for anyone who wants to customize or integrate software to work with View. The information in this document is written for experienced Windows or Linux system administrators who are familiar with virtual machine technology and datacenter operations.
VMware, Inc. |
4 |
Introduction to View Integration |
1 |
With View, system administrators can provision desktops and control user access to these desktops. Client software connects users to virtual machines running in VMware vSphere™, or to physical systems running within your network environment. In addition, View administrators can configure Remote Desktop Services (RDS) hosts to provide View desktop and application sessions to client devices.
This section includes the following topics:
nView Components
nIntegration Interfaces to View
View Components
You can use View with VMware vCenter Server to create desktops from virtual machines that are running on VMware ESX® or VMware ESXi™ hosts and deploy these desktops to end users. You can also install View on RDS hosts to deploy desktops and applications to end users. View uses your existing Active Directory infrastructure for user authentication and management.
After you create a desktop or application, authorized end users can use Web-based or locally installed client software to securely connect to centralized virtual machines, back-end physical systems, or RDS hosts.
View consists of the following major components.
View Connection |
A software service that acts as a broker for client connections by |
Server |
authenticating and then directing incoming user requests to the appropriate |
|
virtual machine, physical system, or RDS host. |
Horizon Agent |
A software service that is installed on all guest virtual machines, physical |
|
systems, or RDS hosts to allow them to be managed by View. |
|
Horizon Agent provides features such as connection monitoring, virtual |
|
printing, USB support, and single sign-on. |
Horizon Client |
A software application that communicates with View Connection Server to |
|
enable users to connect to their desktops. |
VMware, Inc. |
5 |
View Integration
View Administrator |
A Web application that enables View administrators to configure View |
|
Connection Server, deploy desktop and application pools, manage |
|
machines, control user authentication, initiate and examine system events, |
|
and perform analytical activities. |
|
|
|
Note View Administrator is named Horizon Administrator in Horizon 7. |
vCenter Server |
|
A server that acts as a central administrator for ESX/ESXi hosts that are |
|
|
connected on a network. A vCenter Server instance provides the central |
|
point for configuring, provisioning, and managing virtual machines in the |
|
datacenter. |
View Composer |
A software service that is installed on a vCenter Server instance to enable |
|
View to rapidly deploy multiple linked-clone desktops from a single |
|
centralized base image. |
Integration Interfaces to View
You can use several interfaces to integrate View with external applications.
Event database |
You can configure View to record events to a Microsoft SQL Server or |
|
Oracle database. You can then use business intelligence reporting engines |
|
to access and analyze this database. |
Lightweight Directory |
You can export and import LDAP configuration data from and into View. |
Access Protocol |
You can create scripts that update this configuration data without accessing |
(LDAP) |
View Administrator directly. |
Windows Management |
You can examine performance statistics for a PCoIP session. |
Instrumentation (WMI) |
|
VMware, Inc. |
6 |
Integrating View with the Event |
2 |
Database |
You can configure View to record events to a Microsoft SQL Server or Oracle database. View records events such as end-user actions, administrator actions, alerts that report system failures and errors, and statistical sampling.
End-user actions include logging and starting desktop and application sessions. Administrator actions include adding entitlements and creating desktop and application pools. An example of statistical sampling is recording the maximum number of users over a 24-hour period.
You can use business intelligence reporting engines such as Crystal Reports, IBM Cognos, MicroStrategy 9, and Oracle Enterprise Performance Management System to access and analyze the event database.
This section includes the following topics:
nEvent Database Tables and Schemas
nConnection Broker Events
nHorizon Agent Events
nView Administrator Events
nEvent Message Attributes
nSample Database Queries and Views
Event Database Tables and Schemas
View uses database tables to implement the event database. The event database prepends the names of these tables with a prefix that you define when you set up the database.
Event Database Tables
The following table shows the database tables that implement the event database in View.
Table 2 1. Event Database Tables
Table Name |
Description |
|
|
event |
Metadata and search optimization data for recent events. |
|
|
event_data |
Data values for recent events. |
|
|
VMware, Inc. |
7 |
View Integration
Table 2 1. Event Database Tables (Continued)
Table Name |
Description |
|
|
event_data_historical |
Data values for all events. |
|
|
event_historical |
Metadata and search optimization data for all events. |
|
|
View records details about events to all the database tables. After a certain period of time has elapsed since writing an event record, View deletes the record from the event and event_data tables. You can use View Administrator to configure the time period for which the database keeps a record in the event and event_data tables.
Important View does not restrict the growth of the event_historical and event_data_historical tables. You must implement a space management policy for these tables.
A unique primary key, EventID, identifies each event that View records in the event and event_historical tables. View records data values for each event in the event_data and event_data_historical tables. You can obtain the complete set of information for an event by joining the event and event_data tables or the event_ historical and event_data_historical tables on the EventID column.
The EventType, Severity, and Time columns in the event and event_historical tables identify the type and severity of an event and the time at which it occurred.
For information about setting up the event database, see the View Installation document.
Note Events might be lost if you restart View Connection Server instances while the event database is not running. For a solution that avoids this problem see http://kb.vmware.com/kb/1021461.
Event Database Schemas
The following table shows the schema for the event and event_historical database tables.
Table 2 2. Schema for the event and event_historical Tables
Column Name |
Oracle Data Type |
SQL Server Data Type |
Description |
|
|
|
|
|
|
Acknowledged |
SMALLINT |
tinyint |
Whether View acknowledged the event. |
|
|
|
|
n |
0 = false |
|
|
|
n |
1 = true |
|
|
|
|
|
DesktopId |
NVARCHAR2(512) |
nvarchar(512) |
Desktop ID of the associated pool. |
|
|
|
|
|
|
EventID |
INTEGER |
int |
Unique primary key for the event. |
|
|
|
|
|
|
EventType |
NVARCHAR2(512) |
nvarchar(512) |
Event name that corresponds to an item in |
|
|
|
|
the message catalog. For example, |
|
|
|
|
BROKER_USERLOGGEDIN. |
|
|
|
|
|
|
FolderPath |
NVARCHAR2(512) |
nvarchar(512) |
Full path of the folder that contains the |
|
|
|
|
associated object. |
|
|
|
|
|
|
GroupId |
NVARCHAR2(512) |
nvarchar(512) |
SID of the associated group in Active |
|
|
|
|
Directory. |
|
|
|
|
|
|
VMware, Inc. |
8 |
View Integration
Table 2 2. Schema for the event and event_historical Tables (Continued)
Column Name |
Oracle Data Type |
SQL Server Data Type |
Description |
|
|
|
|
LUNId |
NVARCHAR2(512) |
nvarchar(512) |
ID of the LUN that stores the associated |
|
|
|
object. |
|
|
|
|
MachineId |
NVARCHAR2(512) |
nvarchar(512) |
ID of the associated physical or virtual |
|
|
|
machine. |
|
|
|
|
Module |
NVARCHAR2(512) |
nvarchar(512) |
View component that raised the event. For |
|
|
|
example, Admin, Broker, Tunnel, |
|
|
|
Framework, Client, or Agent. |
|
|
|
|
ModuleAndEventText |
NVARCHAR2(512) |
nvarchar(512) |
Event message with values substituted for |
|
|
|
attribute parameters. |
|
|
|
|
Node |
NVARCHAR2(512) |
nvarchar(512) |
Name of the virtual device node. |
|
|
|
|
Severity |
NVARCHAR2(512) |
nvarchar(512) |
Severity level. For example, INFO, |
|
|
|
WARNING, ERROR, AUDIT_SUCCESS, |
|
|
|
AUDIT_FAIL. |
|
|
|
|
Source |
NVARCHAR2(512) |
nvarchar(512) |
Identifier for the source of the event. |
|
|
|
|
ThinAppId |
NVARCHAR2(512) |
nvarchar(512) |
ID of the associated ThinApp™ object. |
|
|
|
|
Time |
TIMESTAMP |
datetime |
Time at which the event occurred, |
|
|
|
measured from the epoch (January 1, |
|
|
|
1970). |
|
|
|
|
UserDiskPathId |
NVARCHAR2(512) |
nvarchar(512) |
ID of the user disk. |
|
|
|
|
UserSID |
NVARCHAR2(512) |
nvarchar(512) |
SID of the associated user in Active |
|
|
|
Directory. |
|
|
|
|
The following table shows the schema for the event_data and event_data_historical database tables.
Table 2 3. Schema for the event_data and event_data_historical Tables
Column Name |
Oracle Data Type |
SQL Server Data Type |
Description |
|
|
|
|
|
|
BooleanValue |
SMALLINT |
tinyint |
Value of a Boolean attribute. |
|
|
|
|
n |
0 = false |
|
|
|
n |
1 = true |
|
|
|
|
|
EventID |
INTEGER |
int |
Unique primary key for the event. |
|
|
|
|
|
|
IntValue |
INTEGER |
int |
Value of an integer attribute. |
|
|
|
|
|
|
Name |
NVARCHAR2(512) |
nvarchar(512) |
Attribute name (for example, |
|
|
|
|
UserDisplayName). |
|
|
|
|
|
|
StrValue |
NVARCHAR2(512) |
nvarchar(512) |
Value of a string attribute. For other types |
|
|
|
|
of attributes, this column contains an |
|
|
|
|
interpretation of the data type as a string. |
|
|
|
|
|
|
VMware, Inc. |
9 |
View Integration
Table 2 3. Schema for the event_data and event_data_historical Tables (Continued)
Column Name |
Oracle Data Type |
SQL Server Data Type |
Description |
||
|
|
|
|
||
TimeValue |
TIMESTAMP |
datetime |
Value of a date and time attribute. |
||
|
|
|
|
||
Type |
SMALLINT |
tinyint |
The data type of the attribute. |
||
|
|
|
n |
0 |
= StrValue |
|
|
|
n |
1 |
= IntValue |
|
|
|
n |
2 |
= TimeValue |
|
|
|
n |
3 |
= BooleanValue |
|
|
|
|
|
|
Connection Broker Events
Connection broker events report View Connection Server-related information, such as desktop and application sessions, user authentication failures, and provisioning errors.
The BROKER_DAILY_MAX_DESKTOP_SESSIONS event reports the maximum number of concurrent desktop sessions over a 24-hour period. If a user runs multiple desktop sessions concurrently, each desktop session is counted separately.
The BROKER_DAILY_MAX_APP_USERS event reports the maximum number of concurrent application users over a 24-hour period. If a user runs multiple applications concurrently, the user is counted only once. Short-lived sessions might not be included in the count because the sampling is performed every five minutes.
The BROKER_VC_DISABLED and BROKER_VC_ENABLED events report the state of the vCenter driver that View uses to track a vCenter Server instance.
The BROKER_VC_STATUS_* events report the state of a vCenter Server instance.
The following table lists all the event types for View Connection Server.
Table 2 4. Connection Broker Events
Event Type |
Severity |
ModuleAndEventText |
|
|
|
BROKER_AGENT_OFFLINE |
WARNING |
The agent running on machine ${MachineName} has |
|
|
not responded to queries, marking it as offline |
|
|
|
BROKER_AGENT_ONLINE |
WARNING |
The agent running on machine ${MachineName} is |
|
|
responding again, but did not send a startup message |
|
|
|
BROKER_APPLICATION_LAUNCH_FAILURE |
ERROR |
Unable to launch from Pool ${PoolId} for user $ |
|
|
{UserDisplayName}: The broker encountered an error |
|
|
while processing the request, please contact support |
|
|
for assistance |
|
|
|
BROKER_APPLICATION_MISSING |
WARNING |
At least ${ApplicationMissingCount} applications, |
|
|
including ${ApplicationExecutable}, are not installed on |
|
|
${MachineName} in Pool ${PoolId} |
|
|
|
BROKER_APPLICATION_NOT_ENTITLED |
AUDIT_FAIL |
Unable to launch from Pool ${PoolId} for user $ |
|
|
{UserDisplayName}: User is not entitled to this Pool |
|
|
|
VMware, Inc. |
10 |
View Integration
Table 2 4. Connection Broker Events (Continued)
Event Type |
Severity |
ModuleAndEventText |
|
|
|
BROKER_APPLICATION_PROTOCOL_NOT_S |
AUDIT_FAIL |
Unable to launch from Pool ${PoolId} for user $ |
UPPORTED |
|
{UserDisplayName}: Requested protocol ${ProtocolId} |
|
|
is not supported |
|
|
|
BROKER_APPLICATION_REQUEST |
INFO |
User ${UserDisplayName} requested Application $ |
|
|
{ApplicationId} |
|
|
|
BROKER_APPLICATION_SESSION_REQUES |
INFO |
User ${UserDisplayName} requested an application |
T |
|
session from Pool ${PoolId} |
|
|
|
BROKER_DAILY_MAX_DESKTOP_SESSIONS |
INFO |
${Time}: Over the past 24 hours, the maximum number |
|
|
of concurrent desktop sessions was ${UserCount} |
|
|
|
BROKER_DAILY_MAX_APP_USERS |
INFO |
${Time}: Over the past 24 hours, the maximum number |
|
|
of users with concurrent application sessions was $ |
|
|
{UserCount} |
|
|
|
BROKER_DESKTOP_LAUNCH_FAILURE |
ERROR |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: The broker encountered an error |
|
|
while processing the request, please contact support |
|
|
for assistance |
|
|
|
BROKER_DESKTOP_NOT_ENTITLED |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: User is not entitled to this Pool |
|
|
|
BROKER_DESKTOP_PROTOCOL_NOT_SUP |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
PORTED |
|
{UserDisplayName}: Requested protocol ${ProtocolId} |
|
|
is not supported |
|
|
|
BROKER_DESKTOP_REQUEST |
INFO |
User ${UserDisplayName} requested Pool ${DesktopId} |
|
|
|
BROKER_EVENT_HANDLING_STARTED |
INFO |
Broker ${BrokerName} has started handling events |
|
|
|
BROKER_EVENT_HANDLING_STOPPED |
INFO |
${BrokerName} has stopped handling events |
|
|
|
BROKER_MACHINE_ALLOCATED |
INFO |
User ${UserDisplayName} requested Pool $ |
|
|
{DesktopId}, allocated machine ${MachineName} |
|
|
|
BROKER_MACHINE_ASSIGNED_UNAVAILAB |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
LE |
|
{UserDisplayName}: Assigned machine $ |
|
|
{MachineName} is unavailable |
|
|
|
BROKER_MACHINE_CANNOT_CONNECT |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: Failed to connect to Machine $ |
|
|
{MachineName} using ${ProtocolId} |
|
|
|
BROKER_MACHINE_CONFIGURED_VIDEO_S |
INFO |
Successfully configured video settings for Machine VM |
ETTINGS |
|
${MachineName} in Pool ${DesktopId} |
|
|
|
BROKER_MACHINE_NOT_READY |
WARNING |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: Machine ${MachineName} is not |
|
|
ready to accept connections |
|
|
|
BROKER_MACHINE_OPERATION_DELETED |
INFO |
machine ${MachineName} has been deleted |
|
|
|
BROKER_MACHINE_PROTOCOL_NOT_SUPP |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
ORTED |
|
{UserDisplayName}: Machine ${MachineName} does |
|
|
not support protocol ${ProtocolId} |
|
|
|
VMware, Inc. |
11 |
View Integration
Table 2 4. Connection Broker Events (Continued)
Event Type |
Severity |
ModuleAndEventText |
|
|
|
BROKER_MACHINE_PROTOCOL_UNAVAILAB |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
LE |
|
{UserDisplayName}: Machine ${MachineName} did not |
|
|
report protocol ${ProtocolId} as ready |
|
|
|
BROKER_MACHINE_REJECTED_SESSION |
WARNING |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: Machine ${MachineName} |
|
|
rejected the start session request |
|
|
|
BROKER_MACHINE_SESSION_TIMEDOUT |
WARNING |
Session for user ${UserDisplayName} timed out |
|
|
|
BROKER_MULTIPLE_DESKTOPS_FOR_KIOS |
WARNING |
User ${UserDisplayName} is entitled to multiple |
K_USER |
|
desktop pools |
|
|
|
BROKER_POOL_CANNOT_ASSIGN |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: There are no machines available |
|
|
to assign the user to |
|
|
|
BROKER_POOL_COMANAGER_REQUIRED |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: No co-management availability for |
|
|
protocol ${ProtocolId} |
|
|
|
BROKER_POOL_EMPTY |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: The Desktop Pool is empty |
|
|
|
BROKER_POOL_NO_MACHINE_ASSIGNED |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: No machine assigned to this user |
|
|
|
BROKER_POOL_NO_RESPONSES |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: No machines in the Desktop Pool |
|
|
are responsive |
|
|
|
BROKER_POOL_OVERLOADED |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: All responding machines are |
|
|
currently in use |
|
|
|
BROKER_POOL_POLICY_VIOLATION |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: This Desktop Pool does not allow |
|
|
online sessions |
|
|
|
BROKER_POOL_PROTOCOL_NOT_SUPPOR |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
TED |
|
{UserDisplayName}: There were no machines available |
|
|
that support protocol ${ProtocolId} |
|
|
|
BROKER_POOL_PROTOCOL_UNAVAILABLE |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: There were no machines available |
|
|
that reported protocol ${ProtocolId} as ready |
|
|
|
BROKER_POOL_TUNNEL_NOT_SUPPORTED |
AUDIT_FAIL |
Unable to launch from Pool ${DesktopId} for user $ |
|
|
{UserDisplayName}: Tunnelling is not supported for |
|
|
protocol ${ProtocolId} |
|
|
|
BROKER_PROVISIONING_ERROR_CONFIG_ |
INFO |
The previously reported configuration problem is no |
CLEARED |
|
longer present on Pool ${DesktopId} |
|
|
|
BROKER_PROVISIONING_ERROR_CONFIG_ |
ERROR |
Provisioning error occurred on Pool ${DesktopId} |
SET |
|
because of a configuration problem |
|
|
|
BROKER_PROVISIONING_ERROR_DISK_CL |
INFO |
The previously reported disk problem is no longer |
EARED |
|
present on Pool ${DesktopId} |
|
|
|
VMware, Inc. |
12 |
View Integration
Table 2 4. Connection Broker Events (Continued)
Event Type |
Severity |
ModuleAndEventText |
|
|
|
BROKER_PROVISIONING_ERROR_DISK_LC_ |
INFO |
The previously reported error due to available free disk |
RESERVATION_CLEARED |
|
space reserved for linked clones is no longer present |
|
|
on Pool ${DesktopId} |
|
|
|
BROKER_PROVISIONING_ERROR_DISK_LC_ |
ERROR |
Provisioning error occurred on Pool ${DesktopId} |
RESERVATION_SET |
|
because available free disk space is reserved for linked |
|
|
clones |
|
|
|
BROKER_PROVISIONING_ERROR_DISK_SE |
WARNING |
Provisioning error occurred on Pool ${DesktopId} |
T |
|
because of a disk problem |
|
|
|
BROKER_PROVISIONING_ERROR_LICENCE |
INFO |
The previously reported licensing problem is no longer |
_CLEARED |
|
present on Pool ${DesktopId} |
|
|
|
BROKER_PROVISIONING_ERROR_LICENCE |
ERROR |
Provisioning error occurred on Pool ${DesktopId} |
_SET |
|
because of a licensing problem |
|
|
|
BROKER_PROVISIONING_ERROR_NETWOR |
INFO |
The previously reported networking problems with |
KING_CLEARED |
|
Horizon Agent are no longer present on Pool $ |
|
|
{DesktopId} |
|
|
|
BROKER_PROVISIONING_ERROR_NETWOR |
ERROR |
Provisioning error occurred on Pool ${DesktopId} |
KING_SET |
|
because of a networking problem with Horizon Agent |
|
|
|
BROKER_PROVISIONING_ERROR_RESOUR |
INFO |
The previously reported resource problem is no longer |
CE_CLEARED |
|
present on Pool ${DesktopId} |
|
|
|
BROKER_PROVISIONING_ERROR_RESOUR |
ERROR |
Provisioning error occurred on Pool ${DesktopId} |
CE_SET |
|
because of a resource problem |
|
|
|
BROKER_PROVISIONING_ERROR_TIMEOUT |
INFO |
The previously reported timeout while customizing is no |
_CUSTOMIZATION_CLEARED |
|
longer present on Pool ${DesktopId} |
|
|
|
BROKER_PROVISIONING_ERROR_TIMEOUT |
ERROR |
Provisioning error occurred on Pool ${DesktopId} |
_CUSTOMIZATION_SET |
|
because of a timeout while customizing |
|
|
|
BROKER_PROVISIONING_ERROR_VM_CLO |
ERROR |
Provisioning error occurred for Machine $ |
NING |
|
{MachineName}: Cloning failed for Machine |
|
|
|
BROKER_PROVISIONING_ERROR_VM_CUS |
ERROR |
Provisioning error occurred for Machine $ |
TOMIZATION_ERROR |
|
{MachineName}: Customization failed for Machine |
|
|
|
BROKER_PROVISIONING_ERROR_VM_CUS |
ERROR |
Provisioning error occurred for Machine $ |
TOMIZATION_NETWORKING |
|
{MachineName}: Customization error due to no network |
|
|
communication between Horizon Agent and |
|
|
Connection Server |
|
|
|
BROKER_PROVISIONING_ERROR_VM_CUS |
ERROR |
Provisioning error occurred for Machine $ |
TOMIZATION_TIMEOUT |
|
{MachineName}: Customization operation timed out |
|
|
|
BROKER_PROVISIONING_SVI_ERROR_COM |
ERROR |
Provisioning error occurred for Machine $ |
POSER_AGENT_INIT_FAILED |
|
{MachineName}: View Composer agent initialization |
|
|
failed |
|
|
|
BROKER_PROVISIONING_SVI_ERROR_REC |
ERROR |
Provisioning error occurred for Machine $ |
ONFIG_FAILED |
|
{MachineName}: Reconfigure operation failed |
|
|
|
BROKER_PROVISIONING_SVI_ERROR_REFI |
ERROR |
Provisioning error occurred for Machine $ |
T_ FAILED |
|
{MachineName}: Refit operation ${SVIOperation} failed |
|
|
|
VMware, Inc. |
13 |
View Integration
Table 2 4. Connection Broker Events (Continued)
Event Type |
Severity |
ModuleAndEventText |
|
|
|
BROKER_PROVISIONING_SVI_ERROR_ |
ERROR |
Provisioning error occurred for Machine $ |
REMOVING_VM |
|
{MachineName}: Unable to remove Machine from |
|
|
inventory |
|
|
|
BROKER_PROVISIONING_VERIFICATION_ |
WARNING |
Provisioning verification failed for Machine $ |
FAILED_USER_ASSIGNED |
|
{MachineName}: User is already assigned to a machine |
|
|
in Pool ${DesktopId} |
|
|
|
BROKER_PROVISIONING_VERIFICATION_ |
WARNING |
Provisioning verification failed for Machine $ |
FAILED_USER_CANNOT_BE_ASSIGNED |
|
{MachineName}: A user cannot be assigned because |
|
|
Pool ${DesktopId} is not persistent |
|
|
|
BROKER_PROVISIONING_VERIFICATION_ |
WARNING |
Provisioning verification failed for Machine $ |
FAILED_VMNAME_IN_USE |
|
{MachineName}: A machine already exists in Pool $ |
|
|
{DesktopId} with name ${MachineName} |
|
|
|
BROKER_SECURITY_SERVER_ADD_FAILED |
AUDIT_FAIL |
Failed to add security server ${SecurityServerId} |
|
|
|
BROKER_SECURITY_SERVER_ADD_FAILED |
AUDIT_FAIL |
Failed to add security server ${SecurityServerId}, |
_ PASSWORD_EXPIRED |
|
pairing password expired |
|
|
|
BROKER_SECURITY_SERVER_ADD_FAILED |
AUDIT_FAIL |
Failed to add security server ${SecurityServerId}, |
_ PASSWORD_INCORRECT |
|
pairing password incorrect |
|
|
|
BROKER_SECURITY_SERVER_ADD_FAILED |
AUDIT_FAIL |
Failed to add security server ${SecurityServerId}, |
_ PASSWORD_NOT_SET |
|
pairing password not set |
|
|
|
BROKER_SECURITY_SERVER_ADDED |
AUDIT_SUCCESS |
Security server ${SecurityServerId} added |
|
|
|
BROKER_SVI_ARCHIVE_UDD_FAILED |
AUDIT_FAIL |
Failed to archive user data disk ${UserDiskName} to |
|
|
location ${SVIPath} |
|
|
|
BROKER_SVI_ARCHIVE_UDD_SUCCEEDED |
AUDIT_SUCCESS |
Archived user data disk ${UserDiskName} to location $ |
|
|
{SVIPath} |
|
|
|
BROKER_SVI_ATTACH_UDD_FAILED |
AUDIT_FAIL |
Failed to attach user data disk ${UserDiskName} to VM |
|
|
${SVIVMID} |
|
|
|
BROKER_SVI_ATTACH_UDD_SUCCEEDED |
AUDIT_SUCCESS |
Attached user data disk ${UserDiskName} to VM $ |
|
|
{SVIVMID} |
|
|
|
BROKER_SVI_DETACH_UDD_FAILED |
AUDIT_FAIL |
Failed to detach user data disk ${UserDiskName} from |
|
|
VM ${SVIVMID} |
|
|
|
BROKER_SVI_DETACH_UDD_SUCCEEDED |
AUDIT_SUCCESS |
Detached user data disk ${UserDiskName} from VM $ |
|
|
{SVIVMID} |
|
|
|
BROKER_USER_AUTHFAILED_ACCOUNT_ |
AUDIT_FAIL |
User ${UserDisplayName} failed to authenticate |
DISABLED |
|
because the account is disabled |
|
|
|
BROKER_USER_AUTHFAILED_ACCOUNT_ |
AUDIT_FAIL |
User ${UserDisplayName} failed to authenticate |
EXPIRED |
|
because the account has expired |
|
|
|
BROKER_USER_AUTHFAILED_ACCOUNT_ |
AUDIT_FAIL |
User ${UserDisplayName} failed to authenticate |
LOCKED_OUT |
|
because the account is locked out |
|
|
|
BROKER_USER_AUTHFAILED_ACCOUNT_ |
AUDIT_FAIL |
User ${UserDisplayName} failed to authenticate |
RESTRICTION |
|
because of an account restriction |
|
|
|
BROKER_USER_AUTHFAILED_BAD_USER_ |
AUDIT_FAIL |
User ${UserDisplayName} failed to authenticate |
PASSWORD |
|
because of a bad username or password |
|
|
|
VMware, Inc. |
14 |
View Integration
Table 2 4. Connection Broker Events (Continued)
Event Type |
Severity |
ModuleAndEventText |
|
|
|
BROKER_USER_AUTHFAILED_GENERAL |
AUDIT_FAIL |
User ${UserDisplayName} failed to authenticate |
|
|
|
BROKER_USER_AUTHFAILED_NO_LOGON_ |
AUDIT_FAIL |
User ${UserDisplayName} failed to authenticate |
SERVERS |
|
because there are no logon servers |
|
|
|
BROKER_USER_AUTHFAILED_PASSWORD_ |
AUDIT_FAIL |
User ${UserDisplayName} failed to authenticate |
EXPIRED |
|
because the password has expired |
|
|
|
BROKER_USER_AUTHFAILED_PASSWORD_ |
AUDIT_FAIL |
User ${UserDisplayName} failed to authenticate |
MUST_CHANGE |
|
because the password must change |
|
|
|
BROKER_USER_AUTHFAILED_SECUREID_ |
AUDIT_FAIL |
SecurID access denied for user ${UserDisplayName} |
ACCESS_DENIED |
|
|
|
|
|
BROKER_USER_AUTHFAILED_SECUREID_ |
AUDIT_FAIL |
SecurID access denied for user ${UserDisplayName} |
NEWPIN_REJECTED |
|
because new pin was rejected |
|
|
|
BROKER_USER_AUTHFAILED_SECUREID_ |
AUDIT_FAIL |
SecurID access denied for user ${UserDisplayName} |
WRONG_NEXTTOKEN |
|
because wrong next token entered |
|
|
|
BROKER_USER_AUTHFAILED_SECUREID_ |
AUDIT_FAIL |
SecurID access denied for user ${UserDisplayName} |
WRONG_STATE |
|
because of incorrect state |
|
|
|
BROKER_USER_AUTHFAILED_TIME_ |
AUDIT_FAIL |
User ${UserDisplayName} failed to authenticate |
RESTRICTION |
|
because of a time restriction |
|
|
|
BROKER_USER_NOT_AUTHORIZED |
AUDIT_FAIL |
User ${UserDisplayName} has authenticated, but is not |
|
|
authorized to perform the operation |
|
|
|
BROKER_USER_NOT_ENTITLED |
AUDIT_FAIL |
User ${UserDisplayName} has authenticated, but is not |
|
|
entitled to any Pools |
|
|
|
BROKER_USERCHANGEDPASSWORD |
AUDIT_SUCCESS |
Password for ${UserDisplayName} has been changed |
|
|
by the user |
|
|
|
BROKER_USERLOGGEDIN |
AUDIT_SUCCESS |
User ${UserDisplayName} has logged in |
|
|
|
BROKER_USERLOGGEDOUT |
AUDIT_SUCCESS |
User ${UserDisplayName} has logged out |
|
|
|
BROKER_VC_DISABLED |
INFO |
vCenter at address ${VCAddress} has been temporarily |
|
|
disabled |
|
|
|
BROKER_VC_ENABLED |
INFO |
vCenter at address ${VCAddress} has been enabled |
|
|
|
BROKER_VC_STATUS_CHANGED_CANNOT_ |
WARNING |
Cannot log in to vCenter at address ${VCAddress} |
LOGIN |
|
|
|
|
|
BROKER_VC_STATUS_CHANGED_DOWN |
INFO |
vCenter at address ${VCAddress} is down |
|
|
|
BROKER_VC_STATUS_CHANGED_INVALID_ |
WARNING |
vCenter at address ${VCAddress} has invalid |
CREDENTIALS |
|
credentials |
|
|
|
BROKER_VC_STATUS_CHANGED_NOT_YET |
INFO |
Not yet connected to vCenter at address ${VCAddress} |
_ CONNECTED |
|
|
|
|
|
BROKER_VC_STATUS_CHANGED_ |
INFO |
Reconnecting to vCenter at address ${VCAddress} |
RECONNECTING |
|
|
|
|
|
BROKER_VC_STATUS_CHANGED_UNKNOW |
WARNING |
The status of vCenter at address ${VCAddress} is |
N |
|
unknown |
|
|
|
BROKER_VC_STATUS_CHANGED_UP |
INFO |
vCenter at address ${VCAddress} is up |
|
|
|
VMware, Inc. |
15 |
Loading...