Endpoint Protection

 View Only
  • 1.  Possible reason for an SEPM notification to trigger with false information?

    Posted Jul 14, 2016 12:16 AM

    Hey guys,

     

    I recieved an email from our SEPM notification about an SEP agent that is outdated. But upon checking the actual server it is updated. What's the possible reason for this?


    Thank you,
    Daryl



  • 2.  RE: Possible reason for an SEPM notification to trigger with false information?

    Trusted Advisor
    Posted Jul 14, 2016 01:38 AM

    Hello,

    This could happen when the Client has not reported the latest definition entry to SEPM or it's respective database.

    I hope you are running the latest version of SEP 12.1.6 MP5.

    I believe there were some bugs with SEPM in the earlier versions.



  • 3.  RE: Possible reason for an SEPM notification to trigger with false information?

    Posted Jul 14, 2016 05:24 AM

    Do you know a KB where I can reference that this is a bug from the earlier version? Our SEPM Server and workstations are already on 12.1.6 mp5 but the machines that I'm talking about are servers for another application, so I need some proof to present on the owners/admins of those server that they need to upgrade their SEP agents.

     

    Thanks



  • 4.  RE: Possible reason for an SEPM notification to trigger with false information?

    Posted Jul 14, 2016 05:43 AM

    The easiest and quickest step to take would be to delete and re-create the notification first to see if that fixes it.



  • 5.  RE: Possible reason for an SEPM notification to trigger with false information?
    Best Answer

    Broadcom Employee
    Posted Jul 14, 2016 08:23 AM

    Hi,

    There is a bug fix in SEP 12.1 RU6 & details are as per below. See if it applies in your case or not. 

    Cannot enable "Include only clients that have checked in with the management server today" in SEPM

    Fix ID: 3646594

    Symptom: You cannot enable Include only clients that have checked in with the management server today in the Virus Definitions Out-of-date notification.

    Solution: A new notification type in 12.1.5 (12.1 RU5) inadvertently overwrote the setting that stores the check box selection for out-of-date content notification conditions. This issue has been corrected.

    Reference: http://www.symantec.com/docs/TECH230558 

     



  • 6.  RE: Possible reason for an SEPM notification to trigger with false information?

    Posted Jul 15, 2016 12:20 AM

    Thanks Chetan, you always have the right answer since day one.



  • 7.  RE: Possible reason for an SEPM notification to trigger with false information?

    Posted Jul 15, 2016 12:21 AM

    This might work too, but I'll go for the upgrade route for now, those servers are running 12.1.1 anyway so might aswell see if it will work with  the upgrade of version. Thanks man.



  • 8.  RE: Possible reason for an SEPM notification to trigger with false information?

    Broadcom Employee
    Posted Jul 15, 2016 05:50 AM

    You are welcome.