Greetings,

I am moving my organizations SEPM's to new servers with new names and IPs.  I see a lot of articles on moving the servers but I have some questions about the DB's.  The old SEPMs will need to remain up for maybe a few months until most of the clients move over because we have several thousand clients - some of which are only on every couple months.

1. Do I need to create new instances?

2. Can I copy the old DB's to the new instances?

3. I will need the old SEPMs to remain up for some time untill all the clients move to the new SEPM but do I need to shut down the old DB?

4. Are there any other things I need to keep in mind?

Thanks

Case 1.

If you need to move clients reporting to current SEPM to another SEPM Server with different hostname and IP address of SEPM and DB both.

 Prepare new Server for SEPM and DB Install SQL freshly and Install a replication site of SEPM server which connects to new database and chanage management server list in currennt SEPM server on priority 2 add new SEPM server IP address and once all the clients will be having updated policy with priority 2 of newly created SEPM server you can shut down current SEPM server and change the management server list to use new SEPM server only on priority one.

Case 2.

If you need to move clients reporting to current SEPM to another SEPM Server with different hostname and IP address of SEPM only and need same DB.

Install new SEPM server server as an additional site and connect same DB with new SEPM server.and once configuration is done change the management server list in currennt SEPM server ,add new SEPM server IP address  on priority 2 and once all the clients will be having updated policy with priority 2 of newly created SEPM server you can shut down current SEPM server and change the management server list to use new SEPM server only on priority one.

Hi Jerry,

There are lots of other way by which you can fullfill your requirement, here I will suggest you simple method.

Perform the activity step by step,

1) Took all the backups, which includes DB backup, Server private key etc.

2) Stop the services of your current SEPM server.(Symantec endpoint protection manager and Symantec endpoint protect manager web services)

3) Install fresh SEPM on your new windows server with old host name and IP address along with same version which you are using currently on old setup.

4) Restore the backup of old server on your new windows server platform and shout down old windows server.

5) Once backup will restored successfully, your all the SEP clients will migrate to this server.

6) Now, edit in MSL (management server list) and add new server host-name and IP address as a first priority.

7) Wait for multiple heartbeat interval, once the policy pushed the clients will start getting offline.

8) Change IP address and hostname of your windows server.

9) Run management console wizard from start menu.

10) configure SEPM console with new IP and hostname.

11) Once reconfiguration done all the client will start pointing to this console this new IP and hostname.

12) Delete old server details from MSL.

Thanks

Thanks all.  I ended up creating a ticket for this.  I installed SEPM from backup to new server on the same site and pointed to the same DB the old SEPM pointed to.  Then I updated the MSL.  After waiting several weeks for the clients to communicate with the new server i deleted the old server from the site.  Everything seems to be working just fine.

Thank you.

Here's the Solution that worked for me.. 

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. (a new password for the new sem5 db is fine<- I didn't know the old one.)
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 <--this was already done in SEPM 14.2x
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)

Hi Sur,

In this case, if we need to use SEPM both 2 server,

It's copyright violation or not ?

My meaning we have cover license of all client, but need to separate SEPM to 2 servers.

Thanks in advance.

Hi Suwit,

Installation of SEPM does not require licensing, just the number of clients. So as long as you have 2 SEPM to migrate the clients across to the new server and then shut down/decommission the old server when you have finished, you will be OK.