Endpoint Protection

hello I need a solution,

My customer periodically receives a single risk event notification which is 3years old.

I know that this issue should be solved in RU1. But it is a RU3 version.

Should I open a case, or do you have a solution.

thanks alot

Rudolf

Since you're on latest version, you may want to check with support.

Did you delete and re-create notification?

Hi

Please Check this link

http://www.symantec.com/docs/TECH144817
 

Thnaks

Shailesh

Hello,

Please open a case with symantec support team .

How to create a new case in My Support

http://www.symantec.com/business/support/index?page=content&id=TECH58873

Phone numbers to contact Tech Support:-

Regional Support Telephone Numbers:

·         United States: https://support.broadcom.com (407-357-7600 from outside the United States)

·         Australia: 1300 365510 (+61 2 8220 7111 from outside Australia)

·         United Kingdom: +44 (0) 870 606 6000

Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp

Hi,

Thank you for posting in Symantec community.

SEP 12.1 RU1 has the following fix.

A notification for "new risk detected" is triggered repeatedly, despite longer damper setting
Fix ID: 2497657, 2212158
Symptom: The damper setting on a notification for new risks is configured for a specific time value. The first risk triggers the notification correctly. Subsequent risks before the damper period time incorrectly trigger the notification.
Solution: The damper option on notifications was modified to prevent this issue.

Do you see three years old singler risk detection triggering repeateadly?

If possible could you please attach the screen-shot?

Hello,

If the number of Single Risk Event notifications is small, removing/re-creating the notifications will resolve the issue.  This works because newly created notification conditions will include the time zone name value.

Hope that helps!!

Hello,

In SEP 12.1 there are two weekly scheduled reports & seven pre-defined notifications configured by Symantec.

I believe the issue need to be reproduced by Technical Support. Kindly be ready with the sep Database copy while you are opening a Support Ticket.