Exporting the client-server communications file manually
| Article:HOWTO81111 | | | Created: 2012-10-24 | | | Updated: 2013-01-30 | | | Article URL http://www.symantec.com/docs/HOWTO81111 |
If the client and server do not communicate, you may need to reinstall 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 are:
To convert an unmanaged client into a managed client.
To reconnect a previously orphaned client to the management server.
See Disabling or enabling secure communications between the server and the client.
To install a Security Virtual Appliance in a VMware vShield environment.
See What do I need to do to install a Security Virtual Appliance?.
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, redeploy the client installation package instead of using this method.
See Restoring client-server communications with Communication Update Package Deployment.
To export the client-server communications file manually
In the console, click Clients.
Under View 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.
In the Export Communication Settings for group name dialog box, select one of the following options:
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 client.
|
|
Legacy ID
v73083950_v81626096
Article URL http://www.symantec.com/docs/HOWTO81111
Terms of use for this information are found in Legal Notices
Thank you.