Im having a problem where the daily update to the virus scan, where it dramatically slows down the XP machine while its going on.
In our environment we have one main AV server which pushes out the updates to about 6 distributed repositories (all server 2003 boxes) in our regional offices, then at 1PM each day i have the update set to run on peoples machine (except for one office which has it when people log in). Ive set it flash up the box so people know its doing an update but while its doing the update the XP machines grind to a halt!
Surely a daily update shouldnt big that large that it makes the machine unusable?
On the schedule for the anti virus update is as follows:
Stop the task if it runs for 10 minutes
Enable randomization of 15 minutes
Run missed task 20 minute delay
It run Monday to Friday
Any suggestions to speed this up would be great
Ive excluded .*dat files from the On-Access Default Processes policy & added mcscript_inuse.exe to the On-Access Low-Risk Processes policy so i will roll this out to a few test machines and see how i get on.
You should see some positive results on your test machines.
I've had all kinds of crazy high CPU issues with mcafee procceses, since going to v8.8 patch 1. Added many exclusions to try and resolve the issue, some help.
Problem children processes: mcshield.exe, mfevtps.exe, and mcscript_inuse.exe.
just thought i would ask, how comes it doesnt tend to affect the Windows 7 machines we have as much as the XP ones?
My Windows 7 machine is just the same hardware as the XP apart from having 2GB of RAM instead of 1GB, surely that 1GB of extra RAM isnt going to help with the update?
You should find the McAfee VSE best pratice guides. it gives lots of hints and tips on how to improve performance, since I made my policy follow this guide performance has been much better!
Ive gone through the best practise for VSE and made exclusions that stanw mentioned, but still the XP machines suffer severely when the daily AV update runs.
While its running McScript_inUse.exe uses about 400Mb of memory and can take up to 95%, then once it has finished updating the mcshield.exe takes over hogging up the CPU for a few minutes.
The weird thing is, as i said in my first comment, it only really affect XP. Windows 7 machines using practically using the same hardware can still work while the update is going on
experiencing the same issue with XP and McAfee i fear to shutdown my laptop and only make it on standby option so that i may save 10-15 minutes at the startup and taking control over my machine. Dont know its McAfee issue or XP issue but i am really hurting