Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

SEP Version 11.0.4202.75

  • 1.  SEP Version 11.0.4202.75

    Posted Jun 03, 2009 03:56 PM
    We recently upgraded to 11.0.4202.75 Endpoint Protection Manager and after the upgrade discovered that two clients who had previously been managed by SEP were no longer showing up as managed.  They still have Symantec Client installed on the client pc's, but neither one will show up as managed in SEP manager and have tried redeploying both through find unmanaged and through deployment wizard.  Have also tried status update directly from the client machines...no luck.  Able to ping both machines, otherwise fully connected to SBS 2003 server.

    One has a short SEP_INST.LOG  file and the other one has a very long SEP_INST.LOG  file.
    Policy Serial Numbers on these two clients are much older than those on the SEP Manager.
    Trial manual update from client, timed out.
    Tried opening the browser and was able to view the following page:  http://<management server name>:9090

    Need some help here...I can pass along a log file if needed.
    Thanks.
    Bonnie


  • 2.  RE: SEP Version 11.0.4202.75

    Posted Jun 03, 2009 04:02 PM
     well if the clients are installed then no need of SEP_INSt log.
    The first thing you can try is Replace sylink.xml.
    If that doesn't help.
    Go to ADMIN - INstall Packages- Client install Settins -ADD- selct the last option "remove previous logs and reset-client server communication"
    Give it a name click OK
    Go back to Find Unamanged computers
    Search for these two computers ..once found check them.
    Scroll down client install settings you will find your new settings select that and -Start Installation.
    That should work if it was working earlier..


  • 3.  RE: SEP Version 11.0.4202.75

    Posted Jun 09, 2009 02:18 PM
    If replacing the sylink.xml file does not resolve the issue, then run the sylinkmonitor tool to gather the communication logs using the document below:
    https://www-secure.symantec.com/connect/articles/how-capture-sep-sepm-communication-logs-sylinkmonitor-mr3-onwards-troubleshooting-communica

    Also, please follow the documents below:

    Testing Communication from an Endpoint Protection client to the Endpoint Protection Manager
    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/a6b9dc2d869c89a58825737700642895?OpenDocument

    Symantec Endpoint Protection: Troubleshooting Client/Server Connectivity
    http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/16638b5449556ae3882574c200793618?OpenDocument

    Cheers,
    Aniket



  • 4.  RE: SEP Version 11.0.4202.75

    Posted Jun 09, 2009 02:49 PM
    You can also open the sylink.xml file and verify that the ip address and hostnames still match the Policy manager if you haven't done so already.


  • 5.  RE: SEP Version 11.0.4202.75

    Posted Jun 09, 2009 03:11 PM
    If it was a couple of hundred clients, then this would not be practical.  Try uninstalling the client, rebooting, renaming the C:\Program Files\Symantec folder, then reinstalling.


  • 6.  RE: SEP Version 11.0.4202.75

    Posted Jun 09, 2009 04:14 PM
    I am seeing the same problem on some of my Windows 2000 Pro systems after upgrading them to MR4 MP2.  They lose connectivity to the SEP servers and SMC.exe spikes at 99% on these systems.  Tried removing & reinstalling, running Cleanwipe, etc. 
    I'm about to open a support case.


  • 7.  RE: SEP Version 11.0.4202.75

    Posted Jun 09, 2009 09:12 PM
    Do either (or both) of them have either a single quote (') or a double quote (") character in the computer description?   (see My Computer, Properties, Computer Name).  I had a problem client a few weeks back which had somewhat similar symptoms ... although it would install correctly, it would not communicate with the server ... but removing the computer's description, rebooting, uninstalling and reinstalling the SEP client seemed to fix it.


  • 8.  RE: SEP Version 11.0.4202.75

    Posted Jun 10, 2009 01:08 AM
    Hi,

    I have the same problem (case opened for this problem). Computers who's upgraded on MR4 MP2 is viewed on manager "status offline" and the client don't updaqte definitions and smc.exe use 50% of cpu.

    When uninstall Mr4 MP2 and run cleanwipe and installer mr3 there is no problem. after i i try to upgrade on the same computer to mr4 mp2 by manager the computer as the same problem.

    Another issue what i see, when you upgrade from mr3 to mr4 mp2, some computers lose ip configuration (ipconfig /all is blank in command line) and tefeer2 driver have a problem.

    For the moment, i blocked the migration to mr4 mp2.

    I have sended logs of computers, log of sylink (there is an error http 468), logs of sep support tools....

    Have you any ideas for this problem ?


  • 9.  RE: SEP Version 11.0.4202.75

    Posted Jun 10, 2009 04:35 AM
    Bonnie
    I guess you have enough comments as solution to ressolve ur issue.
    Try the solutions and update us so that other member who is facing this problem will be able to fix it


  • 10.  RE: SEP Version 11.0.4202.75

    Posted Jun 10, 2009 05:57 AM
    NT


  • 11.  RE: SEP Version 11.0.4202.75

    Posted Jul 03, 2009 05:12 PM
    How are these clients connecting to the SEPM. We are seeing an issue that seems to be affecting computers that connect to the SEPM via a VPN client. More information can be found in the ongoing thread here:

    https://www-secure.symantec.com/connect/forums/smcexe-using-50-or-more-processor-while-vpned-office#comment-2662281

    If your clients are connecting via VPN then this could be the cause of the high CPU usage. If this is the case please post or PM me and I would like to get some further information from you to help solve this issue.

    Thanks
    Grant