Management Pack Reference Guide

Citrix SCOM Management Pack for XenApp and XenDesktop Reference Guide

About

Citrix Management Pack Library

Display Name Citrix Management Pack Library
Version 1.0.8.0
Description Common definitions for Citrix Management Packs.

Top

Citrix Management Pack for XenApp and XenDesktop (EndUser)

Display Name Citrix Management Pack for XenApp and XenDesktop (EndUser)
Version 3.8.41.0
Description This management pack provides complete functionality (monitors, rules, tasks and views) for monitoring of Citrix XenApp and XenDesktop end-user logons, Server OS, as well as Desktop OS sessions.

Top

Citrix Management Pack for XenApp and XenDesktop (EndUser) Reports

Display Name Citrix Management Pack for XenApp and XenDesktop (EndUser) Reports
Version 3.8.41.0
Description This management pack provides reports used for analyzingysis and planning related to Citrix XenApp and XenDesktop environment.

Top

Citrix Management Pack for XenApp and XenDesktop

Display Name Citrix Management Pack for XenApp and XenDesktop
Version 3.8.41.0
Description This management pack provides monitoring functionality for Citrix XenApp and XenDesktop, version 7 and above, desktop and application virtualization platform.

Top

Citrix Management Pack for XenApp and XenDesktop Reports

Display Name Citrix Management Pack for XenApp and XenDesktop Reports
Version 3.8.41.0
Description Provides reports for Citrix XenApp and XenDesktop environment.

Top


Discoveries

Target Display Name Description Enabled by default Discovery interval
XAXD Site Data Collector Application Discovery (1 of 5)
Discovers all applications published on the delivery groups. By default all applications are discovered, but also specific applications can be included/excluded in/from discovery. 

Parameters: 
- ApplicationIncludeRegExPattern: Only applications with application name matching this regular expression will be discovered.
- ApplicationExcludeRegExPattern: Only applications with application name NOT matching this regular expression will be discovered.
Yes 14400 sec
XAXD Site Data Collector Application Discovery (2 of 5)
Discovers all applications published on the delivery groups. By default all applications are discovered, but also specific applications can be included/excluded in/from discovery. 

Parameters: 
- ApplicationIncludeRegExPattern: Only applications with application name matching this regular expression will be discovered.
- ApplicationExcludeRegExPattern: Only applications with application name NOT matching this regular expression will be discovered.
Yes 14400 sec
XAXD Site Data Collector Application Discovery (3 of 5)
Discovers all applications published on the delivery groups. By default all applications are discovered, but also specific applications can be included/excluded in/from discovery. 

Parameters: 
- ApplicationIncludeRegExPattern: Only applications with application name matching this regular expression will be discovered.
- ApplicationExcludeRegExPattern: Only applications with application name NOT matching this regular expression will be discovered.
Yes 14400 sec
XAXD Site Data Collector Application Discovery (4 of 5)
Discovers all applications published on the delivery groups. By default all applications are discovered, but also specific applications can be included/excluded in/from discovery. 

Parameters: 
- ApplicationIncludeRegExPattern: Only applications with application name matching this regular expression will be discovered.
- ApplicationExcludeRegExPattern: Only applications with application name NOT matching this regular expression will be discovered.
Yes 14400 sec
XAXD Site Data Collector Application Discovery (5 of 5)
Discovers all applications published on the delivery groups. By default all applications are discovered, but also specific applications can be included/excluded in/from discovery. 

Parameters: 
- ApplicationIncludeRegExPattern: Only applications with application name matching this regular expression will be discovered.
- ApplicationExcludeRegExPattern: Only applications with application name NOT matching this regular expression will be discovered.
Yes 14400 sec
Windows Computer XenApp/XenDesktop Machine Agent Proxy Computer Role Discovery
Discovers computers with Citrix XenApp and XenDesktop Machine Agent installed. 
Yes 14400 sec
XAXD Delivery Controller Computer Role Delivery Controller Discovery
Discovers Delivery Controllers and their corresponding Windows services. By default, all controllers are discovered, but also controllers for specific sites can be included/excluded in/from discovery.

Parameters:
- SiteIncludeRegExPattern: Only delivery controllers belonging the same o sites with site name matching this regular expression will be discovered.  This parameter must have the same value as "Site Data Collector Discovery" discovery "SiteIncludeRegExPattern" parameter.
- SiteExcludeRegExPattern: Only delivery controllers NOT belonging to sites with site name matching this regular expression will be discovered.  This parameter must have the same value as "Site Data Collector Discovery" discovery "SiteExcludeRegExPattern" parameter.

NOTE: When using filer parameters, you must change the same parameters must also be changed in 'Delivery Groups and Hypervisor Connections Discovery' and 'Site Data Collector Discovery' discoveries accordingly.
Yes 14400 sec
XAXD Site Data Collector Delivery Groups and Hypervisor Connections Discovery
Discovers hypervisor connections, delivery groups, and Server OS machines that deliver desktops and published applications.
By default all data for all sites is discovered, but also specific sites and/or delivery groups can be included/excluded in/from discovery. 

Parameters:
- SiteIncludeRegExPattern: Only sites (with belonging components) with site name matching this regular expression will be discovered.  This parameter must have the same value as "Delivery Controller Discovery" discovery "SiteIncludeRegExPattern" parameter.
- SiteExcludeRegExPattern: Only sites (with belonging components) with site name NOT matching this regular expression will be discovered.  This parameter must have the same value as "Delivery Controller Discovery" discovery "SiteExcludeRegExPattern" parameter.
- DeliveryGroupIncludeRegExPattern: Only delivery groups with delivery group name matching this regular expression will be discovered.
- DeliveryGroupExcludeRegExPattern: Only delivery groups with delivery group name NOT matching this regular expression will be discovered.

NOTE: When using filter parameters, you must change the same parameters in 'Delivery Controller Discovery' and 'Site Data Collector Discovery' discoveries accordingly.
Yes 14400 sec
Windows Computer Citrix Computer Discovery
Discovers managed nodes with Citrix software installed on it.
Yes 3600 sec
XAXD Delivery Controller Computer Role Site Data Collector Discovery
Discovers MP site data collector, which is used for collecting and monitoring data on the XenApp/XenDesktop site level. Site data collector is hosted on the XenApp/XenDesktop Delivery Controller computer with the lowest ID in a site.
By default all data for all sites are being monitored. With discovery parameters described below, specific sites can be included/excluded in/from discovery.

Parameters:
- SiteIncludeRegExPattern: Only sites (with belonging components) with site name matching this regular expression will be discovered.  This parameter must have the same value as "Delivery Controller Discovery" discovery "SiteIncludeRegExPattern" parameter.
- SiteExcludeRegExPattern: Only sites (with belonging components) with site name NOT matching this regular expression will be discovered.  This parameter must have the same value as "Delivery Controller Discovery" discovery "SiteExcludeRegExPattern" parameter.

NOTE: When using filer parameters, the same parameters must also be changed in 'Delivery Controller Discovery' and 'Delivery Groups and Hypervisor Connections Discovery' discoveries accordingly.
          
Yes 3600 sec
Citrix MPXAXD Machine Agent Proxy Computer Role Citrix MPXAXD Machine Agent Controller Connection Discovery
Discovers MPXAXD Machine Agent Controller Connection
Yes 14400 sec
XAXD Application Server OS Delivery Group To Published Application Discovery
Discovers the relationship between a Server OS delivery group and its published application.
Yes ---
XAXD Application Desktop OS Random Delivery Group To Published Application Discovery
Discovers the relationship between Desktop OS Random delivery group and its published application.
Yes ---
Citrix MPXAXD Machine Agent Proxy Computer Role XenApp and XenDesktop Machine Agent Discovery
Discovers Windows computers with Citrix MPXAXD Machine Agent installation. These Windows computers are used for proxy monitoring of server/desktop OS machines.
Yes 14400 sec
XAXD Delivery Controller Computer Role XenApp and XenDesktop MP Agent Service Discovery
Discovers XenApp and XenDesktop MP Agent Service used for monitoring XenApp/XenDesktop infrastructure.
Yes 14400 sec
Windows Server Delivery Controller Computer Role Discovery
Discovers XenApp/XenDesktop Delivery Controller Computer Role.
Yes 14400 sec
XAXD Sites Populate a Group of XenDesktop Sites
Populates a group with discovered XenDesktop Sites.
Yes ---
Citrix Management Populate Citrix XenDesktop Root Object
Populates Citrix root group with XenDesktop Sites group.
Yes ---

Monitors

Citrix MPXAXD Agent

Citrix MPXAXD Agent Service Operational Status

Display Name Citrix MPXAXD Agent Service Operational Status
Description
Monitors if the Citrix Management Pack Agent for XenApp and XenDesktop service is operational.
Alert Name Citrix MPXAXD Agent Not Operational
Alert Message
The "Citrix MPXAXD Agent" service on computer {0} is not operational.

Agent Error: 
{1}
Target Citrix MPXAXD Agent
Enabled by default Yes

Health States
Monitor State Health State
AgentOperational Healthy
AgentNotOperational Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Citrix MPXAXD Agent Service State

Display Name Citrix MPXAXD Agent Service State
Description
Monitors the Citrix Management Pack Agent for XenApp and XenDesktop mandatory service.
Knowledge Article
Summary

The mandatory Citrix XenApp and XenDesktop Management Pack’s service is not running.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service from the “Actions” pane.

Alert Name Citrix MPXAXD Agent Service Stopped
Alert Message
The "Citrix MPXAXD Agent" service on computer {0} has stopped running.
Target Citrix MPXAXD Agent
Enabled by default Yes

Health States
Monitor State Health State
Service is running Healthy
Service is not running Critical

Overridable parameters
Parameter Default Value
CheckStartupType true

Top

Citrix MPXAXD Machine Agent

Citrix MPXAXD Machine Agent Service State

Display Name Citrix MPXAXD Machine Agent Service State
Description
Monitors the Citrix XenApp and XenDesktop Machine Agent service.
Knowledge Article
Summary

The “Citrix MPXAXD Machine Agent” service is not running.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service from the “Actions” pane.

Alert Name Citrix MPXAXD Machine Agent Service Stopped
Alert Message
The "Citrix MPXAXD Machine Agent" service on computer {0} has stopped running.
Target Citrix MPXAXD Machine Agent
Enabled by default Yes

Health States
Monitor State Health State
Running Healthy
NotRunning Critical

Overridable parameters
Parameter Default Value
CheckStartupType true

Top

Citrix MPXAXD Machine Agent Controller Connection

Citrix MPXAXD Machine Agent Delivery Controller Connection Status

Display Name Citrix MPXAXD Machine Agent Delivery Controller Connection Status
Description
Monitors if Citrix MPXAXD Machine Agent can connect to configured Citrix Delivery Controllers.
Alert Name Citrix MPXAXD Machine Agent - Delivery Controller Not Accessible
Alert Message
Citrix XenApp and XenDesktop MP Machine Agent on {0} cannot connect to Citrix Delivery Controller.

Delivery Controller Name: {1}
Connection status: {2}
Connection user: {3}
Error: {4}
{5}
Target Citrix MPXAXD Machine Agent Controller Connection
Enabled by default Yes

Health States
Monitor State Health State
ConnectionOK Healthy
ConnectionFailed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false

Top

Citrix MPXAXD Machine Agent Proxy Computer Role

Citrix MPXAXD Machine Agent Discovery Duration

Display Name Citrix MPXAXD Machine Agent Discovery Duration
Description
Monitors and alerts if Citrix MPXAXD Machine Agent discovery duration takes too long - more than discovery interval on agent.
Alert Name MPXAXD Machine Agent - Discovery Duration
Alert Message
Time needed to get performance data from Server OS and Desktop OS machines on "{0}" exceeded the Citrix MPXAXD Machine Agent discovery interval ({1} seconds).
{3}

Discovery duration: {2} seconds

Server OS machines: {5}
Desktop OS machines: {4}
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes

Health States
Monitor State Health State
DiscoveryOK Healthy
DiscoveryLongerThanDiscoveryInterval Warning
DiscoveryTerminated Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false

Top

Citrix MPXAXD Machine Agent Failed Connections To Machines

Display Name Citrix MPXAXD Machine Agent Failed Connections To Machines
Description
Monitors the percentage of machines where agent could not get data from (could not connect to) and alerts if percentage is above threshold.
Alert Name Citrix MPXAXD Machine Agent - Failed Connections To Machines
Alert Message
The percentage of failed connections to machines from Citrix MPXAXD Machine Agent on "{0}" has exceeded the threshold value.

Machine connection status:

OK Machines: {1}
Partial Machines: {2}
Failed Machines: {3}
Percentage of failed Machines: {4} %
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes

Health States
Monitor State Health State
BelowThreshold Healthy
AboveThreshold Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Threshold 30
Debug false

Top

XAXD Delivery Controller Computer Role

Citrix MPXAXD Agent Installation

Display Name Citrix MPXAXD Agent Installation
Description
Monitors if the XenApp and XenDesktop MP Agent is installed on the Windows computer.
Knowledge Article
Summary

This monitor generates an alert if the XenApp and XenDesktop MP Agent has not been installed on the Delivery Controller. The monitor shows whether your XenApp/XenDesktop Delivery Controller is being monitored by XenApp and XenDesktop MP or not.

Causes

The XenApp and XenDesktop MP Agent is not installed on the Delivery Controller.

Resolutions

To install the XenApp and XenDesktop MP Agent start the following task from the XenApp and XenDesktop Computers view:

Install Citrix MPXAXD Agent

Alert Name Citrix MPXAXD Agent Installation
Alert Message
Citrix Management Pack Agent for XenApp and XenDesktop on node "{0}" is not installed!
Target XAXD Delivery Controller Computer Role
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Error Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime

Top

XAXD Delivery Controller Service

Service Running State

Display Name Service Running State
Description
Monitors the current status of the Windows service.  An alert from this monitor indicates the Windows Service is not currently running.
Knowledge Article
Summary

The Windows service is not running.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service from the "Actions" pane.

You can also attempt to restart the Windows service by using:

Start the Service

Alert Name XenDesktop Controller Service Stopped
Alert Message
The '{0}' service on computer {1} has stopped running.
Target XAXD Delivery Controller Service
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
CheckStartupType true

Top

XAXD Delivery Group

Avg. User Logon Authentication Time

Display Name Avg. User Logon Authentication Time
Description
Monitors average user logon authentication time (in seconds) for a delivery group. Authentication time is the time taken to complete authentication to the remote session.
Knowledge Article
Summary

Monitors the average user logon authentication time (in seconds) for a delivery group. During this phase the user is authenticated to the domain and his rights are checked for access to the either server or desktop OS machine.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which the monitor is started (the default value is set to 300 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 10 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

A session can only be initiated after the user’s credentials have been verified. This typically happens by communicating with an Active Directory domain controller over the network.

Authentication is an often an overlooked piece of the logon puzzle. In an environment with an overloaded or inaccessible domain controller, this can have a dramatic impact on logon times. Additionally, applications themselves may also authenticate to Active Directory, adding significant additional time to any application startup if the AD server is unresponsive.

Common issues include the following:

  • Overloaded Active Directory server which leads to additional time to log on.

  • Unavailable Active Directory server which may block authorization process for up to 30 seconds before AD server fails over to secondary AD server.

  • Slow authentication because domain controllers are at remote offices.

  • DNS issues.

Resolutions

To view the logon phase trend on a delivery group in the past days, open the following link:

Delivery group average logon performance

Also, please see the Delivery Group - Logons per Week (Plan & Manage) report to view how the average logon phase time changed for the past weeks.

Also ensure the following:

  • AD servers should have enough resources to handle the load also during logon storms.

  • The server/desktop OS machine to which user is connecting can contact the AD server.

  • Enough domain controllers should be placed to all main user locations to facilitate the authentication process.

  • The server/desktop OS machines are using AD DNS servers. Also check if the name registrations for your DCs are correct.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

You may also want to check out the Citrix logon optimization guide:

Logon Optimization Guide

Alert Name User Logon Process - Delivery Group Average Logon Authentication Time
Alert Message
The average user logon authentication time for delivery group '{0}' in site '{1}' is {2} s.
Target XAXD Delivery Group
Enabled by default No

Health States
Monitor State Health State
Ok Healthy
AuthenticationTimeTooLong Warning

Overridable parameters
Parameter Default Value
WarningThreshold 10
Debug false
IntervalSeconds 300

Top

Avg. User Logon Brokering Time

Display Name Avg. User Logon Brokering Time
Description
Monitors average user logon brokering time (in seconds) for a delivery group. This is the time taken to complete the process of brokering the session.
Knowledge Article
Summary

Monitors the average user logon brokering time (in seconds) for a delivery group.

Brokering is a process that allows a user to click a desktop or application resource, and have a 'worker' (server or desktop machine) selected and prepared for an inbound ICA/HDX connection. During brokering process, the Broker Service is responsible for negotiating session launch requests with delivery group machines. The Broker Service communicates with the VDA agent over a CBP (connection brokering protocol) protocol to validate a machine’s readiness to fulfil a session launch request, gather the necessary details (IP address or host name), and send the details to the StoreFront site to be packaged and delivered as an '.ICA' launch file that’s consumed by the Receiver.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which the monitor is started (the default value is set to 300 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 5 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

Reasons for a slower brokering logon phase can be:

  • Delivery controller is under heavy load.

  • WCF operations timing out.

Resolutions

To view the logon phase trend on a delivery group in the past days, open the following link:

Delivery group average logon performance

Also, please see the Delivery Group - Logons per Week (Plan & Manage) report to view how the average logon phase time changed for the past weeks.

If the brokering time is slow in general, please escalate the issue to the XenApp/XenDesktop administrator to check the load balancing on the Delivery Controller.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

Alert Name User Logon Process - Delivery Group Average Logon Brokering Time
Alert Message
The average user logon brokering time for delivery group '{0}' in site '{1}' is {2} s.
Target XAXD Delivery Group
Enabled by default No

Health States
Monitor State Health State
Ok Healthy
BrokeringTimeTooLong Warning

Overridable parameters
Parameter Default Value
WarningThreshold 5
Debug false
IntervalSeconds 300

Top

Avg. User Logon Duration

Display Name Avg. User Logon Duration
Description
Monitors average user logon duration (in seconds) for a delivery group.  Total logon duration is the elapsed time from the point when a user launches a desktop or application via Storefront to the point when a user can start using it.
Knowledge Article
Summary

Monitors the average logon duration for a delivery group. The logon duration is the elapsed time from the point when a user launches a desktop or application via Storefront to the point when a user can start using it.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which the monitor is started (the default value is set to 300 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 90 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

There are various reasons for a slower user logon including:

  • A new application was installed.

  • An operating system update occurred.

  • Configuration changes were made.

Also, check root causes of all logon phases which are included into the complete logon duration.

Resolutions

To view the logon duration trend on a delivery group in the past days, open the following link:

Delivery group average logon performance

Also, please see the Delivery Group - Logons per Week (Plan & Manage) report to view how the average logon duration changed for the past weeks.

Additional

User logon is a complex and a resource intensive process on a Citrix server or desktop OS machine. It is initiated when Citrix delivery group load balancing algorithm selects the system where published application and/or desktop that user has selected will be started, and ends when the application and/or desktop is running and the user is able to interact with it.

Management Pack breaks down the Citrix XenApp/XenDesktop logon process into the following phases.

Phase 1: Brokering

The time taken to decide which desktop to assign to the user.

Phase 2: VM start

In case the session required a machine to be started, the time taken to boot the desktop.

Phase 3: HDX connection

The time taken to complete the steps required in setting up the HDX connection from the client to the VM, dependding on the network.

Phase 4: Authentication

The time taken to complete authentication to the remote session.

Phase 5: Profile load

The phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).

Phase 6: GPOs

During this phase, group policy objects are applied/defined on the Domain Controller.

Phase 7: Logon scripts

This phase covers the time taken for the logon scripts to be executed.

Phase 8: Interactive session

The phase starts in parallel with GPOs phase and covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

You may also want to check out the Citrix logon optimization guide:

Logon Optimization Guide

Alert Name User Logon Process - Delivery Group Average Logon Duration
Alert Message
The average user logon duration for delivery group '{0}' in site '{1}' is {2} s.
Target XAXD Delivery Group
Enabled by default Yes

Health States
Monitor State Health State
Ok Healthy
LogonDurationTooLong Warning

Overridable parameters
Parameter Default Value
WarningThreshold 90
Debug false
IntervalSeconds 300

Top

Avg. User Logon GPOs Time

Display Name Avg. User Logon GPOs Time
Description
Monitors average user logon GPOs time (in seconds) for a delivery group. During this phase the desktop/server machine applies user settings defined on the Domain Controller.
Knowledge Article
Summary

Monitors the average user logon GPOs time (in seconds) for a delivery group. During this phase the desktop/server machine applies user settings defined on the Domain Controller.

When an application or desktop is launched through Citrix, it kicks off a huge stream of events. Profiles are engaged, printers are mapped, and policies are applied.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which the monitor is started (the default value is set to 300 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 40 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

Applying GPOs can have a large impact on start time. Some of the most common ways that GPOs increase logon times are:

  • Numerous GPOs, rather than a few large ones.

  • Large numbers of access control rewrites on folders and files.

  • Large numbers of mapped drives.

  • Large numbers of network printers.

  • Unused GPO sections (Computer/User) are not disabled.

  • Numerous XenApp/XenDesktop policies.

Resolutions

To view the logon phase trend on a delivery group in the past days, see:

Delivery group average logon performance

Also, please see the Delivery Group - Logons per Week (Plan & Manage) report to view how the average logon phase time changed for the past weeks.

Resolutions to some common issues are as follows:

Issue Description

Mitigation

Having GPOs that heavily rewrite access to files and folders on boot can have a significant impact on logon times.

Optimize access control to reduce number of required changes. Use AD groups and build permissions into base image.

Merging GPOs takes additional time and adds load to the AD server.

Merge GPOs where possible, so that only several larger GPOs exist, instead of hundreds of small ones.

Having many printer and driver mappings can increase logon time.

Reduce the number of required printer and drive mappings where possible, and ensure that client printer mapping is allowed to occur after logon in XenApp/XenDesktop.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

You may also want to check out the Citrix logon optimization guide:

Logon Optimization Guide

Alert Name User Logon Process - Delivery Group Average Logon GPOs Time
Alert Message
The average user logon GPOs time for delivery group '{0}' in site '{1}' is {2} s.
Target XAXD Delivery Group
Enabled by default No

Health States
Monitor State Health State
Ok Healthy
GPOsTimeTooLong Warning

Overridable parameters
Parameter Default Value
WarningThreshold 40
Debug false
IntervalSeconds 300

Top

Avg. User Logon HDX Connection Time

Display Name Avg. User Logon HDX Connection Time
Description
Monitors average user logon HDX connection time for a delivery group. This is the time taken to complete the steps required in setting up the HDX connection from the client to the VM.
Knowledge Article
Summary

Monitors the average user logon HDX connection time (in seconds) for a delivery group. This is the time taken to complete the steps required in setting up the HDX connection from the client to the VM.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which the monitor is started (the default value is set to 300 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 40 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

The HDX connection time is heavily dependent on the network, so there can be many issues related to slow HDX connection time.

Resolutions

To view the logon phase trend on a delivery group in the past days, open the following link:

Delivery group average logon performance

Also, please see the Delivery Group - Logons per Week (Plan & Manage) report to view how the average logon phase time changed for the past weeks.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

Alert Name User Logon Process - Delivery Group Average Logon HDX Connection Time
Alert Message
The average user logon HDX connection time for delivery group '{0}' in site '{1}' is {2} s.
Target XAXD Delivery Group
Enabled by default No

Health States
Monitor State Health State
Ok Healthy
HDXConnectionTimeTooLong Warning

Overridable parameters
Parameter Default Value
WarningThreshold 40
Debug false
IntervalSeconds 300

Top

Avg. User Logon Interactive Session Time

Display Name Avg. User Logon Interactive Session Time
Description
Monitors average user logon interactive session time (in seconds) for a delivery group. The logon phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.
Knowledge Article
Summary

Monitors the average user logon interactive session time (in seconds) for a delivery group. This logon phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which the monitor is started (the default value is set to 300 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 60 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Resolutions

To view the logon phase trend on a delivery group in the past days, open the following link:

Delivery group average logon performance

Also, please see the Delivery Group - Logons per Week (Plan & Manage) report to view how the average logon phase time changed for the past weeks.

One of the issues related to long interactive session times is the following:

Black or Blue Screen When Connecting to Published Desktop

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

Alert Name User Logon Process - Delivery Group Average Logon Interactive Session Time
Alert Message
The average user logon interactive session time for delivery group '{0}' in site '{1}' is {2} s.
Target XAXD Delivery Group
Enabled by default No

Health States
Monitor State Health State
Ok Healthy
InteractiveSessionTooLong Warning

Overridable parameters
Parameter Default Value
WarningThreshold 60
Debug false
IntervalSeconds 300

Top

Avg. User Logon Profile Load Time

Display Name Avg. User Logon Profile Load Time
Description
Monitors average user logon profile load time (in seconds) for a delivery group. The logon phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).
Knowledge Article
Summary

Monitors the average user logon profile load time (in seconds) for a delivery group. The logon phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).

Once the user is authenticated, the operating system can start to build his/her session. First, a user profile is needed. All of the following phases require the user profile to be set up and the user’s registry hive to be loaded.

If the user does not already have a profile, a new one is created. This slows down the initial logon quite a bit compared to subsequent logons. The main reason is that Active Setup runs the IE/Mail/Theme initialization routines.

Profile load times are one of the most significant logon times in most organizations. Several types of Microsoft profiles exist: local, roaming, mandatory, as well as many third-party solutions.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which the monitor is started (the default value is set to 300 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 30 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

Some of the most common issues are that either a huge roaming profile needs to be copied over the network, or connection issues to the profile store (generally a file share, though some third-party solutions may utilize databases).

Other reasons for a slower profile load logon phase include:

  • Large profiles.

  • Corrupt profiles.

  • Unavailable profile store.

  • Overloaded profile store.

Resolutions

To view the logon phase trend on a delivery group in the past days, see:

Delivery group average logon performance

Also, please see the Delivery Group - Logons per Week (Plan & Manage) report to view how the average logon phase time changed for the past weeks.

Resolutions for some common issues are as follows:

Issue Description

Mitigation

Profiles need to be downloaded on each logon, and un-optimized profiles can grow to hundreds of megabytes or thousands of files. Either size or quantity of files in a roaming profile can increase the download size.

Redirect most user folders to a network share (Desktop, Documents) or ignore folders if allowable by the business (Cookies & History).

If a user commonly opens up multiple sessions, this increases the chances of developing corrupt roaming profiles.

With Windows Server 2008 R2 Active Directory, enable interim roaming profile writes. Alternatively, use a third-party profile solution that manages multiple sessions more appropriately.

The profile store is unavailable, resulting in a logon delay and possibly default user settings or an inability to connect.

Ensure the profile store is highly available.

The server hosting the profile store has either too many users connecting, or may not be optimized as a file server, causing delays in delivering roaming profiles.

Optimize the server for file sharing, ensure the hardware (including disks and network) can handle the necessary load, and distribute to multiple servers if necessary.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

You may also want to check out the Citrix logon optimization guide:

Logon Optimization Guide

Alert Name User Logon Process - Delivery Group Average Logon Profile Load Time
Alert Message
The average user logon profile load time for delivery group '{0}' in site '{1}' is {2} s.
Target XAXD Delivery Group
Enabled by default No

Health States
Monitor State Health State
Ok Healthy
ProfileLoadTooLong Warning

Overridable parameters
Parameter Default Value
WarningThreshold 30
Debug false
IntervalSeconds 300

Top

Avg. User Logon Scripts Execution Time

Display Name Avg. User Logon Scripts Execution Time
Description
Monitors average user logon scripts execution time (in seconds) for a delivery group. This logon phase covers the time taken for the logon scripts to be executed.
Knowledge Article
Summary

Monitors the average user logon scripts execution time (in seconds) for a delivery group. This logon phase covers the time taken for the logon scripts to be executed.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which the monitor is started (the default value is set to 300 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 60 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

Logon scripts can have a large impact on start time. Some of the most common ways that logon scripts increase logon times are:

  • Slow or resource-intensive startup scripts (for example, those that move large numbers of files).

  • Inefficient loops in scripts.

  • Nested calls to different scripts.

Resolutions

To view the logon phase trend on a delivery group in the past days, open the following link:

Delivery group average logon performance

Also, please see the Delivery Group - Logons per Week (Plan & Manage) report to view how the average logon phase time changed for the past weeks.

Some scripts may complete a lot of actions, including calls to other scripts, long loops, mapping network drives, and others.

Optimize and merge logon scripts where possible. Windows Server 2008 introduced Group Policy Preferences, which when used can reduce, or in some cases eliminate, the need for logon scripts. When not using Group Policy Preferences, assign logon scripts to users via GPOs, rather than the AD User Account property setting.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

You may also want to check out the Citrix logon optimization guide:

Logon Optimization Guide

Alert Name User Logon Process - Delivery Group Average Logon Scripts Execution Time
Alert Message
The average user logon scripts execution time for delivery group '{0}' in site '{1}' is {2} s.
Target XAXD Delivery Group
Enabled by default No

Health States
Monitor State Health State
Ok Healthy
LogonScriptsTimeTooLong Warning

Overridable parameters
Parameter Default Value
WarningThreshold 60
Debug false
IntervalSeconds 300

Top

Avg. User Logon VM Start Time

Display Name Avg. User Logon VM Start Time
Description
Monitors average user logon VM start time (in seconds) for a delivery group. This is the time taken to start a VM.
Knowledge Article
Summary

Monitors the average user logon VM start time (in seconds) for a delivery group.

VM start logon phase includes the time taken to start VMs by the user. VM start time will be 0 in case there was no need to start a new machine, since a machine could be brokered instantly.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which the monitor is started (the default value is set to 300 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 90 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

If desktops are not powered on when the users try to access their desktop, it would take some time for the desktop to boot and be ready for login.

Resolutions

To view the logon phase trend on a delivery group in the past days, open the following link:

Delivery group average logon performance

Also, please see the Delivery Group - Logons per Week (Plan & Manage) report to view how the average logon phase time changed for the past weeks.

Try also to fine tune idle pool settings for the desktop OS machines, to be ready for users when they are expected to be used.

Additionally, optimize the startup process by disabling or delaying services and applications that are scheduled to run at power on.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

Alert Name User Logon Process - Delivery Group Average Logon VM Start Time
Alert Message
The average user logon VM start time for delivery group '{0}' in site '{1}' is {2} s.
Target XAXD Delivery Group
Enabled by default No

Health States
Monitor State Health State
Ok Healthy
VMStartTimeTooLong Warning

Overridable parameters
Parameter Default Value
WarningThreshold 90
Debug false
IntervalSeconds 300

Top

Delivery Group Availability

Display Name Delivery Group Availability
Description
This monitor checks the availability of a delivery group. Delivery group is available if it contains at least one machine that can provide a published resource (application or desktop).
Knowledge Article
Summary

This monitor checks the availability of a delivery group. Delivery group is available if it contains at least one machine that can provide a published resource (application or desktop).

Machines can provide published resources when following conditions are met:

  • Machine is not in maintenance mode

  • Machine is registered

  • Machine is not fully loaded (For Server OS machine: LoadIndex < 100%; For Desktop OS machine: has no session)

If delivery group is not available and if all machines in a delivery group are operational (not in maintenance and are registered), then, additional machines should be added to that delivery group. Otherwise, make sure all machines are operational.

With Server OS Load Performance view you can check weather delivery group maximum capacity was hit or if there are problems with some machines in a delivery group. If "LoadCapacityUtilization" counter is 100%, then, all machines are fully loaded, meaning that capacity of delivery group should be expanded. If, on other hand, there are unregistered machines and "LoadIndex" counter is 100%, then, this indicates some machines in DG are not operational.

This monitor is not applicable for Static Desktop OS delivery groups.

Note: By default alert is not generated as primary use of this monitor is for "Application – Availability" report. But if you want alert to be generated just override "Generates Alert" parameter.

Alert Name Delivery Group Not Available
Alert Message
Delivery group is not available.

Site: {0}
Delivery group: {1}
Target XAXD Delivery Group
Enabled by default Yes

Health States
Monitor State Health State
Unavailable Critical
Available Healthy

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 1
Debug false

Top

Delivery Group In Maintenance

Display Name Delivery Group In Maintenance
Description
Monitors if the delivery group is in maintenance mode.

This monitor is not applicable for Static Desktop OS delivery groups.
Knowledge Article
Summary

This monitor checks whether delivery group is in maintenance mode.

By default alert is not generated as primary use of this monitor is for "Application – Availability" report.

This monitor is not applicable for Static Desktop OS delivery groups.

Alert Name Delivery Group In Maintenance
Alert Message
Delivery group is in maintenance mode.

Site: {0}
Delivery group: {1}
          
Target XAXD Delivery Group
Enabled by default Yes

Health States
Monitor State Health State
Available Healthy
In Maintenance Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 1
Debug false

Top

Failed Registrations in Delivery Group

Display Name Failed Registrations in Delivery Group
Description
Monitors whether there are any failed registrations for a delivery group.
Knowledge Article
Summary

Before any desktop/application can be brokered by the controller, a Virtual Delivery Agent installed on the desktop or server machines has to register with one of the controllers in the XenApp/XenDesktop site. A machine (VDA) registers with one of controllers every time it is going to be used (started) by XenDesktop. Machines for which registration fail are not available and directly decrease number of available machines in a delivery group which they belong to.

Causes

There are many causes, including: no Virtual Delivery Agent being installed on a machine, DNS problems, firewall configuration, time synchronization. For a complete list, see causes documented in Citrix knowledge articles below.

Resolutions

To resolve registration problems, first check for which machines registration failed. Either check alerts for the delivery group in question in 'Machines->Failed Registrations' alert view or by selecting 'Alert View' on delivery group in 'Citrix Management Topology'.

Then, try to resolve the problem according to Citrix knowledge articles:

CTX136668 - Virtual Delivery Agent Registration Troubleshooting Flowchart

CTX129700 - XenApp/XenDesktop Virtual Machines Do Not Successfully Register with the Desktop Delivery Delivery Controller

CTX129225 - VDAs fail to register when using disjoint namespaces in a XenApp/XenDesktop Environment

CTX126992 - Troubleshooting Virtual Desktop Agent Registration with Controllers in XenDesktop

Alert Name Group Failed Registrations
Alert Message
Number of failed registrations in '{0}' delivery group is equal or above threshold.

Site: {1}
Target XAXD Delivery Group
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
FailedRegistrations Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 1
Debug false

Top

Number of Active Sessions

Display Name Number of Active Sessions
Description
Monitors the number of active XenApp/XenDesktop sessions in a delivery group. 
Knowledge Article
Summary

This monitor checks the number of active sessions in a delivery group.

Active sessions are sessions where a user is active within his/her session (e.g. Remote Desktop). For example, running applications, web browsing, or similar activity that involves using a mouse or keyboard.

Alert Name Number of Active Sessions
Alert Message
The number of active XenApp/XenDesktop sessions in a delivery group has exceeded the threshold value.

Site: {0}
Delivery group: {1}
Active sessions: {2}
Target XAXD Delivery Group
Enabled by default No

Health States
Monitor State Health State
BelowThreshold Healthy
AboveThreshold Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 300
Debug false

Top

Number of All Sessions

Display Name Number of All Sessions
Description
Monitors the number of all XenApp/XenDesktop sessions in a group. 
Knowledge Article
Summary

This monitor shows the number of all sessions in a delivery group.

All sessions are sessions that are either in active or disconnect state.

Alert Name Number of All Sessions
Alert Message
The number of all XenApp/XenDesktop sessions in a group has exceeded the threshold value.

Site: {0}
Delivery group: {1}
All sessions: {2}
Target XAXD Delivery Group
Enabled by default No

Health States
Monitor State Health State
BelowThreshold Healthy
AboveThreshold Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 300
Debug false

Top

Number of Disconnected Sessions

Display Name Number of Disconnected Sessions
Description
Monitors the number of disconnected XenApp/XenDesktop sessions in a delivery group. 
Knowledge Article
Summary

This monitor shows the number of disconnected sessions in a delivery group.

Monitors the number of ready desktops in a Desktop OS Random delivery group. Ready desktops are machines which are running and are ready for brokering (are ready to be used by users). Only one user sessions is allowed on one Desktop OS machine.

Alert Name Number of Disconnected Sessions
Alert Message
The number of disconnected XenApp/XenDesktop sessions in a delivery group has exceeded the threshold value.

Site: {0}
Delivery group: {1}
Disconnected sessions: {2}
Target XAXD Delivery Group
Enabled by default Yes

Health States
Monitor State Health State
BelowThreshold Healthy
AboveThreshold Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 30
Debug false

Top

XAXD Delivery Group Desktop OS Random

Desktop OS Random Delivery Group Usage (in %)

Display Name Desktop OS Random Delivery Group Usage (in %)
Description
Monitors the percentage of used desktops (In use or Disconnected) for Desktop OS Random delivery group.
Knowledge Article
Summary

This monitor checks the desktop utilization for each Desktop OS Random delivery group in a site.

Monitoring delivery groups is very important for the correct configuration and capacity planning in the XenApp/XenDesktop environment. If all virtual desktops in a delivery group are in use, the delivery group becomes unavailable to new users.

Desktop OS Random delivery groups are groups for which users cannot be assigned to specific desktops.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The monitoring period (the default interval is set to 300 seconds).

SyncTime

Time at which to start time interval (not set by default).

WarningThreshold

Warning threshold for the monitor (the default is 90).

CriticalThreshold

Critical threshold for the monitor (the default is 98).

Alert Name Desktop OS Random Delivery Group Utilization (in %)
Alert Message
The percentage of used desktops (In use or Disconnected) has exceeded the threshold.

Site: {0}
Delivery group: {1}

Usage: {2} %
Target XAXD Delivery Group Desktop OS Random
Enabled by default Yes

Health States
Monitor State Health State
GreaterThanEqualCriticalThreshold Critical
GreaterThanEqualWarningThreshold Warning
LessThanWarningThreshold Healthy

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
WarningThreshold 90
CriticalThreshold 98
Debug false

Top

Number of Ready Desktops Too Low

Display Name Number of Ready Desktops Too Low
Description
Monitors the number of ready desktops in a Desktop OS Random delivery group. Ready desktops are machines which are running and are ready for brokering (are ready to be used by users). Only one user sessions is allowed on one Desktop OS machine.
Knowledge Article
Summary

This monitor checks the number of ready desktops in each Desktop OS Random delivery group in a site.

If the number of active desktops in ready pool is too low, new users may experience very slow response time while connecting to desktops.

Alert Name Number of Ready Desktops
Alert Message
Number of ready desktops in the delivery group '{1}' is below threshold.

Site: {0}
Delivery group: {1}
Ready desktops: {3}
Target XAXD Delivery Group Desktop OS Random
Enabled by default No

Health States
Monitor State Health State
ReadyDesktopsTooLow Warning
OK Healthy

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 5
Debug false

Top

XAXD Delivery Group Desktop OS Static

Desktop OS Static Delivery Group Usage (in %)

Display Name Desktop OS Static Delivery Group Usage (in %)
Description
Monitors the percentage of assigned desktops for a Desktop OS Static delivery group.
Knowledge Article
Summary

This monitor checks the desktop utilization for each Desktop OS Static delivery group in a site.

Monitoring delivery groups is very important for the correct configuration and capacity planning in the XenApp/XenDesktop environment. If all virtual desktops in a delivery group are already assigned to some users, delivery group becomes unavailable to new users. Monitoring Desktop OS Static delivery group is especially important if "assign on first use" approach is used.

Desktop OS Static delivery group is a group for which users are assigned to specific desktops (either manually or on first use).

Alert Name Desktop OS Static Delivery Group Usage (in %)
Alert Message
The percentage of assigned desktops has exceeded the threshold.

Site: {0}
Delivery group: {1}

Usage: {2} %
Target XAXD Delivery Group Desktop OS Static
Enabled by default No

Health States
Monitor State Health State
GreaterThanEqualCriticalThreshold Critical
GreaterThanEqualWarningThreshold Warning
LessThanWarningThreshold Healthy

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
WarningThreshold 90
CriticalThreshold 98
Debug false

Top

XAXD Delivery Group Server OS

Load Available (%)

Display Name Load Available (%)
Description
Monitors the percentage of currently available delivery group load/capacity. Load availability is the percentage of free load index on all active server machines vs. total available load index on all active server machines. Free load index is a total non-used load index on all active servers in the delivery group. Total available load index is a number obtained by counting all active server machines in the delivery group. Each server machine has a potential of load index 10000.
Knowledge Article
Summary

This monitor shows the percentage of currently available delivery group load/capacity and alerts if the available capacity is below threshold. Available capacity is the capacity that is instantly available to the end-users. If there is no capacity available (all active machines have reached maximum load) the delivery controller will start a new machine in the delivery group if available. Power management defines idle pool settings (delivery group power time scheme and peak buffer) which enable Citrix administrators to control, for example, how many machines should be kept available in an idle state during peak hours.

The primary purpose of this monitor is to detect situations where instantly available capacity is low, although overall delivery group capacity is not nearing its maximum potential. When there is no free capacity left, end-users will temporary not be able to make new connections until a new machine gets started and is ready to accept connections.

Load availability (in %) shows the currently available capacity of a delivery group at a certain point in time if no additional machines are made available by the delivery controller.

Currently available capacity is the percentage of available load on all active machines vs. load potential on all active machines in the delivery group. Each machine has a maximum load potential of 10000 (load index). Load index is calculated based on the load management policy settings.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The monitoring period (the default interval is set to 300 seconds).

SyncTime

Time at which to start time interval (not set by default).

Threshold

The currently available load/capacity (in %) of a delivery group (the default is 10%).

Causes

Available capacity may be low because of various reasons, such as:

  • Too few machines in the delivery group.

  • No new machines available in the delivery group.

  • Failure of one or more machines in the delivery group.

  • Abnormal high resource usage of one or more users/applications.

Resolutions

Maximum delivery group capacity reached

Check the delivery group load usage by seeing:

View Load Usage (in %)

View Load Performance

If the load is constantly near or at delivery groups' maximum capacity during peak hours, please consult with your Citrix administrator to add additional machines to the delivery group.

No available capacity

In this case, the total capacity is not reached, but the available capacity is low. This indicates that there are possible machine registration issues. Check if there are any recent machine registration failures for the delivery group.

View machine failed registrations

If unused machines exist in the delivery group and are pending in "Unregistered" state or are being restarted periodically by the delivery controller, there may be registration issues with the machines that need attention.

If available capacity is low for short periods of time, then, a possible root cause could be that the infrastructure (delivery controller and hypervisor) isn't able to properly manage the "idle pool" - pool of machines that are ready for new connections. Machine idle pool is being managed by setting the power management policies for the delivery group. It may take up to a few minutes for the new machine to be ready for new connections.

Failure of one or more servers in the delivery group

Check if there were any recent machine failures which may happen for various reasons, such as, hypervisor or network issues, OS failures or end-user application defects.

Abnormal high resource usage of one or more users/applications on the servers in delivery group

Check if processor usage on the servers is higher than usual. It may happen that a certain applications consumes abnormal amount of resources (i.e. defect in application itself).

Server OS Machine Performance

External

For more information on XenApp/XenDesktop power management features, see the following information:

Citrix Broker SDK - Machine Power Management

Alert Name Free Capacity (%) Is Lower Than Expected
Alert Message
Free capacity (available load) for the delivery group '{0}' is lower than expected.

Site: {1}
Delivery group: {2}
Available load/capacity (in %): {3}
Target XAXD Delivery Group Server OS
Enabled by default Yes

Health States
Monitor State Health State
FreeCapacityTooLow Warning
Ok Healthy

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 10
Debug false

Top

Number of Available Machines

Display Name Number of Available Machines
Description
Monitors the number of available servers in Server OS delivery group. Available servers are machines that are running, are registered with the delivery controller, are not in maintenance mode, and have Load Evaluator Index less than 100%.
Knowledge Article
Summary

This monitor shows the number of available machines in Server OS delivery group.

Available servers are machines that are powered on, registered, not in maintenance mode and having Load Evaluator Index less than 100%.

When users try to launch an application or desktop while all active servers are reporting a full load, a new server will be started and made available for new connections. If there are no servers to start, or the machines are put in maintenance mode, the connection will fail.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The monitoring period (the default interval is set to 300 seconds).

SyncTime

Time at which to start time interval (not set by default).

Threshold

The minimum number of available Server OS machines (the default is 1).

Alert Name Number of Available Servers Too Low
Alert Message
Number of available servers in the delivery group '{0}' is below threshold.

Site: {1}
Delivery group: {2}
Available servers: {3}
Target XAXD Delivery Group Server OS
Enabled by default Yes

Health States
Monitor State Health State
AvailableServersTooLow Warning
Ok Healthy

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 1
Debug false

Top

Total Load/Capacity Usage (%)

Display Name Total Load/Capacity Usage (%)
Description
Monitors the percentage of total delivery group load/capacity usage. Usage is the percentage of actual load index vs. total load index potential. Actual load index is the sum of load index of all the servers in the delivery group. Total load index potential is a number obtained by counting all server machines in the delivery group except those that are in the maintenance mode. Each server machine has a potential of load index 10000.
Knowledge Article
Summary

This monitor checks the percentage of the used delivery group load/capacity and alerts if load/capacity usage is above threshold. If the capacity usage is high, the delivery group is reaching its maximum load potential. When there is no free capacity left, end-users will not be able to make new connections.

Total load/capacity usage (in %) shows the usage of the total (or maximal) delivery group capacity if all machines were made available to the end-users (excluding machines that are in the maintenance mode).

Load/capacity usage is the percentage of actual load vs. total load potential in the delivery group. Each machine has a maximum load potential of 10000 (load index). Load index is calculated based on the load management policy settings.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The monitoring period (the default interval is set to 300 seconds).

SyncTime

Time at which to start time interval (not set by default).

Threshold

The load/capacity usage (in %) of a delivery group (the default is 90%).

Causes

Delivery group load may be high for various reasons, such as:

  • Too few machines in the delivery group.

  • No new machines available in the delivery group.

  • Failure of one or more machines in the delivery group.

  • Abnormal high resource usage of one or more users/applications.

As a consequence of the above root causes, increased load can be observed on all machines in the delivery group. In some cases, high load can be observed also on only one or a few machines (e.g. end-users running defective application).

Resolutions

To view the load/capacity usage performance, see:

View Load Usage (in %)

To view available machines, see:

View available Server OS machines

If the load is constantly near or at delivery groups' maximum capacity during peak hours, please consult with your Citrix administrator to add additional machines to the delivery group.

Alert Name Load/Capacity Usage (%) Too High
Alert Message
The load/capacity usage for the delivery group '{0}' is too high. You should either add new resources to the delivery group or optimize the Server OS machine usage.

Site: {1}
Delivery group: {2}
Load/capacity usage: {3}
          
Target XAXD Delivery Group Server OS
Enabled by default Yes

Health States
Monitor State Health State
Ok Healthy
LoadTooHigh Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 90
Debug false

Top

XAXD Orchestration Service

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Orchestration Service database connection is configured.
Alert Name Orchestration Service Has No Database Connection Configured
Alert Message
The Orchestration Service  Has No Database Connection Configured.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Orchestration Service
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for Orchestration Service Cannot Be Located
Alert Message
The specified database could not be located with the configured connection string.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Orchestration Service
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Orchestration Service currently in use is compatible with the version of the Orchestration Service schema  in the database. It detects if the schema is newer.
Alert Name Incompatible Version of Orchestration Service
Alert Message
The version of the Orchestration Service currently in use is incompatible with the version of the Orchestration Service schema in database.  Upgrade the Orchestration Service to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Orchestration Service
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Orchestration service schema on the database is compatible with the version of the Orchestration Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of Orchestration Service
Alert Message
The version of the Orchestration Service schema on the database is incompatible with the version of the Orchestration Service currently in use.  Upgrade the database schema to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Orchestration Service
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name Orchestration Service Database Schema Upgrade in Progress
Alert Message
A database schema upgrade is currently in progress.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Orchestration Service
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name Orchestration Service Invalid Database Configuration
Alert Message
The expected stored procedures are missing from the database.  

This could be because the Orchestration Service schema has not been added to the database.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Orchestration Service
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Login to Database Rejected

Display Name Login to Database Rejected
Description
Monitors if the database logon attempt from the Orchestration Service was successful.
Alert Name Logon Attempt from Orchestration Service Rejected by Database
Alert Message
The Logon Attempt from Orchestration Service Rejected by Database.

This could be because the service attempted to log on with invalid credentials or because a database has not been installed in the specified location.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Orchestration Service
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBRejectedConnection Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Orchestration Service EnvironmentTest Interface Probe Status

Display Name Orchestration Service EnvironmentTest Interface Probe Status
Description
Monitors the status of the EnvironmentTest interface for the Orchestration Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix Orchestration Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Orchestration Service
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

SDK Interface Probe Status

Display Name SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Orchestration Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Probe for Orchestration Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Orchestration Service
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Failed State

Display Name Service Failed State
Description
Monitors if the Orchestration Service has failed.
Alert Name Orchestration Service Failed
Alert Message
The Orchestration Service has failed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Orchestration Service
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Failed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Server OS Machine

Check Load Index

Display Name Check Load Index
Description
Monitors load of Server OS machines that are delivering desktops and applications to users.
Knowledge Article
Summary

This monitor checks the load of server machines delivering desktops and/or applications to the end users.

Load index can be in the range of 0 to 10000, where 0 means that there is no load and 10000 means that the server is fully loaded. Load index is calculated based on the load management policy settings and is used by the delivery controller when end-users are making new connections.

When users try to launch an application or desktop while all active servers are reporting a full load, a new server will be started and made available for new connections. If there are no servers to start or the machines are put in maintenance mode, then the connection will fail.

The following is a list of default load management policies settings:

  • CPU usage: Report full load if CPU is 90%, disabled by default

  • Disk usage: Report 75% load if disk queue length is 8, disabled by default

  • Memory usage: Report full load if Memory usage is 90%, disabled by default

  • Memory usage base load: Report zero load if the base operating system's memory usage is below 768 MB, enabled by default

  • Maximum number of sessions: Limit 100, enabled by default

  • Concurrent logons tolerance: Target value 2, enabled by default

  • CPU usage excluded process priority: Exclude processes that have a priority of Below Normal or Low, enabled by default

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The monitoring period (the default interval is set to 300 seconds).

SyncTime

Time at which to start time interval (not set by default).

NumSamples

The number of monitoring periods in which the load index has to be over threshold to trigger a health state change (the default is 1 sample).

Threshold

The load index threshold (the default is set to 8000).

Causes

Load index on one machine may be high for various reasons, such as:

  • Load management policy settings

  • Too few machines in the delivery group

  • Failure of one or more machines in the delivery group

  • Abnormal high resource usage of one or more users/applications on the machine

As a consequence of the above root causes, increased load can be observed on all machines in the delivery group. In some cases, high load can be observed also on only one or a few machines (e.g. end-users running defective application).

Resolutions

Identify first if load index is high only on the machine where the issues is reported or also on one or more other machines in the delivery group.

It is also important to find out if load is high on only one or more than one machine. Please check also if the load is balanced evenly throughout all the machines in the delivery group.

To view and compare load index between machines, see:

View Server OS machine performance

If high load index is isolated on one machine only, try to check if the load management policy settings fit your needs and also check OS performance parameters on the machines, such as, cpu usage, mem usage, disk usage and disk iops, number of concurrent user sessions, etc.

If high load index is not isolated and exists on all registered servers, check if load balancing works correctly and if new machines, that can handle new users connections, are being powered on and are registering themselves to the delivery controller. Checking if there are machine registration issues can be done. See:

View machine failed registrations

If unused machines exist and are pending in "Unregistered" state or are being regularly restarted there may be registration issues with you machines that need attention.

External

For more information, see the "Citrix XenApp and XenDesktop User Guide" and especially the following information:

Manage Server OS machine server load

Load Management policy settings

Alert Name Load Index Too High
Alert Message
Load index of server '{0}' exceeded the threshold value.

Server: {1}
Delivery Group: {2}
Site: {3}

Load index: {4} 
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
LoadIndexHigh Warning
OK Healthy

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Threshold 8000
NumSamples 1
SyncTime
Debug false

Top

Citrix Audio Redirection Service State

Display Name Citrix Audio Redirection Service State
Description
Monitors the current state of Citrix Audio Redirection Service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Audio Redirection Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Audio Redirection Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Desktop Service State

Display Name Citrix Desktop Service State
Description
Monitors the current state of Citrix Desktop Service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Desktop Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Desktop Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Device Redirector Service

Display Name Citrix Device Redirector Service
Description
Monitors the current state of Citrix Device Redirector Service. The service is part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Device Redirector Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Device Redirector Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
          
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Diagnostic Facility COM Server Service State

Display Name Citrix Diagnostic Facility COM Server Service State
Description
Monitors the current state of Citrix Diagnostic Facility COM Server service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Diagnostic Facility COM Server” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Diagnostic Facility COM Server Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Encryption Service State

Display Name Citrix Encryption Service State
Description
Monitors the current state of Citrix Encryption Service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Encryption Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Encryption Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix End User Experiencing Monitoring Service State

Display Name Citrix End User Experiencing Monitoring Service State
Description
Monitors the current state of Citrix End User Experiencing Monitoring service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix End User Experiencing Monitoring” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix End User Experiencing Monitoring Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Group Policy Engine Service State

Display Name Citrix Group Policy Engine Service State
Description
Monitors the current state of Citrix Group Policy Engine service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Group Policy Engine” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Group Policy Engine Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix HDX MediaStream for Flash Service State

Display Name Citrix HDX MediaStream for Flash Service State
Description
Monitors the current state of Citrix HDX MediaStream for Flash Service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix HDX MediaStream for Flash Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix HDX MediaStream for Flash Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Location and Sensor Virtual Channel Service State

Display Name Citrix Location and Sensor Virtual Channel Service State
Description
Monitors the current state of Citrix Location and Sensor Virtual Channel Service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Location and Sensor Virtual Channel Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Location and Sensor Virtual Channel Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Mobile Receiver Virtual Channel Service State

Display Name Citrix Mobile Receiver Virtual Channel Service State
Description
Monitors the current state of Citrix Mobile Receiver Virtual Channel Service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Mobile Receiver Virtual Channel Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Mobile Receiver Virtual Channel Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix MultiTouch Redirection Service

Display Name Citrix MultiTouch Redirection Service
Description
Monitors the current state of Citrix MultiTouch Redirection Service. The service is part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix MultiTouch Redirection Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix MultiTouch Redirection Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
          
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Personal vDisk

Display Name Citrix Personal vDisk
Description
Monitors the current state of Citrix Personal vDisk. The service is part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Personal vDisk” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Personal vDisk Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
          
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Print Manager Service State

Display Name Citrix Print Manager Service State
Description
Monitors the current state of Citrix Print Manager Service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Print Manager Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Print Manager Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Profile Management Service State

Display Name Citrix Profile Management Service State
Description
Monitors the current state of Citrix Profile Management service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Profile Management” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Profile Management Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Pvs for VMs Agent Service State

Display Name Citrix Pvs for VMs Agent Service State
Description
Monitors the current state of Citrix Pvs for VMs Agent Service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Pvs for VMs Agent” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix PVS for VMs Agent Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Services Manager Service State

Display Name Citrix Services Manager Service State
Description
Monitors the current state of Citrix Services Manager Service. The service is part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Services Manager” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Services Manager Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Smart Card Service State

Display Name Citrix Smart Card Service State
Description
Monitors the current state of Citrix Smart Card Service. The service is a part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Smart Card Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Smart Card Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Stack Control Service State

Display Name Citrix Stack Control Service State
Description
Monitors the current state of Citrix Stack Control Service. The service is part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Stack Control Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Stack Control Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

Citrix Telemetry Service

Display Name Citrix Telemetry Service
Description
Monitors the current state of Citrix Telemetry Service. The service is part of VDA Agent on the Server OS machine.
Knowledge Article
Summary

Monitors if Virtual Delivery Agent service “Citrix Telemetry Service” is running on Server OS machine. Alert is not generated if machine or its delivery group is in maintenance mode.

Configuration

By default an alert will be raised only if the service is set to start automatically and the service is not currently running. If the service is set to start manually or is disabled, no alert will be raised when the service is stopped.

Causes

A service can stop for many reasons, including:

  • The service was stopped by an administrator.

  • The service encountered an exception that stopped it.

  • The service was improperly configured, which prevented it from starting.

  • Another service, that this service is dependent on, was stopped.

Resolutions

Start the service.

Alert Name Citrix Telemetry Service Not Running
Alert Message
The VDA Agent service '{0}' on computer '{1}' has stopped running.

Site: {2}
Delivery group: {3}
Server OS machine power state: {4}
Server OS machine registration state: {5}
          
Target XAXD Server OS Machine
Enabled by default Yes

Health States
Monitor State Health State
ServiceOK Healthy
ServiceNotRunning Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
CheckStartupType true
Debug false

Top

XAXD Service AD Identity

AD Identity Service EnvironmentTest Interface Probe Status

Display Name AD Identity Service EnvironmentTest Interface Probe Status
Description
Monitors the status of the EnvironmentTest interface for the AD Identity Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix AD Identity Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the AD Identity Service database connection is configured.
Alert Name AdIdentity Service Has No Database Connection Configured
Alert Message
The AdIdentity Service  Has No Database Connection Configured.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for AdIdentity Service Cannot Be Located
Alert Message
The specified database could not be located with the configured connection string.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the AD Identity Service currently in use is compatible with the version of the AD Identity Service schema  in the database. It detects if the schema is newer.
Alert Name Incompatible Version of AdIdentity Service
Alert Message
The version of the AdIdentity Service currently in use is incompatible with the version of the AdIdentity Service schema in database.  Upgrade the AdIdentity Service to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the AD Identity Service schema on the database is compatible with the version of the AD Identity Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of AdIdentity Service
Alert Message
The version of the AdIdentity Service schema on the database is incompatible with the version of the AdIdentity Service currently in use.  Upgrade the database schema to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name AdIdentity Service Database Schema Upgrade in Progress
Alert Message
A database schema upgrade is currently in progress.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

InterService Interface Probe Status

Display Name InterService Interface Probe Status
Description
Monitors the status of the InterService interface for the AD Identity Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name InterService Probe for AdIdentity Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name AdIdentity Service Invalid Database Configuration
Alert Message
The expected stored procedures are missing from the database.  

This could be because the AdIdentity Service schema has not been added to the database.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Login to Database Rejected

Display Name Login to Database Rejected
Description
Monitors if the database logon attempt from the AD Identity Service was successful.
Alert Name Logon Attempt from AdIdentity Service Rejected by Database
Alert Message
The Logon Attempt from AdIdentity Service Rejected by Database.

This could be because the service attempted to log on with invalid credentials or because a database has not been installed in the specified location.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBRejectedConnection Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Peer Interface Probe Status

Display Name Peer Interface Probe Status
Description
Monitors the status of the Peer interface for the AD Identity Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name Peer Probe for AdIdentity Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

SDK Interface Probe Status

Display Name SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the AD Identity Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Probe for AdIdentity Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Failed State

Display Name Service Failed State
Description
Monitors if the AD Identity Service has failed.
Alert Name AdIdentity Service Failed
Alert Message
The AdIdentity Service has failed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Failed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Unknown State

Display Name Service Unknown State
Description
Detects if the AD Identity Service status cannot be determined.
Alert Name AdIdentity Service Status Unknown
Alert Message
The Service status cannot be determined.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service AD Identity
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Unknown Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Analytics

Analytics Service Environment Test Interface Probe Status

Display Name Analytics Service Environment Test Interface Probe Status
Description
Monitors the status of the Environment Test interface for the Analytics Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix Analytics Service Not Responding
Alert Message
            Host: {0}
            Service: {1}
            Probe Type: {2}
            Probe URL: {3}

            Probe Status: {4}
          
Target XAXD Service Analytics
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Analytics Service database connection is configured.
Alert Name Analytics Service Has No Database Connection Configured
Alert Message
            The Analytics Service does not have a database connection configured.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service Analytics
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for Analytics Service Cannot be Located
Alert Message
            The specified database could not be located with the configured connection string.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service Analytics
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Analytics Service currently in use is compatible with the version of the Analytics Service schema in database. It detects if the schema is newer.
Alert Name Incompatible Version of Storefront Service
Alert Message
            The version of the Analytics Service currently in use is incompatible with the version of the Analytics Service schema on the database.  Upgrade the Analytics Service to a more recent version.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service Analytics
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Analytics Service schema on the database is compatible with the version of the Analytics Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of Analytics Service
Alert Message
            The version of the Analytics Service schema on the database is incompatible with the version of the Analytics Service currently in use.  Upgrade the database schema to a more recent version.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service Analytics
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name Analytics Service Database Schema Upgrade in Progress
Alert Message
            A database schema upgrade is in progress.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service Analytics
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name Analytics Service Invalid Database Configuration
Alert Message
            The expected stored procedures are missing from the database.  This may be because the Analytics Service schema has not been added to the database.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service Analytics
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

SDK Interface Probe Status

Display Name SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Analytics Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Interface Probe for Citrix Analytics Service Not Responding
Alert Message
            Host: {0}
            Service: {1}
            Probe Type: {2}
            Probe URL: {3}

            Probe Status: {4}
          
Target XAXD Service Analytics
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service App Library

App Library Service Environment Test Interface Probe Status

Display Name App Library Service Environment Test Interface Probe Status
Description
Monitors the status of the Environment Test interface for the App Library Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix App Library Service Not Responding
Alert Message
            Host: {0}
            Service: {1}
            Probe Type: {2}
            Probe URL: {3}

            Probe Status: {4}
          
Target XAXD Service App Library
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

App Library Service InterService Interface Probe Status

Display Name App Library Service InterService Interface Probe Status
Description
Monitors the status of the InterService interface for the App Library Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name InterService Interface Probe for Citrix App Library Service Not Responding
Alert Message
            Host: {0}
            Service: {1}
            Probe Type: {2}
            Probe URL: {3}

            Probe Status: {4}
          
Target XAXD Service App Library
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

App Library Service Peer Interface Probe Status

Display Name App Library Service Peer Interface Probe Status
Description
            Monitors the status of the Peer interface for the App Library Service instance. Possible states are: Responding, NotResponding and BadBindingType.
          
Alert Name Peer Interface Probe for Citrix App Library Service Not Responding
Alert Message
            Host: {0}
            Service: {1}
            Probe Type: {2}
            Probe URL: {3}

            Probe Status: {4}
          
Target XAXD Service App Library
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Analytics Service database connection is configured.
Alert Name AppLibrary Service Has No Database Connection Configured
Alert Message
            The AppLibrary Service does not have a database connection configured.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service App Library
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for AppLibrary Service Cannot be Located
Alert Message
            The specified database could not be located with the configured connection string.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service App Library
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Analytics Service currently in use is compatible with the version of the Analytics Service schema in database. It detects if the schema is newer.
Alert Name Incompatible Version of AppLibrary Service
Alert Message
            The version of the AppLibrary Service currently in use is incompatible with the version of the AppLibrary Service schema on the database.  Upgrade the AppLibrary Service to a more recent version.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service App Library
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Analytics Service schema on the database is compatible with the version of the Analytics Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of AppLibrary Service
Alert Message
            The version of the AppLibrary Service schema on the database is incompatible with the version of the AppLibrary Service currently in use.  Upgrade the database schema to a more recent version.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service App Library
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name AppLibrary Service Database Schema Upgrade in Progress
Alert Message
            A database schema upgrade is in progress.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service App Library
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name AppLibrary Service Invalid Database Configuration
Alert Message
            The expected stored procedures are missing from the database.  This may be because the AppLibrary Service schema has not been added to the database.

            Host: {0}
            Service: {1}

            Service Status: {2}
          
Target XAXD Service App Library
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

SDK Interface Probe Status

Display Name SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the App Library Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Interface Probe for Citrix App Library Service Not Responding
Alert Message
            Host: {0}
            Service: {1}
            Probe Type: {2}
            Probe URL: {3}

            Probe Status: {4}
          
Target XAXD Service App Library
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Broker

Broker Service Environment Test Interface Probe Status

Display Name Broker Service Environment Test Interface Probe Status
Description
Monitors the status of the Environment Test interface for the Broker Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix Broker Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Broker Service InterService Interface Probe Status

Display Name Broker Service InterService Interface Probe Status
Description
Monitors the status of the InterService interface for the Broker Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name InterService Probe for Broker Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Connectivity Between Broker Service and Database

Display Name Connectivity Between Broker Service and Database
Description
Detects if connectivity between the Broker Service and the database has been lost. 
Alert Name Lost Connectivity Between Broker Service and Database
Alert Message
Connectivity between the Broker Service and the database has been lost. This may be a transitory network error, but may indicate a loss of connectivity that requires administrator intervention.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
PendingFailure Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Missing Mandatory Feature

Display Name Database Missing Mandatory Feature
Description
Detects if the broker is connected to a database that is valid, but it does not have the full functionality required, so the broker cannot function. 
Alert Name Broker Service Database Missing Mandatory Feature
Alert Message
The broker is connected to a database that is valid, but it does not have the full functionality required, so the broker cannot function. Upgrading the database is required.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBMissingMandatoryFeature Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Missing Optional Feature

Display Name Database Missing Optional Feature
Description
Detects if the broker is connected to a database that is valid, but it does not have the full functionality required for optimal performance.
Alert Name Broker Service Database Missing Optional Feature
Alert Message
The broker is connected to a database that is valid, but it does not have the full functionality required for optimal performance. Upgrading the database is advisable.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBMissingOptionalFeature Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Broker Service database connection is configured.
Alert Name Broker Service Has No Database Connection Configured
Alert Message
The broker does not have a database connection configured.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for Broker Service Cannot Be Located
Alert Message
Specified database could not be located with the configured connection string.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Broker Service currently in use is compatible with the version of the Broker Service schema in database. It detects if the schema is newer.
Alert Name Incompatible Version of Broker Service
Alert Message
The broker is too old to use the database. A newer version is required.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Broker Service schema in the database is compatible with the version of the Broker Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of Broker Service
Alert Message
The database is too old for the Broker Service. Upgrade the database.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name Broker Service Database Schema Upgrade in Progress
Alert Message
A database schema upgrade is in progress.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name Broker Service Invalid Database Configuration
Alert Message
Database schema is missing (possibly just the stored procedures in it).

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Login to Database Rejected

Display Name Login to Database Rejected
Description
Monitors if the database logon attempt from the Broker Service was successful.
Alert Name Database Logon Attempt from Broker Service Rejected
Alert Message
The database rejected the logon from the Broker Service. This may be caused by invalid credentials, or the database not being installed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBRejectedConnection Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

SDK Interface Probe Status

Display Name SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Broker Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Probe for Broker Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Failed State

Display Name Service Failed State
Description
Monitors if the Broker Service has failed.
Alert Name Broker Service Failed
Alert Message
Connectivity between the broker and the database has been lost for an extended period of time, or has failed due to a configuration problem. The broker service cannot operate while its connection to the database is unavailable.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Failed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Unknown State

Display Name Service Unknown State
Description
Detects if the Broker Service status cannot be determined.
Alert Name Broker Service Status Unknown
Alert Message
Service's status cannot be determined.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Broker
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Unknown Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Configuration

Configuration Service EnvironmentTest Interface Probe Status

Display Name Configuration Service EnvironmentTest Interface Probe Status
Description
Monitors the status of the EnvironmentTest interface for the Configuration Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest interface Probe for Citrix Configuration Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Configuration Service Feature Checks Interface Probe Status

Display Name Configuration Service Feature Checks Interface Probe Status
Description
Monitors the status of the Feature Checks interface for the Configuration Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name FeatureChecks Interface Probe for Citrix Configuration Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Configuration Service database connection is configured.
Alert Name Configuration Service’s Database Connection Not Configured
Alert Message
The Configuration Service’s Database Connection Not Configured.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for Configuration Service Cannot be Located
Alert Message
The specified database could not be located with the configured connection string.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Configuration Service currently in use is compatible with the version of the Configuration Service schema in database. It detects if the schema is newer.
Alert Name Incompatible Version of Configuration Service
Alert Message
Version of the Configuration Service currently in use is incompatible with the version of the Configuration Service schema in database.  Upgrade the Configuration Service to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Configuration Service schema on the database is compatible with the version of the Configuration Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of Configuration Service
Alert Message
The version of the Configuration Service schema on the database is incompatible with the version of the Configuration Service currently in use. Upgrade the database schema to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name Configuration Service Database Schema Upgrade in Progress
Alert Message
A database schema upgrade is currently in progress.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

InterService Interface Probe Status

Display Name InterService Interface Probe Status
Description
Monitors the status of the InterService interface for the Configuration Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name InterService Interface Probe for Citrix Configuration Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name Configuration Service Invalid Database Configuration
Alert Message
The expected stored procedures are missing from the database.  This could be because the Configuration Service schema has not been added to the database.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Login to Database Rejected

Display Name Login to Database Rejected
Description
Monitors if the database logon attempt from the Configuration Service was successful.
Alert Name Logon Attempt from Configuration Service Rejected by Database
Alert Message
The database rejected the logon attempt from the Configuration Service. This could be because the service attempted to log on with invalid credentials or because a database has not been installed in the specified location.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBRejectedConnection Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

SDK Interface Probe Status

Display Name SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Configuration Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Interface Probe for Citrix Configuration Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Failed State

Display Name Service Failed State
Description
Monitors if the Configuration Service has failed.
Alert Name Configuration Service Failed
Alert Message
The Configuration Service has failed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Failed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Unknown State

Display Name Service Unknown State
Description
Detects if the Configuration Service status cannot be determined.
Alert Name Configuration Service Status Unknown
Alert Message
The Service status cannot be determined.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Unknown Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Configuration Logging

Configuration Logging Service Environment Test Interface Probe Status

Display Name Configuration Logging Service Environment Test Interface Probe Status
Description
Monitors the status of the Environment Test interface for the Configuration Logging Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix Configuration Logging Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Configuration Logging Service InterService Interface Probe Status

Display Name Configuration Logging Service InterService Interface Probe Status
Description
Monitors the status of the InterService interface for the Configuration Logging Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name InterService Interface Probe for Citrix Configuration Logging Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Configuration Logging Service SDK Interface Probe Status

Display Name Configuration Logging Service SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Configuration Logging Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Interface Probe for Citrix Configuration Logging Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Configuration Logging Service database connection is configured.
Alert Name Configuration Logging Service Has No Database Connection Configured
Alert Message
The Configuration Logging Service does not have a database connection configured.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for Configuration Logging Service Cannot be Located
Alert Message
The specified database could not be located with the configured connection string.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Configuration Logging Service currently in use is compatible with the version of the Configuration Logging Service schema in database. It detects if the schema is newer.
Alert Name Incompatible Version of Configuration Logging Service
Alert Message
The version of the Configuration Logging Service currently in use is incompatible with the version of the Configuration Logging Service schema on the database.  Upgrade the Configuration Logging Service to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Configuration Logging Service schema on the database is compatible with the version of the Configuration Logging Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of Configuration Logging Service
Alert Message
Version of the Configuration Logging Service schema on the database is incompatible with the version of the Configuration Logging Service currently in use.  Upgrade the database schema to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name Configuration Logging Service Database Schema Upgrade in Progress
Alert Message
A database schema upgrade is currently in progress.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name Configuration Logging Service Invalid Database Configuration
Alert Message
The expected stored procedures are missing from the database.  This may be because the Configuration Logging Service schema has not been added to the database.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Login to Database Rejected

Display Name Login to Database Rejected
Description
Monitors if the database logon attempt from the Configuration Logging Service was successful.
Alert Name Logon Attempt from Configuration Logging Service Rejected by Database
Alert Message
The database rejected the logon from the Configuration Logging Service. This may be caused by invalid credentials, or the database not being installed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBRejectedConnection Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Failed State

Display Name Service Failed State
Description
Monitors if the Configuration Logging Service has failed.
Alert Name Configuration Logging Service Failed
Alert Message
The Configuration Logging Service has failed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Failed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Unknown State

Display Name Service Unknown State
Description
Detects if the Configuration Logging Service status cannot be determined.
Alert Name Configuration Logging Service Status Unknown
Alert Message
The service status cannot be determined.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Configuration Logging
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Unknown Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Delegated Administration

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Delegated Administration Service database connection is configured.
Alert Name Delegated Administration Service Has No Database Connection Configured
Alert Message
The DelegatedAdmin Service does not have a database connection configured.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified database for Delegated Administration Service Cannot be Located
Alert Message
The specified database could not be located with the configured connection string.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Delegated Administraton Service currently in use is compatible with the version of the Delegated Administration Service schema in database. It detects if the schema is newer.
Alert Name Incompatible Version of Delegated Administration Service
Alert Message
The version of the DelegatedAdmin Service currently in use is incompatible with the version of the DelegatedAdmin Service schema on the database.  Upgrade the DelegatedAdmin Service to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Delegated Administration Service schema on the database is compatible with the version of the Delegated Administration Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of Delegated Administration Service
Alert Message
The version of the DelegatedAdmin Service schema on the database is incompatible with the version of the DelegatedAdmin Service currently in use.  Upgrade the database schema to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name Delegated Administration Service Database Schema Upgrade in Progress
Alert Message
A database schema upgrade is in progress.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Delegated Administration Service Environment Test Interface Probe Status

Display Name Delegated Administration Service Environment Test Interface Probe Status
Description
Monitors the status of the Environment Test interface for the Delegated Administration Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix Delegated Administration Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Delegated Administration Service InterService Interface Probe Status

Display Name Delegated Administration Service InterService Interface Probe Status
Description
Monitors the status of the InterService interface for the Delegated Administration Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name InterService Interface Probe for Citrix Delegated Administration Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Delegated Administration Service SDK Interface Probe Status

Display Name Delegated Administration Service SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Delegated Administration Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Interface Probe for Citrix Delegated Administration Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name Delegated Administration Service Invalid Database Configuration
Alert Message
The expected stored procedures are missing from the database.  This may be because the DelegatedAdmin Service schema has not been added to the database.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Login to Database Rejected

Display Name Login to Database Rejected
Description
Monitors if the database logon attempt from the Delegated Administration Service was successful.
Alert Name Logon Attempt from Delegated Administration Service Rejected by Database
Alert Message
The database rejected the logon attempt from the DelegatedAdmin Service.  This may be because the service attempted to log on with invalid credentials or because a database has not been installed in the specified location.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBRejectedConnection Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Failed State

Display Name Service Failed State
Description
Monitors if the Delegated Administration Service has failed.
Alert Name Delegated Administration Service Failed
Alert Message
The DelegatedAdmin Service has failed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Failed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Unknown State

Display Name Service Unknown State
Description
Detects if the Delegated Administration Service status cannot be determined.
Alert Name Delegated Administration Service Status Unknown
Alert Message
The Service's status cannot be determined.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Delegated Administration
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Unknown Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Environment Test

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Environment Test Service database connection is configured.
Alert Name Environment Test Service Has No Database Connection Configured
Alert Message
The Environment Test Service does not have a database connection configured.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnconfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for Environment Test Service Cannot be Located
Alert Message
The specified database could not be located with the configured connection string.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Environment Test Service currently in use is compatible with the version of the Environment Test Service schema in database. It detects if the schema is newer.
Alert Name Incompatible Version of Environment Test Service
Alert Message
The version of the EnvTest Service currently in use is incompatible with the version of the EnvTest Service schema on the database.  Upgrade the EnvTest Service to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Environment Test Service schema on the database is compatible with the version of the Environment Test Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of Environment Test Service
Alert Message
The version of the EnvTest Service schema on the database is incompatible with the version of the EnvTest Service currently in use.  Upgrade the database schema to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name Environment Test Service Database Schema Upgrade in Progress
Alert Message
A database schema upgrade is in progress.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Environment Test Service Environment Test Interface Probe Status

Display Name Environment Test Service Environment Test Interface Probe Status
Description
Monitors the status of the Environment Test interface for the Environment Test Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix Environment Test Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Environment Test Service Peer Interface Probe Status

Display Name Environment Test Service Peer Interface Probe Status
Description
Monitors the status of the Peer interface for the Environment Test Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name Peer Interface Probe for Citrix Environment Test Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Environment Test Service SDK Interface Probe Status

Display Name Environment Test Service SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Environment Test Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Interface Probe for Citrix Environment Test Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name Environment Test Service Invalid Database Configuration
Alert Message
The expected stored procedures are missing from the database.  This may be because the EnvTest Service schema has not been added to the database.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Login to Database Rejected

Display Name Login to Database Rejected
Description
Monitors if the database logon attempt from the Environment Test Service was successful.
Alert Name Logon attempt from the Environment Test Service Rejected by Database
Alert Message
Database rejected the logon attempt from the EnvTest Service.  This may be because the service attempted to log on with invalid credentials or because a database has not been installed in the specified location.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBRejectedConnection Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Failed State

Display Name Service Failed State
Description
Monitors if the Environment Test Service has failed.
Alert Name Environment Test Service Failed
Alert Message
The EnvTest Service has failed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Failed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Unknown State

Display Name Service Unknown State
Description
Detects if the Environment Test Service status cannot be determined.
Alert Name Environment Test Service Status Unknown
Alert Message
The Service's status cannot be determined.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Environment Test
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Unknown Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Host

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Host Service database connection is configured.
Alert Name Host Service Has No Database Connection Configured
Alert Message
The Host Service does not have a database connection configured.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for Host Service Cannot be Located
Alert Message
The specified database could not be located with the configured connection string.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Host Service currently in use is compatible with the version of the Host Service schema in database. It detects if the schema is newer.
Alert Name Incompatible Version of Host Service
Alert Message
The version of the Host Service currently in use is incompatible with the version of the Host Service schema in database. Upgrade the Host Service to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Host Service schema on the database is compatible with the version of the Host Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of Host Service
Alert Message
The version of the Host Service schema on the database is incompatible with the version of the Host Service currently in use. Upgrade the database schema to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name Host Service Database Schema Upgrade in Progress
Alert Message
A database schema upgrade is currently in progress.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Host Service Environment Test Interface Probe Status

Display Name Host Service Environment Test Interface Probe Status
Description
Monitors the status of the Environment Test interface for the Host Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix Host Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

InterService Interface Probe Status

Display Name InterService Interface Probe Status
Description
Monitors the status of the InterService interface for the Host Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name InterService Interface Probe for Citrix Host Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name Host Service Invalid Database Configuration
Alert Message
The expected stored procedures are missing from the database. This could be because the Host Service schema has not been added to the database.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Login to Database Rejected

Display Name Login to Database Rejected
Description
Monitors if the database logon attempt from the Host Service was successful.
Alert Name Logon Attempt from Host Service Rejected by Database
Alert Message
The database rejected the logon attempt from the Host Service. This could be because the service attempted to log on with invalid credentials or because a database has not been installed in the specified location.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBRejectedConnection Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Peer Interface Probe Status

Display Name Peer Interface Probe Status
Description
Monitors the status of the Peer interface for the Host Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name Peer Interface Probe for Citrix Host Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

SDK Interface Probe Status

Display Name SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Host Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Interface Probe for Citrix Host Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Failed State

Display Name Service Failed State
Description
Monitors if the Host Service has failed.
Alert Name Host Service Failed
Alert Message
The Host Service has failed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Failed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Unknown State

Display Name Service Unknown State
Description
Detects if the Host Service status cannot be determined.
Alert Name Host Service Status Unknown
Alert Message
The Service status cannot be determined.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Host
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Unknown Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Machine Creation

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Machine Creation Service database connection is configured.
Alert Name Machine Creation Service Has No Database Connection Configured
Alert Message
The MachineCreation Service does not have a database connection configured.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for Machine Creation Service Cannot be Located
Alert Message
The specified database could not be located with the configured connection string.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Machine Creation Service currently in use is compatible with the version of the Machine Creation Service schema in database. It detects if the schema is newer.
Alert Name Incompatible Version of Machine Creation Service
Alert Message
The version of the MachineCreation Service currently in use is incompatible with the version of the MachineCreation Service schema in database. Upgrade the MachineCreation Service to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Machine Creation Service schema on the database is compatible with the version of the Machine Creation Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of MachineCreation Service
Alert Message
The version of the MachineCreation Service schema on the database is incompatible with the version of the MachineCreation Service currently in use. Upgrade the database schema to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name Machine Creation Service Database Schema Upgrade in Progress
Alert Message
A database schema upgrade is currently in progress.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name Machine Creation Service Invalid Database Configuration
Alert Message
The expected stored procedures are missing from the database. This could be because the MachineCreation Service schema has not been added to the database.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Login to Database Rejected

Display Name Login to Database Rejected
Description
Monitors if the database logon attempt from the Machine Creation Service was successful.
Alert Name Logon Attempt from Machine Creation Service Rejected by Database
Alert Message
The database rejected the logon attempt from the MachineCreation Service. This could be because the service attempted to log on with invalid credentials or because a database has not been installed in the specified location.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBRejectedConnection Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Machine Creation Service Environment Test Interface Probe Status

Display Name Machine Creation Service Environment Test Interface Probe Status
Description
Monitors the status of the Environment Test interface for the Machine Creation Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix Machine Creation Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Machine Creation Service InterService Interface Probe Status

Display Name Machine Creation Service InterService Interface Probe Status
Description
Monitors the status of the InterService interface for the Machine Creation Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name InterService Interface Probe for Citrix Machine Creation Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

SDK Interface Probe Status

Display Name SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Machine Creation Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Interface Probe for Citrix Machine Creation Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Failed State

Display Name Service Failed State
Description
Monitors if the Machine Creation Service has failed.
Alert Name Machine Creation Service Failed
Alert Message
The MachineCreation Service has failed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Failed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Unknown State

Display Name Service Unknown State
Description
Detects if the Machine Creation Service status cannot be determined.
Alert Name Machine Creation Service Status Unknown
Alert Message
The Service status cannot be determined.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Machine Creation
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Unknown Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Monitor

Citrix Monitor Service Command Interface Probe Status

Display Name Citrix Monitor Service Command Interface Probe Status
Description
Monitors the status of the Command interface for the Citrix Monitor Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name Command Interface Probe for Citrix Monitor Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Monitor
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Citrix Monitor Service Environment Test Interface Probe Status

Display Name Citrix Monitor Service Environment Test Interface Probe Status
Description
Monitors the status of the Environment Test interface for the Citrix Monitor Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix Monitor Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Monitor
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Citrix Monitor Service OData Interface Probe Status

Display Name Citrix Monitor Service OData Interface Probe Status
Description
Monitors the status of the OData interface for the Citrix Monitor Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name OData Interface Probe for Citrix Monitor Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Monitor
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Citrix Monitor Service Peer Interface Probe Status

Display Name Citrix Monitor Service Peer Interface Probe Status
Description
Monitors the status of the Peer interface for the Citrix Monitor Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name Peer Interface Probe for Citrix Monitor Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Monitor
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Citrix Monitor Service SDK Interface Probe Status

Display Name Citrix Monitor Service SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Citrix Monitor Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Interface Probe for Citrix Monitor Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Monitor
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Storefront

Database Not Configured

Display Name Database Not Configured
Description
Monitors if the Storefront Service database connection is configured.
Alert Name Storefront Service Has No Database Connection Configured
Alert Message
The Storefront Service does not have a database connection configured.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBUnconfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Not Found

Display Name Database Not Found
Description
Monitors if the specified database can be located.
Alert Name Specified Database for Storefront Service Cannot be Located
Alert Message
The specified database could not be located with the configured connection string.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNotFound Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (newer) With Service

Display Name Database Schema Incompatible (newer) With Service
Description
Monitors if the version of the Storefront Service currently in use is compatible with the version of the Storefront Service schema in database. It detects if the schema is newer.
Alert Name Incompatible Version of Storefront Service
Alert Message
The version of the Storefront Service currently in use is incompatible with the version of the Storefront Service schema on the database.  Upgrade the Storefront Service to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBNewerVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Incompatible (older) With Service

Display Name Database Schema Incompatible (older) With Service
Description
Monitors if the version of the Storefront Service schema in the database is compatible with the version of the Storefront Service currently in use. It detects if the schema is older.
Alert Name Incompatible Version of Storefront Service
Alert Message
The version of the Storefront Service schema on the database is incompatible with the version of the Storefront Service currently in use.  Upgrade the database schema to a more recent version.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBOlderVersionThanService Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Database Schema Upgrade In Progress

Display Name Database Schema Upgrade In Progress
Description
Monitors if a database schema upgrade is currently in progress.
Alert Name Storefront Service Database Schema Upgrade in Progress
Alert Message
A database schema upgrade is in progress.
          
Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBVersionChangeInProgress Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Invalid Database Configured

Display Name Invalid Database Configured
Description
Monitors if the expected stored procedures exist in the database.
Alert Name Storefront Service Invalid Database Configuration
Alert Message
The expected stored procedures are missing from the database.  This may be because the Storefront Service schema has not been added to the database.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
InvalidDBConfigured Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Login to Database Rejected

Display Name Login to Database Rejected
Description
Monitors if the database logon attempt from the Storefront Service was successful.
Alert Name Logon attempt from the Storefront Service Rejected by Database
Alert Message
The database rejected the logon attempt from the Storefront Service.  This may be because the service attempted to log on with invalid credentials or because a database has not been installed in the specified location.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
DBRejectedConnection Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

SDK Interface Probe Status

Display Name SDK Interface Probe Status
Description
Monitors the status of the SDK interface for the Storefront Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name SDK Interface Probe for Citrix Storefront Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Failed State

Display Name Service Failed State
Description
Monitors if the Storefront Service has failed.
Alert Name Storefront Service Failed
Alert Message
The Storefront Service has failed.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Failed Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Service Unknown State

Display Name Service Unknown State
Description
Detects if the Storefront Service status cannot be determined.
Alert Name Storefront Service Status Unknown
Alert Message
The Service's status cannot be determined.

Host: {0}
Service: {1}

Service Status: {2}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Unknown Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Storefront Service Peer Interface Probe Status

Display Name Storefront Service Peer Interface Probe Status
Description
Monitors the status of the Peer interface for the Storefront Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name Peer Interface Probe for Citrix Storefront Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Storefront Service SDK Interface Probe Status

Display Name Storefront Service SDK Interface Probe Status
Description
Monitors the status of the Environment Test interface for the Storefront Service instance. Possible states are: Responding, NotResponding and BadBindingType.
Alert Name EnvironmentTest Interface Probe for Citrix Storefront Service Not Responding
Alert Message
Host: {0}
Service: {1}
Probe Type: {2}
Probe URL: {3}

Probe Status: {4}
Target XAXD Service Storefront
Enabled by default Yes

Health States
Monitor State Health State
Responding Healthy
Unknown Warning
NotResponding Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Windows

Process Private Memory (in MB)

Display Name Process Private Memory (in MB)
Description
Monitors current XenApp/XenDesktop service memory usage (in MB)
Knowledge Article
Summary

This monitor checks current XenApp/XenDesktop service memory usage (in MB).

High memory consumption may be caused by memory leak. To check memory consumption growth, open Delivery Controller Services Performance view.

Alert Name Process Private Memory Usage High
Alert Message
Process private memory has exceeded the threshold value.

Server name: {0}
Service name: {1} ({2})
Process name: {3}

Value: {4} MB
Target XAXD Service Windows
Enabled by default Yes

Health States
Monitor State Health State
BelowThreshold Healthy
AboveThreshold Warning

Overridable parameters
Parameter Default Value
Threshold 900
IntervalSeconds 300
SyncTime

Top

Process Processor Time

Display Name Process Processor Time
Description
Monitors current XenApp/XenDesktop service processor utilization (in %).
Alert Name Process CPU Utilization High
Alert Message
Process  CPU utilization has exceeded the threshold value.

Server name: {0}
Service name: {1} ({2})
Process name: {3}

Value: {4} %
Target XAXD Service Windows
Enabled by default Yes

Health States
Monitor State Health State
Processor Time High Warning
Processor Time Low Healthy

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Threshold 80
NumSamples 3

Top

XAXD Site

AD Identity Services Status

Display Name AD Identity Services Status
Description
Monitors operational state of AD Identity service on all controllers.
Knowledge Article
Summary

Citrix AD Identity service manages Active Directory Computer Accounts. It takes care of creating new Active Directory computer accounts.

If AD Identity service is not operational on any controller, above mentioned functionality will not be available in XenDesktop. But as long as there is operational AD Identity service on at least one controller, functionality is not broken.

Impact if AD Identity service is not operational on all controllers:

  • New catalog cannot be created if machine type is one of Pooled or Dedicated.

  • Adding new machines with new AD accounts to existing Pooled or Dedicated catalogs is not working.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The monitoring period for checking health state of AD Identity service on all controllers (the default interval is set to 5 minutes).

Resolutions

Check alerts related to non operational AD Identity service on specific controllers. First thing to try is to restart the AD Identity service if there is no obvious cause of the problem (e.g. database connection problem).

Alert Name AD Identity Services Not Operational
Alert Message
{0}

Site: {1}
Target XAXD Site
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Warning Warning
Critical Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Broker Services Status

Display Name Broker Services Status
Description
Monitors operational state of Broker service on all controllers.
Knowledge Article
Summary

Citrix Broker service brokers connections from endpoint devices to desktop and applications.

If Broker service is not operational on any controller, above mentioned functionality will not be available in XenDesktop. But as long as there is operational Broker service on at least one controller, functionality is not broken.

Impact if Broker service is not operational on all controllers:

  • Users cannot connect to desktops.

  • Users cannot connect to applications.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The monitoring period for checking health state of AD Identity service on all controllers (the default interval is set to 5 minutes).

Resolutions

Check alerts related to non operational Broker service on specific controllers. First thing to try is to restart the Broker service if there is no obvious cause of the problem (e.g. database connection problem).

Alert Name Broker Services Not Operational
Alert Message
{0}

Site: {1}
Target XAXD Site
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Warning Warning
Critical Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Configuration Services Status

Display Name Configuration Services Status
Description
Monitors operational state of Configuration service on all controllers.
Knowledge Article
Summary

Citrix Configuration service stores configuration information on Citrix Services.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The monitoring period for checking health state of AD Identity service on all controllers (the default interval is set to 5 minutes).

Resolutions

Check alerts related to non operational Configuration service on specific controllers. First thing to try is to restart the Configuration service if there is no obvious cause of the problem (e.g. database connection problem).

Alert Name Configuration Services Not Operational
Alert Message
{0}

Site: {1}
Target XAXD Site
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Warning Warning
Critical Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Host Services Status

Display Name Host Services Status
Description
Monitors operational state of Host service on all controllers.
Knowledge Article
Summary

Citrix Host service manages hosts and hypervisor connections. It takes part in catalog creation containing virtual machines and starting/stopping virtual machines.

If Host service is not operational on any controller, above mentioned functionality will not be available in XenDesktop. But as long as there is operational Host service on at least one controller, functionality is not broken.

Impact if Host service is not operational on all controllers:

  • New catalog cannot be created if machine type is one of Pooled or Dedicated.

  • Machines from catalogs being of machine type - Pooled, Dedicated or Existing - cannot be started and therefore not available to users.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The monitoring period for checking health state of Host service on all controllers (the default interval is set to 5 minutes).

Resolutions

Check alerts related to non operational Host service on specific controllers. First thing to try is to restart the Host service if there is no obvious cause of the problem (e.g. database connection problem).

Alert Name Host Services Not Operational
Alert Message
{0}

Site: {1}
Target XAXD Site
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Warning Warning
Critical Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Machine Creation Services Status

Display Name Machine Creation Services Status
Description
Monitors operational state of Machine Creation service on all controllers.
Knowledge Article
Summary

Citrix Machine Creation service creates new virtual machines.

If Machine Creation service is not operational on any controller, above mentioned functionality will not be available in XenDesktop. But as long as there is operational Machine Creation service on at least one controller functionality is not broken.

Impact if Machine Creation service is not operational on all controllers:

  • Not possible to create new virtual machines in a catalog (Pooled or Dedicated).

  • Cannot update catalog's (Pooled or Dedicated) master image.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The monitoring period for checking health state of Machine Creation service on all controllers (the default interval is set to 5 minutes).

Resolutions

Check alerts related to non operational Machine Creation service on specific controllers. First thing to try is to restart the Machine Creation service if there is no obvious cause of the problem (e.g. database connection problem).

Alert Name Machine Creation Services Not Operational
Alert Message
{0}

Site: {1}
Target XAXD Site
Enabled by default Yes

Health States
Monitor State Health State
OK Healthy
Warning Warning
Critical Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Site Data Collector

Citrix Management Pack for XenApp and XenDesktop License Validation

Display Name Citrix Management Pack for XenApp and XenDesktop License Validation
Description
Monitors validity of Citrix Management Pack for XenApp and XenDesktop license.
Knowledge Article
Summary

This monitor checks if the license for Citrix Management Pack for XenApp and XenDesktop is valid.

Citrix Management Pack for XenApp and XenDesktop licensing depends on having valid XenApp/XenDesktop Platinum license with valid Subscription Advantage. Monitoring works only on XenApp/XenDesktop Platinum edition sites.

Causes

The monitor generates an alert in any of the following circumstances:

  • XenApp/XenDesktop edition is not Platinum

  • No XenApp/XenDesktop Platinum license can be found.

  • The XenApp/XenDesktop Platinum license has expired.

  • The Subscription Advantage period for XenApp/XenDesktop Platinum license does not cover this version of Citrix Management Pack for XenApp and XenDesktop.

Resolutions

If XenApp/XenDesktop site is not Platinum change it to Platinum. Otherwise make sure there is a valid XenApp/XenDesktop Platinum license with valid Subscription Advantage on the license server.

Alert Name Citrix Management Pack for XenApp and XenDesktop License Validation
Alert Message
Citrix Management Pack for XenApp and XenDesktop has no valid license for site '{0}'.

Reason: {1}

License info
Product: {2}
Edition: {3}
Type: {4}
Expiration date: {5}
SA date: {6}
Required SA date: {7}
Target XAXD Site Data Collector
Enabled by default Yes

Health States
Monitor State Health State
LicenseValid Healthy
LicenseInvalid Critical

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Number of Active Sessions

Display Name Number of Active Sessions
Description
Monitors the number of active XenApp/XenDesktop sessions on a site.
Alert Name Number of Active Sessions
Alert Message
The number of active XenApp/XenDesktop sessions on a site has exceeded the threshold value.

Site: {0}
Active sessions: {1}
Target XAXD Site Data Collector
Enabled by default No

Health States
Monitor State Health State
BelowThreshold Healthy
AboveThreshold Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 1000
Debug false

Top

Number of All Sessions

Display Name Number of All Sessions
Description
Monitors the number of all XenApp/XenDesktop sessions on a site.
Alert Name Number of All Sessions
Alert Message
The number of all  XenApp/XenDesktop sessions on a site has exceeded the threshold value.

Site: {0}
All sessions: {1}
Target XAXD Site Data Collector
Enabled by default No

Health States
Monitor State Health State
BelowThreshold Healthy
AboveThreshold Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 1000
Debug false

Top

Number of Currently Connected Users

Display Name Number of Currently Connected Users
Description
Monitors the number of currently connected users on a site.
Knowledge Article
Summary

This monitor checks the number of currently connected users on a site. Only distinct users having active sessions are counted, while users having disconnected sessions are not.

Alert Name Number of Connected Users
Alert Message
The number of connected users on a site has exceeded the threshold value.

Site: {0}
Connected users: {1}
Target XAXD Site Data Collector
Enabled by default No

Health States
Monitor State Health State
BelowThreshold Healthy
AboveThreshold Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 1000
Debug false

Top

Number of Disconnected Sessions

Display Name Number of Disconnected Sessions
Description
Monitors the number of disconnected XenApp/XenDesktop sessions on a site. 
Alert Name Number of Disconnected Sessions
Alert Message
The number of disconnected  XenApp/XenDesktop sessions on a site has exceeded the threshold value.

Site: {0}
Disconnected sessions: {1}
Target XAXD Site Data Collector
Enabled by default Yes

Health States
Monitor State Health State
BelowThreshold Healthy
AboveThreshold Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Threshold 100
Debug false

Top

XAXD Site Hypervisor Connection

Hypervisor Connection Status

Display Name Hypervisor Connection Status
Description
Monitors hypervisor connection status which can be in following states: On, Unavailable or InMaintenanceMode.
Knowledge Article
Summary

This monitor checks the hypervisor connection status. It can be in one of following states:

  • Unavailable: The broker is unable to contact the hypervisor

  • InMaintenanceMode: The hosting server is in maintenance mode

  • On: The broker is in contact with the hypervisor

Alert Name Hypervisor Connection Not Operational
Alert Message
Hypervisor connection '{0}' is not operational ({1}).

Site: {2}
Target XAXD Site Hypervisor Connection
Enabled by default Yes

Health States
Monitor State Health State
On Healthy
Unavailable Critical
InMaintenanceMode Warning

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top


Rules

Citrix MPXAXD Machine Agent Proxy Computer Role

Desktop OS Session Bandwidth Usage (Alert)

Display Name Desktop OS Session Bandwidth Usage (Alert)
Description
Generates alert if session bandwidth usage is consistently high over multiple consecutive samples.
Knowledge Article
Summary

Helps to identify Desktop OS sessions with high bandwidth usage (traffic from Citrix Receiver to VDA and in opposite direction). High bandwidth usage could be caused by, including but not limited to, printing to a local printer, copying to/from client storage, displaying animations. This can have large impact on all other users working from the same remote office if bandwidth is limited and XenApp/XenDesktop Bandwidth Policy is not set accordingly.

Before enabling this rule set threshold according to your environment expectations.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 3). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to a value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 400 KBps).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • DeliveryGroupName - Name of the delivery group of machine hosting the session.

  • MachineName - Host name of the machine hosting the session.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • HypervisorName - Hostname of the machine’s hypervisor (for virtual machines only).

  • MachineOSType - Identifies the operating system that is running on the machine.

  • User - Name of the user connected to the desktop or application.

  • SessionStart - Date and time value indicating the start time of the session.

  • SessionType - Indicates if this is an Application or Desktop session.

  • SessionState - Indicates the state of the session.

  • SessionKey - Citrix unique identifier for this session.

  • CPU - CPU utilization of Desktop OS machine.

  • PhysicalMem/PhysicalMemUtil - Values indicating physical memory usage, in MB and percentage.

  • VirtualMem/VirtualMemUtil - Values indicating virtual memory usage, in MB and percentage.

  • PageFaultsPerSec - Memory hard page faults per second for Desktop OS machine.

  • NetworkReceive/NetworkSend – Desktop OS machine’s network receive/send values in KBps.

  • NetworkTraffic - Desktop OS machine’s network bandwidth consumption (send and receive) in KBps.

  • DiskIOPS - Rate of read and write operations on disk per second.

  • DiskRead/DiskWrite - Disk read/write values in KBps.

  • DiskQueue - Disk queue length.

  • DiskLatency - Disk latency in milliseconds.

  • SessionInput – Citrix session input bandwidth used (KBps). It includes all session traffic from Citrix Receiver to VDA machine.

  • SessionOutput – Citrix session output bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver.

  • SessionBandwidthUsage – Citrix session bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver and in opposite direction.

  • SessionLatency – Network latency detected between the Citrix Receiver and the VDA machine (ms).

  • SessionRTT – ICA Round Trip Time (ms). The time interval measured at the client between the first step (user action) and the last step (graphical response displayed).

  • Applications – List of application in use.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default No
Category Alert
Generate Alert True
Alert Name Desktop OS Session Bandwidth Usage
Alert Message
Session bandwidth usage on {0} machine is above the threshold for several consecutive samples.

Bandwidth usage: {1} KBps

User: {2} 
Session type: {3} 
Site: {4} 
Delivery group: {5} 
Hypervisor hostname: {6} 
Application: {7} 

For more information about session see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 400
ConsolidationInterval 660
NumberOfSamples 3
Priority 1
Severity 1

Top

Desktop OS Session CPU Utilization (Alert)

Display Name Desktop OS Session CPU Utilization (Alert)
Description
Generates alert if CPU utilization on Desktop OS session is consistently high over multiple consecutive samples.
Knowledge Article
Summary

Helps to identify Desktop OS sessions that host CPU hungry applications/processes.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 3). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to a value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 80 percent).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Resolutions

Troubleshooting

Identify the processes/services consuming processor time using Citrix Director (Alert Task: Start Citrix Director) or Task Manager/Resource Monitor locally on the machine.

  • If all processes/services work within normal parameters and the level of CPU consumption is as expected,, consider adding additional CPU resources to this system in the future.

  • If a process/service that works outside normal parameters can be identified, the process should be killed. Please note that killing a process can cause unsaved data to be lost.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • DeliveryGroupName - Name of the delivery group of machine hosting the session.

  • MachineName - Host name of the machine hosting the session.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • HypervisorName - Hostname of the machine’s hypervisor (for virtual machines only).

  • MachineOSType - Identifies the operating system that is running on the machine.

  • User - Name of the user connected to the desktop or application.

  • SessionStart - Date and time value indicating the start time of the session.

  • SessionType - Indicates if this is an Application or Desktop session.

  • SessionState - Indicates the state of the session.

  • SessionKey - Citrix unique identifier for this session.

  • CPU - CPU utilization of Desktop OS machine.

  • PhysicalMem/PhysicalMemUtil - Values indicating physical memory usage, in MB and percentage.

  • VirtualMem/VirtualMemUtil - Values indicating virtual memory usage, in MB and percentage.

  • PageFaultsPerSec - Memory hard page faults per second for Desktop OS machine.

  • NetworkReceive/NetworkSend – Desktop OS machine’s network receive/send values in KBps.

  • NetworkTraffic - Desktop OS machine’s network bandwidth consumption (send and receive) in KBps.

  • DiskIOPS - Rate of read and write operations on disk per second.

  • DiskRead/DiskWrite - Disk read/write values in KBps.

  • DiskQueue - Disk queue length.

  • DiskLatency - Disk latency in milliseconds.

  • SessionInput – Citrix session input bandwidth used (KBps). It includes all session traffic from Citrix Receiver to VDA machine.

  • SessionOutput – Citrix session output bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver.

  • SessionBandwidthUsage – Citrix session bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver and in opposite direction.

  • SessionLatency – Network latency detected between the Citrix Receiver and the VDA machine (ms).

  • SessionRTT – ICA Round Trip Time (ms). The time interval measured at the client between the first step (user action) and the last step (graphical response displayed).

  • Applications – List of application in use.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Desktop OS Session CPU Utilization
Alert Message
CPU utilization of a Desktop OS session on {0} machine is above the threshold for several consecutive samples.

CPU utilization: {1} %

User: {2} 
Session type: {3} 
Site: {4} 
Delivery group: {5} 
Hypervisor hostname: {6} 
Application: {7} 

For more information about session see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 80
ConsolidationInterval 660
NumberOfSamples 3
Priority 1
Severity 1

Top

Desktop OS Session Disk Latency (Alert)

Display Name Desktop OS Session Disk Latency (Alert)
Description
Generates alert if disk transfer (reads and writes) latency is consistently high over multiple consecutive samples.
Knowledge Article
Summary

High disk read and write latency (Avg. Disk sec/Transfer) indicates a disk performance bottleneck. The physical disk, and possibly even overall system performance, may significantly diminish, which will result in poor operating system and application performance.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 4). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to a value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 20 miliseconds).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Resolutions

Troubleshooting

Identify the processes/services consuming disk time using Task Manager/Resource Monitor:

  • If all processes/services work within normal parameters and the level of disk consumption is as expected, consider upgrading to a more capable disk subsystem in the future.

  • If a process/service that works outside normal parameters can be identified, the process should be killed. Please note that killing a process can cause unsaved data to be lost.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • DeliveryGroupName - Name of the delivery group of machine hosting the session.

  • MachineName - Host name of the machine hosting the session.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • HypervisorName - Hostname of the machine’s hypervisor (for virtual machines only).

  • MachineOSType - Identifies the operating system that is running on the machine.

  • User - Name of the user connected to the desktop or application.

  • SessionStart - Date and time value indicating the start time of the session.

  • SessionType - Indicates if this is an Application or Desktop session.

  • SessionState - Indicates the state of the session.

  • SessionKey - Citrix unique identifier for this session.

  • CPU - CPU utilization of Desktop OS machine.

  • PhysicalMem/PhysicalMemUtil - Values indicating physical memory usage, in MB and percentage.

  • VirtualMem/VirtualMemUtil - Values indicating virtual memory usage, in MB and percentage.

  • PageFaultsPerSec - Memory hard page faults per second for Desktop OS machine.

  • NetworkReceive/NetworkSend – Desktop OS machine’s network receive/send values in KBps.

  • NetworkTraffic - Desktop OS machine’s network bandwidth consumption (send and receive) in KBps.

  • DiskIOPS - Rate of read and write operations on disk per second.

  • DiskRead/DiskWrite - Disk read/write values in KBps.

  • DiskQueue - Disk queue length.

  • DiskLatency - Disk latency in milliseconds.

  • SessionInput – Citrix session input bandwidth used (KBps). It includes all session traffic from Citrix Receiver to VDA machine.

  • SessionOutput – Citrix session output bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver.

  • SessionBandwidthUsage – Citrix session bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver and in opposite direction.

  • SessionLatency – Network latency detected between the Citrix Receiver and the VDA machine (ms).

  • SessionRTT – ICA Round Trip Time (ms). The time interval measured at the client between the first step (user action) and the last step (graphical response displayed).

  • Applications – List of application in use.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Desktop OS Session Disk Latency
Alert Message
Disk latency of Desktop OS session on {0} machine is above the threshold for several consecutive samples.

Disk latency: {1} ms

User: {2} 
Session type: {3} 
Site: {4} 
Delivery group: {5} 
Hypervisor hostname: {6} 
Application: {7} 

For more information about session see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 20
ConsolidationInterval 990
NumberOfSamples 4
Priority 1
Severity 1

Top

Desktop OS Session Memory Hard Page Faults (Alert)

Display Name Desktop OS Session Memory Hard Page Faults (Alert)
Description
Generates alert if memory page hard faults (per second) on Desktop OS session is consistently high over multiple consecutive samples.
Knowledge Article
Summary

Memory page faults per second is the rate at which pages are read from or written to disk to resolve hard page faults.

High value typically indicates a memory bottleneck. In case there is still plenty of RAM available, an application is probably sequentially reading a file from memory. Please refer to KB139609 for further information.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 3). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to a value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 20).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • DeliveryGroupName - Name of the delivery group of machine hosting the session.

  • MachineName - Host name of the machine hosting the session.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • HypervisorName - Hostname of the machine’s hypervisor (for virtual machines only).

  • MachineOSType - Identifies the operating system that is running on the machine.

  • User - Name of the user connected to the desktop or application.

  • SessionStart - Date and time value indicating the start time of the session.

  • SessionType - Indicates if this is an Application or Desktop session.

  • SessionState - Indicates the state of the session.

  • SessionKey - Citrix unique identifier for this session.

  • CPU - CPU utilization of Desktop OS machine.

  • PhysicalMem/PhysicalMemUtil - Values indicating physical memory usage, in MB and percentage.

  • VirtualMem/VirtualMemUtil - Values indicating virtual memory usage, in MB and percentage.

  • PageFaultsPerSec - Memory hard page faults per second for Desktop OS machine.

  • NetworkReceive/NetworkSend – Desktop OS machine’s network receive/send values in KBps.

  • NetworkTraffic - Desktop OS machine’s network bandwidth consumption (send and receive) in KBps.

  • DiskIOPS - Rate of read and write operations on disk per second.

  • DiskRead/DiskWrite - Disk read/write values in KBps.

  • DiskQueue - Disk queue length.

  • DiskLatency - Disk latency in milliseconds.

  • SessionInput – Citrix session input bandwidth used (KBps). It includes all session traffic from Citrix Receiver to VDA machine.

  • SessionOutput – Citrix session output bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver.

  • SessionBandwidthUsage – Citrix session bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver and in opposite direction.

  • SessionLatency – Network latency detected between the Citrix Receiver and the VDA machine (ms).

  • SessionRTT – ICA Round Trip Time (ms). The time interval measured at the client between the first step (user action) and the last step (graphical response displayed).

  • Applications – List of application in use.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Desktop OS Session Memory Hard Page Faults
Alert Message
Memory hard page faults rate of Desktop OS session on {0} machine is above the threshold for several consecutive samples.

Memory hard page faults rate: {1} pages/second

User: {2} 
Session type: {3} 
Site: {4} 
Delivery group: {5} 
Hypervisor hostname: {6} 
Application: {7} 

For more information about session see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 20
ConsolidationInterval 660
NumberOfSamples 3
Priority 1
Severity 1

Top

Desktop OS Session Physical Memory Utilization (Alert)

Display Name Desktop OS Session Physical Memory Utilization (Alert)
Description
Generates alert if physical memory utilization on Desktop OS machine is high.
Knowledge Article
Summary

Helps to identify Desktop OS sessions that host memory hungry applications/processes.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 3). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to a value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 80 percent).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Resolutions

Troubleshooting

Identify the processes/services consuming memory using Citrix Director (Alert Task: Start Citrix Director) or Task Manager or Resource Monitor locally on the machine.

  • If all processes/services work within normal parameters and the level of memory consumption is as expected, consider adding additional memory to this system in the future.

  • If a process/service that works outside normal parameters can be identified, the process should be killed. Please note that killing a process can cause unsaved data to be lost.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • DeliveryGroupName - Name of the delivery group of machine hosting the session.

  • MachineName - Host name of the machine hosting the session.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • HypervisorName - Hostname of the machine’s hypervisor (for virtual machines only).

  • MachineOSType - Identifies the operating system that is running on the machine.

  • User - Name of the user connected to the desktop or application.

  • SessionStart - Date and time value indicating the start time of the session.

  • SessionType - Indicates if this is an Application or Desktop session.

  • SessionState - Indicates the state of the session.

  • SessionKey - Citrix unique identifier for this session.

  • CPU - CPU utilization of Desktop OS machine.

  • PhysicalMem/PhysicalMemUtil - Values indicating physical memory usage, in MB and percentage.

  • VirtualMem/VirtualMemUtil - Values indicating virtual memory usage, in MB and percentage.

  • PageFaultsPerSec - Memory hard page faults per second for Desktop OS machine.

  • NetworkReceive/NetworkSend – Desktop OS machine’s network receive/send values in KBps.

  • NetworkTraffic - Desktop OS machine’s network bandwidth consumption (send and receive) in KBps.

  • DiskIOPS - Rate of read and write operations on disk per second.

  • DiskRead/DiskWrite - Disk read/write values in KBps.

  • DiskQueue - Disk queue length.

  • DiskLatency - Disk latency in milliseconds.

  • SessionInput – Citrix session input bandwidth used (KBps). It includes all session traffic from Citrix Receiver to VDA machine.

  • SessionOutput – Citrix session output bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver.

  • SessionBandwidthUsage – Citrix session bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver and in opposite direction.

  • SessionLatency – Network latency detected between the Citrix Receiver and the VDA machine (ms).

  • SessionRTT – ICA Round Trip Time (ms). The time interval measured at the client between the first step (user action) and the last step (graphical response displayed).

  • Applications – List of application in use.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Desktop OS Session Physical Memory Utilization
Alert Message
Physical memory utilization of Desktop OS session on {0} machine is above the threshold for several consecutive samples.

Physical memory utilization: {1} %

User: {2} 
Session type: {3} 
Site: {4} 
Delivery group: {5} 
Hypervisor hostname: {6} 
Application: {7} 

For more information about session see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 80
ConsolidationInterval 660
NumberOfSamples 3
Priority 1
Severity 1

Top

Server OS Machine CPU Utilization (Alert)

Display Name Server OS Machine CPU Utilization (Alert)
Description
Generates alert if CPU utilization on Server OS machine is consistently high over multiple consecutive samples.
Knowledge Article
Summary

High CPU utilization might be caused by machine having too many sessions or one or more sessions might consume too much CPU.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 3). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 80 percent.).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Resolutions

Troubleshooting

Identify the processes/services consuming processor time using Task Manager or Resource Monitor.

  • If all processes/services work within normal parameters and the level of CPU consumption is as expected,, consider adding additional CPU resources to this system in the future.

  • If a process/service that works outside normal parameters can be identified, the process should be killed. Please note that killing a process can cause unsaved data to be lost.

Additional

In addition to alert description some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • MachineName - Host name of the machine.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • DeliveryGroupName - Name of the delivery group.

  • HypervisorName - Domain name of the hypervisor. Parameter is empty if server is a physical machine.

  • MachineOSType - Identifies the operating system that is running on the machine.

  • CPU - Value indicating CPU utilization.

  • PhysicalMem/PhysicalMemUtil - Values indicating physical memory usage, in MB and percentage.

  • VirtualMem/VirtualMemUtil - Values indicating virtual memory usage, in MB and percentage.

  • PageFaultsPerSec - Memory hard page faults per second for current machine.

  • NetworkReceive/NetworkSend - Network receive/send values in KBps.

  • NetworkTraffic - Network bandwidth consumption (send and receive) in KBps.

  • DiskRead/DiskWrite - Disk read/write values in KBps.

  • DiskQueue - Disk queue length.

  • DiskLatency - Disk latency in milliseconds.

  • DiskIOPS - Rate of read and write operations on disk per second.

  • SessionLatency - Average Citrix session latency for all active sessions on machine (ms).

  • SessionRTT - Average Citrix session ICA Round Trip Time (RTT) for all active sessions on machine (ms).

  • Load - Citrix Load Index in percentage.

  • SessionCount - Number of all sessions on current machine.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Server OS Machine CPU Utilization
Alert Message
CPU utilization on {0} machine is above the threshold for several consecutive samples.

CPU utilization: {1} %

Number of sessions: {2}
Site: {3} 
Delivery group: {4} 
Hypervisor hostname: {5} 

For more information about machine see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 80
ConsolidationInterval 660
NumberOfSamples 3
Priority 1
Severity 1

Top

Server OS Machine Disk Latency (Alert)

Display Name Server OS Machine Disk Latency (Alert)
Description
Generates alert if disk transfer (reads and writes) latency is consistently high over multiple consecutive samples.
Knowledge Article
Summary

High disk read and write latency (Avg. Disk sec/Transfer) indicates a disk performance bottleneck. The physical disk, and possibly even overall system performance, may significantly diminish, which will result in poor operating system and application performance.

The Avg. Disk sec/Transfer counter measures the average time of data reads and writes on all physical disks.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 4). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 20 ms.).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Resolutions

Troubleshooting

Identify the processes / services consuming disk time using Task Manager or Resource Monitor.

  • If all processes/services work within normal parameters and the level of disk consumption is as expected, consider upgrading to a more capable disk subsystem in the future.

  • If a process/service that works outside normal parameters can be identified, the process should be killed. Please note that killing a process can cause unsaved data to be lost.

Additional

In addition to alert description some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • MachineName - Host name of the machine.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • DeliveryGroupName - Name of the delivery group.

  • HypervisorName - Domain name of the hypervisor. Parameter is empty if server is a physical machine.

  • MachineOSType - Identifies the operating system that is running on the machine.

  • CPU - Value indicating CPU utilization.

  • PhysicalMem/PhysicalMemUtil - Values indicating physical memory usage, in MB and percentage.

  • VirtualMem/VirtualMemUtil - Values indicating virtual memory usage, in MB and percentage.

  • PageFaultsPerSec - Memory hard page faults per second for current machine.

  • NetworkReceive/NetworkSend - Network receive/send values in KBps.

  • NetworkTraffic - Network bandwidth consumption (send and receive) in KBps.

  • DiskRead/DiskWrite - Disk read/write values in KBps.

  • DiskQueue - Disk queue length.

  • DiskLatency - Disk latency in milliseconds.

  • DiskIOPS - Rate of read and write operations on disk per second.

  • SessionLatency - Average Citrix session latency for all active sessions on machine (ms).

  • SessionRTT - Average Citrix session ICA Round Trip Time (RTT) for all active sessions on machine (ms).

  • Load - Citrix Load Index in percentage.

  • SessionCount - Number of all sessions on current machine.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Server OS Machine Disk Latency
Alert Message
Disk latency on {0} machine is above the threshold for several consecutive samples.

Disk latency: {1} ms.

Number of sessions: {2}
Site: {3} 
Delivery group: {4} 
Hypervisor hostname: {5} 

For more information about machine see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 20
ConsolidationInterval 990
NumberOfSamples 4
Priority 1
Severity 1

Top

Server OS Machine Memory Hard Page Faults (Alert)

Display Name Server OS Machine Memory Hard Page Faults (Alert)
Description
Generates alert if memory page hard faults (per second) on Server OS machine is consistently high over multiple consecutive samples.
Knowledge Article
Summary

Memory page faults per second is the rate at which pages are read from or written to disk to resolve hard page faults.

High value typically indicates a memory bottleneck. In case there is still plenty of RAM available, an application is probably sequentially reading a file from memory. Please refer to KB139609 for further information.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 3). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 20 faults per second).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Additional

In addition to alert description some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • MachineName - Host name of the machine.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • DeliveryGroupName - Name of the delivery group.

  • HypervisorName - Domain name of the hypervisor. Parameter is empty if server is a physical machine.

  • MachineOSType - Identifies the operating system that is running on the machine.

  • CPU - Value indicating CPU utilization.

  • PhysicalMem/PhysicalMemUtil - Values indicating physical memory usage, in MB and percentage.

  • VirtualMem/VirtualMemUtil - Values indicating virtual memory usage, in MB and percentage.

  • PageFaultsPerSec - Memory hard page faults per second for current machine.

  • NetworkReceive/NetworkSend - Network receive/send values in KBps.

  • NetworkTraffic - Network bandwidth consumption (send and receive) in KBps.

  • DiskRead/DiskWrite - Disk read/write values in KBps.

  • DiskQueue - Disk queue length.

  • DiskLatency - Disk latency in milliseconds.

  • DiskIOPS - Rate of read and write operations on disk per second.

  • SessionLatency - Average Citrix session latency for all active sessions on machine (ms).

  • SessionRTT - Average Citrix session ICA Round Trip Time (RTT) for all active sessions on machine (ms).

  • Load - Citrix Load Index in percentage.

  • SessionCount - Number of all sessions on current machine.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Server OS Machine Memory Hard Page Faults
Alert Message
Memory hard page faults rate on {0} machine is above the threshold for several consecutive samples.

Memory hard page faults rate: {1} pages/second

Number of sessions: {2}
Site: {3} 
Delivery group: {4} 
Hypervisor hostname: {5} 

For more information about machine see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 20
ConsolidationInterval 660
NumberOfSamples 3
Priority 1
Severity 1

Top

Server OS Machine Network Traffic (Alert)

Display Name Server OS Machine Network Traffic (Alert)
Description
Generates alert if network traffic (send and receive) is consistently high over multiple consecutive samples.
Knowledge Article
Summary

This rule alerts on network traffic across all network interfaces on Server OS machines.

Before enabling this rule threshold must be set according to bandwidth available on Server OS machines. This could be 65% of available bandwidth.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 4). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to a value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 80 MB.).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Resolutions

Troubleshooting

Identify the processes / services consuming network using Task Manager or Resource Monitor.

  • If all processes/services work within normal parameters and the level of bandwidth consumption is as expected, considere moving the respective process/service to a dedicated NIC (or team of NICs).

  • If a process/service that works outside normal parameters can be identified, the process should be killed. Please note that killing a process can cause unsaved data to be lost.

Additional

In addition to alert description some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • MachineName - Host name of the machine.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • DeliveryGroupName - Name of the delivery group.

  • HypervisorName - Domain name of the hypervisor. Parameter is empty if server is a physical machine.

  • MachineOSType - Identifies the operating system that is running on the machine.

  • CPU - Value indicating CPU utilization.

  • PhysicalMem/PhysicalMemUtil - Values indicating physical memory usage, in MB and percentage.

  • VirtualMem/VirtualMemUtil - Values indicating virtual memory usage, in MB and percentage.

  • PageFaultsPerSec - Memory hard page faults per second for current machine.

  • NetworkReceive/NetworkSend - Network receive/send values in KBps.

  • NetworkTraffic - Network bandwidth consumption (send and receive) in KBps.

  • DiskRead/DiskWrite - Disk read/write values in KBps.

  • DiskQueue - Disk queue length.

  • DiskLatency - Disk latency in milliseconds.

  • DiskIOPS - Rate of read and write operations on disk per second.

  • SessionLatency - Average Citrix session latency for all active sessions on machine (ms).

  • SessionRTT - Average Citrix session ICA Round Trip Time (RTT) for all active sessions on machine (ms).

  • Load - Citrix Load Index in percentage.

  • SessionCount - Number of all sessions on current machine.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default No
Category Alert
Generate Alert True
Alert Name Server OS Machine Network Traffic
Alert Message
Network traffic on {0} machine is above the threshold for several consecutive samples.

Network traffic: {1} KBps

Number of sessions: {2}
Site: {3} 
Delivery group: {4} 
Hypervisor hostname: {5} 

For more information about machine see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 80
ConsolidationInterval 990
NumberOfSamples 4
Priority 1
Severity 1

Top

Server OS Machine Physical Memory Utilization (Alert)

Display Name Server OS Machine Physical Memory Utilization (Alert)
Description
Generates alert if physical memory utilization on Server OS machine is high.
Knowledge Article
Summary

High physical memory usage might be caused by machine having too many sessions or one or more sessions might consume too much memory.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 3). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to a value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 80 percent.).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Resolutions

Troubleshooting

Identify the processes/services consuming memory using Task Manager or Resource Monitor.

  • If all processes/services work within normal parameters and the level of memory consumption is as expected, consider adding additional memory to this system in the future.

  • If a process/service that works outside normal parameters can be identified, the process should be killed. Please note that killing a process can cause unsaved data to be lost.

Additional

In addition to alert description some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • MachineName - Host name of the machine.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • DeliveryGroupName - Name of the delivery group.

  • HypervisorName - Domain name of the hypervisor. Parameter is empty if server is a physical machine.

  • MachineOSType - Identifies the operating system that is running on the machine.

  • CPU - Value indicating CPU utilization.

  • PhysicalMem/PhysicalMemUtil - Values indicating physical memory usage, in MB and percentage.

  • VirtualMem/VirtualMemUtil - Values indicating virtual memory usage, in MB and percentage.

  • PageFaultsPerSec - Memory hard page faults per second for current machine.

  • NetworkReceive/NetworkSend - Network receive/send values in KBps.

  • NetworkTraffic - Network bandwidth consumption (send and receive) in KBps.

  • DiskRead/DiskWrite - Disk read/write values in KBps.

  • DiskQueue - Disk queue length.

  • DiskLatency - Disk latency in milliseconds.

  • DiskIOPS - Rate of read and write operations on disk per second.

  • SessionLatency - Average Citrix session latency for all active sessions on machine (ms).

  • SessionRTT - Average Citrix session ICA Round Trip Time (RTT) for all active sessions on machine (ms).

  • Load - Citrix Load Index in percentage.

  • SessionCount - Number of all sessions on current machine.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Server OS Machine Physical Memory Utilization
Alert Message
Physical memory utilization on {0} machine is above the threshold for several consecutive samples.

Physical memory utilization: {1} %

Number of sessions: {2}
Site: {3} 
Delivery group: {4} 
Hypervisor hostname: {5} 

For more information about machine see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 80
ConsolidationInterval 660
NumberOfSamples 3
Priority 1
Severity 1

Top

Server OS Session Bandwidth Usage (Alert)

Display Name Server OS Session Bandwidth Usage (Alert)
Description
Generates alert if session bandwidth usage is consistently high over multiple consecutive samples.
Knowledge Article
Summary

Helps to identify Server OS sessions with high bandwidth usage (traffic from Citrix Receiver to VDA and in opposite direction). High bandwidth usage could be caused by, including but not limited to, printing to a local printer, copying to/from client storage, displaying animations. This can have large impact on all other users working from the same remote office if bandwidth is limited and XenApp/XenDesktop Bandwidth Policy is not set accordingly.

Before enabling this rule set threshold according to your environment expectations.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 4). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to a value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 400 KBps).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • DeliveryGroupName - Name of the delivery group of machine hosting the session.

  • MachineName - Host name of the machine hosting the session.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • HypervisorName - Hostname of the machine’s hypervisor (for virtual machines only).

  • MachineOSType - Identifies the operating system that is running on the machine.

  • User - Name of the user connected to the desktop or application.

  • SessionStart - Date and time value indicating the start time of the session.

  • SessionType - Indicates if this is an Application or Desktop session.

  • SessionState - Indicates the state of the session.

  • SessionKey - Citrix unique identifier for this session.

  • SessionId - Windows session ID.

  • CPU - CPU utilization of Desktop OS machine.

  • PhysicalMem - Values indicating physical memory usage in MB.

  • VirtualMem - Values indicating virtual memory usage in MB.

  • SessionInput – Citrix session input bandwidth used (KBps). It includes all session traffic from Citrix Receiver to VDA machine.

  • SessionOutput – Citrix session output bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver.

  • SessionBandwidthUsage – Citrix session bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver and in opposite direction.

  • SessionLatency – Network latency detected between the Citrix Receiver and the VDA machine (ms).

  • SessionRTT – ICA Round Trip Time (ms). The time interval measured at the client between the first step (user action) and the last step (graphical response displayed).

  • Applications – List of application in use.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default No
Category Alert
Generate Alert True
Alert Name Server OS Session Bandwidth Usage
Alert Message
Session bandwidth usage on {0} machine is above the threshold for several consecutive samples.

Bandwidth usage: {1} KBps

User: {2} 
Session ID: {3}
Session type: {4}
Site: {5} 
Delivery group: {6} 
Hypervisor hostname: {7} 
Applications: {8} 

For more information about session see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 400
ConsolidationInterval 990
NumberOfSamples 4
Priority 1
Severity 1

Top

Server OS Session CPU Utilization (Alert)

Display Name Server OS Session CPU Utilization (Alert)
Description
Generates alert if CPU utilization on Server OS session is consistently high over multiple consecutive samples.
Knowledge Article
Summary

Helps to identify Server OS sessions that host CPU hungry applications/processes.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 3). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to a value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 80 percent).

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • DeliveryGroupName - Name of the delivery group of machine hosting the session.

  • MachineName - Host name of the machine hosting the session.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • HypervisorName - Hostname of the machine’s hypervisor (for virtual machines only).

  • MachineOSType - Identifies the operating system that is running on the machine.

  • User - Name of the user connected to the desktop or application.

  • SessionStart - Date and time value indicating the start time of the session.

  • SessionType - Indicates if this is an Application or Desktop session.

  • SessionState - Indicates the state of the session.

  • SessionKey - Citrix unique identifier for this session.

  • SessionId - Windows session ID.

  • CPU - CPU utilization of Desktop OS machine.

  • PhysicalMem - Values indicating physical memory usage in MB.

  • VirtualMem - Values indicating virtual memory usage in MB.

  • SessionInput – Citrix session input bandwidth used (KBps). It includes all session traffic from Citrix Receiver to VDA machine.

  • SessionOutput – Citrix session output bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver.

  • SessionBandwidthUsage – Citrix session bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver and in opposite direction.

  • SessionLatency – Network latency detected between the Citrix Receiver and the VDA machine (ms).

  • SessionRTT – ICA Round Trip Time (ms). The time interval measured at the client between the first step (user action) and the last step (graphical response displayed).

  • Applications – List of application in use.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Server OS Session CPU Utilization
Alert Message
CPU utilization of a Server OS session on {0} machine is above the threshold for several consecutive samples.

CPU utilization: {1} %

User: {2} 
Session ID: {3}
Session type: {4}
Site: {5} 
Delivery group: {6} 
Hypervisor hostname: {7} 
Applications: {8} 

For more information about session see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 80
ConsolidationInterval 660
NumberOfSamples 3
Priority 1
Severity 1

Top

Server OS Session Physical Memory Usage (Alert)

Display Name Server OS Session Physical Memory Usage (Alert)
Description
Generates alert if physical memory usage on Server OS session is high.
Knowledge Article
Summary

Helps to identify Server OS sessions that host memory hungry applications/processes.

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds). In general this parameter should not be changed. To achieve alert to be triggered after different time than default, update NumberOfSamples parameter.

NumberOfSamples

The number of event occurrences before alert will be triggered (the default value is set to 3). For example, if alert must be triggered after 15 minutes, set it to 3 and set it to 4 if it must be triggered after 20 minutes. NumberOfSamples must not be set to a value less than 2.

Threshold

The value that defines the threshold to be used in the comparison (the default value is set to 4096 MB). Please make sure to override this value according to your environment before enabling the rule.

ConsolidationInterval

This value must be always set based on NumberOfSamples and IntervalSeconds parameters. Please see the formula below.

Debug

Used for troubleshooting (the default value is set to false).

Formula for ConsolidationInterval:

ConsolidationInterval = ((NumberOfSamples - 1) * IntervalSeconds ) * 1.1

Example for monitor to generate alert only when monitored value is above threshold for 20 minutes (4 consecutive samples):

IntervalSeconds = 300 (5 minutes) NumberOfSamples = 4 ( 20 minutes / 5 minutes = 4) ConsolidationInterval = ((4 - 1) * 300) * 1.1 = 990

Resolutions

Troubleshooting

Identify the processes/services consuming memory using Citrix Director (Alert Task: Start Citrix Director) or Task Manager or Resource Monitor locally on the machine.

  • If all processes/services work within normal parameters and the level of memory consumption is as expected,consider adding additional memory to this system in the future.

  • If a process/service that works outside normal parameters can be identified, the process should be killed. Please note that killing a process can cause unsaved data to be lost.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • DateTime - Date and time when the data was gathered.

  • SiteName - Name of the site.

  • DeliveryGroupName - Name of the delivery group of machine hosting the session.

  • MachineName - Host name of the machine hosting the session.

  • VDAVersion - Version of the Citrix Virtual Delivery Agent (VDA) installed on the machine.

  • HypervisorName - Hostname of the machine’s hypervisor (for virtual machines only).

  • MachineOSType - Identifies the operating system that is running on the machine.

  • User - Name of the user connected to the desktop or application.

  • SessionStart - Date and time value indicating the start time of the session.

  • SessionType - Indicates if this is an Application or Desktop session.

  • SessionState - Indicates the state of the session.

  • SessionKey - Citrix unique identifier for this session.

  • SessionId - Windows session ID.

  • CPU - CPU utilization of Desktop OS machine.

  • PhysicalMem - Values indicating physical memory usage in MB.

  • VirtualMem - Values indicating virtual memory usage in MB.

  • SessionInput – Citrix session input bandwidth used (KBps). It includes all session traffic from Citrix Receiver to VDA machine.

  • SessionOutput – Citrix session output bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver.

  • SessionBandwidthUsage – Citrix session bandwidth used (KBps). It includes all the session traffic from VDA machine to Citrix Receiver and in opposite direction.

  • SessionLatency – Network latency detected between the Citrix Receiver and the VDA machine (ms).

  • SessionRTT – ICA Round Trip Time (ms). The time interval measured at the client between the first step (user action) and the last step (graphical response displayed).

  • Applications – List of application in use.

Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default No
Category Alert
Generate Alert True
Alert Name Server OS Session Physical Memory Usage
Alert Message
Physical memory usage of Server OS Session on {0} machine is above the threshold for several consecutive samples.

Physical memory usage: {1} MB

User: {2} 
Session ID: {3}
Session type: {4}
Site: {5} 
Delivery group: {6} 
Hypervisor hostname: {7} 
Applications: {8} 

For more information about session see Alert Context section.

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
Threshold 4096
ConsolidationInterval 660
NumberOfSamples 3
Priority 1
Severity 1

Top

Publish Server OS Machine Performance (1) (Performance DW)

Display Name Publish Server OS Machine Performance (1) (Performance DW)
Description
Collects Server OS machine performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
Debug false
IntervalSeconds 300
SyncTime 00:01

Top

Publish Server OS Machine Performance (2) (Performance DW)

Display Name Publish Server OS Machine Performance (2) (Performance DW)
Description
Collects Server OS machine performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
Debug false
IntervalSeconds 300
SyncTime 00:01

Top

Publish Server OS Machine Performance (3) (Performance DW)

Display Name Publish Server OS Machine Performance (3) (Performance DW)
Description
Collects Server OS machine performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
Debug false
IntervalSeconds 300
SyncTime 00:01

Top

Publish Session Performance (1) (Performance DW)

Display Name Publish Session Performance (1) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (10) (Performance DW)

Display Name Publish Session Performance (10) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (11) (Performance DW)

Display Name Publish Session Performance (11) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (12) (Performance DW)

Display Name Publish Session Performance (12) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (2) (Performance DW)

Display Name Publish Session Performance (2) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (3) (Performance DW)

Display Name Publish Session Performance (3) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (4) (Performance DW)

Display Name Publish Session Performance (4) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (5) (Performance DW)

Display Name Publish Session Performance (5) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (6) (Performance DW)

Display Name Publish Session Performance (6) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (7) (Performance DW)

Display Name Publish Session Performance (7) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (8) (Performance DW)

Display Name Publish Session Performance (8) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

Publish Session Performance (9) (Performance DW)

Display Name Publish Session Performance (9) (Performance DW)
Description
Collects Server OS and Desktop OS session performance data and stores it to Data Warehouse.

Note: All instances of this rule must be either enabled or disabled.
Target Citrix MPXAXD Machine Agent Proxy Computer Role
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime 00:02

Top

XAXD Delivery Controller

Delivery Controller License Warning (Alert)

Display Name Delivery Controller License Warning (Alert)
Description
Generates alerts for the following Citrix XenApp/XenDesktop licensing event messages:
1154 - This controller has entered the licensing grace period.
Target XAXD Delivery Controller
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Delivery Controller Event Log License Errors (Warning)
Alert Message
{0}

Delivery Controller: {1}
Site: {2}

Overridable parameters
Parameter Default Value
Priority 1
Severity 1

Top

Application Event Log Collect

Display Name Application Event Log Collect
Description
Monitors the Application event log for XenApp/XenDesktop controller specific events.
Knowledge Article
Summary

Checks the Application event log for XenApp/XenDesktop controller specific events (except licensing related events 1150 to 1160).

Configuration

By default only events with warning and error severity are collected.

The following configuration parameters are customizable:

EventLevel

The maximum log level for an event to be collected (the default event level is 2 - warning and error events).

ExcludeEventIDs

The vent id exclude regular expression (by default no events are excluded).

ExcludeEventSources

The event source to be excluded (by default no event sources are excluded).

The following event levels are valid:

1

Collect error events only.

2

Collect error and warning events.

3

Collect error, warning and information events.

To exclude events with specific Event IDs or Event Sources, override the "ExcludeEventIDs" or "ExcludeEventSources" parameters. Parameters must be formatted as regex patterns.

ExcludeEventIDs parameter override example: ^(1001)$|^(1002)$|^(1045)$

Causes

See event description for details.

External

Click the following link for a reference of all XenApp/XenDesktop event log messages:

XenApp/XenDesktop 7 - Event Log Messages

Target XAXD Delivery Controller
Enabled by default Yes
Category EventCollection
Generate Alert False

Overridable parameters
Parameter Default Value
EventLevel 2
ExcludeEventIDs ^.{0,0}$
ExcludeEventSources ^.{0,0}$

Top

XAXD Delivery Group

Machine Failed Registrations (Alert)

Display Name Machine Failed Registrations (Alert)
Description
Generate alerts for power managed machines that failed to register. 
Knowledge Article
Summary

Before any desktop/application can be brokered by the XenDesktop, Virtual Delivery Agent installed on the desktop or server machine has to register with one of the controllers in XenApp/XenDesktop site. A machine (VDA) registers with one of controllers every time it is going to be used (started) by XenDesktop. Machine for which registration fails is not available and is a wasted resource.

Failed registrations are monitored only for power managed machines (Desktop or Server OS). When failed registration is detected, an alert is created. Once machine with failed registration successfully registers, failed registration alert is automatically closed.

Causes

There are many causes, including: no Virtual Delivery Agent being installed on desktop machine, DNS problems, firewall configuration, time synchronization. For a complete list, see causes documented in Citrix knowledge articles below.

Resolutions

To resolve registration problems, see Citrix knowledge articles:

CTX136668 - Virtual Delivery Agent Registration Troubleshooting Flowchart

CTX129700 - XenApp/XenDesktop Virtual Machines Do Not Successfully Register with the Desktop Delivery Delivery Controller

CTX129225 - VDAs fail to register when using disjoint namespaces in a XenApp/XenDesktop Environment

CTX126992 - Troubleshooting Virtual Desktop Agent Registration with Controllers in XenDesktop

Target XAXD Delivery Group
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Machine Failed Registration
Alert Message
Machine '{0}' belonging to '{1}' delivery group failed to register with delivery controller(s). 

Site: {2}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
Priority 0
Severity 2

Top

Machine Failed Registrations Resolved

Display Name Machine Failed Registrations Resolved
Description
Successful registrations for machines that failed to register before.
Knowledge Article
Summary

This alert indicates a machine that failed to register with the delivery controller before, and has now successfully registered.

Target XAXD Delivery Group
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Machine Failed Registration Resolved
Alert Message
Machine {0} belonging to '{1}' delivery group successfully registered (after failed registration before).

Site: {2}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
Priority 0
Severity 0

Top

User Logon Process - Applying GPOs Time (Alert)

Display Name User Logon Process - Applying GPOs Time (Alert)
Description
Generates alert if time taken for the GPOs to be applied exceeds a threshold value.
Knowledge Article
Summary

Helps to identify a user whose GPOs logon phase was very slow. During this phase the desktop/server machine applies user settings defined on the Domain Controller.

When an application or desktop is launched through Citrix, it kicks off a huge stream of events. Profiles are engaged, printers are mapped, and policies are applied.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds).

InfoThreshold

Info alert threshold (the default value is set to 20 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 40 seconds).

CriticalThreshold

Critical alert threshold (the default value is set to 60 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

Applying GPOs can have a large impact on start time. Some of the most common ways that GPOs increase logon times are:

  • Numerous GPOs, rather than a few large ones.

  • Large numbers of access control rewrites on folders and files.

  • Large numbers of mapped drives.

  • Large numbers of network printers.

  • Unused GPO sections (Computer/User) are not disabled.

  • Numerous XenApp/XenDesktop policies.

Resolutions

To identify if this is a general issue on a delivery group, compare the user's GPOs load time to the average time for all users in this Delivery Group for the last seven days.

See Delivery Group Average Logon Performance

Check also the User - Logon Activity (Troubleshooting) report to get information about this user's logons in the past.

Resolutions to some common issues are as follows:

Issue Description

Mitigation

Having GPOs that heavily rewrite access to files and folders on boot can have a significant impact on logon times.

Optimize access control to reduce number of required changes. Use AD groups and build permissions into base image.

Merging GPOs takes additional time and adds load to the AD server.

Merge GPOs where possible, so that only several larger GPOs exist, instead of hundreds of small ones.

Having many printer and driver mappings can increase logon time.

Reduce the number of required printer and drive mappings where possible, and ensure that client printer mapping is allowed to occur after logon in XenApp/XenDesktop.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • CatalogName - The server/desktop OS machine catalog name.

  • MachineIP/MachineHostname - The IP address/host name of the machine hosting the session.

  • ClientIP/ClientHostname - The IP address/host name of the client connected to the desktop or application.

  • ClientVersion - The version of the Citrix Receiver running on the client connected to the session.

  • ConnectedViaIP/ConnectedViaHostname - The IP address/host name of the incoming connection. This is usually a gateway, router or client.

  • LaunchedViaIP/LaunchedViaHostname - The IP address/host name of the StoreFront server used to launch the session.

  • ControllerHostname - The host name of the controller that the session's hosting machine is registered with.

  • SessionType - Indicates if this is an Application or Desktop session.

  • IsReconnect - Indicates if the user has reconnected to an already existing session or launched a new one.

  • BrokeringUsername - The user name of the brokering user.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

You may also want to check out the Citrix logon optimization guide:

Logon Optimization Guide

Target XAXD Delivery Group
Enabled by default No
Category Alert
Generate Alert True
Alert Name User Logon Process - Applying GPOs Time
Alert Message
The time taken for the Group Policy settings to be enabled for user '{0}' is {1} s. The user logged on from client machine '{2}' to machine '{3}'.

Duration of logon phases: {4}

Logon start time: {5}
Hypervisor hostname: {6}
Site: {7}
Delivery group: {8}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
CriticalThreshold 60
WarningThreshold 40
InfoThreshold 20
Priority 1
Severity -- defined with discovered object property --

Top

User Logon Process - Authentication Time (Alert)

Display Name User Logon Process - Authentication Time (Alert)
Description
Generates alert if time taken to complete authentication to the remote session exceeds a threshold value.
Knowledge Article
Summary

Helps to identify a user whose authentication logon phase was very slow. During this phase the user is authenticated to the domain and his rights are checked for access to the either server or desktop OS machine.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds).

InfoThreshold

Info alert threshold (the default value is set to 5 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 10 seconds).

CriticalThreshold

Critical alert threshold (the default value is set to 20 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

A session can only be initiated after the user’s credentials have been verified. This typically happens by communicating with an Active Directory domain controller over the network.

Authentication is an often an overlooked piece of the logon puzzle. In an environment with an overloaded or inaccessible domain controller, this can have a dramatic impact on logon times. Additionally, applications themselves may also authenticate to Active Directory, adding significant additional time to any application startup if the AD server is unresponsive.

Common issues include the following:

  • Overloaded Active Directory server which leads to additional time to log on.

  • Unavailable Active Directory server which may block authorization process for up to 30 seconds before AD server fails over to secondary AD server.

  • Slow authentication because domain controllers are at remote offices.

  • DNS issues.

Resolutions

To identify if this is a general issue on a delivery group, compare the user's authorization time to the average time for all users in this Delivery Group for the last seven days.

See Delivery Group Average Logon Performance

Check also the User - Logon Activity (Troubleshooting) report to get information about this user's logons in the past.

Also ensure the following:

  • AD servers should have enough resources to handle the load also during logon storms.

  • The server/desktop OS machine to which user is connecting can contact the AD server.

  • Enough domain controllers should be placed to all main user locations to facilitate the authentication process.

  • The server/desktop OS machines are using AD DNS servers. Also check if the name registrations for your DCs are correct.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • CatalogName - The server/desktop OS machine catalog name.

  • MachineIP/MachineHostname - The IP address/host name of the machine hosting the session.

  • ClientIP/ClientHostname - The IP address/host name of the client connected to the desktop or application.

  • ClientVersion - The version of the Citrix Receiver running on the client connected to the session.

  • ConnectedViaIP/ConnectedViaHostname - The IP address/host name of the incoming connection. This is usually a gateway, router or client.

  • LaunchedViaIP/LaunchedViaHostname - The IP address/host name of the StoreFront server used to launch the session.

  • ControllerHostname - The host name of the controller that the session's hosting machine is registered with.

  • SessionType - Indicates if this is an Application or Desktop session.

  • IsReconnect - Indicates if the user has reconnected to an already existing session or launched a new one.

  • BrokeringUsername - The user name of the brokering user.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

You may also want to check out the Citrix logon optimization guide:

Logon Optimization Guide

Target XAXD Delivery Group
Enabled by default No
Category Alert
Generate Alert True
Alert Name User Logon Process - Authentication Time
Alert Message
The time taken to complete authentication to the remote session for user '{0}' is {1} s. The user logged on from client machine '{2}' to machine '{3}'.

Duration of logon phases: {4}

Logon start time: {5}
Hypervisor hostname: {6}
Site: {7}
Delivery group: {8}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
CriticalThreshold 20
WarningThreshold 10
InfoThreshold 5
Priority 1
Severity -- defined with discovered object property --

Top

User Logon Process - Brokering Time (Alert)

Display Name User Logon Process - Brokering Time (Alert)
Description
Generates alert if duration of delivery controller to broker the session exceeds a threshold value.
Knowledge Article
Summary

Helps to identify a user whose brokering logon phase was very slow.

Brokering is a process that allows a user to click a desktop or application resource, and have a 'worker' (server or desktop machine) selected and prepared for an inbound ICA/HDX connection. During brokering process, the Broker Service is responsible for negotiating session launch requests with delivery group machines. The Broker Service communicates with the VDA agent over a CBP (connection brokering protocol) protocol to validate a machine’s readiness to fulfil a session launch request, gather the necessary details (IP address or host name), and send the details to the StoreFront site to be packaged and delivered as an '.ICA' launch file that’s consumed by the Receiver.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds).

InfoThreshold

Info alert threshold (the default value is set to 3 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 5 seconds).

CriticalThreshold

Critical alert threshold (the default value is set to 10 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

Reasons for a slower brokering logon phase can be:

  • Delivery controller is under heavy load.

  • WCF operations timing out.

Resolutions

To identify if this is a general issue on a delivery group, compare the user's brokering time to the average time for all users in this Delivery Group for the last seven days.

See Delivery Group Average Logon Performance

Check also the User - Logon Activity (Troubleshooting) report to get information about this user's logons in the past.

If the brokering time is slow in general, please escalate the issue to the XenApp/XenDesktop administrator to check the load balancing on the Delivery Controller.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • CatalogName - The server/desktop OS machine catalog name.

  • MachineIP/MachineHostname - The IP address/host name of the machine hosting the session.

  • ClientIP/ClientHostname - The IP address/host name of the client connected to the desktop or application.

  • ClientVersion - The version of the Citrix Receiver running on the client connected to the session.

  • ConnectedViaIP/ConnectedViaHostname - The IP address/host name of the incoming connection. This is usually a gateway, router or client.

  • LaunchedViaIP/LaunchedViaHostname - The IP address/host name of the StoreFront server used to launch the session.

  • ControllerHostname - The host name of the controller that the session's hosting machine is registered with.

  • SessionType - Indicates if this is an Application or Desktop session.

  • IsReconnect - Indicates if the user has reconnected to an already existing session or launched a new one.

  • BrokeringUsername - The user name of the brokering user.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

Target XAXD Delivery Group
Enabled by default No
Category Alert
Generate Alert True
Alert Name User Logon Process - Brokering Time
Alert Message
The time taken to complete the process of brokering the session for user '{0}' is {1} s. The user logged on from client machine '{2}' to machine '{3}'.

Duration of logon phases: {4}

Logon start time: {5}
Hypervisor hostname: {6}
Site: {7}
Delivery group: {8}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
CriticalThreshold 10
WarningThreshold 5
InfoThreshold 3
Priority 1
Severity -- defined with discovered object property --

Top

User Logon Process - Complete Duration (Alert)

Display Name User Logon Process - Complete Duration (Alert)
Description
Generates alert if duration of the complete user logon process exceeds a threshold value.
Knowledge Article
Summary

Helps to identify a user whose logon process was very slow. It provides also information about duration for various logon phases.

The complete logon duration is not an exact sum of all phases. For example, some phases occur in parallel, and in some phases, additional processing occurs that might result in a longer logon duration than the sum.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds).

InfoThreshold

Info alert threshold (the default value is set to 120 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 180 seconds).

CriticalThreshold

Critical alert threshold (the default value is set to 240 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

There are various reasons for a slower user logon including:

  • A new application was installed.

  • An operating system update occurred.

  • Configuration changes were made.

Also, check root causes of all logon phases which are included into the complete logon duration.

Resolutions

To identify if this is a general issue on a delivery group, compare the user's logon time to the average time for all users in this Delivery Group for the last seven days.

See Delivery Group Average Logon Performance

Check also the User - Logon Activity (Troubleshooting) report to get information about this user's logons in the past.

Additional

User logon is a complex and a resource intensive process on a Citrix server or desktop OS machine. It is initiated when Citrix delivery group load balancing algorithm selects the system where published application and/or desktop that user has selected will be started, and ends when the application and/or desktop is running and the user is able to interact with it.

Management Pack breaks down the Citrix XenApp/XenDesktop logon process into the following phases.

Phase 1: Brokering

The time taken to decide which desktop to assign to the user.

Phase 2: VM start

In case the session required a machine to be started, the time taken to boot the desktop.

Phase 3: HDX connection

The time taken to complete the steps required in setting up the HDX connection from the client to the VM, dependding on the network.

Phase 4: Authentication

The time taken to complete authentication to the remote session.

Phase 5: Profile load

The phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).

Phase 6: GPOs

During this phase, group policy objects are applied/defined on the Domain Controller.

Phase 7: Logon scripts

This phase covers the time taken for the logon scripts to be executed.

Phase 8: Interactive session

The phase starts in parallel with GPOs phase and covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.

Additional logon information

In addition to alert description, some information is also available in Alert Context tab:

  • MachineIP/MachineHostname - The IP address/host name of the machine hosting the session.

  • ClientIP/ClientHostname - The IP address/host name of the client connected to the desktop or application.

  • ClientVersion - The version of the Citrix Receiver running on the client connected to the session.

  • ConnectedViaIP/ConnectedViaHostname - The IP address/host name of the incoming connection. This is usually a gateway, router or client.

  • LaunchedViaIP/LaunchedViaHostname - The IP address/host name of the StoreFront server used to launch the session.

  • ControllerHostname - The host name of the controller that the session's hosting machine is registered with.

  • SessionType - Indicates if this is an Application or Desktop session.

  • IsReconnect - Indicates if the user has reconnected to an already existing session or launched a new one.

  • BrokeringUsername - The user name of the brokering user.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

You may also want to check out the Citrix logon optimization guide:

Logon Optimization Guide

Target XAXD Delivery Group
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name User Logon Process - Complete Duration
Alert Message
The complete logon duration of the user '{0}' is {1} s. The user logged on from client machine '{2}' to machine '{3}'.

Duration of logon phases: {4}

Logon start time: {5}
Hypervisor hostname: {6}
Site: {7}
Delivery group: {8}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
CriticalThreshold 240
WarningThreshold 180
InfoThreshold 120
Priority 1
Severity -- defined with discovered object property --

Top

User Logon Process - HDX Connection Time (Alert)

Display Name User Logon Process - HDX Connection Time (Alert)
Description
Generates alert if time taken to complete the steps required in setting up the HDX connection from the client to the VM exceeds a threshold value.
Knowledge Article
Summary

Helps to identify a user whose HDX connection logon phase was very slow. This is the time taken to complete the steps required in setting up the HDX connection from the client to the VM.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds).

InfoThreshold

Info alert threshold (the default value is set to 15 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 25 seconds).

CriticalThreshold

Critical alert threshold (the default value is set to 35 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

The HDX connection time is heavily dependent on the network, so there can be many issues related to slow HDX connection time.

Resolutions

To identify if this is a general issue on a delivery group, compare the user's HDX connection time to the average time for all users in this Delivery Group for the last seven days.

See Delivery Group Average Logon Performance

Check also the User - Logon Activity (Troubleshooting) report to get information about this user's logons in the past.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • CatalogName - The server/desktop OS machine catalog name.

  • MachineIP/MachineHostname - The IP address/host name of the machine hosting the session.

  • ClientIP/ClientHostname - The IP address/host name of the client connected to the desktop or application.

  • ClientVersion - The version of the Citrix Receiver running on the client connected to the session.

  • ConnectedViaIP/ConnectedViaHostname - The IP address/host name of the incoming connection. This is usually a gateway, router or client.

  • LaunchedViaIP/LaunchedViaHostname - The IP address/host name of the StoreFront server used to launch the session.

  • ControllerHostname - The host name of the controller that the session's hosting machine is registered with.

  • SessionType - Indicates if this is an Application or Desktop session.

  • IsReconnect - Indicates if the user has reconnected to an already existing session or launched a new one.

  • BrokeringUsername - The user name of the brokering user.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

Target XAXD Delivery Group
Enabled by default No
Category Alert
Generate Alert True
Alert Name User Logon Process - HDX Connection Time
Alert Message
The time taken to complete the steps required in setting up the HDX connection from the client to the VM for user '{0}' is {1} s. The user logged on from client machine '{2}' to machine '{3}'.

Duration of logon phases: {4}

Logon start time: {5}
Hypervisor hostname: {6}
Site: {7}
Delivery group: {8}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
CriticalThreshold 35
WarningThreshold 25
InfoThreshold 15
Priority 1
Severity -- defined with discovered object property --

Top

User Logon Process - Interactive Session Time (Alert)

Display Name User Logon Process - Interactive Session Time (Alert)
Description
Generates alert if time taken to handoff keyboard and mouse control to the user exceeds a threshold value.
Knowledge Article
Summary

Helps to identify a user whose interactive session logon phase was very slow. This logon phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds).

InfoThreshold

Info alert threshold (the default value is set to 30 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 60 seconds).

CriticalThreshold

Critical alert threshold (the default value is set to 120 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Resolutions

To identify if this is a general issue on a delivery group, compare the user's interactive session time to the average time for all users in this Delivery Group for the last seven days.

See Delivery Group Average Logon Performance

Check also the User - Logon Activity (Troubleshooting) report to get information about this user's logons in the past.

One of the issues related to long interactive session times is the following:

Black or Blue Screen When Connecting to Published Desktop

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • CatalogName - The server/desktop OS machine catalog name.

  • MachineIP/MachineHostname - The IP address/host name of the machine hosting the session.

  • ClientIP/ClientHostname - The IP address/host name of the client connected to the desktop or application.

  • ClientVersion - The version of the Citrix Receiver running on the client connected to the session.

  • ConnectedViaIP/ConnectedViaHostname - The IP address/host name of the incoming connection. This is usually a gateway, router or client.

  • LaunchedViaIP/LaunchedViaHostname - The IP address/host name of the StoreFront server used to launch the session.

  • ControllerHostname - The host name of the controller that the session's hosting machine is registered with.

  • SessionType - Indicates if this is an Application or Desktop session.

  • IsReconnect - Indicates if the user has reconnected to an already existing session or launched a new one.

  • BrokeringUsername - The user name of the brokering user.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

Target XAXD Delivery Group
Enabled by default No
Category Alert
Generate Alert True
Alert Name User Logon Process - Interactive Session Time
Alert Message
The time taken to handoff keyboard and mouse control to the user '{0}' is {1} s. The user logged on from client machine '{2}' to machine '{3}'.

Duration of logon phases: {4}

Logon start time: {5}
Hypervisor hostname: {6}
Site: {7}
Delivery group: {8}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
CriticalThreshold 120
WarningThreshold 60
InfoThreshold 30
Priority 1
Severity -- defined with discovered object property --

Top

User Logon Process - Logon Scripts Time (Alert)

Display Name User Logon Process - Logon Scripts Time (Alert)
Description
Generates alert if time taken for the logon scripts to be executed exceeds a threshold value.
Knowledge Article
Summary

Helps to identify a user whose logon scripts phase was very slow. This logon phase covers the time taken for the logon scripts to be executed.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds).

InfoThreshold

Info alert threshold (the default value is set to 30 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 60 seconds).

CriticalThreshold

Critical alert threshold (the default value is set to 120 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

Logon scripts can have a large impact on start time. Some of the most common ways that logon scripts increase logon times are:

  • Slow or resource-intensive startup scripts (for example, those that move large numbers of files).

  • Inefficient loops in scripts.

  • Nested calls to different scripts.

Resolutions

To identify if this is a general issue on a delivery group, compare the user's load scripts time to the average time for all users in this Delivery Group for the last seven days.

See Delivery Group Average Logon Performance

Check also the User - Logon Activity (Troubleshooting) report to get information about this user's logons in the past.

Some scripts may complete a lot of actions, including calls to other scripts, long loops, mapping network drives, and others.

Optimize and merge logon scripts where possible. Windows Server 2008 introduced Group Policy Preferences, which when used can reduce, or in some cases eliminate, the need for logon scripts. When not using Group Policy Preferences, assign logon scripts to users via GPOs, rather than the AD User Account property setting.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • CatalogName - The server/desktop OS machine catalog name.

  • MachineIP/MachineHostname - The IP address/host name of the machine hosting the session.

  • ClientIP/ClientHostname - The IP address/host name of the client connected to the desktop or application.

  • ClientVersion - The version of the Citrix Receiver running on the client connected to the session.

  • ConnectedViaIP/ConnectedViaHostname - The IP address/host name of the incoming connection. This is usually a gateway, router or client.

  • LaunchedViaIP/LaunchedViaHostname - The IP address/host name of the StoreFront server used to launch the session.

  • ControllerHostname - The host name of the controller that the session's hosting machine is registered with.

  • SessionType - Indicates if this is an Application or Desktop session.

  • IsReconnect - Indicates if the user has reconnected to an already existing session or launched a new one.

  • BrokeringUsername - The user name of the brokering user.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

You may also want to check out the Citrix logon optimization guide:

Logon Optimization Guide

Target XAXD Delivery Group
Enabled by default No
Category Alert
Generate Alert True
Alert Name User Logon Process - Logon Scripts Time
Alert Message
The time taken for the configured logon scripts to be executed for user '{0}' is {1} s. The user logged on from client machine '{2}' to machine '{3}'.

Duration of logon phases: {4}

Logon start time: {5}
Hypervisor hostname: {6}
Site: {7}
Delivery group: {8}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
CriticalThreshold 120
WarningThreshold 60
InfoThreshold 30
Priority 1
Severity -- defined with discovered object property --

Top

User Logon Process - Profile Load Time (Alert)

Display Name User Logon Process - Profile Load Time (Alert)
Description
Generates alert if time taken for the profile to be loaded exceeds a threshold value.
Knowledge Article
Summary

Helps to identify a user whose profile load logon phase was very slow. The logon phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).

Once the user is authenticated, the operating system can start to build his/her session. First, a user profile is needed. All of the following phases require the user profile to be set up and the user’s registry hive to be loaded.

If the user does not already have a profile, a new one is created. This slows down the initial logon quite a bit compared to subsequent logons. The main reason is that Active Setup runs the IE/Mail/Theme initialization routines.

Profile load times are one of the most significant logon times in most organizations. Several types of Microsoft profiles exist: local, roaming, mandatory, as well as many third-party solutions.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds).

InfoThreshold

Info alert threshold (the default value is set to 15 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 30 seconds).

CriticalThreshold

Critical alert threshold (the default value is set to 60 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

Some of the most common issues are that either a huge roaming profile needs to be copied over the network, or connection issues to the profile store (generally a file share, though some third-party solutions may utilize databases).

Other reasons for a slower profile load logon phase include:

  • Large profiles.

  • Corrupt profiles.

  • Unavailable profile store.

  • Overloaded profile store.

Resolutions

To identify if this is a general issue on a delivery group, compare the user's profile load time to the average time for all users in this Delivery Group for the last seven days.

See Delivery Group Average Logon Performance

Check also the User - Logon Activity (Troubleshooting) report to get information about this user's logons in the past.

Resolutions for some common issues are as follows:

Issue Description

Mitigation

Profiles need to be downloaded on each logon, and un-optimized profiles can grow to hundreds of megabytes or thousands of files. Either size or quantity of files in a roaming profile can increase the download size.

Redirect most user folders to a network share (Desktop, Documents) or ignore folders if allowable by the business (Cookies & History).

If a user commonly opens up multiple sessions, this increases the chances of developing corrupt roaming profiles.

With Windows Server 2008 R2 Active Directory, enable interim roaming profile writes. Alternatively, use a third-party profile solution that manages multiple sessions more appropriately.

The profile store is unavailable, resulting in a logon delay and possibly default user settings or an inability to connect.

Ensure the profile store is highly available.

The server hosting the profile store has either too many users connecting, or may not be optimized as a file server, causing delays in delivering roaming profiles.

Optimize the server for file sharing, ensure the hardware (including disks and network) can handle the necessary load, and distribute to multiple servers if necessary.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • CatalogName - The server/desktop OS machine catalog name.

  • MachineIP/MachineHostname - The IP address/host name of the machine hosting the session.

  • ClientIP/ClientHostname - The IP address/host name of the client connected to the desktop or application.

  • ClientVersion - The version of the Citrix Receiver running on the client connected to the session.

  • ConnectedViaIP/ConnectedViaHostname - The IP address/host name of the incoming connection. This is usually a gateway, router or client.

  • LaunchedViaIP/LaunchedViaHostname - The IP address/host name of the StoreFront server used to launch the session.

  • ControllerHostname - The host name of the controller that the session's hosting machine is registered with.

  • SessionType - Indicates if this is an Application or Desktop session.

  • IsReconnect - Indicates if the user has reconnected to an already existing session or launched a new one.

  • BrokeringUsername - The user name of the brokering user.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

You may also want to check out the Citrix logon optimization guide:

Logon Optimization Guide

Target XAXD Delivery Group
Enabled by default No
Category Alert
Generate Alert True
Alert Name User Logon Process - Profile Load Time
Alert Message
The time taken for the profile to be loaded for user '{0}' is {1} s. The user logged on from client machine '{2}' to machine '{3}'.

Duration of logon phases: {4}

Logon start time: {5}
Hypervisor hostname: {6}
Site: {7}
Delivery group: {8}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
CriticalThreshold 60
WarningThreshold 30
InfoThreshold 15
Priority 1
Severity -- defined with discovered object property --

Top

User Logon Process - VM Start Time (Alert)

Display Name User Logon Process - VM Start Time (Alert)
Description
Generates alert if time taken to start a VM (in case this is needed) exceeds a threshold value.
Knowledge Article
Summary

Helps to identify a user whose VM start logon phase was very slow.

VM start logon phase includes the time taken to start VMs by the user. VM start time will be 0 in case there was no need to start a new machine, since a machine could be brokered instantly.

Configuration

Overridable parameters:

IntervalSeconds

The recurring interval of time in seconds in which to run the rule (the default value is set to 300 seconds).

InfoThreshold

Info alert threshold (the default value is set to 60 seconds).

WarningThreshold

Warning alert threshold (the default value is set to 90 seconds).

CriticalThreshold

Critical alert threshold (the default value is set to 120 seconds).

Debug

Used for troubleshooting (the default value is set to false).

Causes

If desktops are not powered on when the users try to access their desktop, it would take some time for the desktop to boot and be ready for login.

Resolutions

To identify if this is a general issue on a delivery group, check if VM need to be booted often for the Delivery Group in the past days.

See Delivery Group Average Logon Performance

Check also the User - Logon Activity (Troubleshooting) report to get information about this user's logons in the past.

Try also to fine tune idle pool settings for the desktop OS machines, to be ready for users when they are expected to be used.

Additionally, optimize the startup process by disabling or delaying services and applications that are scheduled to run at power on.

Additional

In addition to alert description, some information is also available in Alert Context tab:

  • CatalogName - The server/desktop OS machine catalog name.

  • MachineIP/MachineHostname - The IP address/host name of the machine hosting the session.

  • ClientIP/ClientHostname - The IP address/host name of the client connected to the desktop or application.

  • ClientVersion - The version of the Citrix Receiver running on the client connected to the session.

  • ConnectedViaIP/ConnectedViaHostname - The IP address/host name of the incoming connection. This is usually a gateway, router or client.

  • LaunchedViaIP/LaunchedViaHostname - The IP address/host name of the StoreFront server used to launch the session.

  • ControllerHostname - The host name of the controller that the session's hosting machine is registered with.

  • SessionType - Indicates if this is an Application or Desktop session.

  • IsReconnect - Indicates if the user has reconnected to an already existing session or launched a new one.

  • BrokeringUsername - The user name of the brokering user.

External

Click the following link to get more info about logon process:

XenApp/XenDesktop Connection Process and Communication Flow

Also, please see the following Citrix article on troubleshooting slow XenApp logons:

How to Troubleshoot Slow Logons

Target XAXD Delivery Group
Enabled by default No
Category Alert
Generate Alert True
Alert Name User Logon Process - VM Start Time
Alert Message
The time taken to start a VM for user '{0}' is {1} s. The user logged on from client machine '{2}' to machine '{3}'.

Duration of logon phases: {4}

Logon start time: {5}
Hypervisor hostname: {6}
Site: {7}
Delivery group: {8}

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
CriticalThreshold 120
WarningThreshold 90
InfoThreshold 60
Priority 1
Severity -- defined with discovered object property --

Top

Avg. User Logon Authentication Time (Performance DB)

Display Name Avg. User Logon Authentication Time (Performance DB)
Description
Collects average user logon authentication time (in seconds) for a delivery group and stores data to OpsMgr database. 
Authentication time is the time taken to complete authentication to the remote session.
Knowledge Article
Summary

Collects average user logon authentication time (in seconds) for a delivery group and stores data to OpsMgr database. Authentication time is the time taken to complete authentication to the remote session.

Target XAXD Delivery Group
Enabled by default No
Category PerformanceCollection
Generate Alert False
Counter Name AvgAuthenticationTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Avg. User Logon Brokering Time (Performance DB)

Display Name Avg. User Logon Brokering Time (Performance DB)
Description
Collects average user logon brokering time (in seconds) for a delivery group and stores data to OpsMgr database. 
This is the time taken to complete the process of brokering the session.
Knowledge Article
Summary

Collects average user logon brokering time (in seconds) for a delivery group and stores data to OpsMgr database. This is the time taken to complete the process of brokering the session.

Target XAXD Delivery Group
Enabled by default No
Category PerformanceCollection
Generate Alert False
Counter Name AvgBrokeringTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Avg. User Logon Duration (Performance DB DW)

Display Name Avg. User Logon Duration (Performance DB DW)
Description
Collects average user logon duration (in seconds) for a delivery group and stores data to OpsMgr and DataWarehouse databases.
Total logon duration is the elapsed time from the point when a user launches a desktop or application via Storefront to the point when a user can start using it.
Knowledge Article
Summary

Collects average user logon duration (in seconds) for a delivery group and stores data to OpsMgr database. Complete logon duration is time that is needed from a user launching a desktop or application via Storefront to the time when a user can start using it.

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name AvgLogonDuration

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Avg. User Logon GPOs Time (Performance DB)

Display Name Avg. User Logon GPOs Time (Performance DB)
Description
Collects average user logon GPOs time (in seconds) for a delivery group and stores data to OpsMgr database. 
During this phase the desktop/server machine applies user settings defined on the Domain Controller.
Knowledge Article
Summary

Collects average user logon GPOs time (in seconds) for a delivery group and stores data to OpsMgr database. During this phase the desktop/server machine applies user settings defined on the Domain Controller.

Target XAXD Delivery Group
Enabled by default No
Category PerformanceCollection
Generate Alert False
Counter Name AvgGPOsTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Avg. User Logon HDX Connection Time (Performance DB)

Display Name Avg. User Logon HDX Connection Time (Performance DB)
Description
Collects average user logon HDX connection time (in seconds) for a delivery group and stores data to OpsMgr database. 
This is the time taken to complete the steps required in setting up the HDX connection from the client to the VM.
Knowledge Article
Summary

Collects average user logon HDX connection time (in seconds) for a delivery group and stores data to OpsMgr database. This is the time taken to complete the steps required in setting up the HDX connection from the client to the VM.

Target XAXD Delivery Group
Enabled by default No
Category PerformanceCollection
Generate Alert False
Counter Name AvgHDXConnectionTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Avg. User Logon Interactive Session Time (Performance DB)

Display Name Avg. User Logon Interactive Session Time (Performance DB)
Description
Collects average user logon interactive session time (in seconds) for a delivery group and stores data to OpsMgr database. 
The logon phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.
Knowledge Article
Summary

Collects average user logon interactive session time (in seconds) for a delivery group and stores data to OpsMgr database. This logon phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.

Target XAXD Delivery Group
Enabled by default No
Category PerformanceCollection
Generate Alert False
Counter Name AvgInteractiveSessionTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Avg. User Logon Profile Load Time (Performance DB)

Display Name Avg. User Logon Profile Load Time (Performance DB)
Description
Collects average user logon profile load time (in seconds) for a delivery group and stores data to OpsMgr database. 
The logon phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).
Knowledge Article
Summary

Collects average user logon profile load time (in seconds) for a delivery group and stores data to OpsMgr database. The logon phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).

Target XAXD Delivery Group
Enabled by default No
Category PerformanceCollection
Generate Alert False
Counter Name AvgProfileLoadTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Avg. User Logon Scripts Execution Time (Performance DB)

Display Name Avg. User Logon Scripts Execution Time (Performance DB)
Description
Collects average user logon scripts execution time (in seconds) for a delivery group and stores data to OpsMgr database. 
This logon phase covers the time taken for the logon scripts to be executed.
Knowledge Article
Summary

Collects average user logon scripts execution time (in seconds) for a delivery group and stores data to OpsMgr database. This logon phase covers the time taken for the logon scripts to be executed.

Target XAXD Delivery Group
Enabled by default No
Category PerformanceCollection
Generate Alert False
Counter Name AvgLogonScriptsTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Avg. User Logon VM Start Time (Performance DB)

Display Name Avg. User Logon VM Start Time (Performance DB)
Description
Collects average user logon VM start time (in seconds) for a delivery group and stores data to OpsMgr database. 
This is the time taken to start a VM.
Knowledge Article
Summary

Collects average user logon VM start time (in seconds) for a delivery group and stores data to OpsMgr database. This is the time taken to start a VM.

Target XAXD Delivery Group
Enabled by default No
Category PerformanceCollection
Generate Alert False
Counter Name AvgVMStartTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Number of Active Sessions (Performance DB DW)

Display Name Number of Active Sessions (Performance DB DW)
Description
Collects the number of XenApp/XenDesktop active sessions for a delivery group and stores data to OpsMgr and DataWarehouse databases.
Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name ActiveSessions

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Number of All Sessions (Performance DB DW)

Display Name Number of All Sessions (Performance DB DW)
Description
Collects the number of all XenApp/XenDesktop sessions for a delivery group and stores data to OpsMgr and DataWarehouse databases.
Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name AllSessions

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Number of Disconnected Sessions (Performance DB DW)

Display Name Number of Disconnected Sessions (Performance DB DW)
Description
Collects the number of XenApp/XenDesktop disconnected sessions for a delivery group and stores data to OpsMgr and DataWarehouse databases.
Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name DisconnectedSessions

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Number of Logons (Performance DB DW)

Display Name Number of Logons (Performance DB DW)
Description
Collects information about number of logons for a delivery group and stores data to OpsMgr and DataWarehouse databases.
Knowledge Article
Summary

Collects information about number of logons for a delivery group and stores data to OpsMgr and DataWarehouse databases.

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name NumberOfLogons

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Number of Unregistered Machines (Performance DB DW)

Display Name Number of Unregistered Machines (Performance DB DW)
Description
Collects the number of unregistered machines for a delivery group and stores data to OpsMgr and DataWarehouse databases. 
Unregistered machines are machines that can be either turned off or turned on but are not registered with a controller.
Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name UnregisteredMachines

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Total Logon Authentication Time (Performance DW)

Display Name Total Logon Authentication Time (Performance DW)
Description
Collects total logon authentication time (in seconds) for a delivery group and stores data to Data Warehouse.
Authentication time is the time taken to complete authentication to the remote session.
Knowledge Article
Summary

Collects total logon authentication time (in seconds) for a delivery group and stores data to Data Warehouse. Authentication time is the time taken to complete authentication to the remote session.

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name TotalAuthenticationTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Total Logon Brokering Time (Performance DW)

Display Name Total Logon Brokering Time (Performance DW)
Description
Collects total logon brokering time (in seconds) for a delivery group and stores data to Data Warehouse.
This is the time taken to complete the process of brokering the session.
Knowledge Article
Summary

Collects total logon brokering time (in seconds) for a delivery group and stores data to Data Warehouse. This is the time taken to complete the process of brokering the session.

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name TotalBrokeringTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Total Logon Duration (Performance DW)

Display Name Total Logon Duration (Performance DW)
Description
Collects total logon duration (in seconds) for a delivery group and stores data to Data Warehouse.
Complete logon duration is time that is needed from a user launching a desktop or application via Storefront to the time when a user can start using it.
Knowledge Article
Summary

Collects total logon duration (in seconds) for a delivery group and stores data to Data Warehouse. Complete logon duration is time that is needed from a user launching a desktop or application via Storefront to the time when a user can start using it.

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name TotalLogonDuration

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Total Logon GPOs Time (Performance DW)

Display Name Total Logon GPOs Time (Performance DW)
Description
Collects total logon GPOs time (in seconds) for a delivery group and stores data to Data Warehouse.
During this phase the desktop/server machine applies user settings defined on the Domain Controller.
Knowledge Article
Summary

Collects total logon GPOs time (in seconds) for a delivery group and stores data to Data Warehouse. During this phase the desktop/server machine applies user settings defined on the Domain Controller.

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name TotalGPOsTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Total Logon HDX Connection Time (Performance DW)

Display Name Total Logon HDX Connection Time (Performance DW)
Description
Collects total logon HDX connection time (in seconds) for a delivery group and stores data to Data Warehouse.
This is the time taken to complete the steps required in setting up the HDX connection from the client to the VM.
Knowledge Article
Summary

Collects total logon HDX connection time (in seconds) for a delivery group and stores data to Data Warehouse. This is the time taken to complete the steps required in setting up the HDX connection from the client to the VM.

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name TotalHDXConnectionTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Total Logon Interactive Session Time (Performance DW)

Display Name Total Logon Interactive Session Time (Performance DW)
Description
Collects total logon interactive session time (in seconds) for a delivery group and stores data to Data Warehouse.
The logon phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.
Knowledge Article
Summary

Collects total logon interactive session time (in seconds) for a delivery group and stores data to Data Warehouse. The logon phase covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name TotalInteractiveSessionTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Total Logon Profile Load Time (Performance DW)

Display Name Total Logon Profile Load Time (Performance DW)
Description
Collects total logon profile load time (in seconds) for a delivery group and stores data to Data Warehouse.
The logon phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).
Knowledge Article
Summary

Collects total logon profile load time (in seconds) for a delivery group and stores data to Data Warehouse. The logon phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name TotalProfileLoadTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Total Logon Scripts Execution Time (Performance DW)

Display Name Total Logon Scripts Execution Time (Performance DW)
Description
Collects total logon scripts execution time (in seconds) for a delivery group and stores data to Data Warehouse.
This logon phase covers the time taken for the logon scripts to be executed.
Knowledge Article
Summary

Collects total logon scripts execution time (in seconds) for a delivery group and stores data to Data Warehouse. This logon phase covers the time taken for the logon scripts to be executed.

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name TotalLogonScriptsTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Total Logon VM Start Time (Performance DW)

Display Name Total Logon VM Start Time (Performance DW)
Description
Collects total logon VM start time (in seconds) for a delivery group and stores data to Data Warehouse.
This is the time taken to start a VM.
Knowledge Article
Summary

Collects total logon VM start time (in seconds) for a delivery group and stores data to Data Warehouse. This is the time taken to start a VM.

Target XAXD Delivery Group
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name TotalVMStartTime

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Delivery Group Desktop OS Random

Desktop OS Random Delivery Group Usage (%) (Performance DB DW)

Display Name Desktop OS Random Delivery Group Usage (%) (Performance DB DW)
Description
Collects the percentage of used desktops (In use or Disconnected) for Desktop OS Random delivery group and stores data to OpsMgr and DataWarehouse databases.
Target XAXD Delivery Group Desktop OS Random
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name Usage (in %)

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Number of Ready Desktops (Performance DB DW)

Display Name Number of Ready Desktops (Performance DB DW)
Description
Collects the number of ready desktops in a delivery group and stores data to OpsMgr and DataWarehouse databases. 
Ready desktops are machines which are running and are ready for brokering (are ready to be used by users). Only one user sessions is allowed on one Desktop OS machine.
Target XAXD Delivery Group Desktop OS Random
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name AvailableMachines

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Delivery Group Desktop OS Static

Desktop OS Static Delivery Group Usage (%) (Performance DB DW)

Display Name Desktop OS Static Delivery Group Usage (%) (Performance DB DW)
Description
Collects the percentage of assigned desktops for a Desktop OS Static delivery group and stores data to OpsMgr and DataWarehouse databases.
Target XAXD Delivery Group Desktop OS Static
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name Usage (in %)

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Delivery Group Server OS

Avg. Server OS Machine Load Index (Performance DB DW)

Display Name Avg. Server OS Machine Load Index (Performance DB DW)
Description
Collects average load index of all registered Server OS machines (active servers) in the specified delivery group and stores data to OpsMgr and DataWarehouse databases. 
User sessions on a delivery group are load balanced based on the load index.
Target XAXD Delivery Group Server OS
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name LoadIndex

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Load Available (%) (Performance DB DW)

Display Name Load Available (%) (Performance DB DW)
Description
Collects the percentage of currently available delivery group load and stores data to OpsMgr and DataWarehouse databases. 
Load availability is the percentage of free load index on all active server machines vs. total available load index on all active server machines. Free load index is a total non-used load index on all active servers in the delivery group. Total available load index is a number obtained by counting all active server machines in the delivery group. Each server machine has a potential of load index 10000.
Target XAXD Delivery Group Server OS
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name LoadAvailable

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Number of Available Servers (Performance DB DW)

Display Name Number of Available Servers (Performance DB DW)
Description
Collects the number of available servers in Server OS delivery group and stores data to OpsMgr and DataWarehouse databases.
Available servers are machines that are running, are registered with the delivery controller, are not in maintenance mode and have Load Evaluator Index less than 100%.
Knowledge Article
Summary

This rule collects the number of available machines in Server OS delivery group.

Available servers are machines that are powered on, registered, not in maintenance mode and having Load Evaluator Index less than 100%.

Target XAXD Delivery Group Server OS
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name AvailableMachines

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Total Load/Capacity Usage (%) (Performance DB DW)

Display Name Total Load/Capacity Usage (%) (Performance DB DW)
Description
Collects the percentage of total delivery group load usage and stores data to OpsMgr and DataWarehouse databases. 
Usage is the percentage of actual load index vs. total load index potential. Actual load index is the sum of load index of all the servers in the delivery group. Total load index potential is a number obtained by counting all server machines in the delivery group except those that are in maintenance mode. Each server machine has a potential of load index 10000.
Target XAXD Delivery Group Server OS
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name LoadCapacityUtilization

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Server OS Machine

Load Index (Performance DB DW)

Display Name Load Index (Performance DB DW)
Description
Collects load index for a specific Server OS machine and stores data to OpsMgr and DataWarehouse databases.
User sessions on a delivery group are load balanced based on the load index.
Target XAXD Server OS Machine
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name LoadIndex

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Number of Active Sessions (Performance DW)

Display Name Number of Active Sessions (Performance DW)
Description
Collects the number of active sessions for a specific Server OS machine and stores data to Data Warehouse.
Target XAXD Server OS Machine
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name ActiveSessions

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

XAXD Service Broker

Broker Service License Critical Errors (Alert)

Display Name Broker Service License Critical Errors (Alert)
Description
Generates alerts for the following Citrix XenApp/XenDesktop licensing event messages:
1151 - The Citrix Broker Service cannot contact the license server.
1155 - The Citrix Broker Service will now stop providing desktop sessions.
1157 - The version of the license server is older than the version of the Citrix Broker Service.
1159 - The Citrix Broker Service denied a desktop connection because the maximum number of installed licenses for this site has been exceeded.
Target XAXD Service Broker
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Broker Service Event Log License Errors (Critical)
Alert Message
{0}

Delivery Controller: {1}

Overridable parameters
Parameter Default Value
Priority 1
Severity 2

Top

Broker Service License Information (Alert)

Display Name Broker Service License Information (Alert)
Description
Generates alerts for the following Citrix XenApp/XenDesktop licensing event messages:
1150 - The Citrix Broker Service successfully contacted the license server.
1156 - The Citrix Broker Service is successfully communicating with the license server. 
Target XAXD Service Broker
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Broker Service Event Log License Information
Alert Message
{0}

Delivery Controller: {1}

Overridable parameters
Parameter Default Value
Priority 1
Severity 0

Top

Broker Service License Warnings (Alert)

Display Name Broker Service License Warnings (Alert)
Description
Generates alerts for the following Citrix XenApp/XenDesktop licensing event messages:
1153 - This XenApp/XenDesktop site's license expired. The Citrix Broker service will request a new license from the license server.
1158 - The Citrix Broker Service detected that you have exceeded the number of licenses available for this site on the license server for this edition.
1160 - The Citrix Broker service encountered an internal error while managing licenses.
Target XAXD Service Broker
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Broker Service Event Log License Errors (Warning)
Alert Message
{0}

Delivery Controller: {1}

Overridable parameters
Parameter Default Value
Priority 1
Severity 1

Top

XAXD Service Windows

Process Private Memory (in MB) (Performance DB)

Display Name Process Private Memory (in MB) (Performance DB)
Description
Collects the XenApp/XenDesktop service memory usage and stores data to OpsMgr database.
Target XAXD Service Windows
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Object Name $Target/Property[Type="ComTrade.Citrix.XenDesktop.Service"]/ServiceName$ Process
Counter Name Memory: Private Memory (in MB)

Overridable parameters
Parameter Default Value
IntervalSeconds 300

Top

Process Processor Time (in %) (Performance DB)

Display Name Process Processor Time (in %) (Performance DB)
Description
Collects the XenApp/XenDesktop service processor utilization and stores data to OpsMgr database.
Knowledge Article
Summary

The rule collects CPU usage for the Windows service and stores data to OpsMgr database. The counter collected by this rule is Process\% Processor Time.

The data collected by this rule can be viewed using:

View service performance

Configuration

By default this rule is enabled.

The following configuration parameters are customizable:

IntervalSeconds

The recurring interval of time in seconds in which to run the script (the default value is set to 300 seconds).

Target XAXD Service Windows
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Object Name $Target/Property[Type="ComTrade.Citrix.XenDesktop.Service"]/ServiceName$ Process
Counter Name Percent Processor Time

Overridable parameters
Parameter Default Value
IntervalSeconds 300

Top

Process Working Set (in MB) (Performance DB)

Display Name Process Working Set (in MB) (Performance DB)
Description
Collects the XenApp/XenDesktop service working set and stores data to OpsMgr database.
Target XAXD Service Windows
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Object Name $Target/Property[Type="ComTrade.Citrix.XenDesktop.Service"]/ServiceName$ Process
Counter Name Memory: Working Set (in MB)

Overridable parameters
Parameter Default Value
IntervalSeconds 300

Top

XAXD Site Data Collector

Failed Connection (Alert)

Display Name Failed Connection (Alert)
Description
Generates alert if connection has failed.
Knowledge Article
Summary

This rule generates an alert if user connection has failed.

Rule uses regular expressions for filtering by Delivery Groups, Failure Types and Failure Reasons. Use the following overridable parameters to filter alerts:

DeliveryGroupFilterInclude

Filter alerts based on Delivery Group name. Use this filter to limit alerts to specified delivery groups.

DeliveryGroupFilterExclude

Filter alerts based on Delivery Group name. Use this filter to exclude all delivery groups except the specified ones.

FailureTypeFilterInclude

Filter alerts based on Failure Type name. Use this filter to limit alerts to specified failure types. See the list of failure types in a table below .

FailureTypeFilterExclude

Filter alerts based on Failure Type name. Use this filter to limit alerts to all failure types except the specified ones. See the list of failure types in a table below.

FailureReasonFilterInclude

Filter alerts based on Failure Reason name. Use this filter to limit alerts to specified failure reasons. See the list of failure reasons in a table below.

FailureReasonFilterExclude

Filter alerts based on Failure Reason name. Use this filter to limit alerts to all failure reasons except the specified ones. See the list of failure reasons in a table below.

When setting multiple filters at once, all filters are applied to the rule.

Filter examples:

Alert on failed connections for all delivery groups

DeliveryGroupFilterInclude: .*

Alert on failed connections only for "Group 1", "Group 2" and "Group 3" delivery groups

DeliveryGroupFilterInclude: ^(Group 1)$|^(Group 2)$|^(Group 3)$

Alert on failed connections for a delivery group starting with "PROD"

DeliveryGroupFilterInclude: ^(PROD).*

Alert on all failed connections except for "Group 1", "Group 2" and "Group 3" delivery groups

DeliveryGroupFilterExclude: ^(Group 1)$|^(Group 2)$|^(Group 3)$

* The same applies to FailureTypeFilterInclude/FailureTypeFilterExclude and FailureReasonFilterInclude/FailureReasonFilterExclude parameters.

Connection failure types:

Client Connection Failures

Failures due to the inability of the client side to complete the session connection. For example, connection timed out, server was not reachable.

Machine Failures

Connection failures that are the result of the machine being in a failed state or failure to start up or respond.

Unavailable Capacity

Failures due to the configured capacity of a particular delivery group having been completely consumed. For example, too many users logged into a Server Desktop OS delivery group or a user accessing a Pooled Random delivery group while all the machines in the delivery group are already assigned to other users.

Unavailable Licenses

Failures that occur when the delivery controller is unable to acquire a license from the license server to launch the session.

Configuration Errors

Failures caused by configuration errors. For example, an administrator places a Delivery Group or a particular machine in Maintenance mode.

Connection failure reasons:

Session Preparation

Session prepare request from Broker service to VDA failed.

Registration Timeout

VDA did not register in time after being powered on for session launch.

Connection Timeout

Client did not connect to VDA after VDA was prepared for session launch.

Licensing

License request failed (typically no license available).

Ticketing

Failure during ticketing, indicating that the client connection to VDA does not match the brokered request.

Other

General unresolved errors between client and VDI.

General Fail

General unresolved errors during initial brokering operation.

Maintenance Mode

Machine or delivery group in maintenance mode.

Application Disabled

Application can no longer be used and has been disabled by the admin.

License Feature Refused

Feature being used is not licensed (e.g. license doesn’t allow use of multi-session VDAs).

Session Limit Reached

No more sessions allowed (e.g. launching second session on VDI VDA).

Disallowed Protocol

Resource doesn’t allow protocol requested by session launch.

Resource Unavailable

Resource has been removed/disabled since enumeration.

Active Session Reconnect Disabled

Session is already connected to a different endpoint but session stealing is disabled.

No Session To Reconnect

Specified session could not be found during reconnect.

Spin up Failed

VDA could not be powered-on for session launch.

Refused

VDA actively refused session prepare request.

Configuration Set Failure

Failed to send required configuration data to VDA prior to session launch

No Machine Available

No machine available for launch (e.g. all shared VDI machines in group are in use).

Machine Not Functional

Non-power-managed assigned machine not registered.

Target XAXD Site Data Collector
Enabled by default No
Category Alert
Generate Alert True
Alert Name Failed Connection
Alert Message
The connection for user '{0}' has failed. The user tried to access application/desktop in delivery group '{2}' from client machine with IP '{3}'.

Failure type: {5}
Failure reason: {6}
Time of connection failure: {1}
Site: {7}
Delivery group: {2}
Machine: {4}
          

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false
DeliveryGroupFilterInclude .*
DeliveryGroupFilterExclude ^.{0,0}$
FailureTypeFilterInclude .*
FailureTypeFilterExclude ^.{0,0}$
FailureReasonFilterInclude .*
FailureReasonFilterExclude ^.{0,0}$
Priority 1
Severity 1

Top

Site License Errors (Alert)

Display Name Site License Errors (Alert)
Description
Generates alerts for the following Citrix XenApp/XenDesktop licensing event messages:
1152 - This XenApp/XenDesktop site does not have the required licenses present on the license server.
Target XAXD Site Data Collector
Enabled by default Yes
Category Alert
Generate Alert True
Alert Name Site Event Log License Error (Critical)
Alert Message
{0}

Site: {1}

Overridable parameters
Parameter Default Value
Priority 1
Severity 2

Top

Avg. Logon Duration (Performance DB DW)

Display Name Avg. Logon Duration (Performance DB DW)
Description
Collects  average logon duration of user logons on a site and stores data to OpsMgr and DataWarehouse databases.
Knowledge Article
Summary

Collects average user logon duration (in seconds) for a site and stores data to OpsMgr database. Complete logon duration is time that is needed from a user launching a desktop or application via Storefront to the time when a user can start using it.

Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name AverageLogonDuration

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime

Top

Number of Active Sessions (Performance DB DW)

Display Name Number of Active Sessions (Performance DB DW)
Description
Collects the number of active sessions on a site and stores data to OpsMgr and DataWarehouse databases.
Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name ActiveSessions

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime

Top

Number of All Sessions (Performance DB DW)

Display Name Number of All Sessions (Performance DB DW)
Description
Collects the number of all sessions on a site and stores data to OpsMgr and DataWarehouse databases.
Target XAXD Site Data Collector
Enabled by default No
Category PerformanceCollection
Generate Alert False
Counter Name AllSessions

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime

Top

Number of All Sessions per Application (Performance DW)

Display Name Number of All Sessions per Application (Performance DW)
Description
Collects the number of all concurrent sessions per application and stores data to Data Warehouse database.
Knowledge Article
Summary

Collects the number of all (active and disconnected) concurrent sessions per application and stores data to Data Warehouse database.

Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Object Name Application
Counter Name ConcurrentSessions

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top

Number of Concurrent Users (Performance DB DW)

Display Name Number of Concurrent Users (Performance DB DW)
Description
Collects the number of currently connected users on a site and stores data to OpsMgr and DataWarehouse databases. 
Only distinct users having active sessions are counted while users having disconnected sessions are not.
Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name ConnectedUsers

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime

Top

Number of Disconnected Sessions (Performance DB DW)

Display Name Number of Disconnected Sessions (Performance DB DW)
Description
Collects the number of disconnected sessions on a site and stores data to OpsMgr and DataWarehouse databases.
Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name DisconnectedSessions

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime

Top

Number of Logons (Performance DB DW)

Display Name Number of Logons (Performance DB DW)
Description
Collects information about number of user logons on a site and stores data to OpsMgr and DataWarehouse databases.
Knowledge Article
Summary

Collects information about number of logons for a delivery group and stores data to OpsMgr and DataWarehouse databases.

Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name NumberOfLogons

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime

Top

Publish Application Use Data (Performance DW)

Display Name Publish Application Use Data (Performance DW)
Description
          
Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false

Top

Publish Connections and Logons Data (Performance DW)

Display Name Publish Connections and Logons Data (Performance DW)
Description
          
Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false

Top

Publish Machine Discovery (Performance DW)

Display Name Publish Machine Discovery (Performance DW)
Description
Discovers and stores Server OS and Desktop OS machine data to Data Warehouse.
Knowledge Article
Summary

Discovers and stores Server OS and Desktop OS machine data to Data Warehouse.

Configuration

This rule must be enabled in order to store Server OS and Desktop OS machine data

The following configuration parameters are customizable:

IntervalSeconds

Period for publishing machine data to Data Warehouse (the default interval is set to 5 minutes).

Debug

Used for troubleshooting (the default value is set to false).

Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
Debug false
IntervalSeconds 300
SyncTime

Top

Publish Session Discovery (Performance DW)

Display Name Publish Session Discovery (Performance DW)
Description
Discovers and stores Server OS and Desktop OS session data to Data Warehouse.
          
Knowledge Article
Summary

Discovers and stores Server OS and Desktop OS session data to Data Warehouse.

Configuration

This rule must be enabled in order to store Server OS and Desktop OS session data

The following configuration parameters are customizable:

IntervalSeconds

Period for publishing session data to Data Warehouse (the default interval is set to 5 minutes).

Debug

Used for troubleshooting (the default value is set to false).

Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime

Top

Total Logon Duration (Performance DW)

Display Name Total Logon Duration (Performance DW)
Description
Collects total logon duration of user logons on a site and stores data to Data Warehouse.
Knowledge Article
Summary

Collects total user logon duration (in seconds) for a site and stores data to DataWarehouse database. Complete logon duration is time that is needed from a user launching a desktop or application via Storefront to the time when a user can start using it.

Target XAXD Site Data Collector
Enabled by default Yes
Category PerformanceCollection
Generate Alert False
Counter Name TotalLogonDuration

Overridable parameters
Parameter Default Value
IntervalSeconds 300
Debug false
SyncTime

Top

XAXD Sites

Failed Registrations Alerts Handler

Display Name Failed Registrations Alerts Handler
Description
Auto resolves 'Desktop Failed Registration' alerts for corresponding 'Desktop Failed Registrations Resolved' alerts.
Knowledge Article
Summary

When desktop fails to register, "Desktop Failed Registration" alert is generated. When registration succeeds for a desktop that failed to register before, "Desktop Failed Registrations Resolved" alert is generated.

At regular intervals, this monitor resolves (closes) "Desktop Failed Registration" alerts for desktops that eventually registered successfully ("Desktop Failed Registrations Resolved" alert was generated).

Configuration

The following configuration parameters are customizable:

IntervalSeconds

The interval on which desktop failed registration alerts are checked if they can be resolved.

Target XAXD Sites
Enabled by default Yes
Category Operations
Generate Alert False

Overridable parameters
Parameter Default Value
IntervalSeconds 300
SyncTime
Debug false

Top


Roll-up Monitors

Target Category Display Name Roll-up Algorithm
XAXD Delivery Controller Computer Role
Custom
Installation WorstOf
XAXD Delivery Group
AvailabilityHealth
Delivery Group Availability (Aggregate) WorstOf
XAXD Delivery Group Server OS
Custom
Server OS Machine Load (Aggregate) WorstOf
Server OS Machine Load Health Rollup Percentage
AvailabilityHealth
Application Server Availability Health Rollup WorstOf
Citrix Management
AvailabilityHealth
XenApp/XenDesktop Sites Availability Dependency Monitor WorstOf
PerformanceHealth
XenApp/XenDesktop Sites Performance Dependency Monitor WorstOf
XAXD Application
AvailabilityHealth
Delivery Group Application Availability (Desktop OS Machine) BestOf
Delivery Group Application Availability (Server OS Machine) BestOf
XAXD Application Folder
AvailabilityHealth
Application Availability Rollup WorstOf
Application Folder Availability Rollup WorstOf
PerformanceHealth
Application Performance Rollup WorstOf
Application Folder Performance Rollup WorstOf
XAXD Delivery Controller
AvailabilityHealth
AdIdentity Service Availability Rollup WorstOf
Broker Service Availability Rollup WorstOf
Citrix Monitor Service Availability Rollup WorstOf
Configuration Logging Service Availability Rollup WorstOf
Configuration Service Availability Rollup WorstOf
Delegated Administration Service Availability Rollup WorstOf
Environment Test Service Availability Rollup WorstOf
Host Service Availability Rollup WorstOf
Machine Creation Service Availability Rollup WorstOf
App Library Service Availability Rollup WorstOf
Analytics Service Availability Rollup WorstOf
Telemetry Service Availability Rollup WorstOf
Storefront Privileged Administration Service Availability Rollup WorstOf
Storefront Service Availability Rollup WorstOf
Storefront Service Configuration Rollup WorstOf
Storefront Service Performance Rollup WorstOf
Diagnostic Facility Service Availability Rollup WorstOf
Diagnostic Facility Service Performance Rollup WorstOf
Config Synchronizer Service Availability Rollup WorstOf
Config Synchronizer Service Performance Rollup WorstOf
High Availability Service Availability Rollup WorstOf
High Availability Service Performance Rollup WorstOf
Orchestration Service Availability Rollup WorstOf
Orchestration Service Performance Rollup WorstOf
Orchestration Service Configuration Rollup WorstOf
ConfigurationHealth
AdIdentity Service Configuration Rollup WorstOf
Broker Service Configuration Rollup WorstOf
Configuration Service Configuration Rollup WorstOf
Host Service Configuration Rollup WorstOf
Machine Creation Service Configuration Rollup WorstOf
App Library Service Configuration Rollup WorstOf
Analytics Service Configuration Rollup WorstOf
PerformanceHealth
AdIdentity Service Performance Rollup WorstOf
Broker Service Performance Rollup WorstOf
Configuration Service Performance Rollup WorstOf
Host Service Performance Rollup WorstOf
Machine Creation Service Performance Rollup WorstOf
App Library Service Performance Rollup WorstOf
Analytics Service Performance Rollup WorstOf
XAXD Delivery Groups Collection
AvailabilityHealth
Delivery Groups Availability Rollup WorstOf
PerformanceHealth
Delivery Groups Performance Rollup WorstOf
XAXD Hypervisor Connections Collection
AvailabilityHealth
Hypervisor Connections Availability Rollup WorstOf
Citrix MPXAXD Machine Agent
AvailabilityHealth
Controller Connection Availability Rollup WorstOf
XAXD Site
AvailabilityHealth
Application Folder Availability Rollup WorstOf
Site Data Collector Availability Rollup WorstOf
PerformanceHealth
Application Folder Performance Rollup WorstOf
Site Data Collector Performance Rollup WorstOf
ConfigurationHealth
Site Data Collector Configuration Rollup WorstOf
XAXD Site Data Collector
AvailabilityHealth
Delivery Groups Collection Availability Rollup WorstOf
Hypervisor Connections Collection Availability Rollup WorstOf
PerformanceHealth
Delivery Groups Collection Performance Rollup WorstOf
XAXD Sites
AvailabilityHealth
Site Availability Rollup WorstOf
PerformanceHealth
Site Performance Rollup WorstOf

Top


Tasks

Target Display Name Description Parameters
XAXD Delivery Controller Computer Role Check Installation Prerequisites for Citrix MPXAXD Agent
Check installation prerequisites for Citrix Management Pack for XenApp and XenDesktop MP Agent.
          
Parameters:
- AgentInstallationSource: Agent installation and configuration source is specified as either with the management server name where XenApp and XenDesktop MP will be installed or with the UNC path where XenApp and XenDesktop MP Agent installation and configuration files exist. If not specified, the task tries to identify the management server automatically.
          
Parameter Def.value
AgentInstallationSource
XAXD Delivery Controller Computer Role Check Requirements and Configuration for Citrix MPXAXD Agent
Checks if a Citrix system meets the requirements for Citrix Management Pack for XenApp and XenDesktop Agent.
---
XAXD Delivery Controller Computer Role Collect Support Information for Citrix MPXAXD Agent
Collects support information for XenApp and XenDesktop Management Pack Agent.
---
XAXD Delivery Controller Computer Role Install Citrix MPXAXD Agent
Installs Citrix Management Pack Agent for XenApp and XenDesktop on the Citrix system.

Parameters:
- AgentInstallationSource: Agent installation and configuration source is specified as either with the management server name where XenApp and XenDesktop MP was installed or with the UNC path where XenApp and XenDesktop MP Agent installation and configuration files exist. If not specified, the task tries to identify the management server automatically.
- AgentInstallationDestination: Specify the agent installation destination folder optionally.
- UpgradeAgent: If true, then existing agent is uninstalled initially and then the new one is installed. Before the agent is upgraded, put the managed node in the maintenance during the installation.
- IgnorePrereqCheck: Do not use it. It should be used only for support purposes.
Parameter Def.value
AgentInstallationDestination
AgentInstallationSource
UpgradeAgent false
IgnorePrereqCheck false
Debug false
XAXD Delivery Controller Computer Role Uninstall Citrix MPXAXD Agent
Uninstalls Citrix Management Pack Agent for XenApp and XenDesktop from the Citrix system
---
XAXD Delivery Controller Computer Role Update Configuration on Citrix MPXAXD Agent
Updates Configuration on Citrix Management Pack Agent for XenApp and XenDesktop.

Parameters:
- AgentInstallationSource: Agent installation and configuration source is specified as either with the management server name where XenApp and XenDesktop MP was installed or with the UNC path where XenApp and XenDesktop MP Agent installation and configuration files exist. If not specified, the tasks tries to identify the management server automatically.
Parameter Def.value
AgentInstallationSource
XAXD Delivery Group Desktop OS Static Unused Assigned Desktops
This task helps in identifying assigned machines in a static Desktop OS delivery group that are not used anymore. This is done by showing assigned machines to which users didn’t connect to in the last n days.
By default, machines that were not connected to in the last n days, but are currently in use or in a disconnected state, are not shown. To list of such machines, set IncludeInUse/IncludeDisconnected parameters to true.

Parameters:
-IncludeInUse: choose whether to list machines that are currently in use but last connection was not done in the last n days.
-IncludeDisconnected: choose whether to list machines that are currently disconnected but last connection was not done in the last n days.
-NumberOfDays: number of days user didn’t connect to a machine. For example, to list machines users didn’t connect to in the last 30 days, enter 30 for this parameter.
-IncludeAssignedNotConnectedYet: choose whether assigned machines that were not yet connected to are listed.
          
Parameter Def.value
NumberOfDays 60
IncludeInUse false
IncludeDisconnected false
IncludeAssignedNotConnectedYet false
Citrix MPXAXD Machine Agent Proxy Computer Role Collect Support Information for Citrix MPXAXD Machine Agent
Collects support information for MPXAXD Machine Agent
---
Citrix MPXAXD Machine Agent Proxy Computer Role Update Configuration on Citrix MPXAXD Machine Agent
Parameters:
- AgentInstallationSource: Agent installation and configuration source is specified as either with the management server name where XenApp and XenDesktop MP was installed or with the UNC path where MPXAXD Machine Agent Proxy installation and configuration files exist. If not specified, the tasks tries to identify the management server automatically.
Parameter Def.value
AgentInstallationSource
Citrix MPXAXD Machine Agent Proxy Computer Role Check Requirements and Configuration for Citrix MPXAXD Machine Agent
Checks if a Citrix system meets the requirements for MPXAXD Machine Agent.
---
XAXD Service Windows Start Service
Attempts to start the Windows service.
Parameter Def.value
TimeoutSeconds 300
XAXD Service Windows Stop Service
Attempts to stop the Windows service.
Parameter Def.value
TimeoutSeconds 300

Console Tasks

Target Display Name Description
Citrix MPXAXD Machine Agent Proxy Computer Role Start Citrix Director
This task attempts to start the Citrix Director web console in the context of a user. It's primary intent is to be used on session and logon alerts that are triggered by Citrix Management Pack for XenApp and XenDesktop.

Views

Folder Display Name Description Target Category
Citrix Library Citrix Management Topology
This view displays topology for all Citrix Management Packs.
Citrix Management Topology
Citrix Library XenApp/XenDesktop Delivery Controller Computers
Displays computers with installed XenApp/XenDesktop delivery controller version 7 and above.
Object HealthState
Citrix Library XenApp/XenDesktop Machine Monitoring Proxy Computers
This view displays all computers with Machine Monitoring Proxy installed.
Citrix MPXAXD Machine Agent Proxy Computer Role HealthState
Citrix XenApp and XenDesktop XenApp/XenDesktop Alerts
Displays the XenApp/XenDesktop alerts generated by management pack monitors and rules.
XAXD Site Alerts
Citrix XenApp and XenDesktop XenApp/XenDesktop Events
Displays specific XenApp/XenDesktop related events from Windows event log.
XAXD Site Event
Citrix XenApp and XenDesktop XenApp/XenDesktop Health State
Displays the overall health of XenApp/XenDesktop components: sites, controllers, hypervisor hosts, delivery groups.
Object Operations
Citrix XenApp and XenDesktop XenApp/XenDesktop Topology
Displays the XenApp/XenDesktop components topology.
XAXD Sites Topology
Citrix XenApp and XenDesktop->Controllers Delivery Controller Services Performance
Displays the XenApp/XenDesktop Delivery Controller services performance metrics (% Processor Time, Memory Private Bytes, Memory Working Set, etc.).
XAXD Delivery Controller Service Performance
Citrix XenApp and XenDesktop->Controllers Delivery Controller Services State
Displays the XenApp/XenDesktop Delivery Controller services state.
XAXD Delivery Controller Service State
Citrix XenApp and XenDesktop->Controllers Delivery Controller State
Displays the XenApp/XenDesktop Delivery Controller state.
XAXD Delivery Controller State
Citrix XenApp and XenDesktop->Delivery Groups Applications
Displays the XenApp/XenDesktop application health.
XAXD Application Operations
Citrix XenApp and XenDesktop->Delivery Groups Delivery Group State
Displays the XenApp/XenDesktop Delivery Group state. Following properties are displayed for each delivery group: Enabled, Maintenance Mode, Allocation (Random | Static), Number of machines, Machine Type (Server OS | Desktop OS), Session Support
XAXD Delivery Group State
Citrix XenApp and XenDesktop->Delivery Groups Desktop OS Random - Available Machines
Displays number of ready desktops in a Desktop OS Random delivery group. Ready desktops are machines which are running and are ready for brokering (are ready to be used by users). Only one user sessions is allowed on one Desktop OS machine.
XAXD Delivery Group PerformanceCollection
Citrix XenApp and XenDesktop->Delivery Groups Desktop OS Random %Usage
Displays the percentage of Desktop OS machines in Desktop OS Random delivery group on which user sessions (both connected and disconnected) are running.
XAXD Delivery Group Random PerformanceCollection
Citrix XenApp and XenDesktop->Delivery Groups Desktop OS Static %Usage
Displays the percentage of assigned desktops in a Desktop OS Static delivery group.
XAXD Delivery Group Static PerformanceCollection
Citrix XenApp and XenDesktop->Delivery Groups Server OS Available Server Machines
Displays number of available servers in Server OS delivery group. Available servers are machines that are running, are registered with the delivery controller, are not in maintenance mode and have Load Evaluator Index less than 100%.
XAXD Delivery Group PerformanceCollection
Citrix XenApp and XenDesktop->Delivery Groups Server OS Load Performance
Displays delivery group metrics related to delivery group load usage (total load/capacity usage, avg. load index and free load).
XAXD Delivery Group Server OS PerformanceCollection
Citrix XenApp and XenDesktop->Delivery Groups Server OS Load Usage
Displays load/capacity usage for a delivery group.
XAXD Delivery Group Server OS Performance
Citrix XenApp and XenDesktop->Delivery Groups Server OS Performance
Displays several metrics like delivery group load, number of active sessions and number of available servers in one view.
XAXD Delivery Group Server OS Performance
Citrix XenApp and XenDesktop->Delivery Groups Sessions
Displays disconnected and active sessions in the delivery groups.
XAXD Delivery Group PerformanceCollection
Citrix XenApp and XenDesktop->Delivery Groups Unregistered Machines
Displays the number of unregistered machines for a delivery group. Unregistered machines are machines that can be either turned off or turned on but are not registered with a controller.
XAXD Delivery Group PerformanceCollection
Citrix XenApp and XenDesktop->Delivery Groups User Logon Performance
Displays average user logon duration and number of logons for the selected delivery groups.
XAXD Delivery Group PerformanceCollection
Citrix XenApp and XenDesktop->Machines Failed Registrations
Displays failed registration alerts for power managed desktop or server machines that failed to register to the delivery controllers.
XAXD Delivery Group Alerts
Citrix XenApp and XenDesktop->Machines Server OS Machine Alerts
Displays performance alerts for Server OS machines.
Object Alerts
Citrix XenApp and XenDesktop->Machines Server OS Machine Performance
Displays all collected metrics for Server OS machines (LoadIndex).
XAXD Server OS Machine PerformanceCollection
Citrix XenApp and XenDesktop->Machines Server OS Machines
Displays health state of Server OS machines.
XAXD Server OS Machine Operations
Citrix XenApp and XenDesktop->Sessions Session Alerts
Displays performance alerts for (Servers OS and Desktop OS) sessions.
Citrix MPXAXD Machine Agent Proxy Computer Role Alerts
Citrix XenApp and XenDesktop->Sites Connected Users on Site
Displays number of concurrent users on site. Only distinct users having active sessions are counted while users having disconnected sessions are not.
XAXD Site Data Collector PerformanceCollection
Citrix XenApp and XenDesktop->Sites Hypervisor Connection State
Displays the XenApp/XenDesktop Hypervisor Connection state.
XAXD Site Hypervisor Connection Operations
Citrix XenApp and XenDesktop->Sites Sessions on Site
Displays number of active and disconnected sessions on site.
XAXD Site Data Collector PerformanceCollection
Citrix XenApp and XenDesktop->Sites Site State
Displays the XenApp/XenDesktop Site state.
XAXD Site State
Citrix XenApp and XenDesktop->Sites User Logon Performance
Displays average user logon duration and number of logons for the selected site.
XAXD Site PerformanceCollection
Citrix XenApp and XenDesktop->User Connections User Failed Connections
Displays alerts about user failed connections.
XAXD Site Data Collector Alerts
Citrix XenApp and XenDesktop->User Connections User Logon Alerts
Displays alerts about user logons.
XAXD Delivery Group Alerts

Reports

Target Name Description
User - Failed Connections
This report displays failed connection details for selected users, such as Connection Launch Time, Time to Connection Failure which is the time difference in seconds between Launch Time and Failure Time, Failure Type, Failure Reason etc.

Connection failure types: 
            
-Client Connection Failures: Failures due to the inability of the client side to complete the session connection. For example, connection timed out, server was not reachable.
-Machine Failures: Connection failures that are the result of the machine being in a failed state or failure to start up or respond.
-Unavailable Capacity: Failures due to the configured capacity of a particular delivery group having been completely consumed. For example, too many users logged into a Server Desktop OS delivery group or a user accessing a Pooled Random delivery group while all the machines in the delivery group are already assigned to other users.
-Unavailable Licenses: Failures that occur when the delivery controller is unable to acquire a license from the license server to launch the session.
-Configuration Errors: Failures caused by configuration errors. For example, an administrator places a Delivery Group or a particular machine in Maintenance mode.

Connection failure reasons:
            
-Session Preparation: Session prepare request from Broker service to VDA failed.
-Registration Timeout: VDA did not register in time after being powered on for session launch.
-Connection Timeout: Client did not connect to VDA after VDA was prepared for session launch.
-Licensing: License request failed (typically no license available).
-Ticketing: Failure during ticketing, indicating that the client connection to VDA does not match the brokered request.
-Other: General unresolved errors between client and VDI.
-General Fail: General unresolved errors during initial brokering operation.
-Maintenance Mode: Machine or delivery group in maintenance mode.
-Application Disabled: Application can no longer be used and has been disabled by the admin.
-License Feature Refused: Feature being used is not licensed (e.g. license doesn’t allow use of multi-session VDAs).
-Session Limit Reached: No more sessions allowed (e.g. launching second session on VDI VDA).
-Disallowed Protocol: Resource doesn’t allow protocol requested by session launch.
-Resource Unavailable: Resource has been removed/disabled since enumeration.
-Active Session Reconnect Disabled: Session is already connected to a different endpoint but session stealing is disabled.
-No Session To Reconnect: Specified session could not be found during reconnect.
-Spin Up Failed: VDA could not be powered-on for session launch.
-Refused: VDA actively refused session prepare request.
-Configuration Set Failure:Failed to send required configuration data to VDA prior to session launch.
-NoMachineAvailable: No machine available for launch (e.g. all shared VDI machines in group are in use).
-Machine Not Functional: Non-power-managed assigned machine not registered.
 
Report depends on the following data collecting rule(s): -Publish Connections and Logons Data (Performance DW)
          
XAXD Application Application - Availability
This report shows availability of applications and delivery groups in which applications are published during the selected report duration. Application is marked as available at a specific time if a new user could start it at that time, i.e. there is at least one delivery group publishing that application which has a machine that can take a new connection (at least one machine is registered, not fully loaded and not in maintenance mode).
First area shows the availability of an application.
Application availability is displayed as relative time (percentage), absolute time (in hours, minutes and seconds) for whole reporting time range. Stacked column chart displays application availability in percentage either by hour, day or month depending on chart scale selected. By clicking on column, data can be drilled down.
A click on the “Open application downtime periods report” launches the sub-report that shows application downtime periods with exact start, end time and duration of each specific down time period.
Second area shows the availability of each delivery group that hosts the application in similar fashion as first area shows availability for applications.
Report depends on the following unit monitor(s): - Delivery Group Availability - Delivery Group In Maintenance
          
XAXD Application Application - User Activity
This report shows for each selected application which users have been using it and when.  For each specific usage also duration, IP address of client computer and machine name on which application was running is displayed.
Clicking on a user name runs the User – Desktop/Application Activity (Troubleshooting) report for the selected user.
For all application usages for specific application following summary data is shown:  number of all usages, cumulative duration of all usages, number of unique users.

By default application usages are shown for full duration of a session regardless if session is in active or disconnected state. By setting “Show application usages on” parameter to “Active sessions only”, only usages when user was actively using the application (session was active) are shown.

Report shows all the usages that fall in reporting time period at least partly.

Report depends on the following data collecting rule(s): - Publish Application Use Data (Performance DW), - Publish Connections and Logons Data (Performance DW), - Publish Session Discovery (Performance DW), Publish Machine Discovery (Performance DW)
          
XAXD Application Application - User Sessions
This report displays the number of all (active and disconnected) concurrent sessions per application.
Depending on selected data aggregation, maximum number of sessions per hour or day is displayed.
Report depends on the following data collecting rule(s): - Number of All Sessions per Application (Performance DW)
          
XAXD Delivery Group Delivery Group - Active Sessions (Top N)
Top delivery groups by active sessions.
Report depends on the following data collecting rule(s): -Number of Active Sessions (Performance DB DW)
          
XAXD Delivery Group Delivery Group - Active Sessions (Trending)
Report predicting the future number of active sessions in delivery group based on performance history.
Report depends on the following data collecting rule(s): -Number of Active Sessions (Performance DB DW)
          
XAXD Delivery Group Delivery Group - Desktop User Activity
This report shows for each selected Delivery Group which users have been using desktop and when.
For each specific usage also duration, IP address of client computer and machine name on which desktop was running is displayed.
Clicking on a user name runs the User – Desktop/Application Activity (Troubleshooting) report for the selected user.
For all desktop usages for specific delivery group following summary data is shown:  number of all usages, cumulative duration of all usages, number of unique users.

By default desktop usages are shown for full duration of a session regardless if session is in active or disconnected state. By setting “Show desktop usages on” parameter to “Active sessions only”, only usages when user was actively using the desktop (session was active) are shown.

Report shows all the usages that fall in reporting time period at least partly. 

Report depends on the following data collecting rule(s): - Publish Application Use Data (Performance DW), - Publish Connections and Logons Data (Performance DW), - Publish Session Discovery (Performance DW), Publish Machine Discovery (Performance DW)
          
XAXD Delivery Group Delivery Group - Failed Connections
This report displays the number of failed connections on delivery groups, summarized by Failure Types and Failure Reasons.
Report can be run using the automatic, 5 minutes, hourly and daily data scales. Automatic setting displays failed connections aggregated as daily if reporting range is longer than 2 days, hourly if reporting range is less or equal 2 days and more than 5 hours and as 5 minutes if it is less than 5 hours.

Connection failure types:

-Client Connection Failures: Failures due to the inability of the client side to complete the session connection. For example, connection timed out, server was not reachable.
-Machine Failures: Connection failures that are the result of the machine being in a failed state or failure to start up or respond.
-Unavailable Capacity: Failures due to the configured capacity of a particular delivery group having been completely consumed. For example, too many users logged into a Server Desktop OS delivery group or a user accessing a Pooled Random delivery group while all the machines in the delivery group are already assigned to other users.
-Unavailable Licenses: Failures that occur when the delivery controller is unable to acquire a license from the license server to launch the session.
-Configuration Errors: Failures caused by configuration errors. For example, an administrator places a Delivery Group or a particular machine in Maintenance mode.

Connection failure reasons:

-Session Preparation: Session prepare request from Broker service to VDA failed.
-Registration Timeout: VDA did not register in time after being powered on for session launch.
-Connection Timeout: Client did not connect to VDA after VDA was prepared for session launch.
-Licensing: License request failed (typically no license available).
-Ticketing: Failure during ticketing, indicating that the client connection to VDA does not match the brokered request.
-Other: General unresolved errors between client and VDI.
-General Fail: General unresolved errors during initial brokering operation.
-Maintenance Mode: Machine or delivery group in maintenance mode.
-Application Disabled: Application can no longer be used and has been disabled by the admin.
-License Feature Refused: Feature being used is not licensed (e.g. license doesn’t allow use of multi-session VDAs).
-Session Limit Reached: No more sessions allowed (e.g. launching second session on VDI VDA).
-Disallowed Protocol: Resource doesn’t allow protocol requested by session launch.
-Resource Unavailable: Resource has been removed/disabled since enumeration.
-Active Session Reconnect Disabled: Session is already connected to a different endpoint but session stealing is disabled.
-No Session To Reconnect: Specified session could not be found during reconnect.
-Spin Up Failed: VDA could not be powered-on for session launch.
-Refused: VDA actively refused session prepare request.
-Configuration Set Failure:Failed to send required configuration data to VDA prior to session launch.
-No Machine Available: No machine available for launch (e.g. all shared VDI machines in group are in use).
-Machine Not Functional: Non-power-managed assigned machine not registered.

Report depends on the following data collecting rule(s): -Publish Connections and Logons Data (Performance DW)
          
XAXD Delivery Group Delivery Group - Logon Details (Troubleshooting)
This report displays average user logon time and number of logons per delivery group. Logon duration time includes the following phases:

Brokering - The time taken to decide which desktop to assign to the user.
VM start - In case the session required a machine to be started, the time taken to boot the desktop.
HDX connection - The time taken to complete the steps required in setting up the HDX connection from the client to the VM, dependent on the network.
Authentication - The time taken to complete authentication to the remote session.
Profile load - The phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).
GPOs - During this phase, group policy objects are applied/defined on the Domain Controller.
Logon scripts - This phase covers the time taken for the logon scripts to be executed.
Interactive session - The phase starts in parallel with GPOs phase and covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.
            
Report depends on the following data collecting rule(s):
- Number of Logons (Performance DB DW)
- Total Logon Authentication Time (Performance DW)
- Total Logon Brokering Time (Performance DW)
- Total Logon Duration (Performance DW)
- Total Logon GPOs Time (Performance DW)
- Total Logon HDX Connection Time (Performance DW)
- Total Logon Interactive Session Time (Performance DW)
- Total Logon Scripts Execution Time (Performance DW)
- Total Logon Profile Load Time (Performance DW)
- Total Logon VM Start Time (Performance DW)
XAXD Delivery Group Delivery Group - Logon Duration Distribution
This report shows a breakdown of user logon durations into 5-second slots for a selected delivery group.
Logon duration is the time it takes for all logon phases to complete, including Brokering Time, VM Start Time, Authentication Time, Profile Load Time, etc.

Report depends on the following data collecting rule(s): - Publish Connections and Logons Data (Performance DW).
          
XAXD Delivery Group Delivery Group - User Growth Over Time
This report shows how many unique (distinct) users are logging in the selected delivery group over time.
The first chart shows, cumulatively, the number of unique (distinct) users connecting to the delivery group over time. Each data point represents increase in number of unique users from the first day of the reporting interval.
The second chart shows unique user growth per day, i.e. number of unique users that newly connected on a specific day.
Report depends on the following data collecting rule(s): - Publish Connections and Logons Data (Performance DW).
          
XAXD Delivery Group Delivery Group Server OS - Machine Performance
           This report shows average performance data across all running (registered and not in the maintenance mode) server OS machines in a delivery group. It also lists all machines that were in the running state at some point during the reporting period, together with their average performance metrics.

              Displayed metrics:
              - CPU util (%) - CPU utilization.
              - Physical Memory (%) - Percent of physical memory used by processes on a system.
              - Load Index (%) - Citrix Load Index on the server, defined by the Citrix Load Management policy settings. The value is expressed as a percentage. If the value reaches 100%, the server OS machine forbids additional connections.
              - Running machines - Number of machines in the delivery group that are running (are registered and are not in the maintenance mode) and for which performance data was collected.
              - Avg. Sessions per Machine - Average number of sessions (active and disconnected) across machines in the delivery group. The value is based on the machines for which performance data was collected.
              - Max. Sess. On Delivery Group - Maximum number of sessions in the delivery group.
              - Disk Latency (ms) - Disk latency in milliseconds.
              - Network Receive (KB/s) - Network traffic towards the machine.
              - Network Send (KB/s) - Network traffic outwards the machine.
              
              Table specific metric:
              - Max Sessions - The maximum of the hourly average values for the reported time period.

            Report depends on the following data collecting rule(s):
            - Publish Machine Discovery (Performance DW)
            - Publish Server OS Machine Performance (n) (Performance DW), n=[1-3]
            - Number of All Sessions (Performance DB DW)
          
XAXD Delivery Group User - Logon Activity (Troubleshooting)
This report displays all logons for selected user. Logon duration time includes the following phases:

Brokering - The time taken to decide which desktop to assign to the user.
VM start - In case the session required a machine to be started, the time taken to boot the desktop.
HDX connection - The time taken to complete the steps required in setting up the HDX connection from the client to the VM, dependding on the network.
Authentication - The time taken to complete authentication to the remote session.
Profile load - The phase starts just after the user credentials are validated and lasts until the profile is downloaded from the profile storage (network share).
GPOs - During this phase, group policy objects are applied/defined on the Domain Controller.
Logon scripts - This phase covers the time taken for the logon scripts to be executed.
Interactive session - The phase starts in parallel with GPOs phase and covers Citrix specific activity before it launches the requested application: launching seamless windows engine shell, auto creation of client printers and ICA client update process.

Report depends on the following data collecting rule(s):
- Publish Connections and Logons Data (Performance DW)
XAXD Delivery Group Desktop OS Static Delivery Group Desktop OS Static - Delivery Group Usage (Top N)
The percentage of machines already assigned to some user for a Desktop OS Static delivery group.
Report depends on the following data collecting rule(s): -Desktop OS Static Delivery Group Usage (%) (Performance DB DW)
          
XAXD Delivery Group Desktop OS Static Delivery Group Desktop OS Static - Delivery Group Usage (Trending)
Report predicting the future Desktop OS Random delivery group usage based on performance history.
Report depends on the following data collecting rule(s): -Desktop OS Static Delivery Group Usage (%) (Performance DB DW)
          
XAXD Delivery Group Desktop OS Random Delivery Group Desktop OS Random - Delivery Group Usage (Top N)
The percentage of machines in use for a Desktop OS Random delivery group.
Report depends on the following data collecting rule(s): -Desktop OS Random Delivery Group Usage (%) (Performance DB DW)
          
XAXD Delivery Group Desktop OS Random Delivery Group Desktop OS Random - Delivery Group Usage (Trending)
Report predicting the future Desktop OS Random delivery group usage based on performance history.
Report depends on the following data collecting rule(s): -Desktop OS Random Delivery Group Usage (%) (Performance DB DW)
          
XAXD Delivery Group Desktop OS Random Delivery Group Desktop OS Random - Ready Pool Settings Optimizer
This report shows the number of ready desktops for Desktop OS Random delivery group for configurable time range (default 2 weeks). By default graph shows the minimum, average, and maximum number of ready desktops throughout the day by hour, allowing you to compare, for example, what the minimum, average, and maximum values were at 8:00-9:00 AM for all days defined by business hours. 

By selecting “Weekly by weekdays” Histogram, report will show average, minimum and maximum number of ready desktops by week days. This allows you to compare, for example, what the minimum, average, and maximum values were for all Mondays being in defined time range. By tweaking business hours you can further define which part of the day you are interested in. 

Using this report you can determine how well the XenDesktop site maintains the "Ready Pool Settings" levels, which are defined for every delivery group. If you notice that the XenDesktop site struggles to maintain the required level of ready desktops at a specific time of the day, you can increase the "Ready Pool Settings" accordingly. Similarly, if you see a very "stable" situation at a specific time of the day, you can most probably decrease the number of ready desktops waiting for users to connect. 
Report depends on the following data collecting rule(s): -Number of Ready Desktops (Performance DB DW)
          
Citrix MPXAXD Machine Agent Proxy Computer Role Server OS Machine - Performance (Troubleshooting)
This report shows server performance for selected Server OS machines. Displayed metrics: CPU, Memory, Disk, Network, Load Index, average Latency and ICA RTT for sessions on server.
          
Overall metrics:
- CPU util (%) - CPU utilization
- Physical Memory (%) - Percent of physical memory used by processes on a system.
- Virtual Memory (%) - Percent of virtual memory used by processes on a system.
- Load Index (%) - Citrix Load Index on a server, defined by Citrix Load Management policy settings. Values are in percent. If server load reaches 100%, Server OS machine no longer allows new connections. 
- # of session - Number of (active and disconnected) sessions on server

Memory metrics:
- Physical Memory (MB) - Physical memory used by processes on a system in MB.
- Virtual Memory (MB) - Virtual memory used by processes on a system in MB.
- Hard Page Faults per Second - Memory page faults per second is the rate at which pages are read from or written to disk to resolve hard page faults.  High value typically indicates a memory bottleneck. 

Disk metrics:
- Disk Read (KB/s) - Rate at which bytes are transferred from the disk during read operations.
- Disk Write (KB/s) - Rate at which bytes are transferred to the disk during write operations.
- Disk IOPS (IO/s) - Rate of read and write operations on the disk.
- Disk Latency (ms) - Disk latency in ms.

Network metrics:
- Network Send (KB/s) - Network traffic from machine.
- Network Receive (KB/s) - Network traffic to machine.

Citrix metrics:
- Avg. Session Latency - Average network latency of all active sessions on a server in ms.
- Avg. Session ICA RTT -  Average ICA Round Trip Time of all active sessions on a server in ms.


Report depends on the following data collecting rule(s):
- Publish Machine Discovery (n) (Performance DW), n=[1-3]
- Publish Server OS Machine Performance (n) (Performance DW), n=[1-3]
		  
Citrix MPXAXD Machine Agent Proxy Computer Role User - Desktop/Application Activity (Troubleshooting)
This report shows desktop and application activity for selected users. Each activity contains Connection data (Application/Desktop name, Logon Time, Start and End Time etc.), Citrix XenApp/XenDesktop data (Machine, Delivery Group etc.) and Hypervisor hostname.
Activity also includes session performance data for the duration of connection, such as CPU, Memory, Disk, Network, Session Latency and Session ICA RTT.

CPU metrics:
- CPU util (%) - CPU utilization.

Memory metrics:
- Physical Memory (MB) - Physical memory used by processes in MB
- Virtual Memory (MB) - Virtual memory used by processes in MB.
- Physical Memory (%) - Percent of physical memory used by processes.
- Virtual Memory (%) - Percent of virtual memory used by processes.
- Hard Page Faults per Second - Memory page faults per second is the rate at which pages are read from or written to disk to resolve hard page faults. High value typically indicates a memory bottleneck.

Disk metrics:
- Disk Read (KB/s) - Rate at which bytes are transferred from the disk during read operations.
- Disk Write (KB/s) - Rate at which bytes are transferred to the disk during write operations.
- Disk Transfers (IO/s) - Rate of read and write operations on the disk.
- Disk Latency (ms) - Disk latency in ms.

Network metrics:
- Network Send (KB/s) - Network traffic from machine.
- Network Receive (KB/s) - Network traffic to machine.

Citrix metrics:
- Session Network Input (KB/s) - Network input of a session.
- Session Network Output (KB/s) - Network output of a session.
- Session Latency - Network latency of a session in ms.
- Session ICA Round Trip Time (RTT) - ICA Round Trip Time of a session in ms.

Note: Session performance data is only visible for the last 10 days, which is the default grooming interval for raw data performance on Session dataset. To increase retention interval refer to MPXAXD User Guide.

Report depends on the following data collecting rule(s):
- Publish Application Use Data (Performance DW)
- Publish Connections and Logons Data (Performance DW)
- Publish Session Discovery (1-5) (Performance DW)
- Publish Session Performance (1-12) (Performance DW)
          
XAXD Server OS Machine Server OS Machine - Active Sessions
This report shows max/min and average number of active sessions for selected Server OS Machine(s).
Report depends on the following data collecting rule(s): -Number of Active Sessions (Performance DW)
          
XAXD Server OS Machine Server OS Machine - Active Sessions (Top N)
This report shows top/bottom N Server OS machines according to maximum number of active sessions.
Report depends on the following data collecting rule(s): -Number of Active Sessions (Performance DW)
          
XAXD Server OS Machine Server OS Machine - Performance (Plan and Manage)
          
XAXD Site Delivery Group - Logons per Week (Plan & Manage)
This report displays average logon time and number of logons by delivery group in selected sites for each week.

Report depends on the following data collecting rule(s):
- Number of Logons (Performance DB DW)
- Total Logon Duration (Performance DW)
XAXD Site Site - Logon Duration Distribution
This report shows a breakdown of user logon durations into 5-second slots for a selected site.
Logon duration distribution is shown also for each delivery group in the site.
Logon duration is the time it takes for all logon phases to complete, including Brokering Time, VM Start Time, Authentication Time, Profile Load Time, etc.
            
Report depends on the following data collecting rule(s): - Publish Connections and Logons Data (Performance DW).
          
XAXD Site Site – User Concurrency Across Sites
This report shows maximum number of concurrently connected unique users across selected sites for a given time interval. 
Besides this single value, also maximum number of concurrently connected unique users for each day in a reporting interval is also shown on graph and in the table.
XAXD Site Site - User Growth Over Time
This report shows how many unique (distinct) users are logging in the selected site over time.
The first chart shows, cumulatively, the number of unique (distinct) users connecting to the site over time. Each data point represents increase in number of unique users from the first day of the reporting interval.
The second chart shows unique user growth per day, i.e. number of unique users that newly connected on a specific day.
Report depends on the following data collecting rule(s): - Publish Connections and Logons Data (Performance DW).
          
XAXD Site Data Collector Site - Active Sessions (Trending)
Report predicting the future number of active sessions on a site based on performance history.
Report depends on the following data collecting rule(s): -Number of Active Sessions (Performance DB DW)
          
XAXD Site Data Collector Site - Connected Users (Trending)
Report predicting the future number of connected users on a site based on performance history.
Report depends on the following data collecting rule(s): -Number of Concurrent Users (Performance DB DW)
          

Recoveries

Target Display Name Description
Citrix MPXAXD Agent Service Restart Restarts the Windows Service

Disabled by Default

Disabled Monitors

XAXD Delivery Group

Monitor Management Pack
Avg. User Logon Authentication Time Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon Brokering Time Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon GPOs Time Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon HDX Connection Time Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon Interactive Session Time Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon Scripts Execution Time Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon Profile Load Time Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon VM Start Time Citrix Management Pack for XenApp and XenDesktop (EndUser)
Number of Active Sessions Citrix Management Pack for XenApp and XenDesktop
Number of All Sessions Citrix Management Pack for XenApp and XenDesktop

Top


XAXD Delivery Group Desktop OS Static

Monitor Management Pack
Desktop OS Static Delivery Group Usage (in %) Citrix Management Pack for XenApp and XenDesktop

Top


XAXD Delivery Group Desktop OS Random

Monitor Management Pack
Number of Ready Desktops Too Low Citrix Management Pack for XenApp and XenDesktop

Top


XAXD Site Data Collector

Monitor Management Pack
Number of Active Sessions Citrix Management Pack for XenApp and XenDesktop
Number of All Sessions Citrix Management Pack for XenApp and XenDesktop
Number of Currently Connected Users Citrix Management Pack for XenApp and XenDesktop

Top


Disabled Rules

XAXD Delivery Group

Rule Management Pack
Avg. User Logon Authentication Time (Performance DB) Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon Brokering Time (Performance DB) Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon GPOs Time (Performance DB) Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon HDX Connection Time (Performance DB) Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon Interactive Session Time (Performance DB) Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon Scripts Execution Time (Performance DB) Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon Profile Load Time (Performance DB) Citrix Management Pack for XenApp and XenDesktop (EndUser)
Avg. User Logon VM Start Time (Performance DB) Citrix Management Pack for XenApp and XenDesktop (EndUser)
User Logon Process - Authentication Time (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)
User Logon Process - Brokering Time (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)
User Logon Process - Applying GPOs Time (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)
User Logon Process - HDX Connection Time (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)
User Logon Process - Interactive Session Time (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)
User Logon Process - Logon Scripts Time (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)
User Logon Process - Profile Load Time (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)
User Logon Process - VM Start Time (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)

Top


XAXD Site Data Collector

Rule Management Pack
Failed Connection (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)
Number of All Sessions (Performance DB DW) Citrix Management Pack for XenApp and XenDesktop

Top


Citrix MPXAXD Machine Agent Proxy Computer Role

<td class="w
Rule Management Pack
Desktop OS Session Bandwidth Usage (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)
Server OS Session Physical Memory Usage (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)
Server OS Session Bandwidth Usage (Alert) Citrix Management Pack for XenApp and XenDesktop (EndUser)