Application of the Configuration file in large network environments
a multi-level hierarchy of a large computer network, the Configuration
file can be created by the principal network administrator. The
"template" of this file can than be sent to lower-lever network
administrators who may modify the file to reflect their specific needs.
below is an example of a Configuration file created by the principal
network administrator. If a lower level administrator wants to introduce
any changes, the following procedure can be applied: 1/ the file is
saved in a directory on their computer, (e.g. \Program Files\Eset\Cfg),
2/ in the Mirror setup (in the Configuration file group) this file is selected, and, 3/ clicking at Modify the file the Configuration file dialog window will open allowing proper changes to be made.
Lower-level administrators will have to change the Path to the Update files,
to secure update of the end-user workstations from the correct server,
that is from the server where a given lower-level administrators creates
the update mirror. The server username and password should also be
the example presented below, definition of the SMTP messages is defined
as well. One of the messages is sent to the principal (main)
administrator [email protected] , the second one is sent to a specific
administrator in charge of particular end-user workstation. In the
example, the principal administrator has also defined the password to
lock the settings. The lower level administrators don't need to change
the password. Unlocking of the settings may be the over entire network.
EXAMPLE of a CONFIGURATION FILE:
SMTP_Address_Virus="[email protected];[email protected]"
SMTP_Address_Error="[email protected];[email protected]"
SMTP_Format_Virus="%TimeStamp% - Virus alarm of %ProgramName% on %ComputerName%: %InfectedObject% infected with VirusName%."
%TimeStamp% The following error message: %ErrorDescription% has
occurred on %ComputerName% workstation, while %ProgramName% was