So I guess if you haven't been bitten yet then you haven't run a scan. Guess I better get all the clients updated before they scan at noon.
________________________________ From: Jeff Cain [mailto:[email protected]] Sent: Friday, May 07, 2010 11:05 AM To: NT System Admin Issues Subject: RE: Computers becoming unresponsive across entire network. This was just sent out - I figured I'd share with the list. Product Notification: VIPRE Enterprise, VIPRE Enterprise Premium, CounterSpy Enterprise Date: May 7th, 2010 Notification Type: Support Issue Product: VIPRE Enterprise, VIPRE Enterprise Premium, CounterSpy Enterprise Version: All Operating System: All product-supported Operating Systems Dear VIPRE/CounterSpy Enterprise customer, Customers running a scan with definition versions 6272, 6273, or 6274 may experience extremely high CPU usage when running a scan. The issue started with definition 6272, released 5/6/2010 at 5:53:19 PM EDT. The issue is caused by a virus detection (Virus.VBS.Redlof.f) that causes a loop condition on the system, resulting in high CPU usage. This problem has been fixed in definition version 6275. If you are unable to abort a currently running scan on your agent machines, the solution to the 100% CPU usage is to do as follows: 1. Ensure the Enterprise Server has received definition version 6275. 2. Stop the following processes on any unresponsive agent machines: a. SBAMsvc.exe b. SBAMTray.exe (if tray icon is set to be visible) c. sbamui.exe (if agent interface is open) d. SBPIMSvc.exe (4.0 Agents only) 3. Restart your enterprise agents. 4. Update any outdated agents within your console to the latest definitions. We are aggressively researching why this detection was able to release to the public and are putting in place additional quality assurance processes, so that we can ensure that this type of detection doesn't occur again. Thanks for choosing Sunbelt Software, Thanks, Jeff Cain Technical Support Analyst Sunbelt Software Email: [email protected] <mailto:[email protected]> Voice: 1-877-673-1153 Fax: 1-727-562-5199 Web: <http://www.sunbeltsoftware.com <http://www.sunbeltsoftware.com/> > Physical Address: 33 N Garden Ave Suite 1200 Clearwater, FL 33755 United States -------------------------------------------------------- If you do not want further email from us, please forward this message to [email protected] <mailto:[email protected]> with the word 'unsubscribe' in the subject of your email. -------------------------------------------------------- Helpful Sunbelt Software Links: Knowledge Base <http://support.sunbeltsoftware.com/> Open a New Support Ticket <http://www.sunbeltsoftware.com/Support/Contact/> Sunbelt Software Product Support Communities <http://www.sunbeltsoftware.com/communities/> From: Weatherford, Chad [mailto:[email protected]] Sent: Friday, May 07, 2010 12:01 PM To: NT System Admin Issues Subject: RE: Computers becoming unresponsive across entire network. That sounds a lot McAfee's response with the "5958" disaster! >From McAfee: "If you have not rolled out DAT 5958 DON'T!!!! If so roll out the included extra dat...." How do I roll anything to PC's that no longer have network connectivity or are in a constant reboot cycle? Here's you sign! From: [email protected] [mailto:[email protected]] Sent: Friday, May 07, 2010 10:54 AM To: NT System Admin Issues Subject: Re: Computers becoming unresponsive accross entire network. How the @#*& do you force an update to 6275 on a machine that is pretty much unresponsive? VIPRE console says "Inactive", which seems in this case to apply to the whole machine... -- RMc "Tom Miller" <[email protected]> wrote on 05/07/2010 10:29:22 AM: > It is/was a Vipre issue. Force a defs update and you'll be good. > Must have been a bad def. > > >>> "Luke" <[email protected]> 5/7/2010 10:56 AM >>> > The Network Administrator and I have been working on this all > morning. Since about 7:00AM random machines on the Local Network > have been slipping into and out of a random state of > unresponsiveness ("Freezing"). > > The symptoms are pretty serious - I have seen it take up to 5 > minutes to bring an already open window from the background to the > foreground on client machines - and there are servers that are so > unresponsive that I am not even able to log into them (enter > Username and Password and nothing happens for the next 30min.). We > have had to cold boot one server 3 times in the past hour! > > This problem is not specific to any user, profile, machine, OS, > network switch, etc. - at least from what we have been able to > Identify. So far it has affected Windows 7, XP and Server 2003. > However, this issue is not affecting everyone on the network. My > Colleague sitting right next to me has been having all kinds of > trouble with his PC and I have not. > > We have found that cold booting the affected machines does help a > little or at least for a while, but more often than not the machine > will just return to its unresponsive state after a few minutes. On > the machines that I have that are accessible I am attempting scan with Vipre. > > We are seriously starting to suspect that Vipre is doing something > (in the background that we cant see) that is actually causing all > this. We completely removed Vipre from one PC that was having > trouble and it seemed to fix the problem. The PC has been running fine since. > > Any thoughts? > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > 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. > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
