How do I replace the client-server communications file on the client computer?
|Article:HOWTO81460|||||Created: 2012-10-25|||||Updated: 2013-08-20|||||Article URL http://www.symantec.com/docs/HOWTO81460|
If you need to replace the client-server communications file (Sylink.xml) on the client computer, you can use the following methods:
Create a new client installation package and deploy it on the client computers. Use this method if manually importing the Sylink.xml on large environment is physically not possible and requires administrative access.
Write a script that runs the SylinkDrop tool, which is located in the /Tools folder of the Tools product disc. Symantec recommends this method for a large number of clients. You should also use the SylinkDrop tool if you use a software management tool to download the client software to computers. The advantage of the software management tool is that it downloads the Sylink.xml file as soon as the end user turns on the client computer. In comparison, the client installation package downloads the new Sylink.xml file only after the client computer connects to the management server.
Export the Sylink.xml file to the client computer and import it on the client computer manually. Symantec recommends this method if you want to use a software management tool like Altiris. With a software management tool, the job is queued up and completed whenever the users turn on their computer. With the other methods, the client computer must be online.
Table: Steps for exporting and importing the communications file displays the process for exporting and importing the Sylink.xml file into the client computer.
Table: Steps for exporting and importing the communications file
Article URL http://www.symantec.com/docs/HOWTO81460