I have to agree with Tom. I've got Vipre installed at probably a dozen customers, and while a quick-scan is OK during the day, a full scan is VERY noticeable. At all my clients I've had to schedule that for off-hours, changing the default.
I don't notice it on my laptops and PCs, but they are significantly higher-performing than my average customer's desktop. ________________________________ From: Sherry Abercrombie [[email protected]] Sent: Thursday, October 22, 2009 8:52 PM To: NT System Admin Issues Subject: Re: User who doesn't like logging off / shutting down You can't be serious.....I installed Vipre on my pc and started a deep scan right as my lunch hour started. Played a FPS game at lunch and never noticed a performance hit at all. On Thu, Oct 22, 2009 at 5:57 PM, Tom Miller <[email protected]<mailto:[email protected]>> wrote: Welllllllllllllllll, Vipre still bogs down our PCs here when the weekly deep scan is running. We get the same complaints we had when we used Symantec. The quick scans are not noticed, but I'm bummed that the deep scan causes a very noticeable performance loss. It's set at low priority, but still the vipre process is first/second in memory/cpu usage during the deep scans. Anything that uses those sort of resources is *not* running at low priority. >>> Jonathan Link <[email protected]<mailto:[email protected]>> >>> 10/22/2009 7:47 PM >>> Or go to Vipre... On Thu, Oct 22, 2009 at 7:01 PM, Eric Woodford <[email protected]<mailto:[email protected]>> wrote: Sorry, can't help. I hate to logoff my pc because the security team has our AV do a full scan each time I logon. It takes a good 2 hours of 100% processing on my machine. The easy fix is to disable the AV, but... Maybe they just need to remove a few apps out of their startup, so it boots faster. On Thu, Oct 22, 2009 at 1:29 PM, Andrew Levicki <[email protected]<mailto:[email protected]>> wrote: Hi, I've got a user who doesn't want to log off let alone shut down their computer. They claim that it takes too long and they haven't got time to wait to log on again or start up. They're important enough that I can't force them to do so, but I'm worried about possible problems. The only detrimental effects that I can think of are added power consumption and ticket expiration. Can anybody else think of any other pitfalls or even have any experience of this and how did you deal with it? Thanks, Andrew Confidentiality Notice: This e-mail message, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -- Sherry Abercrombie "Any sufficiently advanced technology is indistinguishable from magic." Arthur C. Clarke ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
