This article describes how to prevent disruptions with Symantec Endpoint Protection (SEP) clients when moving Symantec Endpoint Protection Manager (SEPM) to another server. These steps also help prevent the loss of client policies, group memberships and historical reporting data.
The method used to replace the SEPM will vary depending on whether the SEPM is a member of a site using a Microsoft SQL Server database, or an embedded database site.
For embedded databases
Follow the disaster recovery steps best practices for your SEPM version. Make sure you gather the database backup and recovery file(s) from your existing manager, and restore the database and recovery files to the new SEPM.
- Disaster recovery best practices for Endpoint Protection 12.1
- Disaster recovery best practices for Endpoint Protection 11
For Microsoft SQL server databases
- Gather the recovery file from the existing manager. For more information, read Contents of the Endpoint Protection Manager disaster recovery file.
- Decommission the existing manager, making sure it is no longer able to connect to the Microsoft SQL server hosting the SEPM database.
- Ensure the new manager has the same hostname as the existing manager.
Note: If desired, configure the new manager with the same IP address as the existing manager.
- Install the SEPM to the new manager making sure the match the version of SEPM to the existing server.
- Use the following step In the Management Server Configuration Wizard (MSCW):
- On the Welcome screen, select Install an additional management server to an existing Site.
- Check use a recovery file to restore communication with previously deployed clients.
- Browse for the recovery file you exported from the existing manager in step 1 of this process. and click Next.
- Ensure the name in the Server name field matches what was entered for the existing server exactly, including all capitalization and punctuation marks.
- Click Next.
- Follow the rest of the prompts in the MSCW, providing the correct Microsoft SQL server configuration and authentication information, allow the MSCW to update the SEPM database.