ESET SMART SECURITY Guía de usuario descargar pdf (Pagina 39)

tree structure section contains removed values

value / ﬁle has been changed

tree structure section contains modiﬁed values / ﬁles

the risk level has decreased / it was higher in the previous log

the risk level has increased / it was lower in the previous log

The explanation section displayed in the left bottom corner describes

all symbols and also displays the names of logs which are being

compared.

Any comparative log can be saved to a ﬁle and opened at a later time.

Example: – Generate and save a log, recording original information

about the system, to a ﬁle named previous.xml. After changes to the

system have been made, open SysInspector and let it generate a new

log. Save it to a ﬁle named current.xml.

In order to track changes between those two logs, click

File > Compare Log. The program will create a comparative log

showing dierences between the logs.

The same result can be achieved if you use the following command

line option:

SysIsnpector.exe current.xml previous.xml

5.4.1.4 SysInspector as part of ESET Smart Security 4

To open SysInspector in ESET Smart Security, click Tools >

SysInspector. The management system in the SysInspector window

is similar to that of computer scan logs, or scheduled tasks. All

operations with system snapshots ‑ create, view, compare, remove

and export ‑ are accessible within one or two clicks.

The SysInspector window contains basic information about the

created snapshots such as create time, short comment, name of the

user that created the snapshot and snapshot status.

To Compare, Add..., or Remove snapshots, use the corresponding

buttons located below the list of snapshots in the SysInspector

window. Those options are also available from the context menu.

To view the selected system snapshot, use the View context menu

option. To export the selected snapshot to a ﬁle, right‑click it and

select Export.... A detailed description of the available options is

shown below:

Compare ‑ Allows you to compare two existing logs. This feature is

useful if you want to track changes between the current log and an

older log. For this option to take eect you must select two snapshots

to be compared.

Add – Creates a new record. Before that you must enter a short

comment about the record. To see the snapshot creation progress (of

the currently generated snapshot) in percent, see the Status column.

All completed snapshots are marked by the Created status.

Remove – Removes entries from the list

Show – Displays the selected snapshot. Alternatively, you can double‑

click the selected entry.

Export... – Saves the selected entry in an .xml ﬁle (as well as a .zip

version)

5.4.1.5 Service script

Service script is a tool that directly inﬂuences the operating system

and installed applications, allowing users to execute scripts that

remove problematic components in the system, including viruses,

remnants of viruses, blocked ﬁles, virus records in the registry, etc. The

script is stored in a text ﬁle generated from a pre‑existing .xml ﬁle. The

data in the .txt script ﬁle is ordered simply and legibly, for ease of use.

The script will initially exhibit neutral behavior. In other words, it will

not have any impact on the system while in its original form. The user

needs to edit the script for it to have any eect.

Warning:

This tool is intended for advanced users only. Incorrect use may result

in damage to programs or the operating system.

5.4.1.5.1 Generating Service scripts

To generate a script, right‑click any item from the menu tree (in the

left pane) in the SysInspector main window. From the context menu,

select either the Export All Sections To Service Script option or the

Export Selected Sections To Service Script option.

5.4.1.5.2 Structure of the Service script

In the ﬁrst line of the script’s header you can ﬁnd information about

the Engine version (ev), GUI version (gv) and the Log version (lv).

You can use this data to track possible changes in the .xml ﬁle that

generates the script and prevent any inconsistencies during execution.

This part of the script should not be altered.

The remainder of the ﬁle is divided into sections in which items can be

edited (denote those that will be processed by the script). You mark

items for processing by replacing the “‑” character in front of an item

with a “+” character. Sections in the script are separated from each

other by an empty line. Each section has a number and title.

01) Running processes

This section contains a list of all processes running in the system. Each

process is identiﬁed by its UNC path and, subsequently, its CRC16 hash

code in asterisks (*).

Example:

01) Running processes:

‑ \SystemRoot\System32\smss.exe *4725*

‑ C:\Windows\system32\svchost.exe *FD08*

+ C:\Windows\system32\module32.exe *CF8A*

[...]

In this example a process, module32.exe, was selected (marked by a “+”

character); the process will end upon execution of the script.

02) Loaded modules

This section lists currently used system modules.

Example:

02) Loaded modules:

‑ c:\windows\system32\svchost.exe

‑ c:\windows\system32\kernel32.dll

+ c:\windows\system32\khbekhb.dll

1 2 ... 34 35 36 37 38 39 40 41 42 43 44 45 46

Comentarios a estos manuales

Sin comentarios

ESET SMART SECURITY Guía de usuario Pagina 39

Comentarios a estos manuales

Relacionado con productos y manuales para Software de seguridad antivirus ESET SMART SECURITY