Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

CPU Usage Issues.

Updated: 23 May 2010 | 3 comments
Tharkun's picture
Tharkun
0 0 Votes
Login to vote
IT recently installed Endpoint and we have had several major problems.  We are having issues with workstations slowing to a crawl.  Checking Task Manager shows that several programs are using big chunks of CPU time.  LUCOMS~2.exe pops up every couple of minutes.
 
 Also SescLU.exe runs at the same time.   Is this normal?  Any issues I can take to our IT may help to resolve the issues.  Thanks for any assistance you can provide.
discussion Filed Under:
,

Comments

Josie's picture
21
Jan
2008
0 Votes 0
Login to vote
Josie

we are havign the same problem.
dollars2donuts's picture
21
Jan
2008
0 Votes 0
Login to vote
dollars2donuts

Ditto.  Here are things I've tried to make the PCs run faster:

  1. Cancel the startup scans.  For managed clients, I changed the policies to allow the user to modify startup scans.  In most cases I tell them to stop the scans altogether, especially for laptops.  The PCs are almost always on so there's not much need for the startup scan
  2. Disabled the Outlook, Internet, and Lotus email auto-protect.  We scan emails at the mail server so its unnecessary. 
  3. Never schedule a scan during the day (or anytime your users are likely to be on)

Those helped a little but we're still having performance problems.  That's all I can think of off the top of my head.  I'll add to the list as I remember things.

0WN3D's picture
21
Jan
2008
0 Votes 0
Login to vote
0WN3D
Symantec Employee

Before you start "cancelling" things, please understand the real issue.  LUCOMS is the LiveUpdate process..not the scanner.  LiveUpdate and the associated definition processing engine are a little CPU intensive at present.  You can start by turning OFF continious LiveUpdate in the LiveUpdate policy section BOTH at the server level (Server properties) and also in the Policy section.  4 hour LiveUpdate seems to work well.  If your server is a dual cpu (not DUAL CORE) system then you can probably get away with continuous LiveUpdate.  I've had really good success since changing this setting.  You can also request a script from support that will allow you to schedule Rapid Release updates at your leisure.  It drops a .jdb (update) file on the server and will push out updates to all the clients.

Technical Support

Symantec.com

Store

Community Stats

Total Content Items
Members
258,959