31
3.7 ESET Configuration Editor
The ESET Configuration Editor is an important component of ERAC and is used for several purposes. Some of the most
important are the creation of the following:
Predefined configurations for installation packages
Configurations sent as tasks or policies to clients
A general (.xml) configuration file
Configuration Editor is a part of ERAC and is represented mainly by the
cfgedit.*
files.
The Configuration Editor allows the administrator to remotely configure many of the parameters available in any ESET
security product, especially those installed on client workstations. It also allows the administrator to export
configurations to .xml files which can later be used for multiple purposes, such as creating tasks in ERAC, importing a
configuration locally in ESET Smart Security, etc.
The structure used by the Configuration Editor is an
.xml
template which stores the configuration in a tree-like
structure. The template is stored in the
cfgedit.exe
file. That is why we recommend that ERAS and ERAC be updated
regularly.
Warning:
The Configuration Editor allows you to modify any .
xml
file. Please avoid modifying or rewriting the
cfgedit.xml
source file.
For the Configuration Editor to function, the following files must be available:
eguiEpfw.dll, cfgeditLang.dll, eguiEpfwLang.
dll
and
eset.chm.
3.7.1 Configuration layering
If a value is changed in the Configuration Editor, the change is marked by a blue symbol . Any entry with the grey
icon has not been changed and will not be written to the
.xml
output configuration.
When applying a configuration to clients, only modifications which have been saved to the
.xml
output configuration
file will be applied ( ) All other items ( ) will remain unchanged. This behavior allows for gradual application of several
different configurations without undoing previous modifications.
An example is shown in the figure below. In this configuration the username
EAV-12345678
and password are inserted
and using a proxy server is prohibited.