|
To edit Dr.Web Server schedule
1.Select the Administration item in the main menu of the Control Center. Select Dr.Web Server Task Scheduler in the control menu of the window that opens. The list of Dr.Web Server tasks will open.
2.To manage the schedule, use the corresponding elements from the toolbar:
a)General elements on the toolbar are used to create new tasks and manage the schedule section. These tools are always available on the toolbar.
 Add tasks from default schedule—add all tasks from the default schedule to the current schedule. All current tasks on the list are preserved, and all tasks from the default schedule are added to them. The default schedule tasks are added in any case, even if the current schedule already contains these tasks (original or modified), or fully coincides with the default schedule.
 Set default schedule—remove all tasks from the current schedule and set the default task schedule.
|
The default schedule is a list of tasks that are created during the initial Dr.Web Server installation. This schedule cannot be changed.
|
 Create task—add a new task. This action is described in detail below, in the Task Editor section.
 Export settings from this section to the file—export schedule to a file of a special format.
 Import settings to this section from the file—import schedule from a file of a special format.
|
Import of the Task Scheduler list for Dr.Web Server into the Task Scheduler for workstations and vice versa is not allowed.
|
b)To manage existing tasks, set flags next to the necessary tasks or in the table header to select all tasks from the list. The following elements on the toolbar for managing the selected tasks become available:
Option
|
Action
|
 Run type
|
Synchronous type
|
Run all tasks marked below synchronously. The task with the specified periodicity will be placed in the general queue of the Scheduler tasks to be executed sequentially.
|
Asynchronous type
|
Run all tasks marked below asynchronously. The task with the specified periodicity will be executed in parallel with other tasks, out of turn.
|
 Status
|
Enable execution
|
Activate execution of the selected tasks according to their schedule, if they were disabled.
|
Disable execution
|
Disable execution of the selected tasks. The tasks will remain on the list but will not be executed.
|
|
The same option can be set in the task editor on the General tab by setting the Enable execution flag.
|
|
 Severity
|
Make critical
|
Perform an extra execution of the task if the scheduled execution is skipped.
|
Make noncritical
|
Execute the task only at the scheduled time regardless of whether its execution has been skipped or not.
|
|
The same option can be set in the task editor on the General tab by setting the Critical task flag. The reason for missing the launch of a critical task may be, for example, that Dr.Web Server is turned off. Executing another task is not the reason for missing the task start.
|
|
 Duplicate settings
|
Duplicate tasks that are selected in the current schedule. When you use the Duplicate settings option, new tasks are created with the same settings as the selected tasks.
|
 Schedule to repeat
|
For tasks which are executed once: execute the task one more time according to the specified time settings (see how to change how many times a task is executed below, in the Task Editor section).
|
 Remove selected tasks
|
Remove the selected task from the schedule.
|
 Execute task
|
Execute the tasks selected on the list immediately. A task will be launched even if it is disabled for execution on a schedule.
|
 Edit task
|
Change task parameters. The Task editor window described below opens.
|
Task Editor
The Task Editor allows you to specify settings to:
1.Create a new task.
Click Create task on the toolbar.
2.Edit an existing task.
Click the name of one of the tasks on the task list and click Edit task on the toolbar.
A window for editing a task will open. The settings for editing an existing task are the same as the settings for creating a new task.
|
Values of fields marked with the * character must be specified.
|
To edit task settings
1.On the General tab in the General section, specify the following parameters:
•In the Name field, specify the name of the task that will be 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 can be set in the main window of the Scheduler via the Status toolbar option.
|
•Set the Critical task flag to perform an extra execution of the task if its scheduled execution is skipped for any reason. The Scheduler rechecks the task list every minute and executes any skipped critical task if it is found. If the task has been skipped several times at the moment of its execution, it will be executed only once.
|
The same option can be set in the main window of the Scheduler via the Severity toolbar option.
|
•If the Run the task asynchronously flag is cleared, the task will be added to the general queue of Scheduler tasks that are executed sequentially. Set the flag to execute this task in parallel to the queue.
2.In the Time section, specify the task launch parameters:
•In the Periodicity drop-down list, select when the task will be executed according to the specified periodicity:
Execution type
|
Parameters and description
|
Shutdown
|
The task will be launched at the Dr.Web Server shut down.
No additional parameters required to run the task.
|
Startup
|
The task will be executed at Dr.Web Server startup.
No additional parameters are required to run the task.
|
N minutes after initial task
|
In the Initial task drop-down list, select the task in relation to which the execution time of the current task is set.
In the Minute field, specify or select the number of minutes that should pass after the execution of the initial task to execute the task being edited.
|
Daily
|
Specify the hour and the minute for the task to be executed at.
|
Monthly
|
Specify the day of the month, the hour, and the minute for the task to be executed at.
|
Weekly
|
Select the day of the week, specify the hour and the minute for the task to be executed at.
|
Hourly
|
Specify a number from 0 to 59 to set the minute of every hour at which the task will be executed.
|
Every N minutes
|
The N value should be specified to set the time interval for the execution of the task.
At N equal to 60 or more, the task will be run every N minutes. At N of less than 60, the task will be run every minute of the hour multiple of N.
|
•Set the Disable after the first execution flag to execute the task only once at the specified time. If the flag is cleared, the task will be executed multiple times according to the specified periodicity.
To repeat the execution of a once executed task, use the Schedule to repeat option on the toolbar of the schedule section.
3.On the Action tab, in the Action drop-down list, select the type of the task and specify the task parameters needed to perform the task:
Task type
|
Parameters and description
|
Available licenses are close to the limit
|
|
The task is designed to send the Number of stations in the group is close to the license limit notification if the number of licenses in all keys assigned to the selected groups of stations is close to the end.
|
License keys assigned of the selected groups can also be assigned to other licensing objects.
|
Specify the following parameters:
•Number of available licenses—maximum number of licenses left in the license keys assigned to the selected groups, at which the notification will be sent to the administrator.
•Percentage of available licenses—maximum percentage of licenses left in the license keys assigned to the selected groups, at which the notification will be sent to the administrator.
•Groups—the list of groups which will be checked on the number of licenses left. Use ctrl and shift to select several groups. |
|
Back up critical Dr.Web Server data
|
|
The task is designed to backup the following critical data of Dr.Web 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 G3.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 statistical report on the anti-virus network.
For a report to be created, the Statistic report notification (see Notification Configuration) must be enabled in an active notification profile. The generated report is saved on the computer where Dr.Web Server is installed. Report delivery depends on the type of notification:
•For messages delivered via Email: an email with the report attached as well as a link to the report location is sent to the mail address which is specified in the notification settings.
•For all other methods of delivery: a notification with a link to the report location is sent.
To create this task in the schedule, specify the following parameters:
•Report language—language of the data in the report.
•Date format—format of dates in the statistical data. The following formats are available:
▫European: DD-MM-YYYY HH:MM:SS
▫American: MM/DD/YYYY HH:MM:SS
•Report format—format of the document containing the statistical report.
•Report period—time period for which the statistics will be included in the report.
•Groups—list of anti-virus network station groups the data on which will be included in the report. To select multiple groups, use the CTRL or SHIFT key.
•Report tables—list of statistical tables the data on which will be included in the report. To select multiple tables, use the CTRL or SHIFT key.
•Report retention period—time period for storing a report on the computer with running Dr.Web Server, starting from report generation. |
|
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 Dr.Web Servers, which use one database may result in errors.
When running Lua scripts, administrator gets the access to all file system within the Dr.Web Server folder and some system commands on a computer with Dr.Web 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 key expiration
|
|
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 Dr.Web Server has not connected for a long time
|
|
The task is designed to issue notifications in case the neighbor Dr.Web Servers have not been connected to the current Dr.Web 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 Dr.Web 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 Dr.Web Server database using the vacuum command.
No additional parameters required to run the task.
|
|
Purge expired stations
|
|
Specify the period after which the stations with expired access should be purged. You can view the date (day, month, year) when the station has the access to Dr.Web Server, in the station properties (on the General tab, the Expiration date field displays the certain date or Never to disable limitations).
If the period is set to 0 days, all expired stations will be considered obsolete and deleted when the task is executed.
|
|
Purge old records
|
|
The task is designed to purge outdated information from the database. The types of deleted records is given in the task parameters. You have to specify the number of days after which the records in the database are considered outdated and purged from Dr.Web Server. The period after which the records are purged is specified for each type of records separately.
Records for which the period is set to 0 days will be considered outdated and deleted when the task is executed.
|
|
Purge old stations
|
|
The task is designed to purge outdated stations.
You have to specify the time period (90 days by default) after which all stations that have not been connected to Dr.Web Server, are considered old and are moved to the Deleted group of the anti-virus network. The final deletion of such stations from the Dr.Web Server database is performed at execution of the Purge old records task (the time period of deleting the stations from the Deleted group is set in the Purge old records task parameters, for the Deleted stations type and counted from the moment of moving to the Deleted group).
|
|
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 increase the value, Dr.Web 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 unactivated stations
|
|
Specify the period after which the unused station accounts should be purged. You can view the list of unused station accounts in the hierarchical list of the anti-virus network, in the Status → New group (see the New Stations Approval Policy section for more details).
If the period is set to 0 days, all non-activated stations will be considered obsolete and deleted when the task is executed.
|
|
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 Dr.Web Server sends to a master Dr.Web Server. If sending a message fails, it is moved to the unsent message list. A subordinate Dr.Web 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 tools providing encryption between components:
•the drwcsd.pri private key on Dr.Web Server,
•the *.pub public key on workstations,
•the drwcsd-certificate.pem certificate 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 one of these steps, it is recommended to perform the second step some time after the first one, when certain stations will probably connect to Dr.Web Server.
When creating a task, select the appropriate step from the drop down list:
•Adding a new key—the first step of the procedure when the new inactive encryption key pair and certificate are created. The stations get the new public key and certificate upon the connection to Dr.Web 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 and certificate, followed by replacing the existing tools with the new ones: public keys and certificate on the stations and a private key on Dr.Web Server.
If for any reason some stations did not receive the new public key and the certificate, they will not be able to connect to Dr.Web Server. To resolve this problem, manually put the new public key and certificate 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).
|
|
Restart Dr.Web Server
|
|
The task is designed to restart Dr.Web Server.
No additional parameters required to run the task.
|
|
Run program
|
|
The task is designed to run 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, Dr.Web 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 Dr.Web Server logging only the start of the program. |
|
Send a 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 Dr.Web 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 Dr.Web 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.
Specify the following parameters:
•Active Directory controller—Active Directory controller, e.g. dc.example.com.
•Login—Active Directory user login.
•Password—Active Directory user password.
|
For Dr.Web Servers under Windows OS, settings of Active Directory search are not obligatory. Information of a user on whose behalf the Dr.Web Server process is run (usually, it is LocalSystem) is used as a default registration information.
For Dr.Web Servers under Unix-like OS, the settings must be obligatory specified.
|
•In the Connection security drop-down list, select the type of encrypted data exchange:
▫STARTTLS—switching to secured connection is performed by using the STARTTLS command. The 25 port is used by default for the connection.
▫SSL/TLS—establish a new secured TLS connection. The 465 port is used by default for the connection.
▫No—do not use encryption. Data exchange will be over an unprotected connection.
|
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.
|
After completing the task, you can assign special Office Control settings for users and groups from Active Directory (Office Control -> Group settings -> Access settings -> Per-group settings).
|
|
Update repository
|
|
The task is designed to launch the update of repository products from GUS.
Specify the following parameters:
•In the Product list, set the flags next to those repository products which will be updated by this task.
•Set the Update license keys to activate the procedure of license keys automatic update during repository update. Detailed information is given in the Automatic License Renewal 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 Dr.Web 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. To edit the groups list, click Edit (or the group identifier if groups are already set) and select necessary groups in the opened window. 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, and for the Wake on Magic Packet property, set the Value → Enabled).
|
|
|
Write to log file
|
|
The task is designed to write to the Dr.Web Server log file specified string.
String—message to be logged.
|
|
4.When all parameters for the task are specified, click Save to accept changes of edited parameters if you are editing an existing task, or to create a new task with specified parameters if you created a new task.
The result of task execution is displayed as a table in the Administration → Tasks execution log section.
|