spacer
Support - Platinum Support
tab end BCS Web Site divider MySupport divider Log Out navbar end
navbar end home symantec alerting service security center knowledge base navbar end
spacer
BCS Knowledge Base

spacer
spacer

Rate This Document
1x3 spacer
1x1 spacer

print this documentDocument ID:2008101707165348
Last Modified:03/16/2010

Restoring communication to clients with a new Sylink.xml file

Situation:How to associate clients to a new Symantec Endpoint Protection Manager (SEPM) in the case of retiring an old one or a disaster, etc.?

Solution:MR3 or later:
First export the Sylink.xml from the group you want your clients to report to initially.
  1. Click the Clients tab in the SEPM and select the group you want. Right click on it and select Export Communication Settings.
  2. Click browse, select a convenient location and name the file "Sylink.xml".
  3. Click Export.
  4. Get the SylinkDrop.exe tool out of Tools\NoSupport\Sylinkdrop on CD2 of the SEP 11 install media set.
  5. Using your management software (Tivoli, SMS, Altiris, etc) you will script it to drop the SylinkDrop.exe and the Sylink.xml to C:\Sylink (or whatever directory you choose) and run the Sylinkdrop.exe.
Note: See the Sylinkdrop readme for argument info. You will use an argument list like: Sylinkdrop.exe -silent C:\Sylink\Sylink.xml

Pre-MR3:
Locate the folder containing the Sylink.xml file for the Temporary (Default) client group:
  1. In the Symantec Endpoint Protection console, click the Clients icon and Select the Temporary (Default) group
  2. Go to the 'Details' tab and note the first 4 Alpha-Numerals for the 'Policy Serial Number'
  3. On the computer that runs Symantec Endpoint Protection Manager, go to: "C:\Program Files\Symantec\Symantec Endpoint Protection Manager\data\outbox\agent\"
    You will see folders with 32-character alphanumeric names, each representing a client group.
  4. Find the folder corresponding to the first 4 unique Alpha-Numerals noted for the 'Policy Serial Number'.
  5. Copy the "Sylink.xml" file from that folder, to a convenient location.
  6. Get the SylinkDrop.exe tool out of Tools\NoSupport\Sylinkdrop on CD2 of the SEP 11 install media set.
  7. Using your management software (Tivoli, SMS, Altiris, etc) you will script it to drop the SylinkDrop.exe and the Sylink.xml to C:\Sylink (or whatever directory you choose) and run the Sylinkdrop.exe.
Note: See the Sylinkdrop readme for argument info. You will use an argument list like: Sylinkdrop.exe -silent C:\Sylink\Sylink.xml.
For networked applications the sylinkReplacer utility can be used by contacting support. This utility is also provided as a convience to doing the same thing manually.


Technical Information:Note: The following steps are included if you need to drop the Sylink.xml file manually

For non-English versions of Windows, you may find that either the SylinkDrop.exe is not available or does not work.

In these situations, you may do the following steps manually:

1. Stop the Symantec Management Client (smc.exe) service via Services.msc
i.e. Within Services.msc, right click Symantec Management Client, click Stop

OR

Execute C:\Program Files\Symantec\Symantec Endpoint Protection\smc.exe with the -stop switch
i.e. Start > Run > smc -stop

2. Ensure that you have the correct Sylink.xml that you want to apply (i.e. SEP client to be attached to correct group etc)
Copy the exported SyLink.xml into C:\Program Files\Symantec\Symantec Endpoint Protection\

Exported Sylink.xml can be completed within the SEPM console:
Clients > View clients
Highlight the group in which you require the Sylink.xml from
Right click, & click on "Export Communications Settings ... "

By default, the name of the xml file saved, is in the format of: My Company_Default Group_name of group_sylink.xml
After exporting this xml file, you'll need to rename this in the format sylink.xml, before dropping into SEP folder

It is good practice to always backup the original copy before hand, or to rename the present sylink.xml, before moving or copying over the exported one.

3. After new sylink.xml has been copied to the SEP folder, restart the smc service.

Either:
Start the Symantec Management Client (smc.exe) service via Services.msc
i.e. Within Services.msc, right click Symantec Management Client, click Start

OR

Execute C:\Program Files\Symantec\Symantec Endpoint Protection\smc.exe with the -start switch
i.e. Start > Run > smc -start

After a few minutes or so, you will see the SEP client now attached to the new group as stated within the sylink,xml file


References:How to change a Symantec Endpoint Protection client from unmanaged to managed in MR1 and MR2.
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007082009543848

SylinkDrop or SylinkReplacer fails to assign Symantec Endpoint Protection clients to a new Client Group
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2007120611043048

print this documentDocument ID:2008101707165348
Last Modified:03/16/2010


rate this document
Does this document answer your question?
Yes
No
Maybe, need to test
None of the above
Is this document well written and easy to use?
Submit specific suggestions to improve the quality of this document.


Product(s): Endpoint Protection 11
Operating Systems(s): Windows 2000 Professional, Windows 2000 Server/Advanced Server, Windows XP Professional Edition, Windows XP Tablet PC Edition, Windows Server 2003 Web/Standard/Enterprise/Datacenter Edition, Windows Vista, Windows XP Professional x64 Edition, Windows Server 2003 x64 Edition, Windows Vista x64 Edition, Windows Server 2008 DataCenter 64-bit, Windows Server 2008 DataCenter 32-bit, Windows Server 2008 Enterprise 64-bit, Windows Server 2008 Enterprise 32-bit, Windows Server 2008 Standard 64-bit, Windows Server 2008 Standard 32-bit, Windows Server 2008 Web Server 64-bit, Windows Server 2008 Web Server 32-bit
Date Created: 10/17/2008

  © 1995-2014 Symantec Corporation. All rights reserved. feedback | legal notices | privacy policy