What has the potential to impact logons?

Some of the reasons a logon can slow include but are not limited to:

1. Large profile size, when for example using Roaming Profiles or Citrix Profile Management.
2. Logon scripts.
3. The amount of configured Group Policy settings.
4. Lack of hypervisor resource/resource constraint.
5. Lack of VDA resource, lack of available VDAs, resource constraint.
6. Incorrect Active Directory configuration.
7. Overloaded Domain Controllers, StoreFront servers, or Delivery Controllers.
8. Slow network connections between client endpoint and StoreFront, or client endpoint and VDA.

How will you know?

One of the many challenges a Citrix administrator faces is knowing what is causing a slowdown in logons, or why a logon was slow, even if it was just a handful of logons. This is where monitoring solutions add value to your existing environment and take much of the guesswork out of the troubleshooting and identification process.

It is known that various products exist that can record logon time duration. Take Citrix Director for example. The problem you may face with many of these products is simply the lack of detail that is captured and presented to you when it comes to logons, which results in potentially extra hours getting to the root cause. For example, you might look at a slow logon report and find that GPO processing was slow, which is great, but what exact GPO is causing the slowness in this instance? It could take a serious amount of time evaluating GPOs, testing them in a non-production environment and applying them one by one until you find the culprit.

As another example, if the monitoring product doesn’t investigate application enumeration times, how long will it take before you investigate this as being the cause of your user’s logon slowness? I can tell you that this is something you will likely overlook nine times out of ten, but it is a point in the logon process that absolutely can have an impact.

Therefore, getting to the root cause before more business productivity is lost is the end-goal here. Not only is this great for the end-users, but it is also advantageous to the Citrix administrator, who can get on with other parts of his/her job.

Goliath Technologies set themselves apart with a product that provides extensive amounts of information around logon durations, providing just the information that is needed to get to the problem point faster than ever. Goliath Performance Monitor does this by providing metrics for over 33 steps in the logon process. Three examples of logon times, with two being slow-logon scenarios caused by different issues are shown below:

The normal logon:

• Time to logon: 38 seconds.

A 38 second logon is acceptable by all means. This is a fresh Windows 10 VDA install I am connected to, so it would definitely be possible to reduce the logon times after some optimisations.

Via the XenApp & XenDesktop page, Goliath Performance Monitor reports a logon duration of 38.1 seconds.

Logon duration metrics of interest:

• PLSD: In this logon example, I used Citrix Profile Management, and the profile load time reports in at 10.11 seconds.
• GPO: Nothing wrong with GPO processing times, coming in at 0.36 seconds.
• Brokering: This element in the logon process is also great, at 0.14 seconds taken for the Delivery Controller to broker my connection on to an available VDA.

The slow logon:

• Time to logon: 74 seconds.
• Reason: Desktop load.

74.5 seconds is cause for concern, and Goliath Performance Monitor rightly highlights the time in red for our attention.

Via the XenApp & XenDesktop page, Goliath Performance Monitor reports a logon duration of 74.5seconds.

Drilling into the logon time:

Logon duration metrics of interest:

• Client Valid: The time spent validating the client side session. Normally this metric references any delays that happen on the client-side. For example, launching Citrix Receiver, DNS resolution, establishing connections etc.
• Server Valid: The time spent validating the server side session. Normally this metric references any delays that happen on the server-side. For example, making sure the VDA is ready to host a session.

The extra slow logon:

• Time to logon: 158 seconds.
• Reason: Large profile.

158 seconds, let’s hope that never happens in our production environment!

Via the XenApp & XenDesktop page, Goliath Performance Monitor reports a logon duration of 158.1 seconds.

Logon duration metrics of interest:

• PLSD: This metric is profile load time. At 125 seconds, it is clear that either the profile configuration was wrong, or the profile itself was overly large. In my example, the latter applied.

Summary

With so much data passed to you, you can rule out many steps in the logon process quickly, allowing you to draw a conclusion and reach the root cause of logon slowness much faster, keeping your users happy.

As shown in the above screenshots, you can see the many different steps that are recorded when a user logs on to their desktop or application. Not only does Goliath Performance Monitor record the GPO processing time, profile load time, script processing time and so on, but it goes well beyond this, capturing application enumeration time, brokering time, HDX session establishment time, how long it takes to obtain applicable Group Policies, how long authentication takes and much more.

If you are intrigued by all the different metrics that Goliath Performance Monitor reports on but I have not mentioned, I recommend the comprehensive Complete Guide to Understanding The Citrix Logon Process guide. A small example of the metrics and their meanings are listed below:

• DMSD – The time is takes to map client drives, devices and ports from the client device.
• SSSD – The complete high-level time it takes to perform the entire start-up operation.
• NRWD – The time it takes the Delivery Controller’s XML service to resolve the name of a published application or desktop to a VDA address.
• SCCD – This metric starts as close as possible to the time of the request (mouse-click) and ends when the ICA connection between client and VDA has been established.
• SCD – The time it takes from wfica32.exe launching on your client machine to a connection being established with a VDA.

With Goliath Performance Monitor, you can quickly see the value that such in-depth logon reporting provides. Also note that historical data reporting is possible with the product and you don’t lose any data by way of database trimming, or purging of old data. Without a doubt, there is no comparison between the level of detail found in Goliath Performance Monitor and other tools like Director, etc.

If you’d like to see how Goliath Performance Monitor can proactively solve logon duration and other ‘Citrix is slow’ issues in your environment, you can download a fully functional, fully-supported 30 day free trial here.