This article describes the changes included in adTempus version 4.9, released on September 12, 2022.

Obtaining the Update

See the download page to download the latest version of adTempus. The setup program will update your installation.

Upgrading from Prior 4.x Versions

If you are upgrading from adTempus 4.8 or earlier, you will need an updated license, and your adTempus database will be updated during the upgrade. See the Upgrading from Previous Versions help topic for more information.

.NET Framework Update

This upgrade will update the Microsoft .NET Framework on your computer to version 4.8 if you currently have an older version. This update is likely to require a computer restart to complete. To reduce the chances of a restart, update the .NET Framework yourself before running the adTempus installer:

  1. Download the .NET Framework 4.8 Runtime.
  2. Stop the adTempus service and close the Console and all other adTempus processes.
  3. Check the Processes list in the Windows Task Manager and terminate any "adtempus.jobhost.exe" and "adtempus.jobhost32.exe" processes.
  4. Close as many other running programs as possible.
  5. Run the installer downloaded in step 1.
  6. Restart the computer if required, then run adTempus setup.

If you do not perform these steps prior to installation, the setup process will do the upgrade and a restart will be more likely.

Changes in This Update

This release adds support for OAuth2 authentication when logging in to Microsoft Exchange Online mailboxes for email notification, email triggers, and email processing tasks. This functionality was developed for adTempus 5 but is being made available in adTempus 4.9 to meet the deadline for Microsoft's removal of support for basic authentication.

The release also contains additional minor changes. See the detailed release notes for more information.

Version 4.9.1 was released on September 27, 2022, to correct an issue found in the version 4.9 release related to OAuth2 authentication.

Version 4.9.2 was released on October 23, 2022, to correct an additional issue found in the version 4.9 release related to OAuth2 authentication.