In some scenarios, such as virtualizing physical hardware, it is necessary to migrate the Endpoint Encryption Management Server to a new system. Doing so can disrupt the communication between Endpoint Encryption clients and the server, so this article provides assistance on doing this without the need of updating all of the clients.
Before migrating the server, consider the configuration of the server, and current communication settings for your clients:
Ideally, if clients use an external load balancer or proxy to reach the Management Server, then a new server can have a different hostname and IP address, and the load balancer/proxy can point to the replacement server seamlessly.
If no Load Balancer etc. is being used, and moving to a new server is necessary, go through the following steps:
After the installation is complete, log in to the Symantec Endpoint Encryption Manager and verify that existing client data appears. Check the client communication URL to verify it responds, and make sure clients are able to communicate with the new server.
Scenario 1: Moving SEE Client from Old SEE Management Server to New SEE Management Server
163292 - Migrating from one SEE Management Server to another (Completely new SEE Database)
Scenario 2: (Moving from PGP client/sever to SEE client/server)
227509 - Migrating from Symantec Encryption Desktop to Symantec Endpoint Encryption (Drive Encryption components)
Scenario 3: Moving SEE Clients from the same database to another SEE Management Server with the same Database
154122 - How to Migrate Symantec Endpoint Encryption Management Console and all the clients from one Server to another Server, without moving the existing SQL Server
Scenario 4: Moving same SEE database from one DB instance to another
152340 - How to move the SEE-MS SQL database from one server/instance to another
Scenario 5: Update which hostname the SEE Clients use for communications (Keeping same database)
249333 - Changing Web Access for SEE Clients on Symantec Encryption Management Server