Day: April 1, 2011

Most of the cases this attributes to the cases like constant updates to the DB and/or huge size data insertion to the DB, these by default factors for any DB server high resource utilization. In case of SEPM, the most common case is that SEPM has the Application Learning feature enabled which constantly updates the DB with data and also resulting in overgrown SEP DB.  To control this you need to use the Application Learning feature cautiously. Below are usual recommended options to make effective use of this feature: Disable Application Learning entirely if Application-Based firewall policies or System Lockdown […]

Issue: When configured the SEPM (Symantec Endpoint Protection Manager) to compress identical "risk found" events; identical risk events found within the same one-hour interval are compressed into one summary event with a count. The database settings in the SEPM site properties have been configured to delete compressed events after a number of days. To know the details of the risks that are summarized: < p>check the details of a summarized event, the File/Path section which show each folder where individual detections occurred. This is because the original events are still in the database and can be referenced by the summary […]

when you change the Liveupdate Policy to "Use a LiveUpdate Server", the standard is the Symantec LiveUpdate server on the web (Use the default Symantec LiveUpdate server). You can also change it to an internal LiveUpdate Server. So with this option checked, the clients go to the Symantec Server to get the definitions instead of the Symantec Endpoint Protection Manager. When "Use the default management server " is checked, clients get their definitions from the Symantec Endpoint Protection Manager. For Laptops, which are not always connected to the company network, it’s recommended to check either both or just the Symantec […]