Video Screencast Help

Upgrading Symantec endpoint manager to another Server

Created: 22 May 2012 • Updated: 25 May 2012 | 7 comments
This issue has been solved. See solution.

I am currently running SEPM 11.x on a sever2000 platform (32bit) and 11.x clients (around 100) on a mixture of OS's xp, vista, win 7 (32bit and 64bit).  I am wanting to upgrade the manager to 12.x onto server2008 r2 64bit and all the clients updating to 12.x.

I want to know what is the best way to do this.  Do I install the new SEPM 12.x on the new server then migrate the policies, clients, settings etc... across to the new manager or migrate the current SEPM onto the new server then upgrade to 12.x

I may be putting this on a virtual server also so need to know if this affects anything also

Any advice, guides and/or best practices would be greatlty appricieated as im not sure how to start this project and what is the best way to do it.


Comments 7 CommentsJump to latest comment

pete_4u2002's picture

you can take the backup of SEPM 11 and restore the certs and DB on new server, then upgrade the server to newwer version, then autoupgrade the clients.

How to move SEPM machine from one system to another

SOLUTION's picture

Thanks for the Quick response Pete.

Would there be any problems with the old SEPM being 32bit to 64bit SEPM?

Also would it make a difference if i put the SEPMon a virtual server?

pete_4u2002's picture

there will not be. On SEPM being on virtual server, is the VM machine have enough resource, then it should not be any problem.

what kind of database is used? if SQL, better that be on the physical machine.

how many clients are reporting to SEPM? you set to pull mode as it will reduce the load from SEPM.'s picture

The virtual server will have plenty of resources so this will not cause any problems.

The database isembeded and there are around 100-120 clients.

Think it set to pull mode but where can i check to make sure

John Q.'s picture

You can change communication mode by following this article:

As per Best Practices (, and the few number of clients you have, you might leave communication to PUSH, especially if your SEPM will have high-level of resources (as you mentioned).

Please remember to mark the proper comment as SOLUTION:
 - to identify threads that do not require further assistance
 - to let other visitors know how to fix such issue

Mithun Sanghavi's picture


In your case, Since you are running the Server 2000 platform and SEP 12.1 does not support it. It would be difficult for you to migrate SEPM 11.x to SEPM 12.1 first.

Check this Article:

About Support for Microsoft Windows 2000 in Symantec Endpoint Protection 12.1

So, for you the Plan of Action would be:

1) Move the SEPM 11.x from your old windows 2000 server to the Latest server Windows 2008 server

Check these Articles:

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

Symantec Endpoint Protection 11.x: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

2) Upon Successful moving the SEPM to the Windows 2008 Server, Migrate the SEPM 11.x to SEPM 12.1.

Upgrading or migrating to Symantec Endpoint Protection 12.1 

Hope that helps!!

Mithun Sanghavi
Associate Security Architect


Don't forget to mark your thread as 'SOLVED' with the answer that best helped you.

Chetan Savade's picture


You have to follow upgrade path as SEP 11.x--> SEP 12.1 RU1 --> SEP 12.1 RU1 MP1

Are you using custom policies or default policies? Have specifc setting which you don't wish to loose?

I would suggest to go with fresh install of SEP 12.1 RU1 MP1. 

If don't want to go with fresh install, there are two methods to move Symantec Endpoint Protection Manager (SEPM) from one machine to another:

Method 1: if the SEPM server keeps the same IP and host name, you can refer to "Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager"

Method 2: if the new SEPM server has a different IP and host name, there are two alternatives:

1. Use replication to install a new SEPM and keep the policy the same with old SEPM. See "How to move Symantec Endpoint Protection Manager from one machine to another"

2. Install a new SEPM, then use the Sylink file to establish communication between the new SEPM and the existing SEP client through sylink replacer tool.

Note : Sylink replacer tool is most commonly used option because it's easy to use.

Please go through following thread for more details:

Link for more information :

Chetan Savade
Sr.Technical Support Engineer, Endpoint Security
Enterprise Technical Support

Don't forget to mark your thread as 'SOLVED' with the answer that best helps you.<