|
To edit Dr.Web Server schedule, perform the following actions:
1.Select the Administrating item in the main menu of the Control Center, in the opened window, select Dr.Web Server Task Scheduler in the control menu. The list with the Server tasks will be opened. 2.To manage schedule, use the corresponding elements from the toolbar: a)General elements on the toolbar are used to create new tasks and generally manage schedule section. These tools are always available on the toolbar.  Create task—add a new task. This action is described in details below, in the Task Editor section.
 Export settings from this section to the file—export schedule to the file of special format.
 Import settings to this section from the file—import schedule from the file of special format.
b)To manage existing tasks, set the flags next to the necessary tasks or the common flag in the table header to select all task from the list. At this, elements on the toolbar to manage selected tasks become available:
Option
|
Action
|
Status
|
Enable execution
|
Activate execution of selected tasks according to their schedule, if they were disabled.
|
Disable execution
|
Disable execution of selected tasks. Tasks remain on the list but will not be executed.
|
|
The same option you can specify in the task editor on the General tab by setting the Enable execution flag.
|
|
Severity
|
Make critical
|
Perform extra launch of the task if scheduled execution of this task has been omitted.
|
Make not critical
|
Execute the task only at scheduled time regardless of whether a task launch has been omitted or not.
|
|
The same option you can specify in the task editor on the General tab by setting the Critical task flag.
|
|
 Duplicate settings
|
Duplicate tasks that are selected in the list of current schedule. When you run the Duplicate settings option, new tasks are created with settings similarly to the selected tasks.
|
 Schedule repeatedly
|
For tasks which executed once: execute task one more time according to the specified time settings (changing execution multiplicity of the task is described below, in the Task Editor section).
|
 Remove these settings
|
Remove selected task from the schedule.
|
3.To change task parameters, select it in the tasks list. The Task editor window described below opens. 4.After editing the schedule, click Save to accept changes. Task Editor
In the Task Editor you can specify settings to:
1.Create a new task. For this click Create task on the toolbar.
2.Edit existing task. For this click the name of one of the tasks in the tasks list.
The window for editing a task opens. Settings for editing of existing task are similar to the settings of creating a new task.
|
Values of fields, marked with the * sign, must be obligatory specified.
|
To edit task settings
1.On the General tab you can setup the following parameters: •In the Name field, specify the name of the task displayed in the schedule list. •Set the Enable execution flag, to enable the task execution. If the flag is cleared, the task remains on the list but will not be executed.
|
The same option you can specify on the main window of the Scheduler via the Status option on the toolbar.
|
•Set the Critical task flag to perform extra launch of the task if its scheduled execution has been omitted by any reason. The Scheduler rechecks the task list every minute and launches the omitted critical task if it was found. If at launch, the task was omitted several times, it will be executed only once.
|
The same option you can specify on the main window of the Scheduler via the Severity option on the toolbar.
|
On the Action tab, in the Action drop-down list, select the type of the task and specify task parameters which are needed to perform the task:
Task type
|
Parameters and description
|
Back up critical server data
|
The task is designed to backup the following critical data of the Server:
•database, •license key file, •private encryption key. Specify the following parameters:
•Path—path to the directory where the data will be saved (blank field means that the default directory will be used). •Maximum number of copies—maximum number of backup copies (the 0 value means no limitation). For details see the Appendices document, p. Appendix H4.5.
|
Backup folder must be empty. Otherwise, the folder content will be deleted during the back up.
|
|
Back up repository
|
The task is designed for periodic backups of the repository.
Specify the following parameters:
•Path—full path of the directory where the backup copy will be stored. •Maximum number of copies—maximum number of repository backup copies which are stored by the task in the specified directory. If the maximum number of copies is reached, the oldest copy will be overwritten by the new one. •Repository area defines which part of information on anti-virus component will be saved: ▫Entire repository—save all revisions from the repository for the components that are selected in the list below. ▫Only critical revisions—only revisions marked as important will be saved for the components that are selected in the list below. ▫Only configuration files—only configuration files will be saved for the components that are selected in the list below. •Set the flags for the components selected areas of which will be saved.
|
Backup folder must be empty. Otherwise, the folder content will be deleted during the back up.
|
|
Create statistic report
|
The task is designed to create a report with statistics on the anti-virus network.
To be able to create a report it is mandatory to enable the Periodic report notification (see Notification Configuration). The generated report is saved on a computer where the Server is installed. Report delivery depends on the type of notification:
•For sending messages via Email: a letter with attached report and also the link to the report location is sent to the mail address which is specified in notification settings. •For all other methods of delivery: an appropriate notification with a link to the report location is sent. To create a task in the schedule you have to specify the following parameters:
•Notifications profiles—name of notifications group with common settings for report generation. The title name can be specified when creating a new notifications group. •Report language—language of the data in the report. •Date format—format for dates display in statistic data. The following formats are available: ▫European: DD-MM-YYYY HH:MM:SS ▫American: MM/DD/YYYY HH:MM:SS •Report format—document format to save the statistics report. •Report period—time period for which the statistics will be included in the report. •Groups—list of anti-virus network station groups which data will be included in the report. To select multiple groups, use the CTRL or SHIFT. •Report tables—list of statistical tables which data will be included in the report. To select multiple tables, use the CTRL or SHIFT. •Report retention period—time period for storing a report on the computer with running Server, starting from report generation. |
Execute hook
|
The task is designed for executing user hooks (see the User Hooks section).
In the Name drop-down list, select a group of user hooks that will be executed.
|
Execute script
|
The task is designed for executing lua script which is specified in the Script field.
|
Simultaneous execution of tasks with Execute script type on several Servers which use one database may result in errors.
When running lua scripts, administrator gets the access to all file system within the Server folder and some system commands on a computer with the Server installed.
To forbid the access to the schedule, disable the Edit Server schedule permission for the correspondent administrator (see Administrators and Administrative groups).
|
|
License expiration reminder
|
The task is designed to issue reminders about the license expiration of Dr.Web product.
You have to set the period preceding license expiration starting from which the reminders will be issuing.
|
Neighbor server has not connected for a long time
|
The task is designed to issue notifications in case the neighbor Servers have not been connected to the current Server for a long time.
Notifications display settings can be configured in the Notification Configuration section using the Neighbor server has not been connected for a long time item.
Set values in the Hours and Minutes fields to define a time period after which the neighbor Server will be considered as not connected for a long time.
|
Purge database
|
The task is designed to collect and purge unused records in the Server database using the vacuum command.
No additional parameters required to run the task.
|
Purge old records
|
The task is designed to purge outdated information about the stations from the database.
You have to specify the number of days after which the statistic records on workstations (but not the workstations themselves) are considered outdated and purged from the Server.
The period after which the statistic records are purged is specifies for each type of records separately.
|
Purge old stations
|
The task is designed to purge outdated stations from the database.
You have to specify the time period (90 days by default) after which all stations that did not have at least one connection to the Server are considered old and are purged from the Server.
|
|
Outdated information is purged from the database to save disc space. The period in the Purge old records and Purge old stations tasks by default is 90 days. If you decrease the value, the statistics on the operation of the anti-virus network components will be less representative. If you decrease the value, the Server may need extremely more resources.
|
|
Purge outdated messages
|
The task is designed for purging the following messages from the database:
•agent notifications, •notifications for the web console, •reports created according to the schedule. This also purges messages marked as obsolete, i.e. with expired retention period which can be configured:
•for notifications: for appropriate sending method while creating a notification (see Notification Configuration). •for reports: in a task for creating reports. No additional parameters required to run the task.
|
Purge unsent events
|
The task is designed to purge unsent events from the database.
You have to set the period for storing unsent events after which they will be purged.
This refers to events that a subordinate Server sends to a master Server. If sending a message fails, it is moved to the unsent messages list. A subordinate Server continues its attempts to send the message at the specified interval. When the Purge unsent events task is run, events will be purged if their storage time has reached and exceeded specified period.
|
Replace encryption key
|
The task is designed for periodic replacement of the following encryption keys:
•the drwcsd.pri private key on the Server, •the drwcsd.pub public key on workstations. Because some workstations can be turned off at the time of replacement, the procedure is divided into two steps. You have to create two tasks to perform each of these steps, it is recommended to perform the second step some time after the first one, when certain stations will probably connect to the Server.
When creating a task, select the appropriate step of key replacing from the drop down list:
•Adding a new key—the first step of the procedure when the new inactive encryption key pair is created. The stations get the new public key upon the connection to the Server. •Deleting the old key and switching to the new key—the second step when the stations are notified about switching to the new encryption keys, followed by replacing the existing keys with the new ones: public keys on the stations and private key on the Server. If for any reason some stations did not receive the new public key, they will not be able to connect to the Server. To resolve this problem, the following options are available:
•Manually put the new public key on the station (you can view the procedure of replacing the key on station, in the Appendices document, p. Connecting Dr.Web Agent to Other Dr.Web Server). •Allow the Agents authorize on the Server with incorrect public key (see the Network section in the Agent preferences). |
Restart Dr.Web Server
|
The task is designed to restart the Server.
No additional parameters required to run the task.
|
Run program
|
The task is designed to run a custom program.
|
Programs launched under this task are executed in the background.
|
Specify the following parameters:
•The Path field—full name (with the path) of the program executable file to run. •The Arguments field—command line parameters to run the program. •Set the Wait for the completion of the program flag to wait for the completion of the program which has been launched by this task. At this, the Server logging the start of the program, the returned code and the time of the program end. If the Wait for the completion of the program flag is cleared, the task become completed right after the launch of the program and the Server logging only the start of the program. |
Send message to station
|
The task is designed to send arbitrary message to users of a station or group of stations.
A message settings are given in the Sending Notifications to Stations section.
|
Shut down Dr.Web Server
|
The task is designed to shut down the Server.
No additional parameters required to run the task.
|
Station has not connected for a long time
|
The task is designed to issue notifications in case the stations have not been connected to the current Server for a long time.
Notifications display settings can be configured in the Notification Configuration section using the Station has not been connected for a long time item.
In the Days field specify a time period after which the station will be considered as not connected for a long time.
|
Synchronization with Active Directory
|
The task is designed to synchronize network structures: Active Directory containers which contains computers become groups of anti-virus network to which workstations are placed.
No additional parameters required to run the task.
|
The task is disabled by default. To activate the task execution, set the Enable execution option in the task settings or on the toolbar as described above.
|
|
Update repository
|
The information on this task can be found in the Scheduled Updates section.
|
Wake stations
|
The task is designed to turn on stations, for example before running the scanning task.
The following task parameters define which stations will be turned on:
•Wake all stations—every station which is connected to the Server will be turned on. •Wake stations by specified parameters—only stations that accord to the parameters below will be turned on: ▫IP addresses—the list of IP addresses of the stations that will be turned on. The list is specified in the following format: 10.3.0.127, 10.4.0.1-10.4.0.5, 10.5.0.1/30. Use comma or newline to separate several addresses. You can also use DNS names of the stations instead of their IP addresses. ▫MAC addresses—the list of MAC addresses of the stations that will be turned on. The MAC-address octets have to be separated by the ':' sign. Use comma or newline to separate several addresses. ▫Groups—the list of groups of the stations that will be turned on. Use ctrl and shift to select several groups.
|
To run this task, all stations that are going to be turned on should be equipped with network cards with Wake-on-LAN support.
To check whether your network card supports Wake-on-LAN, please refer to its documentation or see its properties (Control Panel → Network and Internet → Network Connections → Change Adapter Settings → Configure → Advanced).
|
|
Write to log file
|
The task is designed to write to the Server log file specified string.
String—message to be logged.
|
3.On the Time tab: •In the Period drop-down list, set the launch mode of the task and setup the time according to the specified periodicity:
Launch type
|
Description
|
Daily
|
Specify the hour and the minute for the task to be launched at the time specified.
|
Every N minutes
|
The N value should be specified to set the time interval for the execution of the task.
At N equal 60 or more, the task will be run every N minutes. At N less than 60, the task will be run every minute of the hour multiple of N.
|
Hourly
|
Specify a number from 0 to 59 to set the minute of every hour the task will be run.
|
Monthly
|
Specify the day of the month, the hour and the minute for the task to be launched at the time specified.
|
N minutes after initial task
|
In the Initial task drop-down list, select the task relatively to which the time of current task execution is set.
In the Minute field, specify or select from the offered list the number of minutes that should pass after the execution of initial task to start execution of edited task.
|
Shut down
|
The task will be launched at Server shut down.
No additional parameters required to run the task.
|
Start up
|
The task will be launched at Server start up.
No additional parameters required to run the task.
|
Weekly
|
Select a day of the week, specify the hour and the minute, for the task to be launched at the time specified.
|
•Set the Disable after the first execution flag to execute the task only once at specified time. If the flag is cleared, the task will be executed multiple times according to the specified periodicity. To repeat the launch of task already ones executed, use the Schedule repeatedly on the toolbar of the schedule section.
4.When all parameters for the task are specified, click Save to accept changes of edited parameters, if you editing existing task, or to create a new task with specified parameters if you created a new task.
|
