Could Language Regional Settings Cause ALD Script Output Errors in ControlUp?

A user had a problem with an ALD script that showed an output with a duration of 83000 seconds and Logon end in the future. It was suggested that the problem could come from different language regional settings in the console and the target machine, with the decimal separator (e.g. 36,00) being sent to the machine as text and being misinterpreted. The Desktop Load Time could also be an issue and it was suggested to look for an anomalous value in the Windows Shell line.

Read the entire ‘Could Language Regional Settings Cause ALD Script Output Errors?’ thread below:

Hi all, i have a problem with the ALD script. Output gives us a duration of 83000 sec and the Logon end is in the future. See screenshot. Any ideas why we get this output?

I suspect that the console you ran the script from and the target machine have different ~language~ regional settings?

More specifically, ALD gets some data from the console when you run the script. What likely happened is that your console runs in an EU regional setting that uses comma as the decimal separator (for example 36,00)

This value is then sent to the agent on the machine that runs ALD as text. Powershell on the remote machine interprets the value back to a number. Assuming the remote machine runs US regional settings, it interprets 36,00 as 3600

I’ve been working on updating ALD for a very similar problem – fixing an issue with the Desktop Load Time. Can’t tell if this is the same issue, without a complete screen capture. Look for an anomalous value in the Windows Shell line.

ok, thanks for your hint, i will see if that helps 🙂

Continue reading and comment on the thread ‘Could Language Regional Settings Cause ALD Script Output Errors in ControlUp?’.  Not a member? Join Here!