Endpoint Protection

 View Only
  • 1.  SYMANTEC ENDPOINT CLIENT VERSION 5.0 CREATING PROBLEM

    Posted Nov 25, 2009 10:23 PM
      |   view attached
    I HAVE CREATED A MANAGED CLIENT SETUP (.EXE) SELECTING A GROUP, BUT WHEN I RUN THE SETUP IN CLIENT MACHINE CLIENT SETUP IS INSTALLED BUT IT CAN'T JOIN  IN SPECIFIED GROUP, IT SHOWS OFFLINE.I HAVE PRINTSCRN HEREWITH.CAN ANYBODY HELP ME OUT?

    SOUMYA


  • 2.  RE: SYMANTEC ENDPOINT CLIENT VERSION 5.0 CREATING PROBLEM

    Broadcom Employee
    Posted Nov 25, 2009 10:27 PM
    drop the sylink.xml exported from communication settings from the sepcified group and check if the client connects to server and to intended group. Even after replcating sylink.xml if it doe snot connect, run sylink monitor and paste the gathered logs here.


  • 3.  RE: SYMANTEC ENDPOINT CLIENT VERSION 5.0 CREATING PROBLEM

    Posted Nov 25, 2009 11:10 PM

    It is very difficult to provide sylink in everytime in client installation.



  • 4.  RE: SYMANTEC ENDPOINT CLIENT VERSION 5.0 CREATING PROBLEM

    Broadcom Employee
    Posted Nov 25, 2009 11:23 PM

    may be you can create a different package again and see if that help.



  • 5.  RE: SYMANTEC ENDPOINT CLIENT VERSION 5.0 CREATING PROBLEM

    Posted Nov 26, 2009 02:42 AM
    Is this the same package that you have deployed to other clients as well?. If yes and the other clients are communicating then this particular machine definitely has a communication issue. Please refer the following document.

    Troubleshooting Client Communication with SEPM
    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2009082701244448

    http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2008091215040048


    The second option would be to install SEO as an unmanaged client and then try converting it to a managed client.

    The third option would be to create an MSI package and then try pushing it to the client and then check for its status.


  • 6.  RE: SYMANTEC ENDPOINT CLIENT VERSION 5.0 CREATING PROBLEM

    Posted Nov 26, 2009 03:18 AM
    Please run the sylink toogle and paste the logs

    https://www-secure.symantec.com/connect/downloads/sylink-toggle