Video Screencast Help

Is there a way to upate the sylink.xml file to PC's that report to the old server.

Created: 25 Jan 2013 | 9 comments

I know there is a sylink dropper, which I have used, and I know I can use the communication setting options in the latest version. The issue is, I ONLY want to replace the Sylink file from the PC's that report to that old server. The communication setting option is finding ALL PC's in the subnet.

Comments 9 CommentsJump to latest comment

.Brian's picture

You can call support and get the Sylinkreplacer tool for 12.1. They will provide instructions on how to use it. You should be able to input a text file of only the PCs you want to replace it on.

If it is only a few PCs, sylinkdrop is easiest.

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.

Mithun Sanghavi's picture

Hello,

Yes, SylinkReplacer Utility version 12.1 is an option.

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

However, From the Symantec Endpoint Protection Manager 12.1 RU2 onwards, there is another way to replace sylink.xml, check the following items:

Restoring client-server communication using a client installation package

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

Symantec Endpoint Protection 12.1 RU2 and Client Communication reset

https://www-secure.symantec.com/connect/articles/sep-121-ru2-and-reset-client-communication

To get that SylinkReplacer version_12.1 tool you will have to call symantec or log a web case.

How to create a new case in MySymantec

http://www.symantec.com/business/support/index?page=content&id=TECH58873

Phone numbers to contact Tech Support:-

Regional Support Telephone Numbers:

  • United States: 800-342-0652 (407-357-7600 from outside the United States)
  • Australia: 1300 365510 (+61 2 8220 7111 from outside Australia)
  • United Kingdom: +44 (0) 870 606 6000

Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp

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.

SebastianZ's picture

Depending what SEP version are you running and how many clients you want to switch to another server.

- with low amount of clients you can simply export communications setting directly from sepm group to a sylink.xml file and the import it on the client GUI

- for more clients 12.1 RU2 offers the Communications Update Package Deployment which is executed from the Client Deployment Wizard and equals the push of mentioned sylink.xml to remote machine.

The Conquistador's picture

The communication update deployment is finding clients I do not want it to find, such as SAV clients. All I want is to replace my remaining SEP clients who reported to the old server, there has GOT to be a way to narrow this down.

.Brian's picture

Pull a list of all old clients and use sylink replacer. You can input the file and it will do it that way.

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.

SebastianZ's picture

To narrow it down even more you can use the mentioned Sylink replacer that will accept a text file with desire computers to change the communication settings for - only these machines then will be affected.

The Conquistador's picture

The thing is, I do not know which PC's are outdated since they are not reporting. I can just do the entire subnet, but that is overkill. The Sylink looks for EVERY IP I specify within the range. I just want the out of date ones.

.Brian's picture

It is overkill but it shouldn't hurt anything

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.