0

User logon Duration Explanation

We have uberAgent 3.5 and run a custom application that has ongoing code changes that are rolled out. We saw a significant spike in "total duration" start the week of a change. This change also included enabling Special Folder Redirection in StoreFront. I see the processes starting when I select a user in the data table but I do not see how much time is being consumed just the CPU milliseconds. What I am attempting to do is determine what is taking longer with "total duration". Our custom app has processes that run after the user sees the splash screen that a user can see while they're in the app. The question asked by our team is what is included in "user logon duration" and what is not.  

 

Thank you

3 comments

  • 0
    Avatar
    Dominik Britz

    Hi Bill,

    To see the runtime of a process during logon do the following:

    • Go to the User Logon Duration dashboard
    • Click on a user in the data table
    • Point the mouse on a process in the column Lifetime (screenshot below)

     

    A detailed list of metrics which are collected is available here: https://uberagent.com/docs/uberagent/latest/metrics/user-logon/

  • 0
    Avatar
    Bill Barnes

    For some of the users in the table there is no data in "logon process performance" just no results found. Is it something I am doing incorrectly? Thanks for the tip with hovering in Lifetime. I am starting to think we may have something going with Splunk because I am also seeing users in the "last hour" but not in the last month that should include users from the last hours if I am understanding this correctly.

    .

  • 0
    Avatar
    Dominik Britz

    Hi Bill,

    Since Windows 8.1, respectively Windows Server 2012R2, the Group Policy client waits five minutes before it runs logon scripts https://support.microsoft.com/en-us/help/2895815/logon-scripts-do-not-run-for-five-minutes-after-a-user-logs-on-to-a-wi 

    To check if the five-minute delay applies to your environment please search for GetGpLogonScriptDelayMs in the uberAgent log file:

    GetGpLogonScriptDelayMs,Determined GP logon script delay for session 2: <5> minutes

    As user logon scripts are part of the logon process performance data, uberAgent sends this information to the backend after the logon scripts have finished.

    That means, that the session ended before the logon scripts even started and that is why you don't see any logon process performance data on the dashboard.

    You have two options to solve the problem:

    1. Wait longer in a session before logging off
    2. Set the following group policy to Disabled, to disable the logon script delay -> Computer Configuration\Administrative Templates\System\Group Policy: Configure Logon Script Delay

    As for the missing user logons. You are correct, every logon that you saw in the last hour's timeframe should also be available in the last month's timeframe. You are possibly affected by this bug. Please disable the datamodel acceleration for uberAgent and try again.

Please sign in to leave a comment.