Logon Performance Test

The process of a user logging into a desktop/server OS machine managed by a XenDesktop Broker is complex. First, the user’s login credentials are authenticated. Then, the corresponding user profile is identified and loaded. Next, group policies are applied and logon scripts are processed to setup the user environment. Then, a HDX connection is established with the VM, subsequent to which, the VM starts and hands off keyboard and mouse control to the user. In the meantime, additional processing may take place for a user – say, applying system profiles, creating new printers for the user, and so on. A slowdown in any of these steps can significantly delay the logon process for a user and may adversely impact the logins for other users who may be trying to access desktops/applications at the same time. Hence, if a user complains that he/she is unable to access an application/desktop, administrators must be able to rapidly isolate exactly where the logon process is stalling and for which user.

The Logon Performance test tracks user connections to each delivery group, measures the average time taken for users to access desktops/applications delivered by each group, isolates the group to which user logins are slow, and accurately pinpoints where the login process is bottlenecked. Detailed diagnostics provided by this test point to the precise user who is experiencing the slowness.

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
Test period - How often should the test be executed Host - The host for which the test is to be configured. port – The port number at which the specified HOST listens to. By default, this is 80. 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. 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. 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. CONFIRM PASSWORD – Confirm the PASSWORD by retyping it here. fully qualified DOMAIN name – Here, specify the fully-qualified name of the domain to which the specified controller belongs. ssl – Indicate whether/not the controller used for metrics collection is SSL-enabled. By default, this flag is set to Yes. 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. 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
Average logon duration:	Indicates the average time taken for users to login to desktops/applications offered by this delivery group.	Secs	If this measure reports a high value consistently, it could indicate a slowdown in the logon process. You can use the detailed diagnosis of this measure to understand the logon experience of each user to the delivery group, identify that user who took the maximum time to login, and accurately isolate where he/she experienced slowness.
Logons:	Indicates the number of users who recently logged into desktops/applications delivered by this delivery group.	Number	This is a good indicator of the current user load on a delivery group.
Brokering duration:	Indicates time taken to complete the process of brokering sessions to this delivery group.	Secs	A high value indicates that brokering is taking a long time. If the Average logon duration is very high, you may want to compare the value of this measure with that of the Time taken for starting VM, HDX connection duration, Authentication time, GPOs duration, Logon scripts duration, Profile load time, and Interactive session duration measures to know where exactly the user logon process slowed down – is it during authentication? Is it during brokering? Is it when establishing the HDX connection? Is it when applying GPOs? Is it during logon scripts execution? Is it while loading user profiles? Is it when starting the VM? Or is it when handing over control to the user?
Time taken for starting VM:	Indicates the time taken for starting the machines in this delivery group.	Secs	A high value indicates that machines are taking too long to startup. If the Average logon duration is very high, you may want to compare the value of this measure with that of the Brokering duration, HDX connection duration, Authentication time, GPOs duration, Logon scripts duration, Profile load time, and Interactive session duration measures to know where exactly the user logon process slowed down – is it during authentication? Is it during brokering? Is it when establishing the HDX connection? Is it when applying GPOs? Is it during logon scripts execution? Is it while loading user profiles? Is it when starting the VM? Or is it when handing over control to the user?
HDX connection duration:	Indicates the time taken to complete the steps required for setting up the HDX connection from the client to the machines in this delivery group.	Secs	A high value indicates that HDX connections are taking time to be established. If the Average logon duration is very high, you may want to compare the value of this measure with that of the Brokering duration, Time taken for starting VM, Authentication time, GPOs duration, Logon scripts duration, Profile load time, and Interactive session duration measures to know where exactly the user logon process slowed down – is it during authentication? Is it during brokering? Is it when establishing the HDX connection? Is it when applying GPOs? Is it during logon scripts execution? Is it while loading user profiles? Is it when starting the VM? Or is it when handing over control to the user?
Authentication time:	Indicates the time time taken to authenticate remoe sessions to the machines in this delivery group.	Secs	A high value indicates authentication delays. If the Average logon duration is very high, you may want to compare the value of this measure with that of the Brokering duration, Time taken for starting VM, HDX connection duration, GPOs duration, Logon scripts duration, Profile load time, and Interactive session duration measures to know where exactly the user logon process slowed down – is it during authentication? Is it during brokering? Is it when establishing the HDX connection? Is it when applying GPOs? Is it during logon scripts execution? Is it while loading user profiles? Is it when starting the VM? Or is it when handing over control to the user?
GPOs duration:	Indicates the time taken to apply group policy settings on the machines in this delivery group.	Secs	A high value indicates that GPO application is taking time. If the Average logon duration is very high, you may want to compare the value of this measure with that of the Brokering duration, Time taken for starting VM, HDX connection duration, Authentication time, Logon scripts duration, Profile load time, and Interactive session duration measures to know where exactly the user logon process slowed down – is it during authentication? Is it during brokering? Is it when establishing the HDX connection? Is it when applying GPOs? Is it during logon scripts execution? Is it while loading user profiles? Is it when starting the VM? Or is it when handing over control to the user?
Logon scripts duration:	Indicates the time taken for logon scripts to be executed on the machines in this delivery group.	Secs	A high value indicates that logon script execution is taking time. If the Average logon duration is very high, you may want to compare the value of this measure with that of the Brokering duration, Time taken for starting VM, HDX connection duration, Authentication time, GPOs duration, Profile load time, and Interactive session duration measures to know where exactly the user logon process slowed down – is it during authentication? Is it during brokering? Is it when establishing the HDX connection? Is it when applying GPOs? Is it during logon scripts execution? Is it while loading user profiles? Is it when starting the VM? Or is it when handing over control to the user?
Profile load time:	Indicates the time taken by the logon process to load the profile of the users to this delivery group.	Secs	A high value indicates that profiles are taking too long to load. If the Average logon duration is very high, you may want to compare the value of this measure with that of the Brokering duration, Time taken for starting VM, HDX connection duration, Authentication time, GPOs duration, Logon scripts duration, and Interactive session duration measures to know where exactly the user logon process slowed down – is it during authentication? Is it during brokering? Is it when establishing the HDX connection? Is it when applying GPOs? Is it during logon scripts execution? Is it while loading user profiles? Is it when starting the VM? Or is it when handing over control to the user?
Interactive session duration:	Indicates the time taken by the logon process to handoff keyboard and mouse control to the users to this delivery group.	Secs	A high value indicates delays in handing off keyboard and mouse control to users. If the Average logon duration is very high, you may want to compare the value of this measure with that of the Brokering duration, Time taken for starting VM, HDX connection duration, Authentication time, GPOs duration, Logon scripts duration, and Profile load time measures to know where exactly the user logon process slowed down – is it during authentication? Is it during brokering? Is it when establishing the HDX connection? Is it when applying GPOs? Is it during logon scripts execution? Is it while loading user profiles? Is it when starting the VM? Or is it when handing over control to the user?