Hi there,
Your "Default Management Server List" is generated off the server list show in the "Admin > Servers" panel.
If you replicated with incorrect server names, corrected, and reconnected -- you may have "dummy" servers in your Server List. To correct this, do the following:
- Go to the Admin > Servers tab.
- Open the "Remote Sites" tree.
- Delete/Remove any Servers (and optionally any sites) that do not exist (the ones with the wrong name).
- The "Default Management Server List" on the local site should be updated in a few minutes. The servers you removed from the "Admin > Servers" panel will not be listed.
- Use Replicate Now, or wait for your standard replication schedule to populate these settings to remote servers.
Your other option is to use a Custom Management Server List.
If you manage multiple sites, a Custom list can be useful because you can make a "central" server as a "Priority 2" server. This ensures that if the server at the local sites goes down for any reason, you are still able to communicate with clients and send them policy updates. This can greatly simply disaster scenarios where you are forced to update the IP address of the local SEPM server as part of your recovery process.
Also, a note about replication. Most people like to use a "central reporting server". They do this by having all the servers replicate, which uploads the logs from all servers to one Central server. But, in these scenarios, it's a waste to send logs back down to the "remote" sites.
So people set the replication settings (Under Admin > Servers > Replication Partners > Properties) to only send the logs in one direction (from the remote site to the central site).