Endpoint Protection

 View Only
  • 1.  Symantec System center 10.1.5..unable to initiate definition push out via console

    Posted Jul 19, 2011 05:23 PM

    Not sure I'm in the right place, but Im having an issue with Antivirus 10.1.5 corporate edition.

    From the symantec system center, I am unable to right click on a specific machine, choose update virus definitions now and have it push out the defs.

    Everything else is working fine, the machines are checking in, they are online, they are scanning at the scheduled time, etc

    The error I get is a Symantec Antivirus Management Snap-in error. It states:

     

    Symantec AntiVirus was unable to start a definition download on the following clients <client name here>. Verify that the clients are working correctly. Retry?

     

    I originally tried doing this on a machine that is showing up with old virus defs, but now I find I can't push out manually with the console to any managed machine.

     

    Help!



  • 2.  RE: Symantec System center 10.1.5..unable to initiate definition push out via console

    Posted Jul 20, 2011 11:18 AM

    For starters check this KB -

    Troubleshooting communication problems with Symantec Client Security 3.x or Symantec AntiVirus Corporate Edition 10.x

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

    I noticed that you are running an old version of SAV, you should really consider upgrading to the latest AV for Enterprise, SEP 12 Endpoint Protection.

    http://www-uat.ges.symantec.com/business/theme.jsp?themeid=sep-family

    For free trial versions of the different Endpoint products, please visit the Downloads page - http://www.symantec.com/business/products/downloads/index.jsp

    Moving this thread to the Endpoint Protection forum.

     

    Regards,

    Thomas



  • 3.  RE: Symantec System center 10.1.5..unable to initiate definition push out via console

    Posted Jul 20, 2011 11:49 AM

    are u able to telnet client and server on 2967; thats the communication port used for clients;

    from SSc run  a discovery ; check if that fixes the issue.