Windows Task Scheduler Import

Windows scheduled tasks can be imported into Dollar Universe (on the local Node). Not only Dollar Universe supplements the scheduling functions offered by Windows Task Scheduler (WTS), but production can be monitored across many machines via Univiewer. Dollar Universe can import jobs from Windows Task Scheduler v1.0 and v2.0.

This import cannot be used to import jobs created with the "at" command (or with the WinAT console).

Task Selection

The list displayed shows the Windows Scheduled tasks sorted by submission account.

The Trigger column gives a summary of the triggers found on the job. Some triggers cannot be converted in Dollar Universe; for example: on startup, User logging in… The value of the trigger column displays nothing when the job status is misconfigured.

Status codes:

In the compatibility column, move the mouse over the warnings to display their contents.

In the Job column, check one or more boxes to select jobs to be imported (the Select All or Unselect All buttons can be used).

Click Next at the bottom of the window. Double-click on the title bar if you do not see the buttons.

Task List Preview

This window lists all the scheduled tasks selected from the previous window.

At this point, the jobs have not yet been created in Dollar Universe nor disabled in the Windows Scheduled tasks.

WTS Tasks Preview – Toolbar:

From a Uproc (if an uproc is selected): Refer to section: "Uproc Details".

From a Task: (if a task is selected): Refer to section "Task Details".

For all WTS jobs with the WTS property "Run only when user is logged on", the UniJob associated property "Interactive Job" is activated.

For all WTS jobs with the property WTS "Run whether user is logged on or not," the property of the associated Uproc "Interactive Job" is activated.

The following name is automatically assigned to the target: <SUBMISSION ACCOUNT>_<DUAS NODE NAME>. The name of the Submission account is the same as the user in WTS.

Example: "AUTOMIC\user1" remains "AUTOMIC\user1"

A user service is automatically created and started for this submission account. The user and its password are taken from the conversion wizard and saved in the Windows service.

!XX!: means that XX is a specific Dollar Universe variable

CONVINDEX: is an index, automatically incremented during the job conversion

CMD: is the job command line

To modify the Task name:

Click the arrow and select a name in the list or

Click the arrow and select New to open the "Windows Wizard Rename Pattern" window.

Dollar Universe specific variables (between: ! !) can be used in the "Name" value:

Click OK to apply the pattern to the selected job(s) and close the window (no Undo available).

Click Apply to apply the pattern to the selected job(s) but not close the window (no Undo available).

Click Cancel to close the window.

Click Next at the bottom of the window to start job conversion (no Undo available).

User Service

If the submission account already exists in Dollar Universe, the window does not appear.

The import will create a user service for each submission account (one user service per submission account). The password is necessary to create the user service in Windows.

If the user services do not exist on the system, the wizard displays the list of submission accounts to be created.

The name of the submission account is DOMAIN\USER, DOMAIN and USER being the system info for the WTS job user, or LocalSystem if the WTS job runs for LocalSystem (it is listed only if it does not exist yet on UniJob).

Select the submission account from the list and click Update. Refer to section "V6 Submission Account Details".

No effect on the converted job (such as the "Interactive job" flag in the Uproc)

If the password has not been provided, the User Service will be not created.

If the password is provided, the User Service will be created.

If part of the user information is wrong (domain/user/password), User Service will be created but will not start.

Task Import

A job with a condition of infinite repeat cannot be imported into Dollar Universe as the infinite repeat property is not supported by Dollar Universe.

Jobs must be located in the task library root folder, not in subfolders.

When disabled Windows Task Scheduler jobs are imported into Dollar Universe they become simulated. They must be disabled in Dollar Universe manually.

After importing enabled Windows Task Scheduler jobs into Dollar Universe, the tasks are automatically disabled in Windows Scheduled tasks.

Each job selected from the task list will be imported:

Click Close to close the Wizard.

If the user service creation or startup failed, the submission account will not be created nor will the related job be created.

Messages:

Compatibility with Windows Task Scheduler Features

Windows Task Scheduler 2.0 features are listed below. In some cases, features are not fully supported with UniJob. The following notation is used:

Supported feature:

: Fully supported

: Unsupported

Action during import:

: An action is needed

: A message is displayed

: Can be imported

Category

 

Feature

Action (in the wizard)

General

 

Name

Name is the same as WTS job name

 

 

Location

In UniJob, all the jobs are at the same level.

 

 

 

Auteur

No correspondent notion

 

 

 

Comment

The job comment will be truncated to 32 characters

 

 

Mask

The job will not be masked in UniJob

 

 

Configured for

Compatible with the three proposed configurations

 

 

Enable / Disable Job

Job Enabled/Simulated

 

Security Options

username

Submission account

 

 

Execute when user is connected

The created job will be launched in batch mode

 

 

Execute when user is connected or not

The submission account is associated with the Windows user service “Local System”.

 

 

Execute with the maximum authorization.

The submission account is associated with the corresponding Windows user service. The password must be entered during the import.

Trigger

 

Create several triggers

Accumulated planning

 

 

Synchronizes the time zones

No time zones with UniJob

 

Time

Date and time

 

 

Start of validity

 

 

End of validity

 

 

Stop job if still running

 

Time once

Date and time

Exceptions

 

Time daily

Date and time

Daily rule

 

 

Cycle

Cyclical rule

 

Time weekly

Date and time

Daily rule

 

 

Days in the week

Daily rule

 

 

Cycle

Cyclical rule

 

Time monthly

Date and time

Daily rule

 

 

Months of the year

Daily rule

 

 

Days of the month

Daily rule

 

 

"2nd and 3rd Monday and Sunday" like pattern

Daily rule

 

 

Cycle

Cyclical rule

 

On opening a session

All users and specific users

 

On startup

No other parameter

 

After idle time

Refers to the conditions

 

Connection or disconnection to a user session

All users, specific users, connection from the remote/local computer

 

Lock or unlock a work station

All users, specific

 

Windows Event

basic or custom

 

Creation or modification of a task

 

Advanced settings

Maximum report of the task (random)

 

 

Repeat the task every….for….

 

 

Stop all the tasks at the end of the repeat time

 

 

Stop the task if it executes more than…

Stop the job after…

 

 

Activated

Action

Program

Capacity to create several actions

Several programs

 

 

Program script/path

 

 

Arguments

Command line arguments

 

 

Start in

Specific execution directory

 

Email address

 

Display a message

Conditions

Idle

 

Power

 

Network

Settings

 

Allow task to be run on demand

The contrary is not supported

 

 

Run task as soon as possible after a scheduled start is missed

 

 

If the task fails, restart every…

 

 

Attempt to restart up to n times

 

 

Stop the task if it runs longer than n days

 

 

If the running task does not end when requested, force it to stop

 

 

if the task is not scheduled to run again, delete it after n days

 

If the task is already executing

Do not start a new instance

 

 

 

Execute a new instance in parallel

Functions normally in UniJob

 

 

Put a new instance in a queue

 

 

 

Stop the existing instance

 

If several Program type actions are defined in the WTS task, they are included in the script that was created during the import of the task and carries the name of the task.