Nimsoft Monitor xenapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/xenapp/1.0/xenap… ·...

xenapp Guide v1.0 series

Nimsoft Monitor

CA Nimsoft Monitor Copyright Notice

This online help system (the "System") is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This System may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This System is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. This System may not be disclosed by you or used for any purpose other than as may be permitted in a separate agreement between

.

Notwithstanding the foregoing, if you are a licensed user of the CA Software you may make one copy of the System for internal use by you and your employees, provided that all CA copyright notices and legends are affixed to the reproduced copy.

The right to make a copy of the System is limited to the period during which the license for the CA Software remains in full force and effect. Should the license terminate for any reason, it shall be your responsibility to certify in writing to CA that all copies and partial copies of the System have been destroyed.

WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS SYSTEM, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The manufacturer of this System is CA.

Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2014 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Legal information on third-party and public domain software used in the Nimsoft Monitor solution is documented in Nimsoft Monitor Third-Party Licenses and Terms of Use (http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html).

http://docs.nimsoft.com/prodhelp/en_US/Library/Legal.html

Contact CA

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

Send comments or questions about CA Technologies Nimsoft product documentation to [email protected].

To provide feedback about general CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

http://www.ca.com/support

mailto:[email protected]

http://ca.com/docs

Contents 5

Contents

Chapter 1: xenapp 1.0 7

Overview ...................................................................................................................................................................... 7

Chapter 2: XenApp Monitoring Probe Deployment 9

Requirements ............................................................................................................................................................... 9

Prerequisites ......................................................................................................................................................... 9

Hardware Requirements ....................................................................................................................................... 9

Software Requirements ...................................................................................................................................... 10

Supported Platforms ........................................................................................................................................... 10

Probe Deployment Information ................................................................................................................................. 10

Chapter 3: XenApp Monitoring Probe Configuration 11

Probe Configuration Interface Installation ................................................................................................................. 11

Monitoring Capabilities .............................................................................................................................................. 12

Templates ................................................................................................................................................................... 12

Probe GUI ................................................................................................................................................................... 13

Configuration Interface Navigation ..................................................................................................................... 13

The Toolbar Buttons ............................................................................................................................................ 13

The Navigation (Left) Pane .................................................................................................................................. 13

The Content (Right) Pane .................................................................................................................................... 15

Probe Configuration ................................................................................................................................................... 16

Connecting to the xenapp Environment ............................................................................................................. 16

Configure WinRM and PowerShell ...................................................................................................................... 18

Using an HTTPS Connection ................................................................................................................................ 20

Using an HTTP Connection .................................................................................................................................. 22

Troubleshooting Connection Issues .................................................................................................................... 22

General Setup ..................................................................................................................................................... 26

Create a New Resource ....................................................................................................................................... 26

Access for Users Without Administrator Permissions ........................................................................................ 30

Message Pool Manager ....................................................................................................................................... 30

Create New Template ......................................................................................................................................... 32

Advanced Configuration ...................................................................................................................................... 32

Chapter 4: Adding Monitors 35

Manually Selecting Monitors to be Measured ........................................................................................................... 35

6 xenapp Guide

Enabling the Monitors for QoS and Alarming ..................................................................................................... 36

To Edit Monitor Properties ................................................................................................................................. 36

Monitors of Type Value ....................................................................................................................................... 36

Using Templates ......................................................................................................................................................... 38

To Create a New Template .................................................................................................................................. 39

To Add Monitors to a Template .......................................................................................................................... 39

To Apply a Template ........................................................................................................................................... 39

Using Automatic Configurations ................................................................................................................................ 39

Adding a Monitor to the Auto Configurations Node ........................................................................................... 40

Exploring the Contents of the Auto Configurations Node .................................................................................. 41

Checking the Auto Monitors Node ...................................................................................................................... 41

Chapter 5: Metrics 43

Farm Node .................................................................................................................................................................. 43

Administrators Node .................................................................................................................................................. 43

Applications Node ...................................................................................................................................................... 44

LoadBalancingPolicy Node ......................................................................................................................................... 48

LoadEvaluator Node ................................................................................................................................................... 48

Servers Node .............................................................................................................................................................. 50

Processes Nodes ................................................................................................................................................. 51

PerformanceMetrics Nodes ................................................................................................................................ 53

Services Node ...................................................................................................................................................... 59

Zone Node ........................................................................................................................................................... 61

Session Node ....................................................................................................................................................... 61

WorkerGroups Node .................................................................................................................................................. 64

Appendix A: Troubleshooting 67

Probe Not Collecting Data .......................................................................................................................................... 68

Out of Memory Errors ................................................................................................................................................ 68

Probe Delays in Fetching XenApp Farm Data ............................................................................................................. 69

Probe Not Fetching Performance Metrics for some Servers in Farm ........................................................................ 70

Probe Not Fetching Performance Metrics even when WinRM Enabled .................................................................... 71

Probe Not Fetching ICA Latency Metrics .................................................................................................................... 71

Known Issues .............................................................................................................................................................. 72

Chapter 1: xenapp 1.0 7

Chapter 1: xenapp 1.0

This description applies to the XenApp Monitoring probe version 1.0.

This section contains the following topics:

Overview (see page 7) Documentation Changes (see page 8)

Overview

The CA Nimsoft XenApp Monitoring probe automates all common monitoring and data collection tasks in the Citrix XenApp Server environment.

The XenApp Monitoring probe collects and stores data about xenapp servers and XenApp server farms and XenApp managed applications. Data is collected for the Administrators, Applications, Load Balancing Policy, Load Evaluator, Servers, Services, Worker Groups, and Zone components. In addition to collecting the information about different components, the probe also collects performance metrics of XenApp servers. The XenApp environment can be monitored individually or through a common access in a high availability configuration.

The probe generates QoS metrics for real-time status and for display in charts, dashboards, and historical reports. You can define alarms to be issued and propagated to the Alarm Console when specified thresholds are breached.

Overview

8 xenapp Guide

Documentation Changes

This table describes the version history for this document.

Version Date What's New?

1.0 June 2014 Initial release

Related Documentation

Documentation for other versions of the xenapp probe

The Release Notes for the xenapp probe

Monitor Metrics Reference Information for CA Nimsoft Probes (http://docs.nimsoft.com/prodhelp/en_US/Probes/ProbeReference/index.htm)

http://docs.nimsoft.com/prodhelp/en_US/Probes/AdminConsole/xenapp/ReleaseNotes/index.htm

http://docs.nimsoft.com/prodhelp/en_US/Probes/ProbeReference/index.htm

Chapter 2: XenApp Monitoring Probe Deployment 9

Chapter 2: XenApp Monitoring Probe Deployment

This section contains information about deploying the XenApp Monitoring probe.


Requirements (see page 9) Probe Deployment Information (see page 10)

Requirements

This section describes prerequisites, hardware requirements, and software requirements for the XenApp Monitoring probe.

Prerequisites

This section describes the prerequisites for this probe:

■ CA Nimsoft Monitor version 6.5 or later environment.

■ Windows PowerShell command line interface on the XenApp server. The latest version of PowerShell that comes with Windows Server 2008R2 or later is required. For information on configuring PowerShell for use with the XenApp Monitoring probe, see the Citrix XenApp Guide.

■ Windows Remote Management (WinRM) enabled on the xenapp server. For instructions on enabling WinRM, see the xenapp Guide.

Hardware Requirements

The XenApp Monitoring probe should be installed on a system with the following minimum resources:

■ Memory: 4 GB of RAM

■ CPU: 3 GHz dual-core processor, 32-bit or 64-bit

Probe Deployment Information

10 xenapp Guide

Software Requirements

The XenApp Monitoring probe requires the following software environment:

■ Nimsoft Monitor Server 5.1.1 or later

■ Nimsoft Robot 5.23 or later

■ Java Virtual Machine 1.6 or later (typically installed with NMS 5.0 and later)

■ Infrastructure Manager 4.02 or later

■ Microsoft .NET Framework 3.5 on the system where the Infrastructure Manager application is running

Important!: On 64-bit Linux systems, the Java jre included in the XenApp Monitoring probe package does not install successfully when you deploy the XenApp Monitoring probe on a CA Nimsoft robot.

Supported Platforms

The xenapp probe is supported on the same set of operating systems and databases as the Nimsoft Monitor Server solution. Please refer to the:

■ Nimsoft Compatibility Support Matrix for the latest information on supported platforms.

■ Support Matrix for Nimsoft Probes for additional information on the xenapp probe.

Probe Deployment Information

There are two ways to distribute the probe archive packages. You can distribute the package within Infrastructure Manager or use the standalone Nimsoft Distribution application.

http://support.nimsoft.com/downloads/doc/NMSCompatibility_SupportMatrix_current.pdf

http://support.nimsoft.com/downloads/doc/Platform_Support_Availability_current.pdf


Chapter 3: XenApp Monitoring Probe Configuration

This section describes the configuration concepts and procedures for setting up the XenApp Monitoring probe.

After installing the XenApp Monitoring probe, you must define what to monitor. At a high level there are three steps:

1. Connect to the XenApp server environment.

2. Add monitors (checkpoints). See the description in the section Adding Monitors (see page 35).

3. Configure the properties for the checkpoints, in which you define QoS data, and define alarms to be sent if specified thresholds are breached.

Note: You must click the Apply button to activate any configuration changes made in the XenApp Monitoring Probe Configuration Window.


Probe Configuration Interface Installation (see page 11) Monitoring Capabilities (see page 12) Templates (see page 12) Probe GUI (see page 13) Probe Configuration (see page 16)

Probe Configuration Interface Installation

The probe configuration interface is automatically downloaded and installed by the Nimsoft Infrastructure Manager when the probe is deployed on a robot.

Monitoring Capabilities

12 xenapp Guide

Monitoring Capabilities

The following XenApp components can be monitored:

■ Farms

■ Administrators

■ Applications

■ Load Balancing Policy

■ Load Evaluators

■ Services

■ Worker groups

■ Zones

■ Servers

■ Health information of xenapp servers

■ License Server

■ Sessions of the servers

Templates

Templates allow you to define reusable sets of monitors to apply to XenApp components. After you create a template and add monitors (checkpoints) to the template, do one of the following:

■ Drag-and-drop the template onto the XenApp component you want to apply the template to. This creates a static monitor for that component and its children (recursively) based on the template contents at the time the static monitor is created.

■ Drag-and-drop the template into the Auto Configurations node to add the template contents to the list of auto configuration monitors.

Important! The XenApp Monitoring probe does not contain any default templates.

See the section Using Templates (see page 38) for details.

Probe GUI


Probe GUI

This section contains the basic GUI information for the XenApp Monitoring probe.

The XenApp Monitoring probe collects and stores data and information from the monitored components in a XenApp server environment about the applications managed by XenApp.

Double-click the line representing the XenApp Monitoring probe in the Infrastructure Manager to launch the XenApp Monitoring probe configuration interface. It initially appears with the Resources hierarchy empty.

Configuration Interface Navigation

The configuration interface consists of a row of tool buttons above a window split into two parts:

■ The Navigation pane

■ The Content pane

In addition, a status bar at the bottom of the window shows version information and date and time when the probe was last started.

The Toolbar Buttons

The configuration interface contains a row of toolbar buttons:

■ The General Setup button allows you to configure the log level for the probe.

■ The New Resource button allows you to add a new resource.

■ The Message Pool Manager button allows you to add, remove, or edit alarm messages.

■ The Create New Template button allows you to create a new template.

The Navigation (Left) Pane

The division on the left side of the window is the navigation pane. It displays the monitored resources and any templates you have created.

Probe GUI

14 xenapp Guide

Resources

You can create a new Resource by clicking the New Resource button, or by right-clicking Resources and selecting New Resource.

The Resource is configured as a link to the XenApp server environment. Note the following icons for the Resource node:

Resource is inactive

Resource is marked for deletion

Resource is unable to connect

New resource (not yet saved)

Resource is connected and inventory is ready to browse

Resource is loading inventory. Not ready to browse

The Resources node contains the following sub-hierarchies:

■ The Auto Configurations node

One or more checkpoints (or templates) can be added to this node, using drag-and-drop. These checkpoints can to be used for auto configuring unmonitored devices. See the section Using Automatic Configurations for further information.

■ The Auto Monitors node

This is a list of the monitors that have been created based on the Auto-Configuration entries and the inventory available on the Resource.

See the section Using Automatic Configurations for further information.

■ The All Monitors node

This node contains the complete list of Monitors for the Resource. This includes Auto Monitors and manually configured Monitors. See the section Using Automatic Configurations for further information.

■ The XenApp server hierarchy

This is a list of the farms, administrators, applications, load evaluators, servers, services, worker groups, and zones auto-discovered and available in the XenApp environment for monitoring.

Probe GUI


Create Templates

Templates let you define reusable sets of monitors for the various XenApp environment resources.

■ To add a template, click the Create New Template button.

■ To edit or delete a template, click on the template name to select it, then right-click and select the action you want.

The properties for a template are Name and Description. See the section Using Templates (see page 38) for details.

Important! The XenApp Monitoring probe does not contain any default templates.

Navigation Pane Updates

A right-click with the mouse pointer in the navigation pane over the hostname or IP address node opens a pop-up menu with menu items for managing the selected object or creating new objects of its type. Options typically include: New, Edit, Delete, Deactivate, and Refresh.

Note: When available, the Refresh menu item retrieves updated values and refreshes the display.

The Content (Right) Pane

The content of the right pane depends on the selection in the navigation pane.

If you select a Resources node in the navigation pane, the content pane lists the XenApp environment.

If you select a component in the navigation pane, the content pane lists the available monitors. Active Monitors are check-marked. The following icons can appear there:

Indicates that the monitor is active but not enabled to send alarms. The Enable Monitoring checkbox was not selected for this monitor.

Black: Indicates that the monitor is NOT activated. The Action option is not set in the properties dialog for the monitor.

Green: Indicates that the monitor is activated for monitoring and, if an alarm threshold is set, the threshold value defined in the properties dialog for the monitor is not exceeded.

Gray: Indicates that the monitor is an inactive static monitor.

Probe Configuration

16 xenapp Guide

Other colors: Indicates that the monitor is activated for monitoring and the threshold value defined in the properties dialog for the monitor is exceeded. The color reflects the message token selected in the properties dialog for the monitor.

This icon represents a monitor where no value has been measured.

Note: Any monitor name in italics indicates that the monitor has been modified and you must apply the changes before the monitor results are updated.

Content Pane Updates

A right-click with the mouse pointer on objects in the content pane opens a pop-up menu with menu items for managing the selected object type (Edit, Delete, and Add to Template).

Note: When available, the Refresh menu item fetches updated values and refreshes the display.

Probe Configuration

This section contains specific configuration information for the XenApp Monitoring probe.

Connecting to the xenapp Environment

The XenApp Monitoring probe connects to the XenApp server using the Windows Remote Management (WinRM) service. WinRM is used for general communications and to manage data collection, conducted through the remote execution of PowerShell commands using the WS-Man protocols.

WinRM on the XenApp server must be enabled and properly configured for use with the XenApp Monitoring probe. The XenApp Monitoring probe also requires remote unrestricted, unencrypted execution of PowerShell commands on the XenApp server. The PowerShell commands must have direct access (with valid user credentials) to the data store.

Note: If credentials must be delegated across multiple servers in your environment, you may need to enable CredSSP. See Set Up Multi-Hop Authentication (see page 24) for more information.

PowerShell must also be installed on the system where the XenApp Monitoring probe is running (not the system running the probe configuration GUI, which typically talks to the head-less probe remotely).

Probe Configuration


For High Availability (HA) XenApp configurations, appropriate network access must be granted so the same IP address and user credentials continue to work in the event of a failover.

The XenApp Monitoring probe requires account access to the following applications/databases:

■ Local Administrator user access to the XenApp server remotely over the port specified for WinRM (the default is 5985). Ensure that you use the local Administrator account and not the domain administrator account because the system where the XenApp Monitoring probe is deployed may be in a different domain.

■ One of the following:

■ Configuration of WinRM on the XenApp server to allow remote access via a WinRM listener on HTTP.

■ If SSL is used for communication between the robot system and the XenApp server, configuration of WinRM on the XenApp server to use the HTTPS connection type. The default HTTPS port is 5986. You will need the keystore location and keystore password to enter in the XenApp Monitoring probe Edit Resource dialog.

Probe Configuration

18 xenapp Guide

Configure WinRM and PowerShell

The XenApp Monitoring probe requires Windows PowerShell and Windows Remote Management (WinRM) to be enabled and properly configured on the xenapp server.

Important! By default, WinRM and PowerShell is installed on all Windows Server 2008 machines as part of the operating system.

Follow these steps:

1. Open a PowerShell window on the XenApp server and enter the following command:

Get-ExecutionPolicy

2. (Optional) If the response says Restricted, you must change the setting to Unrestricted or RemoteSigned.

For example, to set it to RemoteSigned:

a. Enter the following command:

b. Set-ExecutionPolicy RemoteSigned

c. Enter Y to accept the policy.

d. Enter the Get-ExecutionPolicy command again to verify the setting.

3. Open a Command Prompt window on the XenApp server as the Administrator user.

4. Enter the following command:

winrm quickconfig

5. Enter Y to accept the changes.

Note: This configures WinRM with default settings.

6. Enter the following command to check the authentication status:

get winrm/config/service

7. To the last line of the response,add the following command to allow unencrypted data:

winrm set winrm/config/service @{AllowUnencrypted="true"}

For example:

Auth

Basic = false

Kerberos = true

Negotiate = true

Certificate = false

CredSSP = false

CBTHardeningLevel = Relaxed

winrm setwinrm/config/service@{AllowUnencrypted="true"}

WinRM and Powershell are configured.

Probe Configuration


Note: Complete the probe configuration process by creating either an HTTP or HTTPS connection. Use an HTTPS connection type if you are using SSL.

More information:

Using an HTTPS Connection (see page 20)

Using an HTTP Connection (see page 22)

Configure WinRM and Powershell on Servers Added as Resources

Configure WinRM and Powershell on servers added as Resources or Alternate Resources.

Follow these steps:


Get-ExecutionPolicy

If the response says Restricted, you must change the setting to Unrestricted or RemoteSigned. For example, to set it to RemoteSigned:


Set-ExecutionPolicy RemoteSigned

b. Enter Y to accept the policy.

c. Enter the Get-ExecutionPolicy command again to verify the setting.

2. Open a Command Prompt window on the XenApp server as the Administrator user.

3. Enter the following command:

winrm quickconfig

4. Enter Y to accept the changes.

This configures WinRM with default settings.

5. Enter the following command to check the authentication status:

winrm get winrm/config/service

You see a section in the response similar to the following:

Auth

Basic = false

Kerberos = true

Negotiate = true

Certificate = false

CredSSP = false

CBTHardeningLevel = Relaxed

Probe Configuration

20 xenapp Guide

6. (Optional) If the probe must use basic authentication, enter the following command:

winrm set winrm/config/service/auth @{Basic="true"}

7. Enter the following command to allow unencrypted data:

winrm set winrm/config/service @{AllowUnencrypted="true"}

This setting is not required if the probe uses HTTPS to communicate with the xenapp server.

8. Enter the following command to trust all hosts:

winrm set winrm/config/client @{TrustedHosts="*"}

To trust only specified hosts list the host names, as in the following example:

winrm set winrm/config/client @{TrustedHosts="host1, host2, host3"}

9. Enter the following command to provide sufficient memory, 1024 MB, for the probe to execute PowerShell commands on the xenapp server:

winrm set winrm/config/winrs @{MaxMemoryPerShellMB="1024"}

Note: If you see a message saying "Process is terminated due to StackOverflowException" in the xenapp.log file, increase this setting.

WinRM and Powershell are configured.

Note: Complete the probe configuration process by creating either a HTTP or HTTPS connection. Use an HTTPS connection type if you are using SSL.

Using an HTTPS Connection

You must use an HTTPS connection type if you are using SSL to connect to the XenApp server.

Follow these steps:

1. Create a self-signed certificate for the remote host using makecert.exe or a similar tool.

2. Open a PowerShell window and enter the following command to find the thumbprint for the certificate for the remote host:

Get-childItem cert:\LocalMachine\Root\ | Select-String -pattern HOSTNAME

3. Enter the following command to create an HTTPS WinRM listener for the remote host with the thumbprint from the previous step:

winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname="CN"; CertificateThumbprint="THUMBPRINT"}

Probe Configuration


4. Export the certificate.

If you want to create a backup copy of the certificate or use it on another computer, you must first export it. Exporting the certificate puts it in a file that you can then transfer to another computer or put in a safe place. We recommend that you export certificates to removable media, such as a floppy disk or USB flash drive.

a. Click the Windows Start button.

b. Enter certmgr.msc in the Search field.

c. Enter administrator credentials if prompted.

The Certificate Manager opens.

d. Right-click the certificate you want to export, choose All Tasks, then click Export.

e. Click Next in the Certificate Export Wizard.

f. Click Yes and select do not export the private key.

g. Select the Base64 encoded X.509 format, then click Next.

h. Enter the password you want to use to encrypt the key, confirm it, and click Next.

The export process creates a file to store the certificate in.

i. Specify a name and location for the certificate file.

j. Click Finish.

5. Create a keystore file to use in the XenApp Monitoring probe configuration UI. This procedure tells you how to use Java keytool to generate the keystore. The keystore can be generated from a machine where a JRE is installed and available in %PATH%.

a. Open a command prompt and enter the following command:

Keytool importcert

For CERTIFICATE enter the file name of the certificate exported in the previous step.

For KEYSTORE enter a name for the keystore in the format <path\name>.jks.

For example:

keytool -importcert -file "C:\Test1.cer" -keystore "C:\

b. Enter a password when prompted.

c. Enter Yes when prompted whether to Trust Certificate.

The keystore is available in the path specified.

6. Copy the keystore file to the CA Nimsoft robot machine where the XenApp Monitoring probe is deployed.

Probe Configuration

22 xenapp Guide

7. In the XenApp Monitoring probe configuration GUI, edit (or create if necessary) the resource that represents the xenapp server:

a. Double-click the line representing the xenapp probe in Infrastructure Manager to launch the xenapp probe configuration GUI.

b. Right-click on the resource for the xenapp server and choose Edit Resource.

c. Click the Use SSL check box.

d. Enter the appropriate information in the Keystore Location and Keystore Password fields.

e. Click OK.

More information:

Create a New Resource (see page 26)

Using an HTTP Connection

Use an HTTP connection type if you are not using SSL to connect to the XenApp server.

Follow these steps:

1. To use HTTP to connect to WinRM on the XenApp server, enter the following command:

winrm create winrm/config/listener?Address=*+Transport=HTTP

2. Enter the following command to test the WinRM connection:

winrm identify -r:http://winrm_server:5985 -auth:basic -u:user_name -p:password -encoding:utf-8

You should see a response similar to the following:

IdentifyResponse

ProtocolVersion = http://schemas.dmtf.org/wbem/wsman/1/wsman.xsd

ProductVendor = Microsoft Corporation

ProductVersion = OS: 6.1.7600 SP: 0.0 Stack: 2.0

If the target computer cannot connect to the xenapp server, you may need to set up multi-hop authentication.

For more information, see Set Up Multi-Hop Authentication (see page 24).

Troubleshooting Connection Issues

This section contains troubleshooting steps you can take if the XenApp Monitoring probe is unable to connect to the XenApp server and no data is collected.

Probe Configuration


Verify the WinRM Connection

If no data is displayed in the XenApp Monitoring probe GUI, you must verify that the WinRM service is connecting to the XenApp server.

Follow these steps:

1. Verify that the WinRM service is running on the XenApp server.

2. Review the WinRM configuration details for any problems by entering the following command at the Command Prompt on the xenapp server:

winrm get winrm/config

3. Verify that the correct port is assigned to Win RM on the XenApp server.

The port number is listed under Default Ports in the output for the previous step. The default is 5985.

Verify PowerShell Access

If the XenApp Monitoring probe cannot connect to the XenApp server, it may be because remote access to PowerShell on the XenApp server is restricted. Verify that the correct access is set for PowerShell on the XenApp server.

Follow these steps:


Get-ExecutionPolicy

If the response says Restricted, you must change the setting to Unrestricted or RemoteSigned. For example, to set it to RemoteSigned:


Set-ExecutionPolicy RemoteSigned

b. Enter Y to accept the policy.

c. Enter the Get-ExecutionPolicy command again to verify the setting.

Probe Configuration

24 xenapp Guide

Set Up Multi-Hop Authentication

If the XenApp Monitoring probe cannot connect to the XenApp server, it may be because credentials must be delegated across multiple remote computers in your environment. In this case, you must configure WinRM to use Credential Security Service Provider (CredSSP) to provide multi-hop support for authentication. Kerberos delegation is not supported by the XenApp Monitoring probe.

Follow these steps:

1. Enable CredSSP on the WinRM client system, either by setting it manually or through a Group Policy setting.

To set it manually enter the following command:

winrm set winrm/config/client/auth '@{CredSSP="true"}'

To set it through a Group Policy, follow these steps:

a. Enter the following command in a Command Prompt window to open the Group Policy dialog:

gpedit.msc

b. Navigate to Computer Configuration\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Client.

c. Double-click on the Allow CredSSP authentication policy in the right pane to open its configuration dialog.

d. Edit the policy as necessary.

2. Enable CredSSP on the WinRM service, either by setting it manually or through a Group Policy setting.

To set it manually enter the following command:

winrm set winrm/config/service/auth '@{CredSSP="true"}'

To set it through a Group Policy, follow these steps:

a. Enter the following command in a Command Prompt window to open the Group Policy dialog:

gpedit.msc

b. Navigate to Computer Configuration\Administrative Templates\Windows Components\Windows Remote Management (WinRM)\WinRM Service.

c. Double-click on the Allow CredSSP authentication policy in the right pane to open its configuration dialog.

d. Edit the policy as necessary.

Probe Configuration


(Optional) Configure Kerberos Authentication

This section describes how to configure Kerberos Authentication on a Windows or Linux system.

Note: Kerberos is not enabled on the XenDesktop server, the probe uses Negotiate Authentication to communicate with the XenApp server.

Important! For Kerberos to work, in Create New Resource dialog box, only hostname should be provided.

Follow these steps:

1. Place the following three configuration files in the probe directory:

■ gssclient.properties

■ jaas.conf

■ krb5-TEMPLATE.conf

2. Determine the file realm name by running the following commands on the XenApp Server machine.

■ echo %userdnsdomain% - Realm

■ echo %LOGONSERVER% - KDC name

3. Rename the krb5-TEMPLATE.conf to krb5.conf

4. Update the krb5.conf file with the file realm name.

Example:

In this example, the file realm name is ASC-FORWARDINC.COM.

[libdefaults]

default_realm = ASC-FORWARDINC.COM

default_tkt_enctypes = RC4-HMAC DES-CBC-MD5 DES-CBC-CRC

default_tgs_enctypes = RC4-HMAC DES-CBC-MD5 DES-CBC-CRC

udp_preference_limit = 1

[realms]

ASC-FORWARDINC.COM = {

kdc = asc-ad.ASC-FORWARDINC.COM

}

[domain_realms]

asc-forwardinc.com = ASC-FORWARDINC.COM

asc-forwardinc.com = ASC-FORWARDINC.COM

5. Verify that the XenApp Server and Probe machines are in the same time zone, and the time-difference between the machines is less than 5 minutes. The Kerberos Authentication mechanism might fail if the machine time is not set correctly.

Kerberos authentications is configured.

Probe Configuration

26 xenapp Guide

General Setup

Click the General Setup button to set the level of details written to the log file for the XenApp Monitoring probe.

Log as little as possible during normal operation to minimize disk consumption. This is a sliding scale, with the level of information logged ranging from fatal errors only to extremely detailed information used for debugging.

Click the Apply button to implement the new log level immediately.

Note: The probe allows you to change the log level without restarting the probe.

Create a New Resource

There are two ways to create a Resource:

■ Click the New Resource button on the toolbar.

■ Right click Resources in the navigation pane and select New Resource.

The Resource (New) dialog box appears. Enter the appropriate field information:

Hostname or IP Address

The hostname or IP address of the XenApp server system. Do not use localhost in place of hostname.

Important! If you use Kerberos authentication, then use only hostname.

Note: If you have multiple servers in a high availability configuration, they must share a single IP address translated using NAT in order to have continuous data collection via the cluster in case of a failover event.

Port

The port number for the XenApp server PowerShell environment. Default is 5985.

Active

Select this checkbox to activate or deactivate monitoring of the resource.

Username

A valid user with administrative privileges that the probe will use to log onto the xenapp server environment.

Note: If you do not have administrative privileges, see Access for Users Without Administrator Permissions (see page 30).

Probe Configuration


Farm Metrics

To allow the probe to get the required metrics, select one or more farm metric groups from this list-box:

Administrators - Queries for the metrics related to administrators belonging to the farm. It fetches metrics like Administrator Name, Type, Id etc.

Application - Queries for the metrics related to applications deployed on the Xenapp servers. It fetches metrics like Application Name, Id, Machine Name, Session Count etc.

LoadEvaluator - Queries for the metrics related to load evaluators of the farm. It fetches metrics like Load Evaluator Name, Id, Load Throttling, Machine Name, Memory Usage, Context Switches etc.

LoadBalancing - Queries for the metrics related to load balancing policies belonging to the farm. It fetches metrics like Policy Name, Id, Priority, Machine Name etc.

WorkerGroup - Queries for the metrics related to worker groups in the farm. It fetches metrics like Worker Group Name, Id, Server Groups, Server Names etc.

Zone - Queries for the metrics related to zones in the farm. It fetches metrics like Zone Name, Machine Name, Data Collector etc.

For more details on the supported metrics, please refer to the Metrics chapter in this document.

Password

Password for the specified user name.

Use SSL

Enables SSL communication between the XenApp Monitoring probe and the XenApp server. Check this box if you are using the HTTPS connection type for WinRM on the XenApp server. Selecting this option enables the Keystore Location and Keystore Password fields.

Keystore Location

Location of the keystore on the disk. The keystore file should be available on the machine where the CA Nimsoft robot and probe are installed. This field is required only if you are using SSL.

Keystore Password

Password for the keystore. This field is required only if you are using SSL.

Probe Configuration

28 xenapp Guide

Query Performance Metrics for Servers

Select this checkbox to activate or deactivate the collection of information about the performance of servers in a XenApp environment. When you enable this option, you must select one or more performance metric groups in the Performance Metrics list box:

IMANetworking Queries for the metrics related to IMA networking performance. It fetches metrics like Bytes Received/sec, Bytes Sent/sec, Network Connections etc.

ICALatency Queries for metrics related to ICA latency time. It fetches metrics like Last Recorded Latency, Session Average Latency, Session Deviation Latency etc.

For ICA metrics other than latency, make sure to select ICASession.

ICASession Queries for the metrics related to ICA sessions of all the applications hosted on a XenApp server. It fetches the metrics like Input/Output Session Bandwidth, Input/Output Session Line Speed, Input/Output Licensing Bandwidth etc.

For ICA metrics other than latency, make sure to select ICASession..

CPUUtilizationMgmtUser Queries for the metrics related to CPU Utilization Mgmt User performance. It fetches metrics like CPU Usage, CPU Shares, CPU Entitlement etc.

SecureTicketAuthority Queries for the metrics related to Secure Ticket Authority. It fetches metrics like Good/Bad Data Request Count, Count of Active Tickets, Peak Data Refresh Rate, Ticket Timeout Count etc.

CitrixLicensing Queries for the metrics related to Citrix licensing performance. It fetches metrics like Average/Maximum/Last Recorded License Check-in and Check-out Response Times, License Server Connection Failure etc.

MetaFramePresentationServer Queries for metrics related to MetaFrame Presentation server performance. It fetches metrics like Application Enumeration/sec, Application Resolutions, DataStore Reads/sec, DataStore Writes/sec, Number of XML Threads, Dynamic Store Reads/sec etc

Processor Queries for metrics related to processor on a XenApp server. It fetches Processor Time Percent metric.

NetworkInterface Queries for metrics related to Network Interface instances in a XenApp server. It fetches Bytes Total Per Sec metric.

LogicalDisk Queries for metrics related to Logical Disk partitions on a XenApp server. It fetches metrics like Disk Queue Length, Disk Sec Read/Write/Transfer, Percent Disk Free Space etc.

System Queries for metrics related to a system. It fetches metrics like Processes, Threads, Processor Queue Length, System Calls Per Sec etc.

Service Queries for metrics related to services running on a Xenapp server. It fetches metrics like Name, Path, Process Id, Status etc.

Probe Configuration


HighCPUMemory Queries for metrics related to processes in a XenApp Server. Only top 10 High CPU Usage and top 10 High Memory Usage processes are shown. For each process, it fetches metrics like Process Name, Process Id, Percent CPU Load, Current Working Set Size, Page Fault Count etc.

For more details on the supported metrics, please refer to the Metrics chapter in this document.

Query Local Host Only

Select this checkbox to fetch XenApp farm metrics and performance metrics only for the XenApp server added as a resource and not from other servers in the farm.

Domain Username

A valid domain user with administrative privileges in the domain containing the XenApp server . The probe uses this user name to log onto the XenApp server environment.

Note: If you do not have administrative privileges, see Access for Users Without Administrator Permissions (see page 30).

Domain Password

Password for the specified domain user.

Note: Domain username and password are mandatory fields if you selected the Query Performance Metrics for Servers checkbox.

Alarm Message

Select the alarm message to be sent if the resource does not respond.

Note: You can edit the message or define a new message using the Message Pool Manager.

Check Interval and Interval Unit

The check interval defines how often the probe checks the values of the monitors. The unit can be set as seconds, minutes, or hours. The default poling interval is 10 minutes. The polling interval should not be smaller than the time required to collect the data, otherwise a data collection error alarm is generated by the probe.

Alternate Resources

In a clustered environment with multiple XenApp servers, add the secondary servers as Alternate Resources so that the probe can monitor all the nodes. Click Add, and the AlternateResource dialog appears. Enter the appropriate information in the Hostname, Port, Username, Password, Use SSL, Keystore Location, and Keystore Password fields.

Test button

Click to verify the connection to the resource.

Probe Configuration

30 xenapp Guide

After completing the fields and testing the connection, click OK to add the resource. The initial data collection/polling cycle starts. The resource hierarchy will populate once the polling cycle has completed.

More information:

Content Pane Updates (see page 16)

Access for Users Without Administrator Permissions

Some users without administrative privileges in the XenApp environment might need access to the XenApp Monitoring. For example, a user might need to query performance metrics. You need to configure access for any local users or domain users who do not have administrative permissions.

Important! You must complete this procedure before configuring the probe. If you do not configure access for non-administrative users, you will receive user authentication errors.

1. Run the following powershell command on XenApp server:

Set-PSSessionConfiguration Microsoft.PowerShell -ShowSecurityDescriptorUI

2. At the prompt, enter: Y

The Permissions window appears.

3. Add the non-administrative local user or non-administrative domain user with the following permissions:

■ For non-administrative local user, assign Read permission.

■ For non-administrative domain user, assign Read and Execute permissions.

Message Pool Manager

You can add, remove, or modify alarm messages. These are the messages sent when a QoS threshold is breached.

Add a New Alarm Message

To add a new alarm message:

1. Click the Message Pool Manager button on the toolbar.

The Message Pool dialog appears.

2. Click the Add button.

The Message Properties dialog appears.

Probe Configuration


3. Complete the field information:

Identification Name

The name of the message.

Token

The type of alarm, either "monitor_error" or "resource_error".

Error Alarm Text

The alarm text sent when a violation occurs. Variables can be used in this field.

Example: $monitor

This variable will put the actual monitor name in the alarm text. There are several available variables: $resource, $host, $port, $descr, $key, $unit, $value, $oper, and $thr.

Clear Alarm Text (OK)

The text sent when an alarm is cleared.

Error Severity

Severity of the alarm.

Subsystem string/id

The NAS subsystem ID for the XenApp server.

4. Click OK to save the new message.

Delete an Alarm Message

To delete an alarm message:



2. Select the message to remove.

3. Click the Remove button.

The alarm message is removed.

4. Close the Message Pool Manager window and click Apply to implement the changes.

Edit an Alarm Message

To edit an alarm message:



2. Select a message ID in the list.

Probe Configuration

32 xenapp Guide

3. Click the Edit button.

The Message Properties dialog appears.

4. Update the message properties as needed.

5. Click OK.

6. Close the Message Pool Manager window and click Apply to implement the changes.

Create New Template

There are two ways to create a new template:

■ Click the New Template button on the toolbar.

■ Right click the Templates node in the navigation pane and select New Template.

See the section Using Templates (see page 38) for more information.

Advanced Configuration

This section describes advanced configuration options for the XenApp Monitoring probe.

Increasing the Heap Space for the Probe

If you have many applications on a xenapp server (represented as a resource in the XenApp Monitoring probe), you may need to increase the heap space for the probe. Heap space is allocated during probe startup. By default the heap space for the XenApp Monitoring probe is 256 MB.

You can increase the heap space setting for the XenApp Monitoring probe in the Raw Configure window for the probe.

Follow these steps:

1. Shift + right-click on the XenApp Monitoring probe in Infrastructure Manager.

2. Choose Raw Configure from the menu.

The Raw Configure dialog opens.

3. Click startup in the left pane.

4. Select the options key and open it for editing.

Probe Configuration


5. Enter a value similar to the following:

-Xms256m Xmx<nnnn>m

where <nnnn> is heap space up to 2048 MB or greater. For example, to increase the heap space to 1024 MB, enter the following:

-Xms256m Xmx1024m

Ensure the machine where the CA Nimsoft robot and probe are deployed has enough RAM.

6. Click OK and Apply.

Adding Servers in a Clustered Environment

The XenApp Monitoring probe can monitor all servers in a clustered environment with multiple xenapp servers. Add one server as the primary resource and the remaining as alternate resources.

Data is collected from the primary resource. If the primary resource is down, data is collected from the next available secondary resource.

Follow these steps:

1. In the XenApp Monitoring probe GUI, click the New Resource icon on the toolbar.

2. Enter the appropriate information in each field of the New Resource dialog box.

3. Click Add in the Alternate Resources section.

This queries the controller for names of xenappservers and populates the drop-down menu for the Hostname field.

4. Select a host in the Hostname field and enter appropriate information in other fields.

5. Click Test to verify that the probe can connect to the resource.

6. Click OK in the AlternateResource dialog.

7. Repeat these steps to add each secondary server as an alternate resource.

Probe Configuration

34 xenapp Guide

Server List Configuration

Configure the probe to fetch metrics only from specified servers.

Follow these steps:

1. Place a text (.txt) file in the probe directory with the name "serversForMetrics_<ResourceName>.txt", where ResourceName is the name of the resource added to the probe, under which metrics for specific servers need to be fetched.

Note: This is an optional configuration, and the absence of this file or an empty file would fetch metrics from all the servers in the farm. Server List configurations will be ignored if "Query Local-host only" is enabled in the Resource dialog box.

2. List the "server names" of all the servers for which performance metrics need to be fetched, one per line in the file.

Note: In the file, if server names which are not part of farm or in which blank lines or IP address are present, polling will be exited immediately on encountering them.

3. Save and close the file.

Note: Repeat steps 1 through 3 for multiple resources, if needed.

The probe is configured to fetch metrics only from specified servers.


Chapter 4: Adding Monitors

There are three different ways to add monitors to XenApp entities:

Manually select the monitors

To manually select and enable monitors, navigate to the target entity within the Resource. This lists its monitors in the right pane. Use the available check boxes to enable QoS monitoring for the selected metrics. To enable Alarm thresholding, you will need to launch the Edit Monitor dialog. See the section Manually Selecting Monitors to be Measured.

Use Templates

Templates let you define reusable sets of monitors to apply to various xenapp monitored entities.

See the section Using Templates (see page 38) for further information.

Use Auto Configurations

Auto Configuration is a powerful way to automatically add monitors to be measured. Monitors are created for new components or items inside the component that are not currently monitored, and would otherwise need manual configuration to be monitored.

Example: Auto Configuration contains an auto-monitor for XenApp server session 'State'. When a new XenApp server session is created, the Auto Configuration feature creates a monitor automatically for monitoring the State property of the session.

See the section Using Automatic Configurations for further information.


Manually Selecting Monitors to be Measured (see page 35) Using Templates (see page 38) Using Automatic Configurations (see page 39)

Manually Selecting Monitors to be Measured

To select a monitor you want to be measured for a resource, click the Resource node in the navigation pane, and navigate through the Resource hierarchy. Select a folder in the hierarchy to see the monitors for it, listed in the right pane. Click the check box beside the Monitors you want to be active.

Note: You can also add monitors using templates (see the section Using Templates (see page 38)).


36 xenapp Guide

Select the All Monitors node to list all monitors currently being measured in the right pane. You can select or deselect monitors here as well.

■ Green icon - the monitor is configured and active

■ Gray icon - the monitor is configured but not active

■ Black icon - the monitor is not configured

Note: If a monitor name is in italics you have changed the configuration but have not applied the changes.

Enabling the Monitors for QoS and Alarming

You can now see the current values for the monitors in the Values column in the monitor list. Selecting the check box next to a monitor name only enables the monitor. To configure the probe to send QoS data and/or send alarms you must modify the properties for each monitor.

Double-click a monitor (or right-click and select Editdialog. See To Edit Monitor Properties (see page 36) for further information.

To Edit Monitor Properties

Double-click a monitor (or right-click and select Editdialog.

Monitors of Type Value

The properties for monitors of type value are as follows:

Name

This is the name of the monitor. The name will be inserted into this field when the monitor is retrieved from the xenapp environment.

Key

This is a read-only field, describing the monitor key.

Description

This is a description of the monitor. This description will be inserted into this field when the monitor is retrieved from the xenapp environment.



Value Definition

This drop-down list lets you select which value to be used, both for alarming and QoS:

You have the following options:

■ The current value. The most current value measured will be used.

■ The delta value (current previous). The delta value calculated from the current and the previous measured sample will be used.

■ Delta per second. The delta value calculated from the samples measured within a second will be used.

■ The average value of the last and current sample: (current + previous) / 2.

■ The average value last ... The user specifies a count. The value is then averaged based on the last "count" items.

Active

This activates the monitoring of the probe.

Enable Alarming

Selecting this option activates the alarming.

Note that the monitor will also be selected in the list of monitors in the right window pane when this option is selected, and that you can enable or disable monitoring of the checkpoint from that list.

This section describes the alarm properties for the monitor.

You can define both a high and a low threshold.

Initially the high threshold is set to the current value. Set this value to match your needs.

The low threshold is initially disabled. If you want to use it, you must select another operator than "disabled" from the list and configure it to match your needs.

Operator

Select from the drop-down list the operator to be used when setting the alarm threshold for the measured value.

Example:

>= 90 means the monitor is in alarm condition if the measured value is equal to or above 90.

= 90 means the monitor is in alarm condition if the measured value is exactly 90.

Threshold

The alarm threshold value. An alarm message is sent when this threshold is violated.

Using Templates

38 xenapp Guide

Unit

This field specifies the unit of the monitored value (for example %, Mbytes etc.). The field is read-only.

Message ID

Select the alarm message to be issued if the specified threshold value is breached. These messages reside in the message pool. You can modify the messages in the Message Pool Manager.

Publish Quality of Service

Select this option if you want QoS messages to be issued on the monitor.

QoS Name

The unique QoS metric. This is a read-only field.

Using Templates

Templates let you define reusable sets of monitors to be measured on multiple XenApp Resources, Farms, Load Evaluators, Servers, Services, Worker Groups, Zones, Administrators, Services, and Applications. Templates allow you to consistently monitor your dynamic XenApp environment.

You can create your own templates and define a set of monitors belonging to each. You can then apply these templates to anything in the Resources or Auto Configurations hierarchies in the navigation pane by dragging the template and dropping it on the appropriate item. This assigns the template monitors to the drop point and everything below it.

If you apply a template to the Auto Configuration, its monitors are applied to all XenApp monitored entities as they appear in the system. If you need a finer level of control, you can apply a template to anything in the Resources hierarchy; in this case the monitors are applied to the drop-point and everything subordinate to it. Any templates applied within the Resources hierarchy are static monitors. The static monitors override any auto monitors for that specific resource entity.

Note: You can do both, placing general-purpose templates in Auto Configuration, and applying special-purpose templates that override the Auto Configuration templates on specific nodes, for specific purposes.

See the Using Automatic Configurations section for details on Auto Configuration.

Using Automatic Configurations


To Create a New Template

There are two ways to create a template:

■ Click the toolbar button for New Template ( ).

■ Right click the Templates node in the navigation pane, and choose New Template from the menu.

In the resulting Template Properties dialog, specify a Name and a Description for the new template.

Note that you can also edit an existing template: Select one of the templates defined under the Templates node in the navigation pane, right-click it, and select Edit from the menu.

To Add Monitors to a Template

There are two ways to add a monitor to a template:

■ Drag it from the content pane and drop it on the template in the navigation pane.

■ Right-click on a monitor in the content pane and select Add to Template.

You can edit the properties for monitors in the template as described in the section To Edit Monitor Properties (see page 36).

To Apply a Template

Drag the monitors in the template to the Auto Configuration node or the Resource component (Farm, Administrator, Server, etc.) where you want it applied, and drop it there.

Note: You can drag the monitors in the template onto an object containing multiple subordinate objects. This applies the template to the entity and all its subordinate entities. A static monitor is created for this entity.


Automatic configuration is an optional but powerful way to automatically add monitors to be measured. This is the preferred method for configuring your resources. When new XenApp monitored entities are detected, "Auto Monitors" are created for devices that are not currently monitored using a static monitor.


40 xenapp Guide

The Auto Configuration feature consists of two sub-nodes located under the Resource node in the navigation pane:

Auto Configuration node

You can add contents from one or more templates or individual checkpoints to this node, using drag and drop. You must click the Apply button of the probe to activate the changes. The probe then searches through the XenApp environment for applicable entities. Auto Monitors representing the monitor(s) under the Auto Configuration node are created (and listed under the Auto Monitors node, see below) for applicable entities where the metric does not already have a static monitor configured against it.

Important! If you are experiencing performance problems, we recommend increasing the polling interval and/or the memory configuration for the probe. Increase memory when the probe is running out of memory. Increase the polling interval when the collection takes longer than the configured interval.

Auto Monitors node

This node lists Auto Monitors, created based on the contents added to the Auto Configuration node. The Auto Monitors are only created for content without a pre-existing static monitor.

Adding a Monitor to the Auto Configurations Node

You can add a single monitor (checkpoint) to the Auto Configurations node.

To list available monitors:

1. Select the Resource node in the navigation pane and navigate to the point of interest.

2. Select an object to list its monitors in the right pane.

3. Add the monitor to the Auto Configurations node by dragging the monitor to the Auto Configurations node and dropping it there.

4. Click the Auto Configurations node and verify that the monitor was successfully added.

Note: You must click the Apply button of the probe to activate configuration changes.



Exploring the Contents of the Auto Configurations Node

To verify that the monitors were successfully added, click the Auto Configurations node in the navigation pane.

■ To edit the properties for a monitor, right-click in the list and choose Edit from the menu. See the section To Edit Monitor Properties (see page 36) for detailed information.

■ To delete a monitor from the list, right-click in the list and choose Delete from the menu.

Note: You must click the Apply button and restart the probe to activate configuration changes.

Checking the Auto Monitors Node

Note: When monitors have been added to the Auto Configurations node, you must click the Apply button and restart the probe to activate the Auto Configuration feature.

When you restart the probe, it searches through the Resource's entities. For each one that is currently not monitored, an Auto Monitor is created for each of the monitors listed under the Auto Configurations node.

All defined Auto Monitors are listed under the Auto Monitors node.

The assigned resources limit the scope of Auto Configurations, Auto Monitors, and monitors in the probe. The Auto Configurations and Auto Monitors are separate for each resource.


Chapter 5: Metrics

This section describes the metrics for the XenApp Monitoring probe.


Farm Node (see page 43) Administrators Node (see page 43) Applications Node (see page 44) LoadBalancingPolicy Node (see page 48) LoadEvaluator Node (see page 48) Servers Node (see page 50) WorkerGroups Node (see page 64)

Farm Node

Metrics Unit Description

AdministratorType Enumeration

The type of administrator for the user connecting to this farm. Values are:

0--Unknown

1--Full

2--View Only

3--Custom

4--Null

FarmName String The name of the farm.

MachineName String The name of the computer that created this instance.

ServerVersion String The version of the server to which this client is connected

SessionCount Integer Gets the user session count.

ActiveSessionCount Integer Gets the user active session count.

Administrators Node


AdministratorId String The ID of this object.

AdministratorName String A Citrix administrator friendly name.

Applications Node

44 xenapp Guide


AdministratorType Enumeration

The type of Citrix administrator. Values are:

0--Unknown

1--Full

2--View Only

3--Custom

4--Null

Enabled Boolean Indicates if Citrix administrator is enabled.

FarmPrivileges String The farm level privileges.

FolderPrivileges String The folder level privileges.


Applications Node


AccessSessionConditions String A collection of access conditions, at least one of which must be met by incoming Access Gateway connections. This collection might be empty but it won't be null. This collection is ignored if AllowConnectionsThroughAccessGateway is false.

If this collection is empty, then any Citrix Access Gateway connection is allowed. Otherwise, the Citrix Access Gateway connection must meet at least one filter-farm combination in this list. The first part of the KeyValuePair is the Access Gateway farm name and the second part of the pair is the filter name.

AccessSessionConditionsEnabled Boolean Indicates if the list of conditions is enabled.

AddToClientDesktop Boolean If value is true, create a shortcut to this application on the

AddToClientStartMenu Boolean enu.

AlternateProfiles String A collection of alternate UNC paths and IP addresses to use for this streamed application, to provide better performance.

AnonymousConnectionsAllowed Boolean If value is true, allow all client users to start the application without specifying a user name, domain name and password.

ApplicationId String The ID of this object.

Applications Node



ApplicationType Enumeration

The type of application. Values are:

0--Unknown

1--ServerInstalled

2--ServerDesktop

3--Content

4--StreamedToServer

5--StreamedToClient

6--StreamedToClientOrInstalled

7--StreamedToClientOrStreamedToServer

8--Null

AudioRequired Boolean If value is true, deny connections that cannot support the default audio type. This property is valid only if DefaultAudioType is not set to NotRequired.

AudioType Enumeration

The legacy audio type to use by default. Values are:

0--Unknown

1--None

2--Basic

3--Null

BrowserName String The published application's name. Must be unique in a farm and cannot be null. The length of the name must not exceed 48 characters.

CachingOption String The type of caching to use for this streamed application. This property is valid only if AllowOfflineAccess is set to true.

ClientFolder String The location of the application in the Program Neighborhood interface, backslash-delimited.

ColorDepth Enumeration

The color depth to use by default. Values are:

0--Unknown

1--Colors8Bit

2--Colors16Bit

3--Colors32Bit

4--Null

CommandLineExecutable String The default initial program.

ConnectionsThroughAccessGatewayAllowed

Boolean If value is true, allow connections to this application through Citrix Access Gateway.

ContentAddress String The UNC or URL of the published content

Applications Node

46 xenapp Guide


CpuPriorityLevel Enumeration

The CPU priority level to use for this application. By default, this is CpuPriorityLevel.Normal. Values are:

0--Unknown

1--BelowNormal

2--Low

3--Normal

4--AboveNormal

5--High

6---Null

Description String The description for the published application. The length of the description must not exceed 255 characters.

DisplayName String The name of the application. This name is not guaranteed to be unique in the system, however the name must be unique under the parent folder where the application is located. The length of the name must not exceed 255 characters.

Enabled Boolean If value is true, the published object will be available to users.

EncryptionLevel Enumeration

The default encryption level for the application's sessions. Values are:

0--Unknown

1--Basic

2--LogOn

3--Bits40

4--Bits56

5--Bits128

6--Null

EncryptionRequired Boolean If value is true, deny connections that cannot support the default encryption level. This property is valid only if DefaultEncryptionLevel is not set to Basic.

FolderPath String The parent folder path of the published application.

HideWhenDisabled Boolean If value is true, hide the application when disabled.

InstanceLimit Integer Restrict the number of concurrent instances of this published application in the farm to this number. Specify -1 for no limit. Zero is not a legal value for this property.

LoadBalancingApplicationCheckEnabled Boolean If value is true, enable application installation check during load balancing.

Applications Node




MaximizedOnStartup Boolean If value is true, maximize the application window on startup.

MultipleInstancesPerUserAllowed Boolean If value is true, limit each user to only one instance of this application at a time.

OfflineAccessAllowed Boolean If value is true, support offline access.

OtherConnectionsAllowed Boolean If value is true, allow connections to this application through things other than Citrix Access Gateway

PreLaunch Boolean If value is true, the application is a special pre-launched application.

ProfileLocation String The UNC path of the profile to use by default.

ProfileProgramArguments String The arguments to pass into the streamed application.

ProfileProgramName String The name of the application in the profile to use.

RunAsLeastPrivilegedUser Boolean If set to true, run this streamed application as a least-privileged user.

SequenceNumber Integer The internal sequence number of the application.

SessionCount Integer The user session count for the application.

SslConnectionEnabled Boolean If value is true, allow SSL connections to this application. This cannot be enforced as a minimum requirement on the client side.

StartMenuFolder String The location of the shortcut within the start menu, backslash-delimited. This property is valid only when AddToClientStartMenu is set to true.

TitleBarHidden Boolean If value is true, hide the application window's title bar.

WaitOnPrinterCreation Boolean If value is true, wait for printers to be auto-created before starting this application.

WindowType String The window size/type to use by default.

WorkingDirectory String The default working directory ( on a per-server basis), or empty for a server desktop or not to specify a working directory.

overrideable

LoadBalancingPolicy Node

48 xenapp Guide

LoadBalancingPolicy Node


Description String Specifies the new description for the policy.

Enabled Boolean Enable or disable this policy.


PolicyId String The ID of this object.

PolicyName String Specifies name of a policy.

Priority Integer Set the priority for this policy. This number is used to sort policies. A priority number of 1 is the highest. By default, new policies are given the lowest priority.

LoadEvaluator Node


ApplicationBrowserName String The browser name of published application in the application usage rule.

ApplicationUserLoad Integer The application load for the application usage rule.

ApplicationUserLoadEnabled Boolean The application usage rule enabled flag.

ContextSwitches Integer The number of context switches for the context switch rule.

ContextSwitchesEnabled Boolean The context switches rule enabled flag.

CpuUtilization String The CPU utilization threshold for the CPU utilization rule.

CpuUtilizationEnabled Boolean The CPU utilization rule enabled flag.

Description String The load evaluator description.

DiskDataIO String The disk data IO setting for the disk data IO rule.

DiskDataIOEnabled Boolean The disk data IO rule enabled flag.

DiskOperations Integer The setting for disk operations rule.

DiskOperationsEnabled Boolean The disk operations rule enabled flag.

FridaySchedule String Friday schedules for the scheduling rule.

IPRanges String The IP ranges for the IP range rule.

IPRangesAllowed Boolean The allowed IP ranges for the IP range rule.

LoadEvaluator Node



IPRangesEnabled Boolean The denied IP ranges for the IP range rule.

IsBuiltIn Boolean Indicates if this is a built-in load evaluator (Default, Advanced).

LoadEvaluatorId String The ID of this object.

LoadEvaluatorName String The load evaluator name.

LoadThrottling Enumeration

Load throttling setting for the load throttling rule. Values are:

0--Unknown

1--Extreme

2--High

3--MediumHigh

4--Medium

5--MediumLow

6--Null

LoadThrottlingEnabled Boolean The load throttling rule enabled flag.


MemoryUsage String The memory usage setting for the memory usage rule.

MemoryUsageEnabled Boolean The memory usage rule enabled flag.

MondaySchedule String Monday schedules for scheduling rule.

PageFaults String Page faults setting for the page fault rule.

PageFaultsEnabled Boolean The page fault rule enabled flag.

PageSwaps String The page swaps setting for the page swap rule.

PageSwapsEnabled Boolean The page swap rule enabled flag.

SaturdaySchedule String Saturday schedules for scheduling rule.

ScheduleEnabled Boolean The scheduling rule enabled flag.

ServerUserLoad Integer The server usage setting for the server usage load rule.

ServerUserLoadEnabled Boolean The server usage load rule enabled flag.

SundaySchedule String Sunday schedules for scheduling rule.

ThursdaySchedule String Thursday schedules for scheduling rule.

TuesdaySchedule String Tuesday schedules for scheduling rule.

WednesdaySchedule String Wednesday schedules for scheduling rule.

Servers Node

50 xenapp Guide

Servers Node


CitrixEdition String The Citrix product edition.

CitrixEditionString String The custom Citrix product edition value.

CitrixInstallDate String The Citrix product installation date.

CitrixInstallPath String The Citrix product installation path.

CitrixProductName String The Citrix product name.

CitrixServicePack String The Citrix product service pack information.

CitrixVersion String The Citrix product version.

ElectionPreference Enumeration

The zone election preference. Values are:

0--Unknown

1--MostPreferred

2--Preferred

3--DefaultPreference

4--NotPreferred

5--WorkerMode

6--Null

FolderPath String The parent folder path name.

IcaPortNumber Integer The configured ICA port number.

IPAddresses String The IP addresses. It includes IPV4 and IPV6 addresses.

Is64Bit Boolean Indicates if this server is running a 64-bit operating system.

IsSpoolerHealthy Enumeration

The health of the server print spooler. Values are:

0--False

1--True

2--Unknown

3--Null

LicenseServerName String The license server server name. This setting is only displayed for the server where cmdlet is executed.

LicenseServerPortNumber Integer The license server port number. This setting is only displayed for the server where cmdlet is executed.

Servers Node



LogOnMode Enumeration

Gets the logon control mode. Values are:

0--Unknown

1--AllowLogOns

2--ProhibitNewLogOnsUntilRestart

3--ProhibitNewLogOns

4--ProhibitLogOns

5--Null

LogOnsEnabled Boolean Indicates if logons are enabled.


OSServicePack String The operating system service pack information.

OSVersion String The operating system version number.

PcmMode Enumeration

The Power Management Control Mode. Values are:

0--Unknown

1--Normal

2--DrainUntilRestart

3--Drain

4--Null

RdpPortNumber Integer The configured RDP port number.

ServerFqdn String The FQDN (Fully Qualified Domain Name) of the server.

ServerId String The ID of the server.

ServerName String The name of the server. This name is unique in the farm.

SessionCount Integer The user session count.

ZoneName String The zone name where this server belongs.

Processes Nodes


AccountDisplayName String The user account display name.

BasePriority Long The base priority.

CreationTime String The creation time.

CurrentPagedPoolQuota Bytes The current paged pool quota.

CurrentVirtualSize Bytes The current virtual memory size.

Servers Node

52 xenapp Guide


CurrentWorkingSetSize String The current working set size.

KernelTime Long The kernel time.


PageFaultCount Long The page fault count.

PageFileUsage KBytes The page file use.

ParentId Integer The process Id of the parent process.

PeakNonPagedPoolQuota Bytes The peak non-paged pool quota.

PeakPagedPoolQuota Bytes The peak paged pool quota.

PeakVirtualSize Bytes The peak virtual memory size.

PeakWorkingSetSize KBytes The peak working set size.

PercentCpuLoad Percent The percent of CPU load.

PrivatePageCount Long The private page count.

ProcessId Integer The process Id.

ProcessName String The process name.

ServerName String The server name.

SessionId Long The session Id.

Servers Node



State Enumeration

The process state. Values are:

0--Unknown

1--Initialized

2--Ready

3--Running

4--Standby

5--Terminated

6--InTransit

7--Executive

8--WaitingFreePage

9--WaitingPagedIn

10--WaitingPoolAlloc

11--Delayed

12--Suspended

13--WaitingUserRequest

14--EventHigh

15--EventLow

16--LpcReceive

17--LpcReply

18--WaitingMemory

19--PageOut

20--WaitOther

21--Null

UserTime Long The user time.

PerformanceMetrics Nodes

Node Metrics Unit Description

CitrixLicensing AvgLicenseCheckInRespTime Long The average license check-in response time in milliseconds.

AvgLicenseCheckOutRespTime Long The average license check-out response time in milliseconds.

LastRecordedLicenseCheckInRespTime

Long The last recorded license check-in response time in milliseconds.

LastRecordedLicenseCheckOutRespTime

Long The last recorded license check-out response time in milliseconds.

Servers Node

54 xenapp Guide

LicenseServerConnectFailure Long The number of minutes that the XenApp server has been disconnected from the License Server.

MaxLicenseCheckInRespTime Long The maximum license check-in response time in milliseconds.

MaxLicenseCheckOutRespTime Long The maximum license check-out response time in milliseconds.

CPUUtilizationMgmtUser

AccountName String The user account display name.

BrowserName String The name of the published application associated with this CPUUTIL.

ClientAddress String The client address.

CPUEntitlement Percent The percentage of CPU resource that Citrix CPU Utilization Management makes available to a user at a given time.

CPUReservation Percent The percentage of total computer CPU resource reserved for a user, should that user require it.

CPUShares Percent The client address.

CPUUsage Percent The percentage of CPU resource consumed by a user at a given time, averaged over a few seconds.

LongTermCPUUsage Percent The percentage of CPU resource consumed by a user, averaged over a longer period than the CPU Usage counter.

ServerName String The Netbios name of the server hosting the CPUUTIL.

ICASession AccountName String The user account display name.

BrowserName String The name of the published application associated with this ICASESSION.


InputSessionCompression Double The compression ratio used from client to server for a session.

Servers Node


InputSessionLineSpeed BPS The line speed, measured in bps, used from client to server for a session.

LatencyLastRecorded MilliSeconds

The last recorded latency measurement for the session.

LatencySessionAvg MilliSeconds

The average client latency over the lifetime of a session.

LatencySessionDeviation MilliSeconds

The difference between the minimum and maximum measured latency values for a session.

OutputSessionCompression Double The compression ratio used from server to client for a session.

OutputSessionLineSpeed BPS The line speed, measured in bps, used from server to client for a session.

ServerName String The Netbios name of the server hosting the ICASESSION.

ResourceShares Long The total number of shares used by the session.

IMANetworking BytesReceivedPerSec BytesPerSec

The inbound bytes per second.

BytesSentPerSec BytesPerSec

The outbound bytes per second.

NetworkConnections Long The number of active IMA network connections to other IMA servers.

LogicalDisk DiskQueueLength Long Current Disk Queue Length.

DiskSecRead Double The average time Disk Reads took to complete, in seconds.

DiskSecTransfer Double The average time Disk Transfers took to complete, in seconds.

DiskSecWrite Double The average time Disk Writes took to complete, in seconds.

PercentDiskFreeSpace Percent The percentage of total Free Space on Disk.

PercentDiskTime Percent Percent Disk Time.

MetaframePresentationServer

AppEnumerationsPerSec Double The number of application enumerations per second.

Servers Node

56 xenapp Guide

AppResolFailedPerSec Double The number of application resolutions failed per second.

AppResolutionsPerSec Double The number of resolutions completed per second.

AppResolutionTime Long The time in milliseconds that a resolution took to complete.

CumulativeServerLoad Long Cumulative server load.

DatastoreBytesRead Long The number of bytes read from the data store.

DataStoreBytesReadPerSec BytesPerSec

The number of bytes of data store data read per second.

DataStoreBytesWrittenPerSec BytesPerSec

The number of bytes of data store data written per second.

DataStoreConnectionFailure Long The number of minutes that the XenApp server has been disconnected from the data store.

DatastoreReads Long The number of times data was read from the data store.

DataStoreReadsPerSec Double The number of times data was read from the data store per second.

DataStoreWritesPerSec Double The number of times data was written to the data store per second.

DynamicStoreBytesReadPerSec BytesPerSec

The number of bytes of dynamic store data read per second.

DynamicStoreBytesWrittenPerSec BytesPerSec

The number of bytes of dynamic store data written per second.

DynamicStoreGatewayUpdateBytesSent

Long The number of bytes of data sent across gateways to remote data collectors.

DynamicStoreGatewayUpdateCount Long The number of dynamic store update packets sent to remote data collectors.

DynamicStoreQueryCount Long The number of dynamic store queries performed.

DynamicStoreQueryRequestBytesReceived

Long The number of bytes of data received in dynamic store query request packets.

Servers Node


DynamicStoreQueryResponseBytesSent

Long The number of bytes of data sent in response to dynamic store queries.

DynamicStoreReadsPerSec Double The number of times data was read from the dynamic store per second.

DynamicStoreUpdateBytesReceived Long The number of bytes of data received in dynamic store update packets.

DynamicStoreUpdatePcktReceived Long The number of update packets received by the dynamic store.

DynamicStoreUpdateRespBytesSent Long The number of bytes of data sent in response to dynamic store update packets.

DynamicStoreWritesPerSec Double The number of times data was written to the dynamic store per second.

FilteredAppEnumsPerSec Double The number of filtered application enumerations per second.

ICARoundTripLatencyMedian Long ICA round trip latency median.

LocalHostCacheBytesReadPerSec BytesPerSec

The number of bytes of IMA local host cache data read per second.

LocalHostCacheBytesWrittenPerSec BytesPerSec

The number of bytes of IMA local host cache data written per second.

LocalhostCacheReadsPerSec Double The number of times data was read from the IMA local host cache per second.

LocalhostCacheWritesPerSec Double The number of times data was written to the IMA local host cache per second.

MaxXMLThreads Long The maximum number of threads allocated to service Web-based sessions since the server restarted.

NumBusyXMLThreads Long The number of busy threads.

NumXMLThreads Long The number of threads allocated to service Web-based sessions.

ResolWorkItemQueueExecCount Long The number of resolution work items currently being executed.

ResolWorkItemQueueReadyCount Long The number of resolution work items ready to be executed.

Servers Node

58 xenapp Guide

WorkItemQueueExecCount Long The number of work items currently being executed.

WorkItemQueuePendingCount Long The number of work items not yet ready to be executed.

ZoneElections Long The number of zone elections that occurred. This value starts at zero each time the IMA Service starts and is incremented each time a zone election takes place.

ZoneElectionsTriggered Long The number of zone elections triggered.

ZoneElectionsWon Long The number of times the server won a zone election.

NetworkInterface BytesTotalPerSec BytesPerSec

The rate at which the network adaptor is processing data bytes.

Processor ProcessorTimePercent Percent The percentage of time the processor is busy.

SecureTicketAuthority BadDataReqCount Long The total number of unsuccessful ticket validation and data retrieval requests during the lifetime of the Secure Ticket Authority (STA).

BadRefreshReqCount Long The total number of unsuccessful ticket refresh requests received during the lifetime of the STA.

BadTcktReqCount Long The total number of unsuccessful ticket generation requests received during the lifetime of the STA.

CountOfActiveTickets Long Total count of active tickets currently held in the STA.

GoodDataReqCount Long The total number of successful ticket validation and data retrieval requests received during the lifetime of the STA.

GoodRefreshReqCount Long The total number of successful ticket refresh requests received during the lifetime of the STA.

GoodTcktReqCount Long The total number of successful ticket generation requests received during the lifetime of the STA.

Servers Node


PeakAllReqRate Double The maximum rate of all monitored activities per second.

PeakDataReqRate Double The maximum rate of data requests per second during the lifetime of the STA.

PeakTcktRefreshRate Double The maximum rate of ticket generation requests per second during the lifetime of the STA.

PeakTicketReqRate Double The maximum rate of refresh requests per second during the lifetime of the STA.

TicketTimeoutCount Long The total number of ticket time-outs that occur during the lifetime of the STA.

System ProcessorQueueLength Long Processor queue length.

ServerName String The name of the server.

SystemUpTime Long System up time.

SystemCallsPerSec Long System calls per second.

Threads Long Threads running.

Processes Long Processes running.

PercentRegistryQuotaInUse Long Percent registry quota in use.

ContextSwitchesPerSec Long Context switches per second.

Services Node


DesktopInteract Boolean The DesktopInteract of the service.

DisplayName String The display name of the service.

ErrorControl Enumeration

The ErrorControl of the service. Values are:

0 - Ignore

1 - Normal

2 - Severe

3 - Critical

4 - Null

ExitCode Integer The ExitCode of the service.

Servers Node

60 xenapp Guide


Name Enumeration

The type of service. Values are:

1 - Kernel Driver

2 - File System Driver

3 - Adapter

4 - Recognizer Driver

5 - Own Process

6 - Share Process

7 - Interactive Process

8 - Null

Path String The path of the service.

ProcessId Integer The ProcessId of the service.

ServiceType Enumeration

The Type of Service. Values are:

1 - Kernel Driver

2 - File System Driver

3 - Adapter

4 - Recognizer Driver

5 - Own Process

6 - Share Process

7 - Interactive Process

8 - Null

Started Boolean The service has been started.

StartMode Enumeration

The StartMode of the service. Values are:

0 - Boot

1 - System

2 - Auto

3 - Manual

4 - Disabled

5 - Null

Servers Node



State Enumeration

The state of the service. Values are:

1 -Stopped

2 -StartPending

3 - StopPending

4 - Running

5 - ContinuePending

6 - PausePending

7 - Paused

8 - Null

Status String The status of the service.

Zone Node


DataCollector String The zone data collector.


ZoneName String The zone name.

Session Node


AccessSessionGuid String The access session GUID.

AccountName String The user account display name.

ApplicationState Enumeration

Application state for the session. Values are:

0--NotApplicable

1--Active

2--PreLaunch

3--Lingering

4--NoApplication

5--Null

BrowserName String The name of the published application associated with this session.


Servers Node

62 xenapp Guide


ClientBuffers String The client side buffer size for ICA video.

ClientBuildNumber Integer The build number of the client, or zero if not applicable.

ClientCacheDisk Integer The client cache disk.

ClientCacheLow Integer Client Cache Low.

ClientCacheMinBitmapSize Integer Client Cache Min Bitmap Size.

ClientCacheSize Integer Client Cache Size.

ClientCacheTiny Integer Client Cache Tiny.

ClientCacheXms Integer Client Cache Xms.

ClientDirectory String The client installation directory.

ClientId Long The client Id.

ClientIPV4 String The version-4 IP address of the client.

ClientName String The client name of the session (usually but not always the Netbios name of the client computer).

ClientProductId Integer An identifier that is generated based on the client IP address, client name, and/or other client data. This identifier is not guaranteed to be always unique. But it is unique most of the time.

ClientType String The type of client running this session.

ClientVersion String The client version.

ColorDepth Enumeration

The color depth of the client, or ColorDepth.Unknown if not applicable. Values are:

0--Unknown

1--Colors8Bit

2--Colors16Bit

3--Colors32Bit

4--Null

ConnectTime String The last connection time of this session, in UTC. Null if not applicable.

CurrentTime String The time of day that information about this session was retrieved, in UTC. Null if not applicable.

DirectXEnabled Boolean Indicates if DirectX is enabled on the client.

DisconnectTime String The last disconnect time of this session, in UTC. Null if not applicable.

Servers Node



EncryptionLevel Enumeration

The encryption level of the session. Values are:

0--Unknown

1--Basic

2--LogOn

3--Bits40

4--Bits56

5--Bits128

6--Null

FlashEnabled Boolean Indicates if Flash is enabled on the client.

HorizontalResolution Integer The horizontal resolution of the session in pixels, or zero if not applicable.

LastInputTime String The last input time of this session, in UTC. Null if not applicable.

LogOnTime String The time that this session logged on, in UTC. Null if not applicable.


Protocol Enumeration

The protocol of this session. Values are:

0--Unknown

1--Ica

2--Rdp

3--Console

4--Null

ServerBuffers String The server side buffer size for ICA video.

ServerName String The Netbios name of the server hosting the session.

SessionId Long The session Id.

SessionName String The session name.

SmartAccessFilters String The smart access filters.

WorkerGroups Node

64 xenapp Guide


State Enumeration

The state of this session. Values are:

0--Unknown

1--Active

2--Connected

3--Connecting

4--Shadowing

5--Disconnected

6--Idle

7--Listening

8--Resetting

9--Down

10--Initializing

11--Stale

12--Licensed

13--Unlicensed

14--Reconnected

15--Null

UsbEnabled Boolean Indicates if USB is enabled on the client.

VerticalResolution Integer The vertical resolution of the session in pixels, or zero if not applicable.

VirtualIP String The Virtual IP address of the session, or empty if Virtual IP is not in use.

WmpEnabled Boolean Indicates if Windows Media Player is enabled on the client.

WorkerGroups Node


Description String Worker group description.

FolderPath String The folder path.


OUs String The organizational units.

ServerGroups String The server groups.

ServerNames String The server names.

WorkerGroups Node



WorkerGroupId String The ID of this object.

WorkerGroupName String Worker group name.


Appendix A: Troubleshooting

This section contains troubleshooting tips for the XenApp Monitoring probe.


Probe Not Collecting Data (see page 68) Out of Memory Errors (see page 68) Probe Delays in Fetching XenApp Farm Data (see page 69) Probe Not Fetching Performance Metrics for some Servers in Farm (see page 70) Probe Not Fetching Performance Metrics even when WinRM Enabled (see page 71) Probe Not Fetching ICA Latency Metrics (see page 71) Known Issues (see page 72)

Probe Not Collecting Data

68 xenapp Guide

Probe Not Collecting Data

Symptom:

The probe is not collecting data.

Solution 1:

The probe may not be able to connect to the XenApp environment. There are several issues that can cause this. See the Connecting to the XenApp Environment (see page 16) section of this document, including the subsection on Troubleshooting Connection Issues (see page 22).

Solution 2:

You may need to allocate more memory for the probe to execute PowerShell commands on the XenApp server. We recommend setting this to 1024 MB during initial configuration for the XenApp Monitoring probe. However, in some cases this may need to be increased.

Check the xenapp.log file for the following message:

Process is terminated due to StackOverflowException

If you see this message, enter the following command on the XenApp server:

winrm set winrm/config/winrs @{MaxMemoryPerShellMB="nnnn"}

where nnnn is a number greater than 1024.

Solution 3:

Note: This solution is only valid when Kerberos Authentication is enabled.

You might get the Kerberos error, "Clock Skew too great while getting initial ticket".

This error occurs when there is a time difference between the XenApp server and the probe machine. Verify that both the XenApp server and probe machines are in the same time zone, and the time difference between the machines is not more than 5 minutes.

Out of Memory Errors

Symptom:

Out of memory errors.

Solution:

If you have many applications on a XenApp server (represented as a resource in the XenApp Monitoring probe), you may need to increase the heap space for the probe. For instructions, see Increasing the Heap Space for the Probe (see page 32).

Probe Delays in Fetching XenApp Farm Data


Probe Delays in Fetching XenApp Farm Data

Symptom:

The Add-PSSnapin cmdlet sometimes takes more time, around 60 to 90 seconds. This happens sometimes when the Xenapp Server is not connected to internet, while loading the XenApp SDK Snapin in PowerShell, system tries to verify the Authenticode signature and hence takes more time.

Solution:

To resolve this issue, you can either provide the computer with internet access so it can verify the Authenticode signature, or disable the Authenticode signature checking feature for Microsoft Management Console as mentioned below.

On the XenApp server added under Resources

■ Open "Internet Options" in the Control Panel or Internet Explorer

■ Click the "Advanced" tab

■ Scroll down to "Security"

■ Uncheck "Check for publisher's certificate revocation"

■ Uncheck "Check for server certificate revocation"

■ Click OK

Probe Not Fetching Performance Metrics for some Servers in Farm

70 xenapp Guide

Probe Not Fetching Performance Metrics for some Servers in Farm

Problem:

Resources are configured to fetch performance metrics from specific servers by placing the file "serversForMetrics_<ResourceName>.txt " in Xenapp probe directory on the probe machine; as a result, the servers from which metrics are not fetched might not be listed in the file.

Note: This is an optional configuration, and absence of this file would fetch metrics from all the servers in the farm. More information: Server List Configuration (see page 34).

Solution:

Go the probe installed location and check if the file serversForMetrics_<ResourceName>.txt is present. If the file is present, open the file and check if the server name (from which metrics are not coming) is present in the list.If the name is not present, then append the name to the list, save the file and close it.

Problem:

WinRM configuration is not enabled on the server from which metrics are not fetched. WinRM configuration must be enabled in all servers in the farm from which metrics have to be collected.

Solution:

Enable Winrm configuration on the server from which metrics are not fetched. More information: Configure WinRM and PowerShell (see page 18)l.

Probe Not Fetching Performance Metrics even when WinRM Enabled


Probe Not Fetching Performance Metrics even when WinRM Enabled

Problem:

The probe will not fetch metrics if WinRM is not configured properly.

Solution:

1. Run the below command on windows prompt in the server from which metrics are not coming: winrm get winrm/config/service

2. In the command result, check that the property - AllowUnencrypted = true

3. If the above property value is 'false', then run the below command:

4. winrm set winrm/config/service @{AllowUnencrypted="true"}

5. -1

Probe Not Fetching ICA Latency Metrics

Problem:

Probe fetching all performance metrics except those related to Citrix ICA Latency.

Solution:

1. On Windows servers, open Windows Registry Editor (go to Start->Run, and type "regedit" and Enter)

2. In the Registry Editor, traverse to the path mentioned below:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\CitrixICA\P

erformance

3. Check if the value of the registry Disable Peformance Counters is 1.

4. If the value of the registry is 0, then open the registry Disable Performance Counters and change the value of the registry from 1 to 0.

5. Save the registry value.

6. In the next polling interval, verify that the probe fetches the ICA Latency metrics.

Known Issues

72 xenapp Guide

Known Issues 1. In locales where the system settings are in languages other than English, the probe

may not be able to fetch data for metrics with decimal points.

2. Authentication failure can happen intermittently when the SSL option is enabled while configuring a domain user for a resource

Nimsoft Monitor xenapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/xenapp/1.0/xenap… ·...

Documents

Transcript of Nimsoft Monitor xenapp Guidedocs.nimsoft.com/prodhelp/en_US/Probes/Catalog/xenapp/1.0/xenap… ·...