Understanding Logon Duration Metrics in ControlUp: Differences Between Console and Analyze Logon Duration Script

A discrepancy was observed between the “Logon Duration” metric displayed in the ControlUp console and the results produced by the “Analyze Logon Duration” (ALD) script, with the two values differing significantly. This raised questions about where to begin troubleshooting and how these two measurements relate.

It was clarified that the ALD script and the “Logon Duration” metric in ControlUp use different measurement points, meaning their values are not directly comparable. The ALD script requires specific prerequisite audit policies to be enabled on target systems to function correctly, as detailed in ControlUp’s support documentation at https://support.controlup.com/docs/enable-auditing-for-analyze-logon-duration-script. If these audit policies are disabled or misconfigured, the ALD script’s accuracy will be compromised.

In this particular case, the use of ControlUp’s Disk Monitor revealed excessive disk writes related to enabled audit policies, which led to those audit policies being disabled to reduce disk IO. Disabling the audit policies impacted the ALD script’s ability to provide accurate logon duration measurements. This highlights the dependency of the ALD script on proper audit policy configuration for precise tracking.

Regarding which method to use, it is recommended to use the Digital Employee Experience (DEX) console metric for initial logon duration screening. For more detailed and in-depth analysis, the ALD script should be employed, provided the prerequisite audit configurations are correctly set up. This distinction ensures users leverage each tool according to its strengths: quick overview versus detailed investigation.

Read the entire ‘Understanding Logon Duration Metrics in ControlUp: Differences Between Console and Analyze Logon Duration Script’ thread below:

Recently, we noticed that the “Logon Duration” value is no longer matching what the “Analyze Logon Duration” script says. They are quite different. I’m not even sure where to start in troubleshooting this… any ideas?

Do you have the pre reqs in place?

ALD uses different measurement points than the metric in the console/dex gives so you cnanot compare them 1:1

Ah, that’s the issue.
We had recently used ControlUP’s Disk Monitor to look for excessive Disk IO, and saw excessive writes associated with the Audit policies. These were disabled, and thus the ALD was not accurate. Which is the preferred method of determining Logon Duration in ControlUP? ALD or DEX?

for initial screening use dex for more in depth analysis use ald script

Continue reading and comment on the thread ‘Understanding Logon Duration Metrics in ControlUp: Differences Between Console and Analyze Logon Duration Script’.  Not a member? Join Here!