ESET PROTECT On-Prem

Offline | Go online

ESET PROTECT On-Prem – Table of Contents

# Server Tasks

Copy current article URL Share via email

Server tasks are executed by ESET PROTECT Server on itself or other devices. Server tasks cannot be assigned to any specific client or client group. 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.

## Server Tasks

•Agent Deployment

•Delete Not Connecting Computers

•Generate Report

•Rename computers

•Static Group Synchronization

•User Synchronization

## 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 ESET PROTECT 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 (More > 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.

|  | 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.To create a new Server Task, click Tasks > Add > Server Task or select the desired task type from the tree and click Add > Server Task.

2.In the Basic section, type basic information about the task, such as a Name and Description (optional). Click Select tags to assign tags.
In the Task drop-down menu, select the task type you want to create and configure. If you have selected a specific task type before creating a new task, Task is pre-selected based on your previous choice. Task (see the list of all Tasks) defines the settings and the behavior for the task.

You can also select from the following task trigger settings:

•Run task immediately after finish—Select this option to have the task run automatically after you click Finish.

•Configure trigger—Select this option to enable the Trigger section, where you can configure trigger settings.

To set the trigger later, leave the check boxes deselected.

3.Configure the task settings in the Settings section.

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

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

|  | 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.

˄˅