Server Tasks

Server tasks can automate routine jobs. Each server task can have one trigger configured. If the task needs to be run with various events, there has to be separate server task for each trigger. ERA includes six predefined Server Task types.

icon_details_hoverNOTE

Server tasks cannot be assigned to any specific client or client group.

Server tasks and permissions

The task and trigger both need an executing user. This is the user who modifies the task (and trigger). This user must have sufficient permissions for the chosen action. During execution, the task always takes the executing user from the trigger. If the task is run using the Run task immediately after finish setting, the executing user is the user logged into the ERA Web Console. A user has permissions (Read, Use, Write) for the selected server task instance if it has those permissions selected in its permission set (Admin > Access Rights > Permission Sets) and has these permissions set for that Static Group where the server task is located. See the list of permissions for more information on access rights.

light-bulbEXAMPLE

John, whose home group is John’s Group, wants to remove Server Task 1: Generate Report. The task was originally created by Larry, therefore the task is automatically contained in Larry's home group, Larry's Group. The following conditions must be met for John to remove the task:

John must be assigned a permission set with write permissions for Server Tasks & Triggers - Generate Reports.

The permission set must contain Larry’s Group under Static Groups.

Permissions needed for certain server task actions

To create a new server task, the user needs write permission for the selected task type and proper access rights for the referenced objects (computers, licenses, groups).

To modify a server task, the user needs write permission for the selected server task instance and proper access rights for the referenced objects (computers, licenses, groups).

To remove a server task, the user needs write permission for the selected server task instance.

To run a server task, the user needs use permission for the selected server task instance.

Create a new server task

1.Click Admin > Server Tasks > New.

2.Enter basic information about the task, such as a name, description (optional) and the task type. The task type defines the settings and the behavior of the task.

3.You can decide if you want to:

Run task immediately after finish  - Select this check box to have the task run automatically after you click Finish.

Configure trigger - Select the check box and expand the Trigger section to configure the trigger settings.

Set the trigger later (select no check box).

4.Configure the task settings in the Settings section.

5.Set the trigger in the Trigger section, if it is available.

6.Verify all the settings for this task in the Summary section and then click Finish.

Access Group Filter

access_group

The Access Group filter button enables users to select a static group and filter viewed objects according to the group where they are contained.

icon_details_hoverNOTE

It is recommended for users who are regularly using Server tasks to create their own tasks rather than sharing them with other users. Each time the task is run it uses the permissions of the executing user. This can confuse some users.