Operation
81
Avira Security Management Center
Avira GmbH
6.6
Performing Commands and Planning Tasks
For every Avira product there are various ways of performing actions such as scan
and update, using specific parameters or schedules. You can configure, activate and
plan these actions using Avira SMC for computers and groups in the Security
Environment. An action initiated by Avira SMC (e.g. Scan) is referred to as a
Command
, while the planned, single or periodical action is called a
Task
(e.g.
weekly update).
The Avira SMC is able to run all commands accepted by the installed Avira
products.
For more details on Avira commands and parameters, please refer to the Avira product
documentation.
You should read and observe all instructions before performing Avira SMC
commands and planning tasks.
When SMC Server is closed, ongoing commands are saved as pending operations,
before shutdown.
You can see the results of a command (e.g. Scan) or task (e.g. Scan hard disk) in the
Details panel of the
Events
node or of the group/computer.
Push and Pull Mechanisms
According to the Agents’ settings (see
Changing the SMC Agent Configuration
–
Page 41), there are two mechanisms for performing tasks and commands:
z
push
mechanism performs the commands immediately or sends the tasks to
the scheduler, and they are run as planned.
In the case of offline computers, actions and commands are saved by SMC as
pending operations
and automatically triggered by the program immediately
after the computers are online.
The computers will have the status for pending operations:
dark monitor, orange arrow, red marker on the left side.
z
pull
mechanism should be used for very large networks to reduce the network
traffic. It means the commands are registered as pending operations and they
are all performed when the Agent makes the synchronization.
The status icon for computers with pull Agents is:
green monitor, green arrow, red marker on the left side, if online;
or
dark monitor, orange arrow, if offline.
Even for pull Agents, you might need to force the synchronization. For this case,
you can use the command
Force agent synchronization,
which you can activate as
follows: