Hmmm... Maybe. I will have to look. We took the opportunity to reload them with Windows 7, so all wasn't lost. But it did cause some problems and I have turned off auto-deployment for now.
-- Bob Fronk [email protected] From: Richard Stovall [mailto:[email protected]] Sent: Thursday, March 11, 2010 12:06 PM To: NT System Admin Issues Subject: Re: VIPRE 4 - bad updated installer (4275) By chance do they have Broadcom NICs? http://supportforums.sunbeltsoftware.com/messageview.aspx?catid=27&threadid=3477&highlight_key=y&keyword1=broadcom On Thu, Mar 11, 2010 at 12:01 PM, Bob Fronk <[email protected]<mailto:[email protected]>> wrote: What was happening to you? We had 3 PCs get hosed by a Vipre upgrade from 3 to 4. Windows XP. PC would boot, then pop a service error and shut down. -- Bob Fronk [email protected]<mailto:[email protected]> From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] Sent: Thursday, March 11, 2010 10:06 AM To: NT System Admin Issues Subject: VIPRE 4 - bad updated installer (4275) OK folks, after my series of rants, we have figured out that most if not all of my problems with VIPRE 4 are the result of installing an "update". If you downloaded VIPRE 4 Enterprise between FRI 5-MAR and TUE 9-MAR, but have not yet installed it, DELETE IT! Go back and download another installer. This version (4.0.4275) is known to be so bad that SB pulled it. I downloaded a copy of the original server release last WED, and I installed it on MON. TUE, I saw (on my dashboard) that an update was available. Looking back at things, I see that MON night ALL my agents updated their DEF files with no issues. All my problems (and rants) began after installing 4275. There have been no DEF updates pushed out, etc. All attempts to push out an agent from the server were done after installing 4275. (I ran manual DEF updates on my own workstation WED. I then ran it on a server. My DEFs are stuck at WED late morning. On the server, the DEFs update deleted VIPRE!) I am currently awaiting word as to if I can "fix things" by re-installing 4265 (or will that make things even worse)? Project manager, on the forums replying to a similar rant, says some fixes will be posted (after testing) hopefully by tomorrow (FRI). Thanks for your patience. Again, if you have v. 4.0.4265, you probably have an excellent product. If your install is mostly dysfunctional, check to see if it is v. 4.0.4275. -- Richard D. McClary Systems Administrator, Information Technology Group ASPCA(r) 1717 S. Philo Rd, Ste 36 Urbana, IL 61802 [email protected]<mailto:[email protected]> P: 217-337-9761 C: 217-417-1182 F: 217-337-9761 www.aspca.org<http://www.aspca.org/> The information contained in this e-mail, and any attachments hereto, is from The American Society for the Prevention of Cruelty to Animals(r) (ASPCA(r)) and is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient of this e-mail, you are hereby notified that any dissemination, distribution, copying or use of the contents of this e-mail, and any attachments hereto, is strictly prohibited. If you have received this e-mail in error, please immediately notify me by reply email and permanently delete the original and any copy of this e-mail and any printout thereof. ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
