Video Screencast Help

All my endpoint client not getting update from the endpoint manager

Created: 29 Oct 2012 | 12 comments

After the long weekend, all my client getting defination out of date error. I am on Symantec endpoint protection manager 11. Pls help T_T

Comments 12 CommentsJump to latest comment

pete_4u2002's picture

is SEPM updated?

if not can you try updating SEPM using JDB ?

How to update definitions for Symantec Endpoint Protection Manager using a JDB file

http://symantec.com/docs/TECH102607

 

if the SEPM is updated, can you check the communication

http://www.symantec.com/docs/TECH95789

NHTech's picture

Hi Pete,

Thank for the reply.

I can see the defination for the manager is updated.

I can only see the client on the client list. It just that no matter how i try to update the policy on the client, it won't get updated...

Nagesh Singh's picture

Hi NHTech,

 

if you have GUP server then check GUP server status.

https://www-secure.symantec.com/connect/forums/how-work-gup

If the all client directly taking definition from SEP then check communication between client and SEPM server.

Open cmd->telnet SEPM sever IP address 8014(default port for SEPM server communication)

Check whether you are able to telnet or not and if not then communicate with your network team

and open the port form SEPM communication.

http://www.symantec.com/business/support/index?page=content&id=TECH96419&profileURL=https%3A%2F%2Fsymaccount-profile.symantec.com%2FSSO%2Findex.jsp%3FssoID%3D1351506038169dZHzkfaFebWsFx6k5sCseo21Sax9Cd0a4zUIR

 

 

Thanks & Regards,

Nagesh Singh

 

Chetan Savade's picture

Hi,

Those machines were shut down during weekend days?

Total how many clients do you have in the network?

Total how many clients are affected with mentioned problem?

Have you checked the policy number?

Chetan Savade
Technical Support Engineer, Endpoint Security
Enterprise Technical Support
CCNA | CCNP | MCSE | SCTS |

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<

Mithun Sanghavi's picture

Hello,

Are all the clients facing this issue??

Could you check 1 of the client machine (which is not updated)?

What is the date and revision number you see on the client machine present?

Did you restarting the client machine / server machine and check if that helps??

Secondly, are these clients taking updates from GUP / LUA / SEPM?

Could you pull and upload the log.liveupdate and sylink.log from the client machine to us?

 

You may like to check this Article:

Managing SEPM & SEP after vacation

https://www-secure.symantec.com/connect/articles/managing-sepm-sep-after-vacation

Hope that helps!!

Mithun Sanghavi
Senior Consultant
MIM | MCSA | MCTS | STS | SSE | SSE+ | ITIL v3

Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

pete_4u2002's picture

if teh client is communicating ( green dot) then it should get the updates, can you check troubleshooting communication link and check if it helps.

pass on sylink log

.Brian's picture

What is your heartbeat set to?

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

Riya31's picture

Hi ,

Please upload scm-server-0.log from SEPM and sylink logs from one of client.

NHTech's picture

I manage to solve the connection program by the step below tru this link

 

Right click on the group name in SEPM and export the communication settings. This will also create a sylink file. Import this file on the client by the following method:
1) Client GUI
2) Help and Support - Troubleshooting
3) Import tab under Communication Settings. (The tab might throw up an error stating the option is not for Managed clients. (This can be taken care of by making the client self managed by using the sylink.xml from the installer cd.)
4) After the import, restart the client service once.

PS : Do not use the Sylink Drop.

But another problem arise,

It seem that client's defination not updated regularly. I have to manually do the update by right click the client then it will get the latest defination. Any expert able to help with this?

 

NHTech's picture

scm-server-0.log for my sepm:

2012-10-30 17:07:04.991 SEVERE: ================== Server Environment ===================
2012-10-30 17:07:04.991 SEVERE: os.name = Windows 2003
2012-10-30 17:07:04.991 SEVERE: os.version = 5.2
2012-10-30 17:07:04.991 SEVERE: os.arch = x86
2012-10-30 17:07:04.991 SEVERE: java.version = 1.6.0_14
2012-10-30 17:07:04.991 SEVERE: java.vendor = Sun Microsystems Inc.
2012-10-30 17:07:04.991 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
2012-10-30 17:07:04.991 SEVERE: java.vm.version = 14.0-b16
2012-10-30 17:07:04.991 SEVERE: java.home = E:\Program Files\Symantec\Symantec Endpoint Protection Manager\jdk\jre
2012-10-30 17:07:04.991 SEVERE: catalina.home = E:\Program Files\Symantec\Symantec Endpoint Protection Manager\tomcat
2012-10-30 17:07:04.991 SEVERE: java.user = null
2012-10-30 17:07:04.991 SEVERE: user.language = en
2012-10-30 17:07:04.991 SEVERE: user.country = US
2012-10-30 17:07:04.991 SEVERE: scm.server.version = 11.0.5002.333
2012-10-30 17:07:07.462 SEVERE: ================== StartClientTransport ===================
2012-10-30 17:07:07.706 SEVERE: Schedule is started!
2012-10-31 00:00:03.423 SEVERE: Unknown Exception
java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
    at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
    at java.net.Socket.connect(Socket.java:519)
    at java.net.Socket.connect(Socket.java:469)
    at sun.net.NetworkClient.doConnect(NetworkClient.java:163)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:394)
    at sun.net.www.http.HttpClient.openServer(HttpClient.java:529)
    at sun.net.www.protocol.https.HttpsClient.<init>(HttpsClient.java:272)
    at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:329)
    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:172)
    at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:793)
    at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:158)
    at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1041)
    at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:373)
    at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:318)
    at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:302)
    at com.sygate.scm.server.replication.RemotePartnerCommunicator.login(RemotePartnerCommunicator.java:107)
    at com.sygate.scm.server.replication.RemotePartner.login(RemotePartner.java:93)
    at com.sygate.scm.server.replication.ReplicationTask.initialize(ReplicationTask.java:699)
    at com.sygate.scm.server.replication.ReplicationTask.replicate(ReplicationTask.java:317)
    at com.sygate.scm.server.replication.ReplicationTask.run(ReplicationTask.java:276)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)
com.sygate.scm.common.communicate.CommunicationException: Failed to connect to the server.

Make sure that the server is running and your session has not timed out.
If you can reach the server but cannot log on, make sure that you provided the correct parameters.
If you are experiencing network issues, contact your system administrator. ErrorCode: 0x80020000
    at com.sygate.scm.common.communicate.Communicator.sendRequest(Communicator.java:319)
    at com.sygate.scm.server.replication.RemotePartnerCommunicator.login(RemotePartnerCommunicator.java:107)
    at com.sygate.scm.server.replication.RemotePartner.login(RemotePartner.java:93)
    at com.sygate.scm.server.replication.ReplicationTask.initialize(ReplicationTask.java:699)
    at com.sygate.scm.server.replication.ReplicationTask.replicate(ReplicationTask.java:317)
    at com.sygate.scm.server.replication.ReplicationTask.run(ReplicationTask.java:276)
    at java.util.TimerThread.mainLoop(Timer.java:512)
    at java.util.TimerThread.run(Timer.java:462)
 

I can't seem to find my sylink logs on the client.