Video Screencast Help

Migrating/upgrating SEPM from 2008R2 to 2012

Created: 11 Jul 2013 • Updated: 11 Jul 2013 | 11 comments
This issue has been solved. See solution.

Hello everybody,

 

I have a virtual server under Win Srv 2008 R2 that running the Symantec Endpoint Manager 12.1.1.

 

You have purchase a new server with Win Srv 2012 and I will move the VM from the old server to the new one. In the same time, I need to realize the upgrade of the SEPM to the vers 12.1.2 to be compatible with Windows 8 and Win Srv 2012.

 

So I'm thinnking to create a new VM under Win Srv 2012 and made a fresh install of the SEPM. But I don't know if it's a good idea and how to migrate my old database to the new installation.

 

Can you tell me the main key to do this?

 

Thanks in advance.

 

Regards,

 

Jerome

Operating Systems:

Comments 11 CommentsJump to latest comment

.Brian's picture

Are you keeping the same name/IP address?

Make sure to use 12.1 RU3

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

Article:TECH104389  |  Created: 2008-01-11  |  Updated: 2011-07-22  |  Article URL http://www.symantec.com/docs/TECH104389

 

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.

Rafeeq's picture

Follow this docuemnt

Symantec Endpoint Protection 12.1: Best Practices for Disaster Recovery with the Symantec Endpoint Protection Manager

Jerome Duchene's picture

I plan to change the Server Name, but the IP can be the same. If needed, I can create a entry with the old name in my DNS server.

 

I have readed the article TECH104389, but the followed text trouble me

NOTE: The version installed to the new server must be the same version as on the old server. The new management console can be migrated to a newer version once the transition is complete.

.Brian's picture

For replication, both need to be on the same SEPM version in order for replication to work correctly.

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.

Jerome Duchene's picture

So in my case, as I want to upgrade the version, it's simple to conserve the same IP/hostname and use the disaster recovery procedure. Am I right?

.Brian's picture

Yes, if keeping same IP/name, than go with disaster recovery option.

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.

Rafeeq's picture

how many clients you have in your network? how many groups?

if they are less. You can install the new version, use the communication deployment wizard, to get clients to new sepm. then export policy from old to new.

http://www.symantec.com/business/support/index?page=content&id=TECH199124

 

 

to import a policy

http://www.symantec.com/business/support/index?page=content&id=TECH106486

Jerome Duchene's picture

Make sure to use 12.1 RU3

My current version is 12.1.1101.401 RU1 MP1.

 

Is-it a problem to do the upgrade through the disaster recovery procedure?

 

I have about 100 computers and server managed with SEPM and only 3-4 group.

Rafeeq's picture

12.1.3000 is the latest version so install that on your new server.

Disaster recovery needs same version coz of database.

Install 12.1.1101 same version. complete the disaster recovery

then upgrade the 12.1 to 12.3

or you can install the fresh new version. use the communciation setting deployment  and import policy

SOLUTION
Jerome Duchene's picture

Thanks.

 

I think that's the more simple solution for my case.

AjinBabu's picture

HI, 

Rafeeq's solution will help you to complete faster recovery, i would suggest to do that.

Regards

Ajin