compcas.blogg.se - Sepm symantec

Once verified that all the clients are reporting into the new SEPM, and have moved away from the old one, proceed to the next step.Stop the “Symantec Endpoint Protection Manager” and “Symantec Embedded Database” service on MACHINE_1 to verify whether all clients now report to the new SEPM on MACHINE_2.Add MACHINE_1 under Priority 2 and add MACHINE_2 under Priority 1, and assign this New Management Server List to all the groups.Click Add> Priority and a new Priority would get added named as “Priority2”.Click Policies > Policy Components > Management Server Lists > Add Management Server List.

In the Database Server Choice panel, do one of the following, and then click Next:Ĭheck Embedded database or Microsoft SQL server (whichever database type you’d prefer to install), then complete the installation.

In the Certificate Warning dialog box, click Yes.

The password used to log on to the old console. The Username used to log on to the old console.

In the Replication Information panel, type values in the following boxes:.

In the Site Information panel, accept or change the name in the Site Name box, and then click Next.

In the Server Information panel, accept or change the default values for the following boxes, and then click Next.

In the Management Server Configuration Wizard panel, check Install an additional site, and then click Next.

The new management console can be migrated to a newer version once the transition is complete. NOTE: The version installed to the new server must be the same version as on the old server. Install Symantec Endpoint Protection Manager on MACHINE_2.Management server list will then be updated accordingly and sent automatically to clients.Ģ) MACHINE_2 will have both IP and hostname different from MACHINE_1 Symantec Endpoint Protection clients will be able to reach the new SEPM using either unchanged IP or hostname. IMPORTANT NOTE: SEPM installed on MACHINE_2 must be the same version as on MACHINE_1 (same release and same language)ġ) MACHINE_2 will have at least either same IP or hostname as MACHINE_1įollow “Best Practices for Disaster Recovery with Symantec Endpoint Protection” (see Related Articles below). This solution will be appropriate for both situation 1 and 2 (see Environment section above). (B) Disaster Recovery: this solution is longer to implement but the new SEPM will be an exact copy of the current one. However, this solution will be appropriate for situation 2 only (see Environment section above). (A) Replication: this is a faster solution to implement. There are two solutions available, with their advantages and drawbacks: