Video Screencast Help

Move SEPM Server

Created: 29 Jan 2013 • Updated: 04 Feb 2013 | 10 comments
This issue has been solved. See solution.

I have come across a scenario in my work place where the subnet that my SEPM is located will be shutdown and I will therefore need to move the SEPM to a different subnet.  We only have 1 SEPM are currently running SEP 11.0.5002.333 throughout the company and don't really have any plans to migrate that or add additional SEPM's.  I'm not sure what is the best way to get the 500 clients that we have associated with the new IP address of the SEPM.  I've been reading up on the sylinkdrop and sylinkreplacer and both seem to be feasible in helping complete the task.  Has anyone come accross this type of scenario before?  Will the sylinkdrop and sylinkreplacer be my best or only options?  I've never had to use either one of these utilities before.  Will it be a time consuming process to get all 500 clients associated with the new IP of the SEPM?  Any information would be great.

Comments 10 CommentsJump to latest comment

Brɨan's picture

Check this KB article as it has 3 different solutions

How to migrate Symantec Endpoint Protection Manager(SEPM)from one machine to another machine

Article:TECH148553  |  Created: 2011-01-20  |  Updated: 2012-07-21  |  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.

Ashish-Sharma's picture

How to move Symantec Endpoint Protection Manager from one machine to another

Article:TECH104389 | Created: 2008-01-11 | Updated: 2011-07-22 | Article URL

Check this artical also

Thanks In Advance

Ashish Sharma

SebastianZ's picture

Information about the sylink drop and sylink replacer tools you have asked:

SylinkDrop or SylinkReplacer fails to assign Symantec Endpoint Protection clients to a new Client Group

Using the "SylinkReplacer" Utility


Recovering client communication settings by using the SylinkDrop tool


MASH1's picture

Hi Ehans,

Can you try the below steps and check if it works.

Try it in your test environment first or a test group .
Add a NIC card to current SEPM and give it the new IP address.
Change the MSL and have the New NIC on Priority 1 list. Old IP and the hostname will be at priority 2.
Check if the new clients machines get the new MSL .
Confirm if they are reporting to the new IP address which is on priority 1. 
If this works then you dont need to use sylink replacer.
As the SAME server private key and database password will be used I think it would work. 


MASH1's picture
Or else try the below steps. 
I always recommend to try the steps in test environment first.
1) Change the MSL and add the new IP address on Priority 1.
2) change the IP address of SEPM and run management server configuration wizard using new IP address.
Check if the clients are reporting.


consoleadmin's picture

Agree with all of the above comments and strongly agree with MASH. Try the above step in test enviornment before implement in production.


SMLatCST's picture

"Thumbs Up" to MASH1 above.

There should be no requirement to use any of the Sylink tools, as you're not changing server, merely changing the IP address of your SEPM.  The easiest way of accomplishing this is to change the Management Server list as mentioned above.

Your options are to either add the new IP address into the list before the move, as the same priority as the current IP address.  When the move happens, clients will just find they cannot connect to the old IP and go through the list of addresses until they find one that works.  Or use a list that has only the hostname/fqdn of your SEPM, then when the move happens, they'll resolve the new IP via DNS and connect.

Eitherway, please see below for articles on how to do this:

Ambesh_444's picture


Move SEPM to new server, new hostname, new IP. Maintain all data, logs, etc

Please try with this,

Thank& Regards,


"Your satisfaction is very important to us. If you find above information helpful or it has resolved your issue. Please don't forget to mark the thread as solved."

Ambesh_444's picture


Please mark thread as a solution which helps you best.

Thank& Regards,


"Your satisfaction is very important to us. If you find above information helpful or it has resolved your issue. Please don't forget to mark the thread as solved."

EHans's picture

It only lets me mark one the responses as the solution but I must start by thanking MASH as this led me in the right direction.  The article posted by SMLatCST worked perfectly.