LesRMed

It would be a nice feature if we could push the update manually, in the way the automatic update works.
So select a group of endpoints to be updated next time there is a restart.

Ok thx for your swift response... I assumed that at least some of the 120 clients should have updated itself in the meantime. So I will wait.
But I think there is room for improvement regarding the auto-update feature...

Since everything has been said and explained about this topic's subject and we're just moving in circles which annoys other users, we'll draw it to a close.

Since the OP questions were answered more than once, we'll draw this topic to a close.

This is a great comment. It would be really great if it would just alert me if I had an overage, but it permanently has this warning for when I’m using the correct amount.

I think it is fair to say that most customers whether they are business or consumer have a responsibility of their own to research to a certain extent. it won't always just fall into your lap. Just curious on what the expectation from your position is on how this information should be routed? Email every customer on product updates/releases by default? At a certain point, due diligence is required IMO. I see the same standard across any other AV or software company, it requires you to search up the release notes or updates. IMO I am able to find everything that I need regarding updates/releases/support pretty easily, yeah it may take me looking in a few places but in reality it isn't something that consumes more than a few minutes of time, let alone hours. You can always contact your local ESET support team, it may not require a ticket or anything major, but a simple question of 'Is this supported?' or 'When was this released?'. 
I surely would not want to receive any email/contact without my consent. So ESET gives you the option to sign up for newsletter emails. 
 
EDIT: ESET Business customers also receive auto-updates for the products, so as long as you do your due diligence to enable this and ensure machines meet the requirements.

Hi there,
By default the reboot (or shutdown) alert is set with a 30 second delay. Is it possible to modify this in order to leave for example 5 minutes?
If it is not currently configurable, could this be possible for the next release?
This is in case the user is not in front of the workstation when the task is triggered.
 
Regards, 
Mike

Yeah the thing is in a world where new viruses appear all the time, while no AV can offer full protection, if a user submits a possible malware it shouldn't take 2 weeks to get detected. If actual malware that could have infected multiple users in the meantime 

Yeah, it needs to be analyzed manually.
 
I don't need replies as long as submitted samples get added to the database. Well, I have waited 2 weeks which is long enough. Too long I would say.

Bump 2 - is there a way to get an actual answer on this forum ?
I have just updated the console to 9.1, and now when I hover over the component state version, there is a blue line stating that the number of computer waiting to be updated is 0. 
Tired of waiting, I have launched manual update.
Failing still to see the point of so called 'automatic updates'.

Yes, that's the point, it does and it seems as it's the most reliable option to restart and update ESET. Normal reboot sometimes won't work properly. It's unfortunate because it's not the desired method to do this kind of maintenance, some users are not really tech-savvy.

just to shed a bit more light on it. This is what the end user sees after I run an update task on the outdated Endpoint AV from that particular endpoints menu and tick the "Automatically reboot when needed" tickbox.
After task completes the enduser is presented with the above notification. My question is if that reboot delay can be extended further, and instead of 30s end user has maybe 5 minutes before the reboot is performed?

Are we good now to try the v9?, I have several servers that need to be upgraded but I was afraid since I was reading here

Marcos, since multiple customers appear to be having this same issue, how can we get the devs to look into this?

Also in this post they mentioned upgrading removed the ransomware but never updated the post to say about the files. Kaspersky may have deleted the ransomware but deleting only removes the virus so unsure if they now have encrypted files.
I'd like to also add the fact you have been infected twice in the first place is worrying. As I have mentioned on a previous post about something similar, an AV can protect you but can never be 100 percent reliable. For that reason it is always good to have safe practices e.g. avoiding unknown sites, avoiding downloading cracks etc. If you are repeatedly infected, it is a good idea to look at the source and avoid returning

If you have been encrypted 3 times you really should look at how you got infected in the first place.
An antivirus can help but you really need to look at your habits and those of your employers if your part of a company, try to educate your staff and put in procedures e.g. backups

Shouldn't it be blacklisted?

For important files never rely on others to protect your only copy. That includes multi-billion dollar companies like Microsoft and Google. Keep multiple backups in multiple locations. Then when something like this happens you simply delete those corrupted files and restore them from a backup. This gets you back up and running in minutes and renders these ransomware attacks an inconvenience at most. 

Sure would have been nice if Eset would have chose a different notification in the console other than red to indicate a endpoint needs to restart to apply the update. Seeing a bunch of endpoints with a red status waiting for a restart ...the endpoints with serious issues with a red status get lost in all the restart clutter

Yeah with a previous AV I used before Eset I noticed each year that things got changed each yeah, and not just with AVs but programs in general. Sometimes one or new extras came but it often seemed the change in the UI was to trick people into thinking there was a lot of changes.
As someone who has just moved into a basic IT job that involves basic assistance changes do tend to confuse new users. I'd never say no to changes but I do also appreciate that Esets UI has been pretty consistent for a while.
As for the dark mode and general UI changes, if Eset can do changes then great but I'd rather it focused on protection over UI tweaks. There's features such as wildcards for HIPS, ransomware folder and roll back protection etc. That other AVs offer that many would like to see and I'd rather this took preference over design choices 

Hello,
I'm wondering why those who are not satisfied with ESET or worried about these tests did not simply change their AV ?🙄

Thanks for all your suggestion.
I ask to Eset a working solution. Theese servers are Domain controller and I can't test or joke with it.
I'm on a production environment. Do you have an official solution?
I've 4 servers with same problem (the only 4 server supdated from 8 to 9 but I've other 30 servers).
My best regards

There may be many people that do that but the percentage for that figure is going to be tiny in comparison to regular users that install once and then never look at the GUI again. It's understandable why they haven't allocated any resources to it. But PC techs will be happy that the GUI remains fairly consistent year on year. Unlike other software companies that insist on changing their GUI every year to make it look like there have been improvements. 

But then you don't get the great feature of not having to reboot the computer.
This is what makes the automatic update so great (on paper)

If the update is not that important, then I understand not pushing it automatic right away, but this update is also marked as Critical, thus a big red bar now in the protect Dashboard.

I agree, 30-60 days is a bit much. Plus, having to see the big red bar of outdated products for that long drives me crazy. I usually start manually upgrading my endpoints after a few days of seeing that. As you can see, I've already started pushing it out this morning. Kind of defeats the whole "automatic update" feature.