Converting an unmanaged client to a managed client
If a user installed a client from the product disc, the client is unmanaged and does not communicate with the management server.
You can convert an unmanaged client to a managed client by using either of the following methods:
Install the client as a managed computer.
This method converts an unmanaged client to a managed client by reinstalling the client software.
See Preparing for client installation.
Import the server communications settings.
This method converts an unmanaged client to a managed client by importing the server communications settings.
If you import the server communications settings, you follow this process:
You 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.
You 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.
On the client computer, you or the user imports the file.
You do not need to restart the client computer.
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.
Unmanaged clients are not password-protected, so the user does not need a password on the client. However, if the user tries to import a file onto a managed client that is password-protected, then the user must enter a password. The password is the same one that is used to import or export a policy.
See Password-protecting the client.
You may also need to redirect a managed client to another server.
See Recovering client communication settings by using the SylinkDrop tool.
See Assigning a management server list to a group and location.
To export the communications settings from the server
In the console, click .
Under View Clients, select the group in which you want the client to appear.
Right-click the group, and then click .
In the Export Communication Settings for group name dialog box, click .
In the Select Export File dialog box, locate the folder to where you want to export the .xml file, and then click .
In the Export Communication Settings for group name dialog box, select one of the following options:
To apply the policies from the group from which the computer is a member, click .
To apply the policies from the group from which the user is a member, click .
If the file name already exists, click to overwrite it or 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.
To import the server communications settings into the client
Open Symantec Endpoint Protection on the computer that you want to convert to a managed client.
In the upper right, click , and then click .
In the Troubleshooting dialog box, under Communication Settings, click .
In the Import Communication Settings dialog box, locate the group name_sylink.xml file, and then click .
Click to close the Troubleshooting dialog box.
After you import the communications file, and the client and the management server communicate, the notification area icon with appears in the computer's taskbar. The green dot indicates that the client and the management server are in communication with each other.