Endpoint Protection

Group,

Our SEPM 11.0 MR2 Server had a raid problem - which we're trying to fix - and has taken the server with it.

I have since installed a new replacement server. Is there a way to get the clients to point to the new server for updates? (Even when I try to push install from the new server, the existing clients don't seem to use it for updating).

This is leaving me with clients that are not updating.

Any thoughts/suggestions would be appreciated!

Hi,

If you have already installed SEPM on a new server, you can use the Sylinkreplacer tool to point all the clients to the new SEPM. You don't have to re-deploy SEP to any of the existing clients.

You can download the tool and also the PDF document that explains about how to the use the tool from here,

https://www-secure.symantec.com/connect/downloads/sylinkreplacer-tool-connecting-sep-clients-sepm

Let me know if this helps :-) 

Hi,

1./ Generate a new syslink.xml on the new SEPM server

2./Stop smc services on client via :

CMD --> smc -stop

3./ Replace the old sylink by the new in:
%program files/symantec/symantec end point protection/sylink.xml

4./ Start smc services on client via:

CMD --> start smc -start

Create the new pacakge uisng this

How to restore/retain client-server communication using custom installation settings without having to use the sylink drop tool.
 

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

This will solve 2 objective

1. Restore Client Commuincation
2. Upgrade the Clients

So by doing this the clients will upgrade as well start commuincating with new SEPM

Thank you for the tips. I'm currently using them to rebuild.