In some instances, it may be necessary to migrate existing Symantec Endpoint Encryption version 11.x clients from one Management Server to another. This article discusses the process to complete this migration. This process will remain the same whether keeping the existing SQL Database or creating a new one.
Migration of Symantec Endpoint Encryption Clients may be done while the drive is still encrypted.
Note: This article assumes that the new Symantec Endpoint Encryption Management Server has been installed and configured.
Note: Symantec Endpoint Encryption version 11.1.0 and above have a "Change Web Access" server command. Please refer to the Policy Administrator Guide for instructions on using this command.
Symantec Endpoint Encryption Windows Clients (Versions 11.0.0 through 11.0.1 MP1):
1. From the new Symantec Endpoint Encryption Manager, create a new Management Agent Client with updated communication settings.
2. From the client machine, open Command Prompt as Administrator and run the following command to upgrade the Management Agent Client. (replace <path to .msi> with the full path to the install file)
Scenario 1: (PGP to SEE)
227509 - Migrating from Symantec Encryption Desktop to Symantec Endpoint Encryption (Drive Encryption components)
Scenario 2: 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 3: 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 4: Moving from one SEE database to a completely different SEE database.
163292 - Migrating / moving a SEE client from one SEE environment to another (Symantec Endpoint Encryption)
178631 - How to migrate Symantec Endpoint Encryption version 11 Clients from one Management Server to another