From 11 to 12
Updated: 18 Aug 2011 | 10 comments
This issue has been solved. See solution.
We are looking at upgrading from Endpoint Manager 11 to 12 and, at the same time, moving from a 32-bit server to a 64-bit. Will there be any issues migrating users in this scenario? Any other migration help/information you can provide would be much appreciated.
Discussion Filed Under:
Comments
Upgrading and migrating to
Upgrading and migrating to Symantec Endpoint Protection 12.1
http://www.symantec.com/business/support/index?pag...
Overview of how to move the Symantec Endpoint Protection Manager from one machine to another
http://www.symantec.com/business/support/index?pag...
Endpoint Knowledge Base
Security Best Practices
SEP 11.x to SEP 12.1 Upgrade
SEP 11.x to SEP 12.1 Upgrade process graphical overview
https://www-secure.symantec.com/connect/articles/sep-11x-sep-121-upgrade-process-graphical-overview
Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)
favor
Hi jasongsrn, please update us on any development. I'm personally interested in how it will go.
“Your most unhappy customers are your greatest source of learning.”
Plan of Action.
Hello,
In your case, There would be 2 cases,
Situation 1) Move the SEP 11 to the Latest version of 12.1 first.
Then, take a Backup of the same and Migrate the Server from 32 bit to 64 bit and
then Restore the SEPM.
Situation 2) Take a Backup of the SEP 11 and
Migrate the Server from 32 bit to 64 bit and
then Restore the SEPM. Once Restored, Finally Move the SEP 11 to the Latest version of 12.1.
Articles which may help:
Mithun Sanghavi
Symantec Technical Support Engineer, SEP
MIM | MCSA | SCTS | ITIL v3
Follow me on Twitter: @mithun_sanghavi
Don't forget to mark your thread as 'SOLVED' with the answer that best helped yo
my plan for this
I am going to be doing the same type migration. I am lucky in that my SEPM machines are VM based so here is what I have proposed. Also my SQL servers are on seperate boxes.
1. Do and in place upgrade of the 2003 32 bit SEPM consoles to 12.1.
2. Bring up 2008R2 servers install SEPM and and point them into the existing environment
3. Drop out the 2003 32 bit servers and reclain their space in my VM environment.
I think this will work anyone from Symantec have any comments on this idea on if it is a good plan
Good plan
Hello,
I would say a Good plan.
However, make sure that the new 2008 R2 has the same IP address and same host name.
Incase, not then check the article below:
Overview of how to move the Symantec Endpoint Protection Manager from one machine to another
http://www.symantec.com/docs/TECH148555
Mithun Sanghavi
Symantec Technical Support Engineer, SEP
MIM | MCSA | SCTS | ITIL v3
Follow me on Twitter: @mithun_sanghavi
Don't forget to mark your thread as 'SOLVED' with the answer that best helped yo
Could I rename and IP the new server
Could I rename and IP the new server to the old servers name after the old server has been decommissioned? My idea was to allow replication to pull in all the origional data.
Or you could simply edit your
Or you could simply edit your Management Server List in the SEPM Console to point clients at the new servers. After a reasonable amount of time to ensure all clients have the updated policy (and are talking to the new servers) you could drop the old SEPM servers. This makes the name and IP address irevelant.
Jon
I think I'd follow jbonner's
I think I'd follow jbonner's suggestion and make good use of the management server list. If you're going to have both servers up at the same time, I think it'd be much more risky to rename and re-IP a server that's already running the SEPM, especially since you've got plenty of time to just redirect all clients to start talking to the new one while the old one is online.
I haven't checked this one
I haven't checked this one yet. We're also planning on migrating from 1 server containing the db to 2 servers each with db for replication. And our plan is to replicate the SEPM with db to a new server. Bring the old one down. And then setup another server with db with replication. And on top of that, we're planning on adding another 2 for load balancing.
“Your most unhappy customers are your greatest source of learning.”
Would you like to reply?
Login or Register to post your comment.