Adding a SEPM and the effects on the "Default Management Server List" for the site


Article ID: 177896


Updated On:


Endpoint Protection


A SEPM exists in an environment with SEP clients attached to it. The SEPM makes use of the Default Management Server List that is created during install. You choose to add another SEP Manager for failover or load balance. After adding the SEPM to the environment, the Default Management Server List shows the added Manager. However, when comparing the Sylink.XML that is published on either Managers, you find that the first SEPM only contains entries for itself, and not for the new Manager; on the new Manager, you see entries for both Managers. With that in mind, all SEP clients that currently connects to the first SEPM will never be aware of existence of the new one, and Load Balancing will never function for these clients.


This is the expected behavior of the product


As described in chapter 8 of our Administration Guide, Symantec recommends that with the addition of Management Servers, SEP administrators should also create a customer Management Server List that exactly sets the various SEPMs to use and in which priority. The list can then be assigned to each group as needed.

administration_guide.pdf is part of the documents included in our standard distribution