Endpoint not updating policy
widget displays processor and memory use based on application scope.Virtual memory and memory used by runtime platforms are ignored.According to Symantec, an upgrade to version 12.1.5 will take much longer than you expect (sorry).It’s slow because the upgrade process converts all existing content to an optimized storage format, so plan for an extended upgrade time.Scan the headers below for best practices in all areas of SEP and lots of links to helpful guides, as well as a way to get a free analysis of your SEP environment at the bottom using Symantec’s Best Kept Secret.Installation is a big topic, so I encourage you to read Symantec’s Top 10 SEP installation best practices.The article covers things like ensuring all SEP clients and SEPMS are running the latest maintenance release, using the Group Update Provider (GUP) for content distribution, and how to ensure out-of-date SEP clients to still get incremental updates.
Browser implementations exhibit varying behaviors for single page web applications.
The following policy allows for remote viewing of the Mc Afee Agent log via browser and increases the Agent to Server Connection Interval (ASCI) from the default of 60 minutes to 120 minutes.
One reason to modify the Agent to Server Connection Interval on a group of systems might be to lessen the impact on already taxed WAN connections to remote sites, or simply because you are managing many thousands of systems.
Specifically, some browsers may not call destruction events, which leads to high RAM usage.
Specific browser and behavior optimizations are required for web applications to resolve this issue. For example, Windows Explorer displays an application so that the user can double-click and start the application.
Search for endpoint not updating policy:
Also, tune the scheduling frequency down to one hour.