Endpoint Protection

Is there a way to force a client to report to the server from the SP console/manager?

Right click on the SEP client and click Update Policy.

Do you mean the client is not communicating to sepm ?

1. Click the Clients tab in the SEPM and select the group you want. Right click on it and select Export Communication Settings.
2. Click browse, select a convenient location and name the file "Sylink.xml".
3. Click Export.
4. go to client machine
5. open sep client go to change settings tamper protection disable it if it is 12.1
6. once done go to help troubleshooting >export communication settings and point to xml file which is exported
7. once complete reboot the machine if required and check if it is reporting

for 11.0 go to start run type smc -stop

go to c:\progrfile\symantec\sep\look for sylink.xml delete it and copy the file which is exported

go to start run and type smc -start

make sure port 80 and 8014 is open on sepm machine either through windows firewall or any other firewall if you have any

Thanks for the feedback.  So I guess if the client is not even showing up in the Console, then there is no way for me to get it back unless I force it from the client side?

There is some threashold of when the clients disappear from the console if they haven't reported in so many days?  What is the number of days?

By default the number of days is 30 or 60

This setting is available in Admin Tab >servers>right click on the Local host and it comes up over there.

If the client does not still report in then you could try to replace the sylink.xml and then it should communicate, Please follow the procedure:-

1. Click the Clients tab in the SEPM and select the group you want. Right click on it and select Export Communication Settings.
2. Click browse, select a convenient location and name the file "Sylink.xml".
3. Click Export.
4. go to client machine
5. open sep client go to change settings tamper protection disable it if it is 12.1
6. once done go to help troubleshooting >export communication settings and point to xml file which is exported
7. once complete reboot the machine if required and check if it is reporting

for 11.0 go to start run type smc -stop

go to c:\progrfile\symantec\sep\look for sylink.xml delete it and copy the file which is exported

go to start run and type smc -start

If the Client enrty is showing up in the SEPM console.

You can try Right clicking on the client and select Run command on group >> Update content.

If this doesnot help then replacing the sylink will restore the communication.

Thanks all, I will have helpdesk go the client system and do updates policy.  Looks like this is my only option left.

don't move your enggineer for the client system. Try to update threw remotely.

Pls find the attach thread, it help you to replace the sylink file for the connectivity of client and server remotely

https://www-secure.symantec.com/connect/downloads/solution-doc-manage-unmanaged-system-sep-1106005

Hope it helpful to you.

Hi,

Sylink.xml file contains the communication settings of SEPM server to client so if you will go to replace this file at the respective path then your client will be surely communicate to SEPM server.

Have you tried my attach document??

@mm12345: I agree with sunnyc_1986@yahoo.co.in - Request for the Sylink Replacer tool from Symantec. This is not available in the SEP packages I've downloaded. Then, all you need is the sylink file which you already have if you've created a package from SEPM, and a text file with the list of clients you want to reconnect. File and Print Sharing must be enabled on the targets and you should run the app with Domain Admin rights.

you can also replace sylink.xml file manually as suggested by abnscbnklfoo