Well, I think I'll wait a bit until things settle down a bit. J There's a saying my dad (a retired physician) likes to quote and I'll paraphrase it here as I can't recall the exact phrase --- don't be the first to try the new or the last to discard the old. I plan on sticking with the "middle" group who are waiting for the dust to settle a bit more before upgrading to Vipre 4 Enterprise. J
John-AldrichTile-Tools From: Jeff Johnson [mailto:[email protected]] Sent: Thursday, March 11, 2010 10:32 AM To: NT System Admin Issues Subject: RE: VIPRE 4 - bad updated installer (4275) I must say that my smooth upgrade was to 4265. I guess I got lucky by taking a chance and upgrading early. So far no problems. Almost all systems have been rebooted and all definitions on agent is at 5822. So far, I am happy with my upgrade. I hope everyone that is having problems get them resolved quickly. Jeff Johnson Systems Administrator 714-773-2600 Office 714-773-6351 Fax hydraflow From: [email protected] [mailto:[email protected]] Sent: Thursday, March 11, 2010 7: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 ASPCAR 1717 S. Philo Rd, Ste 36 Urbana, IL 61802 [email protected] P: 217-337-9761 C: 217-417-1182 F: 217-337-9761 <http://www.aspca.org/> 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 AnimalsR (ASPCAR) 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/> ~
<<image002.jpg>>
<<image003.jpg>>
<<image004.jpg>>
