Exporting the client-server communications file (Sylink.xml) manually
|Article:HOWTO81111|||||Created: 2012-10-24|||||Updated: 2014-09-21|||||Article URL http://www.symantec.com/docs/HOWTO81111|
If the client and the server do not communicate, you may need to replace the Sylink.xml file on the client computer to restore communications. You can manually export the Sylink.xml file from Symantec Endpoint Protection Manager on a group basis.
The most common reasons for replacing the Sylink.xml on the client are:
To convert an unmanaged client into a managed client.
To reconnect a previously orphaned client to the management server.
To install a Security Virtual Appliance in a VMware vShield environment.
If you need to update client-server communications for a large number of clients, deploy the Communication Update Package instead of using this method.
To export the client-server communications file manually
In the console, click Clients.
Under Clients, select the group in which you want the client to appear.
Right-click the group, and then click Export Communication Settings.
In the Export Communication Settings for group name dialog box, click Browse.
In the Select Export File dialog box, locate the folder to where you want to export the .xml file, and then click OK.
Under Preferred Policy Mode, select one of the following options:
To apply the policies from the group from which the computer is a member, click Computer Mode.
To apply the policies from the group from which the user is a member, click User Mode.
Computer mode and user mode apply only to Windows client computers.
If the file name already exists, click OK to overwrite it or Cancel to save the file with a new file name.
To finish the conversion, you or a user must import the communications setting on the client computer.
Article URL http://www.symantec.com/docs/HOWTO81111