Endpoint Protection

 View Only

  • 1.  Another Proactive Threat Protection Issue

    Posted Jan 19, 2010 10:30 AM
    In one of my groups I am getting multiple reports that the Proactive Threat Protection is Off.  All the clients are Windows XP SP3 x86, SEP version is 11 MR4 MP2 (11.0.4202)  this just started within the past week, and I am not seeing this issue in any other group.  Any Ideas?

    Capture.JPG


  • 2.  RE: Another Proactive Threat Protection Issue

    Posted Jan 19, 2010 11:26 AM
    go to add/remove programs
    select symantec endpoint
    slect change
    select modify
    remove ptp click install
    reboot
    follow the same method as above
    now install ptp
    run the install
    check if that downloads defs


  • 3.  RE: Another Proactive Threat Protection Issue

    Posted Jan 19, 2010 11:37 AM
    Its downloading Defs just fine, for whatever reason its stuck on "Off" and clicking "Fix" does nothing.


  • 4.  RE: Another Proactive Threat Protection Issue

    Posted Jan 19, 2010 11:44 AM
    tried above method, stil the same?


  • 5.  RE: Another Proactive Threat Protection Issue

    Posted Jan 19, 2010 11:54 AM
    Still the same...however if I remote in as an Admin it shows green, but if a normal user logs in they get the red "X"


  • 6.  RE: Another Proactive Threat Protection Issue

    Posted Jan 19, 2010 01:22 PM
    it should be a permission issue then
    download symantec support tool
    log in as normal user and check the errors
    might get some DCOM issues / registry permission issue


  • 7.  RE: Another Proactive Threat Protection Issue

    Posted Jan 20, 2010 04:02 PM
    "....  and I am not seeing this issue in any other group...  & ... if I remote in as an Admin it shows green...."


    I am suspecting a policy problem(may be a corruption)... Because normally, if you gray down the users ability to change settings in policy , its not applied to the local admin dude... He can log in and change things... And also, I see the defs are uptodate...  Just a basic step to check if SEPM contributes to this issue, move any one of the client to a group that does not have this problem... :) ... and observe...
     
    Alternatively, you can copy the AVAS policy from a working-client-group and paste it here in this affected group...

    Also, like rafeeq said, it could also be permission issues, but in that case I'm guessing you should have error relating SEP (Coh32, to be precise) in the event logs... Please check and get back.. :)

    Cheers,
    Visu.