Citrix SCOM Management Pack for XenApp 6.x Reference Guide

Summary

Alerts if an application is currently in disabled state. Disabled applications are not available to end-users.

Summary

This monitor checks if Citrix XenApp MP Agent is operational.

Configuration

Citrix XenApp MP Agent may not be operational for many reasons, including:

• Citrix IMA service is not running

• Citrix MFCOM service is not running

• Citrix XenApp MP configuration is not valid

To get detailed information why agent is not operational run "Check Requirements and Configuration for Citrix MPXA Agent" task.

Summary

The Citrix XenApp MP Agent mandatory service is not running.

Causes

A service can stop for many reasons, including:

Resolutions

Start the service from the “Actions” pane.

Additional

The topology and the health state of your Citrix XenApp environment managed by this agent will not be properly updated if the service is not running.

Summary

The Windows 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.

Summary

Alerts if the number of sessions in an active state is high. Sessions in an active state are end-user sessions that are currently in progress. This helps to identify a potentially overloaded server, or if load balancing is not working correctly. See also the XenApp Session Summary Performance View for details.

Summary

Alerts if the total number of sessions in all possible states is high. See also the XenApp Session Summary Performance View for details.

Summary

Alerts if the number of sessions in a disconnected state is high. Large number of disconnected sessions may be normal, but can also indicate a sudden drop of end-user connectivity. See also the XenApp Session Summary Performance View for details.

Summary

Alerts if the number of sessions in a down state is high. Sessions in a down state typically indicate sessions that did not log off correctly / hung during logoff. Sometimes it is even difficult to “kill” them, so the only thing that helps is a reboot. See also the XenApp Session Summary Performance View for details.

Summary

Alerts if there is a large number of files across all user profiles.

Summary

Alerts if there is a large volume of files across all user profiles.

Summary

Monitors free space (in MB) on XenApp installation drive.

Summary

Monitors the percentage of free space on XenApp installation drive.

Summary

Alerts if logons to the server are disabled. During the maintenance hours, logons to XenApp servers are typically disabled to prevent users to connect to them. This alert will remind admins that logons to a server need to be re-enabled.

Summary

This monitor checks the number of non-XML-based enumerations (requests for application lists) per second over multiple consecutive samples.

By default monitor is disabled because baseline needs to be established in your environment before appropriate threshold can be defined that would indicate load that could lead to decreased XML Broker performance.

Configuration

Overridable parameters:

Additional

To see monitor performance values, open XenApp Server Performance view.

Summary

This monitor checks the time (in milliseconds) required to resolve the Least-Loaded Server during an application launch. Alert is triggered when threshold is exceeded for configured number of consecutive samples.

By default monitor is disabled because baseline would need to be established in your environment to account for increases during peak logon times before accurate thresholds can be defined.

Configuration

Overridable parameters:

Additional

To see monitor performance values, open XenApp Server Performance view.

Summary

This monitor checks number of XML-based enumerations per second handled by XML Broker over multiple consecutive samples. It indicates number of Web Interface/StoreFront application enumerations (and logons) per second handled by specific XML broker.

By default monitor is disabled because baseline needs to be established in your environment before appropriate threshold can be defined that would indicate load that could lead to decreased XML Broker performance.

Configuration

Overridable parameters:

Additional

To see monitor performance values, open XenApp Server Performance view.

Summary

Alerts if server load is high. Server load is a value reported by the Citrix load evaluator that has been assigned to the server.

Monitor by default ignores planned full load caused by scheduled load evaluator rules (“Citrix Maintenance Mode”).

A server load of 200% (load evaluator value = 20000) indicates that a license cannot be obtained from license server.

Configuration

Overridable parameters:

• IntervalSeconds – monitoring interval (default = 300)

• IgnoreScheduledFullLoad – if set to true, the alert is not generated when server load is 10000 (full load) caused by scheduled load evaluator rule (“Citrix Maintenance Mode”) (default = true)

• WarningThreshold – warning threshold in % (default = 70)

• CriticalThreshold – critical threshold in % (default = 95)

Summary

Alerts if server load is high. Server load is a value reported by the Citrix load evaluator that has been assigned to the server.

Monitor by default ignores planned full load caused by scheduled load evaluator rules (“Citrix Maintenance Mode”).

A server load of 200% (load evaluator value = 20000) indicates that a license cannot be obtained from license server.

Configuration

Overridable parameters:

• IntervalSeconds – monitoring interval (default = 300)

• IgnoreScheduledFullLoad – if set to true, the alert is not generated when server load is 10000 (full load) caused by scheduled load evaluator rule (“Citrix Maintenance Mode”) (default = true)

• NumberOfSamples - the number of event occurrences before monitor state changes will be triggered (the default value is set to 3)

• Threshold - the value that defines the critical threshold to be used in the comparison (the default value is set to 95 percentage)

Summary

This monitor checks the number of XML threads currently being processed over multiple consecutive samples.

There are 16 worker threads in the Citrix XML Service. A count of 16 shows that XML requests are not being processed in a timely manner, which impacts Web Interface/Store Front requests (logons, list and launch applications) being slow or rejected.

Having consistently 10 or more busy XML threads already indicate that XML broker might not be capable of servicing all request in timely manner. By default alert is generated if there are 10 or more busy XML treads on two consecutive samples (5 minutes interval).

Configuration

Overridable parameters:

Causes

The most common reason for the XML service to become unresponsive is because it is busy waiting for a response from the IMA service. Usually, adding CPU power helps reducing IMA service response times and consequently number of busy XML threads.

Additional

To see monitor performance values, open XenApp Server Performance view.

Summary

This monitor checks the number of times the XenApp server has called for an election in a specified time period. This counter is incremented regardless of whether or not a new Zone Data Collector was elected.

By default, alert is generated if two zone elections are triggered on server in one hour. To modify the time period, override NumSamples parameter with the following formula:

NumSamples = 3600 * <time interval in hours> / IntervalSeconds

Configuration

Overridable parameters:

Causes

Zone election can be triggered for many reasons:

• the existing data collector for Zone goes offline (shuts down gracefully)

• the communication between a member server and the Zone Data Collector for its zone failed

• the communication between data collectors failed

• member server (IMA service) is started

• configuration of a zone is changed (member server is added/removed to/from zone)

Note: In XenApp 6.5 worker servers cannot trigger elections.

Additional

To check the number of Zone Elections Triggered, open XenApp Server Performance view.

To check if IMA service is being restarted frequently, search XenApp Server Closed Alerts for multiple "Windows Service Stopped" alerts with "The Citrix Independent Management Architecture service on computer <name> has stopped running." message.

Summary

Monitor checks server availability by checking server load. Server load is a value reported by the Citrix load evaluator that has been assigned to the server. If the load reaches 100% (load evaluator value = 10000) then users can no longer login to server.

Load can be 100% because of the actual load on the server or because of the scheduled load evaluator rule (“Citrix Maintenance Mode”).

In case the license cannot be obtained from license server, server load is 200% (load evaluator value = 20000).

Configuration

Overridable parameters:

• IntervalSeconds – monitoring interval (default = 300)

• TreatScheduledFullLoadAsMaintenance – if set to true, full load caused by scheduled load evaluator rule is treated as “Citrix Maintenance Mode”, otherwise it is treated as normal full load (default = true)

Possible monitor states:

Summary

Alerts if the Citrix XenApp MP Agent has not been deployed to the XenApp server. This is very useful in situations when you are not sure whether a specific XenApp server has been put under control of the XenApp MP or not.

Summary

Alerts if connection to the ICA listener port was refused. Probing is executed from the MS Operations Manager server’s perspective. ICA clients typically connect to the XenApp server via this port. Inability to connect means that end-users are also not going to be able to connect to this system.

Summary

Alerts if connecting to the ICA listener port timed-out. Probing is executed from the MS Operations Manager server’s perspective. ICA clients typically connect to the XenApp server via this port. Inability to connect means that end-users are also not going to be able to connect to this system.

Summary

Alerts if connection to the ICA listener port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. ICA clients typically connect to the XenApp server via this port. Inability to connect means that end-users are also not going to be able to connect to this system.

Summary

Alerts if connection to the ICA listener port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. ICA clients typically connect to the XenApp server via this port. Inability to connect means that end-users are also not going to be able to connect to this system.

Summary

Alerts if connection to the IMA service port was refused. Probing is executed from the MS Operations Manager server’s perspective. IMA service keeps the farm together. If the IMA service stops responding, the server is marked as "offline" by the rest of the XenApp farm.

Summary

Alerts if connection to the IMA service port timed-out. Probing is executed from the MS Operations Manager server’s perspective. IMA service keeps the farm together. If the IMA service stops responding, the server is marked as "offline" by the rest of the XenApp farm.

Summary

Alerts if connection to the IMA service port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. IMA service keeps the farm together. If the IMA service stops responding, the server is marked as "offline" by the rest of the XenApp farm.

Summary

Alerts if connecting to the IMA service port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. IMA service keeps the farm together. If IMA service stops responding, the server is marked as "offline" by the rest of the XenApp farm.

Summary

Alerts if connection to the Management Console port was refused. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Citrix Management Console connects to. It is not that critical if this server is not used for console’s connection.

Summary

Alerts if connection to the Management Console port timed-out. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Citrix Management Console connects to. It is not that critical if this server is not used for console’s connection.

Summary

Alerts if connection to the Management Console port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Citrix Management Console connects to. It is not that critical if this server is not used for console’s connection.

Summary

Alerts if connection to the Management Console port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Citrix Management Console connects to. It is not that critical if this server is not used for console’s connection.

Summary

Alerts if connection to the RDP listener port was refused. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Terminal Services clients (Remote Desktop Connection clients) connect to. If this port is not reachable, RDP clients cannot connect to the server.

Summary

Alerts if connection to the RDP listener port timed-out. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Terminal Services clients (Remote Desktop Connection clients) connect to. If this port is not reachable, RDP clients cannot connect to the server.

Summary

Alerts if connection to the RDP listener port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Terminal Services clients (Remote Desktop Connection clients) connect to. If this port is not reachable, RDP clients cannot connect to the server.

Summary

Alerts if connection to the RDP listener port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. This is the port the Terminal Services clients (Remote Desktop Connection clients) connect to. If this port is not reachable, RDP clients cannot connect to the server.

Summary

Alerts if connection to the Session Reliability port was refused. Probing is executed from the MS Operations Manager server’s perspective. This is a proxy port/service for the ICA port. Session reliability allows quick reconnect to a Citrix session if a connection was lost for a short period of time.

Summary

Alerts if connection to the Session Reliability port timed-out. Probing is executed from the MS Operations Manager server’s perspective. This is a proxy port/service for the ICA port. Session reliability allows quick reconnect to a Citrix session if a connection was lost for a short period of time.

Summary

Alerts if connection to the Session Reliability port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. This is a proxy port/service for the ICA port. Session reliability allows quick reconnect to a Citrix session if a connection was lost for a short period of time.

Summary

Alerts if connection to the Session Reliability port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. This is a proxy port/service for the ICA port. Session reliability allows quick reconnect to a Citrix session if a connection was lost for a short period of time.

Summary

Alerts if connection to the XML Service port was refused. Probing is executed from the MS Operations Manager server’s perspective. This service is used for Web Interface – XenApp server communication. Mostly, just those XenApp servers that are configured as brokers for the Web Interface are critical.

Summary

Alerts if connection to the XML Service port timed-out. Probing is executed from the MS Operations Manager server’s perspective. This service is used for Web Interface – XenApp server communication. Mostly, just those XenApp servers that are configured as brokers for the Web Interface are critical.

Summary

Alerts if connection to the XML Service port failed due to inability to resolve DNS name of the XenApp server to IP address. Probing is executed from the MS Operations Manager server’s perspective. This service is used for Web Interface – XenApp server communication. Mostly, just those XenApp servers that are configured as brokers for the Web Interface are critical.

Summary

Alerts if connecting to the XML Service port failed due to the host being unreachable. Probing is executed from the MS Operations Manager server’s perspective. This service is used for Web Interface – XenApp server communication. Mostly, just those XenApp servers that are configured as brokers for the Web Interface are critical.

Summary

Alerts if a large number of XenApp servers becomes unavailable in a zone. This typically indicates larger outage of XenApp farm’s capacity, and can be attributed to the network connectivity loss, or to a massive server shutdown / power failure.

Summary

Alerts if a large % of XenApp servers becomes unavailable in a zone. This typically indicates a larger outage of XenApp farm’s capacity, and can be attributed to the network connectivity loss, or to a massive server shutdown / power failure.

Summary

Helps to identify user profiles that contain custom file category. This can be configured to any specific set of file extensions as needed.

Summary

Helps to identify user profiles that contain executable files. User profiles should normally not contain any executable files.

Summary

Helps to identify user profiles that contain media files (mp3s, movies, etc.). User profiles should normally not contain any large media files.

Summary

Helps to identify user profiles that contain a large number of files. With roaming profiles, a large number of files in a user’s profile means that user’s logon and logoff processes are going to be slower.

Summary

Helps to identify user profiles that are very large. With roaming profiles, a large user’s profile means that user’s logon and logoff processes are going to be slower.

Summary

Helps to identify a user whose logon process – phase 2 (applying Group Policy Objects) was very slow.

During this phase the server applies user settings defined on the Domain Controller.

Configuration

Overridable parameters:

• IntervalSeconds – monitoring interval (default = 300)

• InfoThreshold – duration is seconds (default = 120)

• WarningThreshold – duration in seconds (default = 180)

• CriticalThreshold – duration in seconds (default = 240)

Causes

Reasons for a slow logon phase can be:

• issues with the required infrastructure (required services and components are either not running or configured as expected),

• issues with network and domain controller availability,

• system time is not configured correctly,

• high network load, or

• a large number of policy settings.

Summary

Helps to identify a user whose logon process – phase 5 (Citrix-specific initialization phase) was very slow.

This 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 – monitoring interval (default = 300)

• InfoThreshold – duration is seconds (default = 120)

• WarningThreshold – duration in seconds (default = 180)

• CriticalThreshold – duration in seconds (default = 240)

Causes

Reasons for a slow logon phase can be:

• issues with the client printer (usually third-party printer drivers), or

• issues with retrieving ICA client version and the rest of the update process.

Summary

Helps to identify a user whose logon process was very slow. It provides also information about duration for each logon phase.

Configuration

Overridable parameters:

• IntervalSeconds – monitoring interval (default = 300)

• InfoThreshold – duration is seconds (default = 120)

• WarningThreshold – duration in seconds (default = 180)

• CriticalThreshold – duration in seconds (default = 240)

Additional

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

XenApp Management Pack breaks down the logon process on a Citrix XenApp server into five phases.

Phase 1: User profile loading

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

Phase 2: Applying group policy objects (GPOs)

During this phase the server applies user settings defined on the Domain Controller.

Phase 3: User environment initialization and Active Setup

During this phase network connections are restored and profile settings, such as fonts and screen colors, are loaded. Also, if this is the first time this profile is being used, some extra initialization is applied. The default profile is created, first time use settings are applied for the shell (Explorer), Internet Explorer, Office (particularly Outlook) and any other application that uses Active Setup.

Phase 4: Logon script execution

The phase is measured by how long the USRLOGON.CMD script (located in %SystemRoot%\system32) is being executed. The script’s original function is to address issues with legacy applications that were not written with a multi-user environment, such as Terminal Server. It uses application compatibility scripts (located in %SystemRoot%\Application Compatibility Scripts) in conjunction with the %ROOTDRIVE% variable to address these issues. USRLOGON.CMD script is also used as a starting point for custom profile frameworks (i.e. not supported by Microsoft), such as Flex or Jumping profiles.

Phase 5: Citrix Application initialization

The 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.

Summary

Helps to identify a user whose logon process failed or was timed out after 5 minutes. It also provides information on which phase of the logon process was responsible for the failure/timeout.

Configuration

Overridable parameters:

• IntervalSeconds – monitoring interval (default = 300)

• IgnoreTerminatedLogons – if set to true, the logons that have been terminated will not be monitored (default = false)

• Threshold – number of completed phases (default = 5)

Additional

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

XenApp Management Pack breaks down the logon process on a Citrix XenApp server into five phases.

Phase 1: User profile loading

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

Phase 2: Applying group policy objects (GPOs)

During this phase the server applies user settings defined on the Domain Controller.

Phase 3: User environment initialization and Active Setup

During this phase network connections are restored and profile settings, such as fonts and screen colors, are loaded. Also, if this is the first time this profile is being used, some extra initialization is applied. The default profile is created, first time use settings are applied for the shell (Explorer), Internet Explorer, Office (particularly Outlook) and any other application that uses Active Setup.

Phase 4: Logon script execution

The phase is measured by how long the USRLOGON.CMD script (located in %SystemRoot%\system32) is being executed. The script’s original function is to address issues with legacy applications that were not written with a multi-user environment, such as Terminal Server. It uses application compatibility scripts (located in %SystemRoot%\Application Compatibility Scripts) in conjunction with the %ROOTDRIVE% variable to address these issues. USRLOGON.CMD script is also used as a starting point for custom profile frameworks (i.e. not supported by Microsoft), such as Flex or Jumping profiles.

Phase 5: Citrix Application initialization

The 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.

Summary

Helps to identify a user whose logon process – phase 4 (logon script execution phase) was very slow.

The phase is measured by how long the USRLOGON.CMD script (located in %SystemRoot%\system32) is being executed. The script’s original function is to address issues with legacy applications that were not written with a multi-user environment, such as Terminal Server. It uses application compatibility scripts (located in %SystemRoot%\Application Compatibility Scripts) in conjunction with the %ROOTDRIVE% variable to address these issues. USRLOGON.CMD script is also used as a starting point for custom profile frameworks (i.e. not supported by Microsoft), such as Flex or Jumping profiles.

Configuration

Overridable parameters:

• IntervalSeconds – monitoring interval (default = 300)

• InfoThreshold – duration is seconds (default = 120)

• WarningThreshold – duration in seconds (default = 180)

• CriticalThreshold – duration in seconds (default = 240)

Causes

Reasons for a slow logon phase can be:

• issues with application compatibility scripts,

• legacy applications, or

• custom profile initialization.

Summary

Helps to identify a user whose logon process – phase 1 (profile loading phase) was very slow.

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

Configuration

Overridable parameters:

• IntervalSeconds – monitoring interval (default = 300)

• InfoThreshold – duration is seconds (default = 120)

• WarningThreshold – duration in seconds (default = 180)

• CriticalThreshold – duration in seconds (default = 240)

Causes

Reasons for a slow logon phase can be:

• issues with network and profile storage availability,

• high network load,

• big profile size,

• using this profile on the server for the first time (a cached version of the roaming profile does not exist yet), or

• a corrupted profile.

Summary

Helps to identify a user whose logon process – phase 3 (User-specific Initialization) was very slow.

During this phase network connections are restored and profile settings, such as fonts and screen colors, are loaded. Also, if this is the first time this profile is being used, some extra initialization is applied. The default profile is created, first time use settings are applied for the shell (Explorer), Internet Explorer, Office (particularly Outlook) and any other application that uses Active Setup.

Configuration

Overridable parameters:

• IntervalSeconds – monitoring interval (default = 300)

• InfoThreshold – duration is seconds (default = 120)

• WarningThreshold – duration in seconds (default = 180)

• CriticalThreshold – duration in seconds (default = 240)

Causes

Reasons for a slow logon phase can be:

• issues with restoring the network connection(s),

• a corrupted profile, or

• using this profile on the server for the first time (Active Setup hasn't been applied yet).

Summary

CPU utilization for process on XenApp server is high.

Configuration

The following configuration parameters are customizable:

CollectionType parameter options:

Summary

IO Operations per second for process on XenApp server is high.

Configuration

The following configuration parameters are customizable:

CollectionType parameter options:

Summary

Page Faults per second for process on XenApp server is high.

Configuration

The following configuration parameters are customizable:

CollectionType parameter options:

Summary

Page file size for process on XenApp server is high.

Configuration

The following configuration parameters are customizable:

CollectionType parameter options:

Summary

Working set size for process on XenApp server is high.

Configuration

The following configuration parameters are customizable:

CollectionType parameter options:

Summary

Helps to identify sessions that host CPU hungry applications. The name of the user, application, and client IP address are included in the alert details.

Alert is triggered only when CPU usage is above threshold for specified number of consecutive samples (NumberOfSamples parameter).

Configuration

The following configuration parameters are customizable:

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

Summary

Helps to identify sessions that host CPU hungry applications. The name of the user, application, and client IP address are included in the alert details.

This monitor is disabled by default because consecutive samples counterpart rule is enabled by default.

Summary

Helps to identify sessions that host applications that are very likely leaking kernel handles. This can potentially lead to an unstable session. The name of the user, application, and client IP address are included in the alert details.

Alert is triggered only when handle count is above threshold for specified number of consecutive samples (NumberOfSamples parameter).

Configuration

The following configuration parameters are customizable:

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

Summary

Helps to identify sessions that host applications that are very likely leaking kernel handles. This can potentially lead to an unstable session. The name of the user, application, and client IP address are included in the alert details.

Summary

Helps to identify sessions that deliver slow responsiveness (screen updates) to end-users. The name of the user, application, and client IP address are included in the alert details.

Alert is triggered only when average latency (in milliseconds) is above threshold for specified number of consecutive samples (NumberOfSamples parameter).

Configuration

The following configuration parameters are customizable:

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

Summary

Helps to identify sessions that deliver slow responsiveness (screen updates) to end-users. The name of the user, application, and client IP address are included in the alert details.

Summary

Helps to identify sessions that have inconsistent responsiveness (screen updates). To an end-user, this can be even worse than slow responsiveness. The name of the user, application, and client IP address are included in the alert details.

Alert is triggered only when latency deviation (in milliseconds) is above threshold for specified number of consecutive samples (NumberOfSamples parameter).

Configuration

The following configuration parameters are customizable:

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

Summary

Helps to identify sessions that have inconsistent responsiveness (screen updates). To an end-user, this can be even worse than slow responsiveness. The name of the user, application, and client IP address are included in the alert details.

Summary

Helps to identify sessions that have just started to deliver slow responsiveness (screen updates) to end-users. The name of the user, application, and client IP address are included in the alert details.

Alert is triggered only when last recorded latency (in milliseconds) is above threshold for specified number of consecutive samples (NumberOfSamples parameter).

Configuration

The following configuration parameters are customizable:

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

Summary

Helps to identify sessions that have just started to deliver slow responsiveness (screen updates) to end-users. The name of the user, application, and client IP address are included in the alert details.

This monitor is disabled by default because consecutive samples counterpart rule is enabled by default.

Summary

Alert is triggered only when number of network errors is above threshold for specified number of consecutive samples (NumberOfSamples parameter).

Configuration

The following configuration parameters are customizable:

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

Summary

Helps to identify sessions that have networking errors/timeouts on end-user connections. This can result in a session being disconnected or having slow responsiveness. The name of the user, application, and client IP address are included in the alert details.

This monitor is disabled by default because consecutive samples counterpart rule is enabled by default.

Summary

Helps to identify sessions that host applications that require a large network bandwidth (animations, printing to a local printer, copying from a local USB drive). If bandwidth is limited and XenApp network throttling policies are not set accordingly, this can have a large impact on all other users working from the same remote office. The name of the user, application, and client IP address are included in the alert details.

Alert is triggered only when network traffic rate is above threshold for specified number of consecutive samples (NumberOfSamples parameter).

Configuration

The following configuration parameters are customizable:

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

Summary

Helps to identify sessions that host applications that require a large network bandwidth (animations, printing to a local printer, copying from a local USB drive). If bandwidth is limited and XenApp network throttling policies are not set accordingly, this can have a large impact on all other users working from the same remote office. The name of the user, application, and client IP address are included in the alert details.

Summary

Alert is triggered only when page file size is above threshold for specified number of consecutive samples (NumberOfSamples parameter).

Configuration

The following configuration parameters are customizable:

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

Summary

Helps to identify sessions that host applications that are very likely leaking memory. The name of the user, application, and client IP address are included in the alert details.

Summary

Helps to identify sessions that host applications that are very likely leaking threads, which can potentially lead to unstable/slow session. The name of the user, application, and client IP address are included in the alert details.

Alert is triggered only when thread count is above threshold for specified number of consecutive samples (NumberOfSamples parameter).

Configuration

The following configuration parameters are customizable:

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

Summary

Helps to identify sessions that host applications that are very likely leaking threads, which can potentially lead to unstable/slow session. The name of the user, application, and client IP address are included in the alert details.

Summary

Helps to identify sessions that host memory hungry applications. The name of the user, application, and client IP address are included in the alert details.

Alert is triggered only when working set size is above threshold for specified number of consecutive samples (NumberOfSamples parameter).

Configuration

The following configuration parameters are customizable:

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

Summary

Helps to identify sessions that host memory hungry applications. The name of the user, application, and client IP address are included in the alert details.

This monitor is disabled by default because consecutive samples counterpart rule is enabled by default.

Summary

Forwards Citrix-related Application Event Log issues to MS Operations Manager.

Summary

Forwards Citrix-related Application Event Log issues to MS Operations Manager.

Summary

Forwards Citrix-related Security Event Log issues to MS Operations Manager.

Summary

Forwards Citrix-related Security Event Log issues to MS Operations Manager.

Summary

Forwards Citrix-related System Event Log issues to MS Operations Manager.

Summary

Forwards Citrix-related System Event Log issues to MS Operations Manager.

Summary

Collects top process information on XenApp server. Data is stored in Data Warehouse.

To select the type of process collection, override the CollectionType parameter with:

Default parameter value is TOP CPU 10.

Summary

This rule collects all user session information per published application on XenApp server. Data is stored in Data Warehouse and is used for reports.

To change session data collection interval, override the IntervalSeconds parameter. Value is entered in seconds. Default IntervalSeconds parameter value is 300 (5 minutes).

It is essential that when IntervalSeconds parameter is updated, ComTradeXAMP.SessionCollectingInterval table in OperationsManagerDW database is also updated shortly before or afterwards. New record has to be added with the following values:

Summary

This rule collects the number of Application Enumerations per second on XenApp Server and stores data to Operations database.

Application Enumerations is the number of non-XML-based enumerations (requests for application lists).

Summary

This rule collects the Application Resolution Time in milliseconds on XenApp Server and stores data to Operations database.

Application Resolution Time is the time required to resolve the Least-Loaded Server during an application launch.

Summary

This rule collects the CPU usage (in %) on XenApp server and stores data to Data Warehouse.

Summary

This rule collects the disk read/write time (in %) on XenApp server and stores data to Data Warehouse.

Summary

This rule collects disk used space (in %) on XenApp server and stores data to Data Warehouse.

Summary

This rule collects the number of Filtered Application Enumerations per second on XenApp Server and stores data to Operations database.

Filtered Application Enumerations is the number of Web Interface/StoreFront application enumerations (and logons) per second handled by specific XML broker.

Summary

Collects the total IO Data Operations per Second for all processes and stores data to Data Warehouse.

IO Data Operations per sec. is the rate at which the process is issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network and device I/Os.

Summary

This rule collects the load of the XenApp server (in %).

Summary

This rule collects the memory usage (in %) on XenApp server and stores data to Data Warehouse.

Summary

This rule collects the average network usage through all network interfaces (in %) on XenApp server and stores data to Data Warehouse.

Summary

This rule collects the number of busy XML threads on XenApp Server and stores data to Operations database.

Number of busy XML threads is the number of XML requests that are currently being processed. The maximum number of requests that the XML service can process at any one time is 16.

Summary

This rule collects the number of triggered zone elections by XenApp server for each monitoring interval.