Login Performance

As of Login PI version 3.4.x, login performance is measured within each session. This chapter will explain how the results shown work together. 

The Dashboard

In the dashboard overview of Login PI 3 a new list item is added for each different environment you have configured. 

This bar shows you that 3 out of 22 measurements have crossed the configured logon threshold.

Once you go one step deeper in to the environment you can see a new measurement block that has been added that shows the same information as mentioned before. But this is clickable. 

Once clicked you can see a more detailed information list of the Login performance and measurements. 


Here there are 4 measurements that we show you. As you can see in the example, the total login time is not always the collection of the other three measurements as they sometimes run longer than when the explorer.exe is loaded and it does not account time between specific actions like Profile load and GPO processing. 

  • Total Login Time
    • The total login time is the time it takes from the session start at the launcher and the start time of explorer.exe.
  • Display Protocol Connection
    • This is the time it takes from the moment the launcher starts the session up to the start of profile loading, this metric is found in the windows event logs. 
  • Profile Load
    • We read this using the User Profile events generated by the profile service from windows event viewer.
  • GPO processing
    • We only measure synchronous group policies. As asynchronous group policies have less impact on user experience and are therefor not measured. 

The Logon performance popup explanation


When hovering over a measuring point in the Logon Performance details a popup appears with more detailed information:

  • Timestamp
    • Moment of logging
  • Duration
    • Logon time at moment of logging
  • Threshold
    • Defined threshold 
  • Launcher
    • Which launcher was used during measurement
  • Remoting Protocol
    • Which remoting protocol was used during the measurement
  • Target host
    • The VM hostname that generated the measurement
  • Target OS
    • Os version of the target VM
  • User account
    • The account used for the measurement

GPO processing

As addition to the explanation above there is more to GPO processing, for those who want to know more about it.

For group policy we pull the start and end times from the registry from the following key:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\State\S-1-5-21-1642230215-40016302-1263235327-14012\Extension-List\{00000000-0000-0000-0000-000000000000}

In this case this SID value (S-1-5-21-1642230215-40016302-1263235327-14012) is the users SID and will vary per session. In this key there are 4 values which are used:

StartTimeLo, StartTimeHi, StartTimeLo, StartTimeHi

Combining these values gives us the start and end times for group policies.

If in rare cases the GPO measurements start timestamp is before the session start time, we discard the data. 


In the Reporting > Chart overview we have added the Login Performance measurements

Selecting these will show a chart with these measurements. The charting works the same way as any of the others.