Symantec endpoint protection client not updating management server
What our sysadmins have reported is that the SEP software does not have any native way to throttle its use of network bandwidth.
It needs to send a 'full' definition update to every client, some hundreds of Mbyte in size.
My organization has a large deployment of Symantec Endpoint Protection (SEP) (~20k clients) with a single SEPM instance running in an ESX VM.
We do have many remote clients designated as Group Update Providers (GUPs) where possible.
Alerts inform the administrator when specific events have occurred, such as a malware infection.
Alerts are displayed in the Alerts node of the Monitoring workspace, or optionally can be emailed to specified users.
- Service: "DNS Server", error: "The network is not present or not started" - See ME954423.
Any custom policies you have deployed are applied by default, within 60 minutes of deploying the client.When you modify the default client settings, these settings are applied to all clients in the hierarchy.You can also configure custom client settings, which override the default client settings when you assign these to collections.- Service: "Server", error: "The server is in use and cannot be unloaded" - See ME910666.
- Service: "Server", error: "Access is denied" - See ME910666.For information about how to configure client settings, see How to Configure Client Settings in Configuration Manager. Use the following sections for more information about the client settings that might require some information before you configure them.