Horizon User Logon Details Test

This test tracks and analyzes the detailed logon sequence for every user connecting to a virtual desktop or application through an Omnissa Horizon pod or cluster. It captures granular metrics across all key stages of the logon process, including client connectivity, authentication, session brokering, machine selection and preparation, user profile loading, logon script execution, shell initialization etc. Each measure reflects a specific step in the user's logon flow, enabling precise visibility into where delays or issues may occur. Monitoring these metrics is essential for maintaining optimal performance and availability across the Horizon infrastructure. If any of these measures show abnormal values (e.g., spikes in profile load time or broker launch delay), it may indicate issues such as:

  • Backend resource contention (e.g., overloaded VMs or brokers),

  • Profile service or Active Directory delays,

  • Inefficient logon scripts or policies,

  • Network congestion or endpoint instability.

By continuously monitoring the Horizon cluster using this test, administrators can detect and resolve performance bottlenecks before they impact end users. The test helps identify which specific phase of the logon process is responsible for slowness or failure, allowing for targeted troubleshooting. It also enables correlation of issues with backend system health, recent policy changes, or user-specific conditions. As a result, administrators can ensure faster and more reliable user logon experiences across the Horizon environment.

Target of the test : An Omnissa Horizon Cluster/Pod

Agent deploying the test : A remote agent

Outputs of the test : One set of results for every user to Omnissa Horizon Cluster/Pod being monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.

Host

The host for which the test is to be configured.

Port

Refers to the port used by the target Omnissa Horizon Cluster/Pod. By default, this is set to NULL.

Connection Server Name

By default, this test connects to every Horizon Connection Server configured in the Omnissa Horizon Cluster/Pod remotely and collects the required metrics. For this, it is necessary to specify valid credentials of the Horizon Connection Servers. To help administrators provide these credentials quickly and easily, the eG administrative interface embeds a special configuration page. To access this page, simply click on the encircled '+' icon that appears alongside this parameter in the test configuration page. To know how to use this special page, refer to Configuring the Omnissa Horizon Connection Servers for Monitoring.

User Name, Password and Confirm Password

By default, this test uses Omnissa Restful APIs to collect the required metrics from the target Omnissa Horizon Cluster/Pod. For this, the eG agent should be configured with read-only user privileges that will allow the agent to communicate with the Horizon Connection Server in a particular domain and extract statistics. Therefore, specify the credentials of the user who is authorized to access the Horizon Connection Server against the User Name, Password and Confirm Password text boxes.

Domain Name

Specify the name of the domain to which the Horizon Connection Server belongs to.

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.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise 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

Number of sessions

Indicates the total number of active sessions for this user.

Number

Use the detailed diagnosis of this measure to find out more details of the connected sessions.

Has user session been reconnected?

Indicates whether/not this user session was reconnected.

 

The values that this measure can report and the numeric values they indicate have been listed in the table below:

Measure Value Numeric Value
Yes 1
No 0

Note:

By default, this measure can report the Measure Values mentioned above while indicating whether/not the user session was reconnected. However, the graph of this measure is indicated using the numeric equivalents.

Average logon duration

Indicates the total time taken for this user to log in.

Seconds

High values may indicate user experience issues due to delays in one or more logon stages.

User profile duration

Indicates the amount of time it took to load this user's profile successfully in the last measurement period.

Seconds

Long duration can point to large profiles or profile server issues.

Group Policy processing time

Indicates the time taken for applying group policies for this user in the last measurement period.

Seconds

 

Shell duration

Indicates the time interval between the beginning of desktop initialization and the time the desktop became available to this user including the Active Setup Phase.

Seconds

 

Interactive duration

Indicates the total time taken for this user to reach an interactive desktop after initiating the logon process during the last measurement period.

Seconds

 

Profile sync time

Indicates the time spent for reconciling user profile during this user's logon during the last measurement period.

Seconds

 

Classes hive load duration

Indicates the total time from when the logon of this user started to when the user registry hive is loaded during the last measurement period.

Seconds

 

Client connect wait duration

Indicates the time taken for a client to establish a connection to a virtual desktop or remote application through the Horizon pod/cluster for this user during the last measurement period.

Seconds

A high value for this measure is a cause of concern as it may be due to various factors such as high network latency, insufficient network bandwidth, firewall settings, improper load balancing etc. Reducing this duration is important for providing users with a responsive and efficient experience.

Protocol startup duration

Indicates the time taken for the remote desktop protocol (e.g., Blast or PCoIP) to initialize and establish a connection between the client device used by this user and the virtual desktop or remote application through the Horizon pod or cluster during the last measurement period.

Seconds

 

User script duration

Indicates the time taken by this user to execute logon scripts during the logon process, such as mapping network drives, setting environment variables, or applying custom configurations during the last measurement period.

Seconds

 

Agent prepare duration

Indicates the time taken to prepare the Horizon agent in the virtual desktop that was provisioned to this user during the last measurement period.

Seconds

The Horizon Agent is responsible for establishing communication between the virtual desktop and the Horizon infrastructure. Longer durations may indicate issues with agent initialization or system load.

Client logon delay

Indicates the time delay noticed when the client device of this user established a connection to a virtual desktop or remote application during the last measurement period.

Seconds

High values may indicate delays in initial communication or connection setup from the client side, often caused by network latency or session broker slowness.

User profile delay

Indicates the delay in time noticed while loading this user’s profile successfully during the last measurement period.

Seconds

To optimize user profile delays, administrators can redirect unnecessary folders, remove unnecessary files, and minimize the size of user profiles to improve logon times.

Agent prepare delay

Indicates the time delay noticed in the prepare stage of the Horizon agent in the virtual desktop that was provisioned to this user during the last measurement period.

Seconds

Similar to agent prepare duration, delays may suggest performance issues within the VM or delayed response from Horizon services.

Brokering duration

Indicates the time taken to complete the process of brokering a session to this user during the last measurement period.

Seconds

A high value indicates that brokering is taking a long time, which may be due to pool exhaustion, slow backend systems, or connection server load.

Broker launch duration

Indicates the time taken by the Horizon Connection Server (broker) to start or initialize brokering this user's session request during the last measurement period.

Seconds

To optimize the broker launch duration, administrators can consider the following steps:

  • Resource Allocation

  • Network Connectivity

  • Update Omnissa Tools

  • Improve Database Performance

  • Check for Service Dependencies

  • Analyze Logs etc

Machine prepare duration

Indicates the time taken to prepare the machine for use by this user during the last measurement period.

Seconds

Longer durations may indicate issues with instant clone preparation, system startup, or VM performance.

Machine selection duration

Indicates the time taken to select a machine for this user during the last measurement period.

Seconds

Delays here may be due to desktop pool capacity issues, selection policies, or resource availability.

Session script duration

Indicates the time taken for user logon scripts to execute during this user's session after the user had successfully logged in to a virtual desktop or remote application during the last measurement period.

Seconds

This script often contain tasks such as setting up user-specific configurations, mapping network drives, or launching specific applications. Optimizing session script duration is crucial for providing users with a responsive and efficient virtual desktop or remote application experience.

To optimize session script duration and enhance the user experience, administrators can do the following:

  • Script Optimization

  • Use Asynchronous Processing

  • Prioritize Essential Tasks

  • Optimize Application Launch

  • Minimize Network Dependencies

  • Use Horizon Smart Policies

  • Monitor Performance Metrics

Authentication duration

Indicates the time taken to authenticate remote sessions to this user during the last measurement period.

Seconds

 

Broker launch delay

Indicates the time delay experienced while launching the Omnissa Horizon Connection Server (broker) for brokering this user's session during the last measurement period.

Seconds

A high value for this measure indicates abnormal delays experienced by the users while launching the broker. To minimize such delays, administrators can check for adequate resource allocation, network connectivity and performance of the database.

Other processing duration

Indicates the time taken for other miscellaneous processing activities during the logon process that are not specifically categorized under known stages like user profile load, session scripts, or agent preparation, for this user during the last measurement period.

Seconds

A high value in this measure may indicate background tasks or custom processes (e.g., third-party logon scripts, antivirus scans, or GPO processing) are delaying the session start. Administrators can analyze session startup logs or use logon simulators to identify and optimize these hidden delays.