Understanding Logon Duration in ControlUp: Exploring Factors and Using the Logon Script for Analysis

A user asked for clarification on the difference between logon duration values shown in the ControlUp console and Citrix Analytics Reports. It was suggested to use the logon duration script for more detailed breakdowns of the values and to isolate users and use Promon for specific time stamps. Links to helpful resources were also provided.

Read the entire ‘Understanding Logon Duration in ControlUp: Exploring Factors and Using the Logon Script for Analysis’ thread below:

Hi! I have a query regarding logon duration values which are being shown up in console ..vs logon duration values which are being shown up in Citrix Analytics Reports. We have a customer, where the logon duration values are showing up relatively high in CU Console, however, when we compare the same with ctx analytics report, its different. Looking to understand, what are the actual factors that are being considered in monitoring for Logon Duration, Desktop Load Time, Logon duration ( others) ….

the think the difference is citrix starts the time count from when u click on the web interface icon and controlup starts its could from when the the username and password is entered into the OS logon screnn

but there is prob other differences as well but the markers will be taken at different times. when u looking at controluo are u using the console on the logon analytics script?

yeah, but the concern is that the difference is huge. And yes i see that values in Logon duration column not the CVAD one…, and i did ran the logon duration script analysis on the session which shows as highest… of all process, it shows windows shell to be consuming more time (s)..

did u run the logon duration script it will give u alot more info on the breakdown

https://www.controlup.com/resources/blog/analyzing-logon-duration-just-got-better/

https://www.controlup.com/script-library-posts/analyze-logon-duration/

@member – yep, i did. the most common process which is the top contributor for higher logon duration is windows shell process.

one thing to remember with digging into the logon duration, doesn’t matter what tool you use it only helps you break it down. Most cases you will need to isolate users on a system on their own and use Promon to see exactly what is happening. With the logon script each breakdown gives you a time stamp. so when you go to Promon you can go to that time stamp and see what is happening. Logon duration issues are like looking for a needle in a hay stack combining Procom with the logon script makes that haystack a lot smaller and easier to find the needle @member

Continue reading and comment on the thread ‘Understanding Logon Duration in ControlUp: Exploring Factors and Using the Logon Script for Analysis’.  Not a member? Join Here!