NOD32 v. 2.12.3?

I noticed that Blackspear said he was running v. 2.12.3 of NOD32, as opposed to v. 2.12.2 which most of us run. I assume this means a minor upgrade of the program is coming. My question is, when we get the program upgrade, should we uninstall the previous version of NOD32 or just install the new version over the old one? I realize this has been asked before with respect to new versions of NOD32, but this is a relatively minor upgrade (compared to ones previously discussed) and I'd like to hear an answer from someone at ESET.


Thanks in advance.

 

Hi Profhsg, while I am not from Eset, I did make 3 installs 2.12.3 straight over the top of 2.12.2 as it is a minor upgrade. I would suggest the majority of users out there will do the same, as it will come to their attention through a “Program Component Update” notification, or auto install of such…

Hope this helps…

Cheers

 

I'm always like an excited child when an update is about to be released, so here's an impatient kid's question

After the update, are IMON's http settings automatically changed from higher compatibility to higher efficiency?

 

LOL, and Correct, website issues have been addressed...

Hope this helps...

Cheers

 

Sorry but I don't understand If this upgrade is out or not... If yes where I can download it? thanks

 

Coming to a town near you soon

Cheers

 

Thanks you so much I will hope that out very soon cheers

 

We assume the newer version will be available as an installer on our website in 1-2 weeks. It should resolve the problem with loading certain pages in higher efficiency mode.

 

Well good news.
Hope Brazilians are included too.

DonKid.

 

I HOPE that this minor PCU will not require a system reboot, as the update from 2.000.9 -> 2.12.2 did. I'm still trying to get some of my 2500+ users to reboot after that one. We're in the manufacturing business, and many of my PCs stay on for extended (weeks/months) at a time during a process run, and can't be rebooted, since they're controlling machinery. I don't mind rebooting for major feature adds, but if it's just to change a setting or two, I'd have to object.

 

I'm not sure on this one, as I only have a full install veriosn of 2.12.3

Cheers

 

I agree with AnotherJack. I have still some computers out there that haven't been restarted yet.

 

The newer version is not going to be available through a component upgrade. Anyway,there's an option in the mirror setup called Require permission... for which allows admins to control when program component upgrade files will be rolled out on workstations.

 

now thats what we call "great support"....

 

Am I reading right?? You will not give us the udpate via component update - so how do we do this - download it and install on top??

Ruben

 

Yep, the newer version will be available as an installer on our website since only a very minor issue has been remedied. I doubt all users would like to receive 6-7 MB component updates every 2 weeks, not taking into account how much testing is required before a component update is issued.

 

Marcos - The issue isn't with the mirror making the updates available, it's whether or not the machine would have to be rebooted after a PCU, as is usually the case. In a large environment, it's a pain (and imposition) to have every protected computer reboot on cue, unless I deploy with the "Don't ask, just reboot" option in the XML file. That opens up a whole OTHER can of worms and people howling for my head on a platter.

Is there a changelog for 2.12.2 -> 2.12.3 ?

 

See your point - just want to know if that means uninstall, and install or can we install on top??

Ruben

 

I guess I will be updating if a pc comes up with an issue.

 

Hi Folks,

Ruben,

Always uninstall it, reboot, delete Eset folder, clean any trace of NOD into Windows´s registry and install the new version.

Best Regards,

DonKid.

 

I assume those of us that do not wish to sterilise our machines before installing a minor software upgrade will be able to simply install over the existing version.

 

Appreciate the thought, but now multiply that times 2000+ machines across multiple locations in multiple countries... Not quite as easy as you'd think.

 

Yes it can be done that way, though always best to uninstall and reinstall. To date, very few problems ever found going over the top of a previous version...

Hope this helps...

Cheers

 

Hello, whilst we're on the subject of un/re-installing nod, is it possible to save my settings for use with a new version or simply as a backup? Or, do I have to configure nod all over again after a re-install?

#
T.

 

That's good to hear. I have happily ignored the 'best' way for years