adTempus 4.9.0.0 Release Notes

adTempus has been recompiled to target version 4.8 of the .NET Framework. This was required to support newer TLS security protocols. To use this update you must update the .NET Framework on your computer to version 4.8 if you currently have an older version.

Support for authenticating using OAuth2 has been added for users who use adTempus to connect to Microsoft mail platforms (Exchange Online/Office 365/Microsoft 365).

adTempus has been modified to ignore shell associations when running targets with the following extensions: .exe, .com, .bat, .cmd. This ensures that adTempus will always execute targets of this time even if the shell association has been altered. For example, if you change the shell settings for the .bat extension so that the default action is to edit the file (rather than execute it), in previous versions of adTempus this would result in adTempus launching the associated editor instead of executing the batch file. With this change, adTempus will ignore the shell association and execute the batch file.

The Email Trigger has been changed so that by default a trigger will ignore all messages that are already in the mailbox the first time the trigger connects to the mailbox. Before this change, each new trigger would process all existing messages in a mailbox, which could lead to unexpected triggers and also lengthy processing delays in cases where the mailbox had a large number of messages to be processed.

The original behavior (process all existing messages) can be restored by changing the "EmailMonitor:MarkAllSeenOnFirstRun" option to "false" in Advanced Server Options.

If a Job Condition is configured with the rule "Job has not run," the condition may be satisfied even though instances of the target job have run.

Console fails to connect to non-default instance of adTempus on another computer with error "This may occur if the adTempus server is in a different domain" even when server is in same domain. This problem is possibly related to recent Windows security update for CVE-2022-21920. The problem was resolved.

When a job running on an Agent executes a Job Control Action, in some cases the command is sent to the Master for execution. When this happens the Master fails to execute the command and logs alert 5406 for the job:

This problem was resolved. The update must be applied to the Master instance of adTempus but is not required for the Agent.

If the Windows performance counter database becomes corrupted, the adTempus service fails to start. This problem was resolved so that adTempus ignores the performance counter errors.

When you use a Database Task to run operations against a database, adTempus may fail to properly reuse connections to the database, causing the number of connections to grow in scenarios where many database tasks are being run frequently. This was corrected so that connections are properly reused. You will still see a separate database connection for each concurrently-executing database task, and those connections may remain for up to 10 minutes after the task completes. New tasks executed in that interval that use the same database and user identity will now reuse the existing connection rather than creating a new connection.

adTempus may log warning ADT005458 ("Job is configured to run with Administrator privileges but user .\administrator is not an Administrator. The job will run with normal privileges.") even though the user is an Administrator. See article K00000611 for more information.

When a Date Rule is configured to run on the day "Nearest" to "a specified day" (defined by another Date Rule), the Console does not save the setting correctly, so the rule does not match any days and does not trigger correctly.