Why do I need to replace the client-server communications file on the client computer?
|Article:HOWTO80762|||||Created: 2012-10-24|||||Updated: 2013-10-07|||||Article URL http://www.symantec.com/docs/HOWTO80762|
Symantec Endpoint Protection Manager connects to the client with a communications file called Sylink.xml. The Sylink.xml file includes the communication settings such as the IP address of the management server and the heartbeat interval. After you install a client installation package on to the client computers, the client and the server automatically communicate.
Normally you do not need to replace the Sylink.xml file. However, you may need to replace the existing Sylink.xml file on the client computer in the following situations:
The client and the server do not communicate. If the clients have lost the communication with the management server, you must replace the old Sylink.xml file with a new file.
You want to convert an unmanaged client to a managed client. If a user installs a client from the product disc, the client is unmanaged and does not communicate with the management server. You can also reinstall the client software on the computer as a managed computer.
You want to manage a previously orphaned client. For example, if the hard drive that the management server is installed on gets corrupted, you must reinstall the management server. You can update the Sylink.xml file to re-establish communication with all your orphaned clients.
You want to move a large number of clients from multiple groups to a single group. For example, you might want to move the client computers in a remote group and a laptop group to a test group. Typically, you need to move the client computers one group at a time.
To install a Security Virtual Appliance in a VMware vShield environment. To install a Security Virtual Appliance, you must export the communications file manually.
Article URL http://www.symantec.com/docs/HOWTO80762