From eScan Wiki
| Revision as of 12:37, 26 June 2009 WikiSysop (Talk | contribs) ← Previous diff |
Revision as of 14:10, 26 June 2009 WikiSysop (Talk | contribs) Next diff → |
||
| Line 1: | Line 1: | ||
| - | {| class="wikitable" border="0" | + | {|class="wikitable" border="0" |
| |- | |- | ||
| {| id="mp-topbanner" style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;" | {| id="mp-topbanner" style="width:100%; background:#fcfcfc; margin-top:1.2em; border:1px solid #ccc;" | ||
| Line 29: | Line 29: | ||
| ---- | ---- | ||
| - | The Parent/Primary server will get live alert from | + | The Parent/Primary server will get live event alerts, like processes executed on the client system, in the Client Live Updater tab of the eScan Management console.It will receive live alerts from: |
| + | |||
| # Client belonging to Parent/Primary server. | # Client belonging to Parent/Primary server. | ||
| # Secondary/Child server | # Secondary/Child server | ||
| - | # Client of Secondary/Child server. (these client alert are also available in Secondary/Child server) | + | # Client of Secondary/Child server. (these client alert will also be available in the Secondary/Child server) |
| - | Overall all the alert in a network having different location can be viewed from Primary/Parent server. | + | Overall, such event alerts in a network can be viewed from Primary/Parent server. |
| - | The customization of alert is also possible referring to Event ID generated by Live Alert, they can be stop/ignore to send alert to server. | + | [[Image:eserv-client.JPG|image|center]] |
| + | Alerts can be customized as per the Event ID generated by Live Alert: | ||
| + | |||
| + | * Open the <B>Eupdate.ini</B> file from <B>\Program files\eScan</B> folder and search for the below entries: | ||
| + | |||
| + | |||
| + | IgnoreEventIds= | ||
| + | (This entry will stop / ignore a particular event id to be broadcasted from the client system to the eScan server. <B>Note:-</B>The settings should be done on the system of which the event is required to be stopped). | ||
| + | eg: IgnoreEventIds= 102,152 | ||
| + | [The local system will not broadcast the Endpoint security (Event id=102) & File AntiVirus(Event id=152) to the eScan Server]. | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | SendOnlyEventIds= | ||
| + | (This entry will only broadcast a particular event id to the eScan Server. <B>Note:-</B>The settings should be done on the system of which the event is required to be broadcasted). | ||
| + | |||
| + | eg: SendOnlyEventIds=102,152 | ||
| + | The local system will broadcast only the Endpoint security (Event id=102) & File AntiVirus(Event id=152)events to the eScan Server). | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | IgnoreEventIdsServToServ= | ||
| + | (This entry is valid for stopping the broadcast of a particular event alerts from one eScan server to another eScan Server. For instance from a secondary eScan server to a primary eScan server. <B>Note:-</B>The settings should be done on the system of the eScan server of which the event is required to stopped). | ||
| + | IgnoreEventIdsServToServ=102,152 | ||
| + | |||
| + | |||
| + | ---- | ||
| + | |||
| + | SendOnlyEventIdsServToServ= | ||
| + | (This entry is valid for broadcasting a paritcular event alerts only from one eScan server to another eScan Server. <B>Note:-</B>The settings should be done on the local system of the eScan server of which the event is required to be broadcasted). | ||
| + | SendOnlyEventIdsServToServ=102,152 | ||
| + | |||
| + | For multiple event id's to be added in the above entry (,)as a separator should be used. | ||
| - | [[Image:eserv-client.JPG|image|center]] | ||
| ---- | ---- | ||
| <B><I><font size=2>Email us your feedback to [mailto:solutions@mwti.net solutions@mwti.net]</font></I></B> | <B><I><font size=2>Email us your feedback to [mailto:solutions@mwti.net solutions@mwti.net]</font></I></B> | ||
Revision as of 14:10, 26 June 2009
|
|
General |
Knowledgebase |
Support |
Q.How does Client Live Updater tab in eScan Management Console work?
The Parent/Primary server will get live event alerts, like processes executed on the client system, in the Client Live Updater tab of the eScan Management console.It will receive live alerts from:
- Client belonging to Parent/Primary server.
- Secondary/Child server
- Client of Secondary/Child server. (these client alert will also be available in the Secondary/Child server)
Overall, such event alerts in a network can be viewed from Primary/Parent server.
Alerts can be customized as per the Event ID generated by Live Alert:
- Open the Eupdate.ini file from \Program files\eScan folder and search for the below entries:
IgnoreEventIds=
(This entry will stop / ignore a particular event id to be broadcasted from the client system to the eScan server. Note:-The settings should be done on the system of which the event is required to be stopped).
eg: IgnoreEventIds= 102,152 [The local system will not broadcast the Endpoint security (Event id=102) & File AntiVirus(Event id=152) to the eScan Server].
SendOnlyEventIds=
(This entry will only broadcast a particular event id to the eScan Server. Note:-The settings should be done on the system of which the event is required to be broadcasted).
eg: SendOnlyEventIds=102,152 The local system will broadcast only the Endpoint security (Event id=102) & File AntiVirus(Event id=152)events to the eScan Server).
IgnoreEventIdsServToServ=
(This entry is valid for stopping the broadcast of a particular event alerts from one eScan server to another eScan Server. For instance from a secondary eScan server to a primary eScan server. Note:-The settings should be done on the system of the eScan server of which the event is required to stopped).
IgnoreEventIdsServToServ=102,152
SendOnlyEventIdsServToServ=
(This entry is valid for broadcasting a paritcular event alerts only from one eScan server to another eScan Server. Note:-The settings should be done on the local system of the eScan server of which the event is required to be broadcasted).
SendOnlyEventIdsServToServ=102,152
For multiple event id's to be added in the above entry (,)as a separator should be used.
Email us your feedback to solutions@mwti.net


