Moving SEPM from one server to another
Updated: 22 Oct 2010 | 11 comments
This issue has been solved. See solution.
Hello,
I'm trying to find some information on moving the Symantec Endpoint Management Console from one server to another.
Will this require installing SEPM on the new server and doing things like Syslink Replacement as well as importing policies, or is there a much more simpler way of migrating the console to another server?
Discussion Filed Under:
Comments
Follow the steps below to
Follow the steps below to move Symantec Endpoint Protection Manager from one server to another with a different IP address and Host name:
1. Install Symantec Endpoint Protection Manager on the new server
2. In the Management Server Configuration Wizard panel, check Install an additional site, and then click Next
3. In the Server Information panel, accept or change the default values for the following boxes, and then click Next
4. Installing and configuring Symantec Endpoint Protection Manager for replication
Server Name
Server Port
Server Data Folder
5. In the Site Information panel, accept or change the name in the Site Name box, and then click Next
6. In the Replication Information panel, type values in the following boxes:
Replication Server Name
(The Name or IP address of the old Symantec Endpoint Protection Manager)
Replication Server Port
(The default is 8443)
Administrator Name
(The Username used to log on to the old console)
Password
(The password used to log on to the old console.)
7. Click Next
8. In the Certificate Warning dialog box, click Yes
9. In the Database Server Choice panel, do one of the following, and then click Next
Check Embedded database, and complete the installation.
Check Microsoft SQL Server, and complete the installation.
Note
: While configuring the new server we can choose any of SQL or Embedded as this process is irrespective of the previous database type.
10. Log in to the new Symantec Endpoint Protection Manager (SEPM) and ensure that all the clients and policies are Migrated sucessfully
11. Click Policies
12. Click Policy Components
13. Click Management Server Lists
14. Click Add Management Server List
15. Click Add > Priority and a new Prioriry would get added named as Priority2
16. Add the Old server under Prority2 and add the new one under Prority1
17. After the sucessful Migration uninstall the old Symantec Endpoint Protection Manager (SEPM)
Check the below
Check the below article
Title: 'How do I move Symantec Endpoint Protection Manager from one server to another with a different IP address and host name?'
Web URL: http://service1.symantec.com/support/ent-security....
Thanks & Regards,
Mudit Kumar
Followed the instructions
Followed the instructions Mudit and others who had the same instructions and it seems to have worked. Thank you for this information.
DO NOT follow the
DO NOT follow the instructions provided by Jason as it's been proven to be problematic later down the road. We have also pulled the document with those instructions because of that reason.
It's better to use the database back-up and restore method:
Title: 'How to back up, restore, and/or move the Symantec Endpoint Protection Manager (SEPM) and embedded Database to another disk or system'
Document ID: 2007102607432048
> Web URL: http://service1.symantec.com/SUPPORT/ent-security....
Or the method Mudit linked will work as well.
Would part of the problem
Would part of the problem being that there is no way of knowing if it is communicating with the alternate server?
Umm... Okay.
If you consider that the procedure I posted was a copy and paste or just about from the Document Provided by Mudit Kumar...
Almost to the letter, yet you say not to use that method.
Than, like sheep following the sheppard, I get a negative vote and yet you guys give a positive vote on said document which has been removed. Laughable.
I don't recall that document
I don't recall that document having those instructions previously. The original document with those instructions was pulled as I recall. Regardless, we have found the procedure to cause problems and it's no longer reccommended. That's the bottom line.
Sorry to burst your Bubble
But the BOTTOM LINE IS:
He followed the article posted by Mudit, which exactly Denotes the procedure I put up and pasted as well as others, in which you state DO NOT FOLLOW and lo and behold. It is Solved.
I will give this one a try
I will give this one a try first to see how it goes.
HI
Move Symantec Endpoint Protection Manager from one server to another with a different IP address and Host name
Follow the steps below to move Symantec Endpoint Protection Manager from one server to another with a different IP address and Host name:
1. Install Symantec Endpoint Protection Manager on the new server
2. In the Management Server Configuration Wizard panel, check Install an additional site, and then click Next
3. In the Server Information panel, accept or change the default values for the following boxes, and then click Next
4. Installing and configuring Symantec Endpoint Protection Manager for replication
Server Name
Server Port
Server Data Folder
5. In the Site Information panel, accept or change the name in the Site Name box, and then click Next
6. In the Replication Information panel, type values in the following boxes:
Replication Server Name
(The Name or IP address of the old Symantec Endpoint Protection Manager)
Replication Server Port
(The default is 8443)
Administrator Name
(The Username used to log on to the old console)
Password
(The password used to log on to the old console.)
7. Click Next
8. In the Certificate Warning dialog box, click Yes
9. In the Database Server Choice panel, do one of the following, and then click Next
Check Embedded database, and complete the installation.
Check Microsoft SQL Server, and complete the installation.
Note: While configuring the new server we can choose any of SQL or Embedded as this process is irrespective of the previous database type.
10. Log in to the new Symantec Endpoint Protection Manager (SEPM) and ensure that all the clients and policies are Migrated sucessfully
11. Click Policies
12. Click Policy Components
13. Click Management Server Lists
14. Click Add Management Server List
15. Click Add > Priority and a new Priority would get added named as Priority2
16. Add the Old server under Prority2 and add the new one under Prority1
17. After the sucessful Migration uninstall the old Symantec Endpoint Protection Manager (SEPM)
If this Info helps to resolve the issue please Mark as Solution
Thanks
I think it's not necessary to
I think it's not necessary to create a replication or to import database (it's not anytime possible).
You could try:
- export your old SEPM Certificat and import in the new SEPM (after have backup the new SEPM certificate by security).
- In a copy of Management Server List Policy, define your new SEPM the adress on Priority 1 and old SEPM priority 2.
- Assign This Policy to a Test Group for validate.
- Normally you do waiting a little time if your SEPM is on PUSH or the Heartbeat if you PULL.
- When you are finish your tests, you could assign this policy to all group and Enjoy.
Would you like to reply?
Login or Register to post your comment.