ESET REMOTE ADMINISTRATOR 4 Manual de instalación Pagina 30

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 92
  • Tabla de contenidos
  • SOLUCIÓN DE PROBLEMAS
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 29
30
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-1234567 and password are inserted and
using a proxy server is prohibited.
The second configuration (shown in the figure below) sent to clients will ensure that previous modifications are preserved,
including the username EAV-1234567 and password. This configuration will also allow the use of a proxy server and defines
its address and port.
Vista de pagina 29
1 2 ... 25 26 27 28 29 30 31 32 33 34 35 ... 91 92

Comentarios a estos manuales

Sin comentarios