Upgrading from Version 3

This topic describes the process for upgrading an adTempus installation from an earlier version.

If you are upgrading from a previous adTempus version, you can (and should) install version 4 without removing the previous version. The setup process will upgrade your existing installation.

Please review the information below for changes that may cause problems for upgrading users. See the What's New topic for an overview of new features.

If you are coming from version 2, please also see the Upgrading from adTempus 2.x topic.

Side-by-Side Installation

Beginning with version 4, adTempus supports side-by-side installations of the server software, meaning that you can install adTempus 4 on a computer alongside a version 3 installation, and run both versions of the software. See Side-by-Side Installation for more information.

Database Changes

This upgrade makes major changes to the adTempus database. Once it has been upgraded, the database cannot be used with previous versions of adTempus. Rolling back an upgrade therefore requires rolling back the database to a backup (the database configuration tool will create a backup before it makes changes).

If you are using the MSDE or SQL Server 2005 Express database engine provided with earlier versions, setup will upgrade the database engine to SQL Server 2017 Express. This upgrade is required if you are still using MSDE, and strongly recommended for SQL Server 2005 Express.

If you have reports or programs that read the adTempus database directly, they will require modification to work with the new schema. Relations between tables are now modeled in the database, which will make it easier to understand the table structure.

adTempus Service Account Requirements

The adTempus service must run under the Local System account for full functionality. Running the service under a user account is no longer fully supported. This is necessary because there are some actions that adTempus needs to perform that Windows does not allow if the service is running under a user account. If you were previously running adTempus under a user account to allow access to a remote SQL Server database, you should reconfigure to either use SQL Server security or grant the adTempus machine account access on the remote database server. If you must use a user account for the adTempus service, review requirements and limitations here.

Upgrading Multiple Servers

adTempus instances from two different versions cannot communicate with each other. If you are using Distributed Scheduling, you must upgrade the Master and all Agents at the same time.

Linked Servers

If you have servers that are linked together through Job Control Actions or Job Conditions, you must upgrade those servers at the same time for those features to continue working. You will also need to establish trust relationships between the servers using the Linked Servers window. adTempus will log an Alert with ID 5270 at service startup if it finds remote targets for which no Linked Server definition has been created. You will need to configure the trust relationship before the conditions or responses can work.

Security Changes

The adTempus security model has changed, and will require review and adjustment of your security configuration after the upgrade. See the Security Changes topic for more information.

Additional Breaking Changes

adTempus Console does not work across major versions

The adTempus Console for version 4 cannot connect to version 3 servers or vice versa. We hope to support backward-compatibility in future major releases.

If you will need to continue administering servers running adTempus 3.x, you can still install the 4.x Console on your computer and use both versions of the Console concurrently.

Note that you can install the adTempus 4.0 Console on a computer with version 3.x or 2.x installed, but you cannot install the version 3.x or 2.x Console on a computer after you have installed version 4.0. Therefore if you need to be able to run both versions of the Console on a computer, be sure to install the 3.x or 2.x version first and then the 4.0 version.

The adTempus export/import format has changed

adTempus 4 uses a slightly different format for the export/import file, but is able to read and write the version 3 file format.

WMI trigger selection script changes

If you are using scripts to filter events for WMI Triggers, changes are required. Filter scripts must now be .NET scripts (VB.NET or C#); WSH scripts (VBScript) are not supported.

Job Log message codes for Scripts

If you have scripts that log messages to the Job Log using the adTempus.LogMessage method, the handling of the messageID has changed: the value that you pass to the LogMessage method will be increased by 100,000 before being logged to the database, to avoid overlap with system-defined message codes. That is, if you call LogMessage with a message ID of 42, your message will appear in the Job Log with a message ID of 100042.

All messages present in the database at the time of the upgrade will be converted to the new values.

If you are querying the adTempus database for specific message IDs from your scripts, you will need to modify your queries accordingly.

No more override of held jobs

The way that jobs/groups/queues are held/released has been changed. Along with this the option to run a job even if it is held (previously available in the execution options for a Job Control Action and when executing a job on demand) has been removed: it is not possible to override the job's Held status. If you have Job Control Actions that rely on this option you will need to change your configuration.

User interaction setting changes

The user interaction settings for jobs have been simplified, and the option to run jobs in the "console" session has been removed because it is less relevant/useful since session isolation was introduced in Windows Server 2008.

The adTempus API has changed

The adTempus API has changed for version 4. Please see the API documentation for more information.

New Web client

Due to the API changes discussed above, the Web-based monitoring client available with version 3 will not work with adTempus 4. A new Web Console is available for version 4.