This article describes how to change sylink.xml, the communication settings file for Symantec Endpoint Protection (SEP) 12.1, so clients can report to a new Symantec Endpoint Protection Manager (SEPM).
These steps re-establish communications when SEP clients are not communicating with the management server.
First, export the sylink.xml file for the target client group:
1. Open the Symantec Endpoint Protection Manager Console.
2. Go to the Clients page.
3. Right-click the desired group (e.g. Default group) and choose Export communications settings.
4. Click Browse, and choose a convenient location to save the file.
5. Rename the file to sylink.xml.
6. Click Save.
Once you have the new sylink.xml file, there are multiple methods to apply it to your clients.
Use the Communication Update Package Deployment from the Symantec Endpoint Protection Manager 12.1 RU2 or newer.
Import the sylink.xml within the client by going to Help > Troubleshooting > Click on Import... under Communication Settings.
Manually replace the sylink.xml file. You must disable Tamper Protection to do so. This can be done on the client by going to Change Settings > Click Configure Settings under Client Management > Tamper Protection (Tab) > Uncheck the box that says Protect Symantec security software from being tampered with or shut down.
Once tamper protection is disabled:
- Stop the SMC service by going to Start > Run > type in > smc -stop.
- Once the service is stopped copy the sylink.xml file from the new SEPM and on the client side put that sylink.xml file under following path:
- for Windows XP and 2003: C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Config
- for Windows Vista, 7, 2008 and 2012: C:\ProgramData\Symantec\Symantec Endpoint Protection\CurrentVersion\Data\Config
- Replace the existing file, then restart the SMC service with Start > Run > smc -start
All Windows Environments using SEP 12.1
Imported Document Id