Video Screencast Help

HOW TO MIGRATE SYMANTEC with diffrent server

Created: 25 Feb 2013 | 5 comments

Hi all,

need your help.

i have a +/- 1000 active user in my company using SEP 11.0.6200, all user connected in one SEPM main server in HO using SEPM 11.0.6200.

now I have a new server using SEPM 12.2015.and i have a plan to migrate all user in old server to new server...the problem is our user locate is in diffrent Province....

ussualy we replace manualy the sylink.xml in every user.

my question......can i migrate the SEPM 11.6200 user into the new server 12.2015 with a single command ?

Thank's for a help

Rae Sinekti

Operating Systems:

Comments 5 CommentsJump to latest comment

ᗺrian's picture

12.1.2 has new a feature which allows you to deploy the sylink file from SEPM to clients. Check this KB article for the steps to do just that:

Restoring client-server communications with Communication Update Package Deployment

padding: 1px;padding-bottom: 3px ;font: 12px Arial; text-align: left;">Article:HOWTO81109 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 0px;font: 12px Arial; text-align: left;">Created: 2012-10-24 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 1px;font: 12px Arial; text-align: left;">Updated: 2013-01-30 padding: 1px;font: 12px Arial; text-align: left;"> |  padding: 1px;font: 12px Arial; text-align: left;">Article URL

Please click the "Mark as solution" link at bottom left on the post that best answers your question. This will benefit admins looking for a solution to the same problem.

ub40's picture

Hi,  Rae.

You can tray the following scenario :

1. Export communication parameters from new SEPM server and place this file on network share

2. Create batch file which does the following on the client computer :

- change current directory to Symantec Endpoint Protection client

- stopped Symantec management client ( smc -stop)

- removes files SyLink.xml, SyLink.bak and SyLinkEx.bak

- copy new sylink file from neywork share

- started Symantec management client (smc -start)

- repeat previous three step, because in first time symantec client make change in the new sylink.* files

3. This batch file must execute once on the client computer with start operation system

4. After the main bulk of client connect to new SEPM server you can update SEP client with installed packages