User Connection Failures

If a user complains that his/her connections to a desktop/application failed, then adinistrators must be able to quickly detect the failure and accurately zero-in on the reason for the failure, so that the problem can be fixed and the user connection can be restored. The User Connection Failures test helps administrators do just that! This test monitors the user connections to each delivery group in a site, promptly detects connection failures, and accurately indicates what caused the failure – is it due to a problem at the client side? is it owing to configuration errors? is it because of machine failures? is it due to the exhaustion of delivery group capacity? or is it due to the absence of a license?

Target of the test : A Citrix Director 7.x

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each delivery group configured in the XenDesktop broker site

Configurable parameters for the test
  1. Test period - How often should the test be executed
  2. Host - The host for which the test is to be configured.
  3. port – The port number at which the specified HOST listens to. By default, this is 80.
  4. controller ip address – Specify the IP address of the delivery controller (i.e., broker) in the site with which the eG agent should communicate for collecting performance metrics.
  5. controller port – Specify the port number of the delivery controller (i.e., broker) in the site with which the eG agent should communicate for collecting performance metrics.
  6. USERNAME and password – To connect to a delivery controller and pull out metrics from it, the eG agent requires Farm Administrator rights. In order to configure the eG agent with Farm Administrator privileges, specify the credentials of the Farm Administrator in the username and password text boxes.
  7. CONFIRM PASSWORD – Confirm the PASSWORD by retyping it here.
  8. fully qualified DOMAIN name – Here, specify the fully-qualified name of the domain to which the specified controller belongs.
  9. ssl – Indicate whether/not the controller used for metrics collection  is SSL-enabled. By default, this flag is set to Yes.
  10. report by machine type – If you want the results of this test to be grouped by machine type then set this flag to Yes. In this case therefore, the machine types (desktop or server OS machines) will be the primary descriptors of this test; expanding them will reveal the secondary descriptors – i.e., the delivery groups containing machines of each type. If you want the results of this test to be indexed only by the names of delivery groups, then set this flag to No.
  11. DD FREQUENCY - Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against dd frequency.
  12. DETAILED DIAGNOSIS - To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability
    • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Client connection failures:

Indicates the number of connections to this delivery group that failed due to a problem at the client side.

Number

The value of this measure indicates the number of connection failures that occurred due to the inability of the client side to complete the session connection; for example, connection timed out, server was not reachable.

Configuration errors:

Indicates the number of connections to this delivery group that failed due to configuration errors.

Number

Connection failures can also occur when administrators change the configuration of the broker; for instance, a failure may occur when administrators put a delivery group or a machine in maintenance mode. 

Machine failures:

Indicates the number of connections to this delivery group that failed due to machine failures.

Number

This refers to connections that failed because the machines that need to launch the sessions itself failed. For probable reasons, refer to the measures of the Failed Machines test. 

Unavailable capacity:

Indicates the number of connections to this delivery group that failed because the configured capacity of the machines was consumed.

Number

This refers to failures that occurred due to the configured capacity of a particular delivery group having been completely consumed. For example, too many users logged into a Server Desktop OS delivery group or a user accessing a Pooled Random delivery group once all the machines in the delivery group are already assigned to other users.

Unavailable licenses:

Indicates the number of connections to this delivery group that failed because of the absence of a license.

Number

These are failures that occur due to the inability of the delivery controller to acquire a license from the license server to launch a session.