Endpoint Protection

 View Only
  • 1.  Scheduled Scan Email Notification?

    Posted Aug 30, 2016 11:26 PM

    Hey guys,

    We're trying to achieve this scenario:

    1. Set a scheduled Scan

    2. Scheduled scan was triggered and completed

    3. A notification email will be sent to the admins about the scan result

    We already have the 1 and 2 tested, but we can't figure out the 3. We've been checking the Monitor->Notification and it seems like it's not there. Are we missing something here? I hope someone can shed some light on us.

    Thank you,

     



  • 2.  RE: Scheduled Scan Email Notification?

    Posted Aug 31, 2016 12:01 AM

    I dont think email notification exists, check in the console

    About Scan reports and logs

    https://support.symantec.com/en_US/article.TECH95545.html



  • 3.  RE: Scheduled Scan Email Notification?

    Posted Aug 31, 2016 01:06 AM

    Hi d4ry1,

    Rafeeq is correct, unfortunately there is no Notification Condition for what you are trying to do :(

    Maybe the closest you might be able to get is using Scheduled Reports with a Report Type of "Scan Report", and a Selected Report of "Computers Not Scanned" or "Computers by Last Scan Time".

    Although it is after the fact, rather than immediate as with the notification, if you know roughly how long your scheduled scan runs you could schedule one of the above reports after the scans are done.

    Hope this gives you some ideas.

    Steve 



  • 4.  RE: Scheduled Scan Email Notification?

    Posted Aug 31, 2016 07:37 AM

    Notification emails about scans do not exists in the SEPM console.



  • 5.  RE: Scheduled Scan Email Notification?
    Best Answer

    Posted Aug 31, 2016 11:37 PM

    Hi System Team,

    Thanks for the alternatives, this is what actually we ended up doing. With an additional manual generation of a risk report per group for the detailed list of detections from the scheduled scan.

     



  • 6.  RE: Scheduled Scan Email Notification?

    Posted Sep 01, 2016 12:03 AM

    Hi d4ry1,

    Glad that pointed you to a workaround  :)

    Steve