General Page

Provide a descriptive name for the job (255 characters maximum). The name is used throughout adTempus to identify the job, and must be unique within the group that the job belongs to.

If you try to use a name that is already in use on another job, you will receive an error message when you try to save the job. Note that the other job with the same name may not be visible to you (based on security settings).

Check this box to enable the job. If the box is unchecked, the job is held and will not be triggered.

The Job ID is a 38-character system-generated unique identifier for the job. This ID remains constant even if the name of the job changes. The Job ID is shown primarily for use in diagnostic situations but can be used instead of the name in command-line utilities such as adtExec.

Specify the priority of this job within the queue. In a queue that limits the number of jobs that can run simultaneously, jobs with higher priorities are executed before jobs with lower priorities. New jobs have a default priority of 100.

Specify the Windows user account that the job should be run under. See Entering User Credentials for more information on how to enter the credentials.

All tasks performed by this job will be run under the user account you specify. For example, when the job executes a program, the program will operate under the same security context (and restrictions) as if the specified user had run the job herself.

Note: This option is available only if the adTempus server is running Windows Vista, Windows Server 2008, or later.

If the specified User Account is an administrative account, check the Run with highest privileges option to have administrative privileges enabled when the program runs. This is equivalent to using the "Run as Admin" command in Windows. If this option is not checked, administrative privileges will not be enabled, and the program may not behave as you expect.

If the User Account is not an administrative account, checking this option has no effect on program execution.

Select the kinds of Windows logon session that this job is allowed to use. The session that a job runs in determines whether it will be visible to interactive users at the computer, and to which users.

The User Interaction selection list specifies which session types the job is allowed to use, and in what order of preference.

The following options are available in the User Interaction selection list:

Setting	Meaning
Console, User's Session, Hidden	If there is a console session for the computer, the job will run in that session. Otherwise, if there is an interactive session for the job's user, the job will run in that session. Otherwise, the job will run in a hidden session.
Console, User's Session	If there is a console session for the computer, the job will run in that session. Otherwise, if there is an interactive session for the job's user, the job will run in that session. Otherwise, the job will fail.
Console, Hidden	If there is a console session for the computer, the job will run in that session. Otherwise, the job will run in a hidden session.
Console	If there is a console session for the computer, the job will run in that session. Otherwise, the job will fail.
User's Session, Console, Hidden	If there is an interactive session for the job's user, the job will run in that session. Otherwise, if there is a console session for the computer, the job will run in that session. Otherwise, the job will run in a hidden session.
User's Session, Console	If there is an interactive session for the job's user, the job will run in that session. Otherwise, if there is a console session for the computer, the job will run in that session. Otherwise, the job will fail.
User's Session, Hidden	If there is an interactive session for the job's user, the job will run in that session. Otherwise, the job will run in a hidden session.
User's Session	If there is an interactive session for the job's user, the job will run in that session. Otherwise, the job will fail.
Hidden	The job will run in a hidden session.

A program that is properly designed for "batch" execution should not rely on direct interaction with users, and therefore should not need to display a user interface. For such programs, use the "Hidden" session whenever possible. This provides more security, and eliminates the annoyance of program windows popping up while a user is logged in to the computer.

If you need to be able to see or interact with programs run in the job, choose one of the interactive options (Console or User's Session) depending on your needs.

For an interactive program, also consider what adTempus should do if no interactive session is available (i.e., no user logged in).

If it is imperative that a user be able to see/interact with the programs, choose a User Interaction option that does not include the "Hidden" option. This will cause the job to fail if no interactive session is available.
If it is more important that the job be run at its scheduled time, be sure to include a User Interaction option that does include the "Hidden" option. Since a hidden session is always available, this will ensure that your job is run even if no interactive session is available.

Enter any extended descriptive information or notes for this job. There is no limit on the length of the text.

Specify how long adTempus should retain the history The history of a job includes the details of each execution, including messages and captured files. for this job.

If you select the Retain Indefinitely option the history will be kept until you change the retention option to a setting that allows adTempus to purge the history.

Job General Page