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
Article Type
How To


Subject


Exporting the client-server communications file (Sylink.xml) manually

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:

See Why do I need to replace the client-server communications file on the client computer?.

If you need to update client-server communications for a large number of clients, deploy the Communication Update Package instead of using this method.

See Restoring client-server communications with Communication Update Package Deployment.

To export the client-server communications file manually

  1. In the console, click Clients.

  2. Under Clients, select the group in which you want the client to appear.

  3. Right-click the group, and then click Export Communication Settings.

  4. In the Export Communication Settings for group name dialog box, click Browse.

  5. In the Select Export File dialog box, locate the folder to where you want to export the .xml file, and then click OK.

  6. 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.

    Note:

    Computer mode and user mode apply only to Windows client computers.

  7. Click Export.

    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.

See Importing client-server communication settings into the Windows client.


Legacy ID



v73083950_v81626096


Article URL http://www.symantec.com/docs/HOWTO81111


Terms of use for this information are found in Legal Notices