Script “Analyze Logon Duration” runs fine but gives different when I run the script manually

A user encountered a difference in result between running the ‘Analyze Logon Duration’ Script manually and as an automated action in ControlUp. Possible causes discussed include the monitor triggering it vs. the console, interpreation of the decimal seperator, and events triggered by Ivanti. Support suggested the customer open a ticket to investigate further and to mention this Slack thread. The ControlUp Agent version on the affected desktop was 8.6.5.427.

Read the entire ‘Investigating Differences in ControlUp Script Action Results’ thread below:

Hello, I’m trying to configure the Script “Analyze Logon Duration” as an automated action. The script runs fine however the result is different when I run the script manually.

Any idea what could cause this?

Hmmz @member this shouldn’t happen should it?

Cc @member as well

From 13 to 1300, that feels like a decimal seperator going haywire somewhere

Yes I was thinking the same. But It’s stange that the value for “Logon End” is different…

@member could it be relevant if the monitor is running it vs the console?

@member ALD always runs on the endpoint, the monitor just triggers it

I figured that, just wondering if how it gets trigger would make a difference… Keep me posted 🙂 I would be curious on why this is happening

@member you should be able to add an argument named CreateOfflineAnalysisPackage with a path to save an offline package can you do that for both methods so we can investigate that package?

The 1300 is I believe calculated off the start and end time, so the 1300 seconds is correct. The issue is the End time possibly be read incorrectly from the logs

1300 be an awfully slow logon though… Maybe a difference in interpretation of the decimal separator? Depending on the locale a comma or dot is used as a decimal separator.

@member Ok not sure how to do this. I tried to add the parameter to the Script Action but there’s no offline package

I believe we have seen this before… I believe the issue is the ControlUp agent monitors for a event that is only available programmatically (Start Menu Ready). This is triggered when the start menu is rendered and available to be clicked on. This event occurs after logon but it’s possible to generate this event when other actions occur (like screen lock/unlock I think).

This should have been fixed in ControlUp 8.6 to only take the first event. @member Can you confirm what version of ControlUp you are using?

I should also note that I’ve seen this behaviour (ever increasing “Desktop Load Time Column”) when Ivanti triggers the lock/unlock events. I haven’t really seen any other technology which triggers the same thing, but if Ivanti figured it out someone else may have discovered the same method

@member We’re using 8.6.5.427

Can you confirm the value in ControlUp for the “Desktop Load Time” column does NOT match what ALD says?

ALD gets it’s value from ControlUp, so when it’s at ~1300 seconds, that value should match the console

Yes I can confirm that the “Desktop load time” does not match what ALD says when it’s executed from an automated action. But it matches, when I run ALD from Console.

I’ve noticed that Logon End time is also in the future…

The customer got Ivanti btw. Do you think that this might cause the issue? But in that case it should also apply if we run ALD from Console?

Hi @member, indeed Ivanti may be related here, as Ivanti may change the default Shell behavior in the Windows session. I suggest you open a ticket via support@controlup,com on this issue, so we can properly investigate

@member – maybe this is the same “Ivanti lock / unlock” issue that effects our code flow

@member – last point for now, you said the ControlUp version is 8.6.5.427, I would just verify the CU Agent version from the affected desktop is also 8.6.5.x (as we do support agent backward compatibility)

Yes, the agent is also 8.6.5.427.

Thx, I’ll proceed and open a ticket 🙂

thx a lot. I suggest you mention this Slack thread in the Support ticket, so Support can see the notes from @member / the Ivanti notes

Great, thank you!

@member I am opening the ticket for you. Please expect a response soon 🙂

@member Thanks a lot 🙂

Continue reading and comment on the thread ‘Script “Analyze Logon Duration” runs fine but gives different when I run the script manually’.  Not a member? Join Here!