How do I replace the client-server communications file on the client computer?
When should I replace the client-server communications file on the client computer?
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 installation file, 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 on the orphaned clients to re-establish communication with them.
- 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.
How do I replace the client-server communications file on the client computer?
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 installation file. 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. 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.Steps for exporting and importing the communications file displays the process for exporting and importing the Sylink.xml file into the client computer.
Step | Description |
|---|---|
Step 1: Export a file that includes all the communication settings for the group that you want the client to be in. | The default file name is group name _sylink.xml. |
Step 2: Deploy the file to the client computer. | You can either save the file to a network location or send it to an individual user on the client computer. |
Step 3: Import the file on the client computer. | Either you or the user can import the file on the client computer. Unmanaged clients are not password-protected, so you do not need a password on the client. However, if you try to import a file into a managed client that is password-protected, then you must enter a password. The password is the same one that is used to import or export a policy. You do not need to restart the client computer. |
Step 4: Verify client and server communication on the client. | The client immediately connects to the management server. The management server places the client in the group that is specified in the communication file. The client is updated with the group's policies and settings. After the client and the management server communicate, the notification area icon with the green dot appears in the client computer's taskbar. |