karlisi

Anyone else that has any experience on the issue? I have still a significant number of Windows 7 machines managed by the Protect and thus so far i am not eager to update it to 11 without knowing the answer.
Specifically, i am interested not only about the status of the already managed machines, but also about whther it would be possible to add new ones (or reinstall/reattach Endpoint installations whose Agents stopped responding for one reason or another, which seems to be not so infrequent issue with 10.1 agent line)
 

Thanks for the confirm. so it seems works. but ESET may refuse to support this kind of configuration if I understand the release notes sentence correctly: "REMOVED: Windows 7/8/8.1 support".
It's strange ESET forum administrators won't answer questions like these which need to clarify  support status. maybe I needs to create ticket.

You have 2 spaces between symbols, that's not allowed in CRON expressions

Description: "does not contain" filter is missing in ESET PROTECT's report template filter settings
Detail: In ESET PROTECT, there is a rather limited choice in the report template filter settings.
For example, it is not possible to create a filter condition to exclude the occurrence of any string ("does not contain" condition).

ESET PROTECT console: Products should not be marked as outdated until the next product's auto-upgrade is released.
Let's refer to this existing post:
 
My ESET PROTECT console dashboard's Component Version Status is lit up in red (Legacy) despite being properly configured for automatic upgrades/updates and all of the clients being on EEA v9.0/9.1. The endpoints' status should remain in a blue "Waiting" status for any supported versions until the auto-upgrade is released.
 

The appropriate update files must first be published in the repository. As I wrote, we are working on adding the functionality to enforce autoupdates from the ESET PROTECT console before they are enabled globally for all Endpoint users.

Please kindly do not deactivate the notifications or you won't probably reactivate them later and missing some important notifications in the future may lead to issues if our message cannot be delivered. We are working on a solution when managed Endpoint won't display the notification in gui. It may take a couple of days and we expect it to be released next week.

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?

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.

Hi Marcos,
I understand that this is the first time you are pushing updates this way, however I wanted to ask whether there will be a more official channel where we can track when a new version will be rolled out. Additionally, having the option to change that time frame would be ideal as in my opinion using an outdated version for nearly two months is too much. A month should be more than sufficient for any critical issues to surface. 

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.

"What have the citizens of russia done to eset or anyone?"
As for me, I believe, the government is there to do things on behalf of me, and if so, every citizen of every country is responsible, not only their presidents.
I suggest to not continue this thread, it could lead to political debates, and ESET security forum is not the right place for that.

"What have the citizens of russia done to eset or anyone?"
As for me, I believe, the government is there to do things on behalf of me, and if so, every citizen of every country is responsible, not only their presidents.
I suggest to not continue this thread, it could lead to political debates, and ESET security forum is not the right place for that.

Our position is clearly laid out on the linked page, so with that being said, we'll close this topic before it gets nasty and political.

"What have the citizens of russia done to eset or anyone?"
As for me, I believe, the government is there to do things on behalf of me, and if so, every citizen of every country is responsible, not only their presidents.
I suggest to not continue this thread, it could lead to political debates, and ESET security forum is not the right place for that.

"What have the citizens of russia done to eset or anyone?"
As for me, I believe, the government is there to do things on behalf of me, and if so, every citizen of every country is responsible, not only their presidents.
I suggest to not continue this thread, it could lead to political debates, and ESET security forum is not the right place for that.

ESET menu should be placed in fancy windows 11 context menu instead the ugly one 😃
👍🏽

 👎🏽

 

Basically follow this guide (including the bottom part of how to rebuild the repo) 
https://kb.acronis.com/content/62731
Here is a quote of the info from there:
 
 

This was in Cloud Administrator topic but should be here too
Description: A new task/setting to reboot computers with a popup message warning,
Detail: Add the possibility to notify user that computer will be restarted when reboot computer task is triggered and let them for example 5 minutes to save/close programs/data.

AFAIK no, every time you create new All-In-One installer, specify port in 'Advanced' step.

Most people prefer using Virustotal's free file analysis as it uses multiple vendors to check if a file is bad/suspicious. It could be argued that is better than just using a single vendors database. 

https://help.eset.com/protect_deploy_va/80/en-US/?va_upgrade_migrate.html

Hi Gang,
Components:
ESET Protect (8.0.2225.0) ESET Endpoint (8.0.2039.0) As part of a task, we install a specific version, in this case Endpoint 8.0.2039.0. This let's us ensure that all nodes are at least on the same version and potentially avoid any niggles by always going on the latest.
However, ESET Protect always sees the latest version? This is currently Endpoint 8.1.2031.0. Thus ESET Protect now shows in the status dashboard that all our Endpoint nodes are now out of date. My question, how do we baseline or set a static version so that ESET Protect is not always referring to the latest version? I'd rather us determine what level we deem is up to do. I thought I achieved this with the task for installing Endpoint but that seems not to be the case.
This is what I am referring to:

Thank you,
Daniel

Tell me, Eset - are you insane?
A few days ago you released version 8.0.2039 . We started a rollout for a few thousand endpoints and now you releasing 8.1.2031??

Hello, for the sake of installing the latest agent, you first need to update your server to the latest version, as the agent installers are linked to the server version. If the server is already updated to ESET PROTECT V8, all agents that you will create / deploy, will be on V8 as well. Updating of previous agents can be done using "components upgrade task", which you can find among the client task in section "ESET PROTECT", once your server is updated. 
With regards to the client, even if your agent / server is on older version, you can choose a particular installer version both in installer, and in software install task. As those are all "version specific", you currently can´t create an installation package that will be always using the latest available version.
However, as of Endpoint V8, we have introduced uPCU auto update functionality, when you will be able to configure your endpoints to automatically download, and prepare the latest installation version, and apply it upon next computer restart. However, your endpoints will have to be upgraded to V8, in order to enable this functionality. Once we will release next server release of Endpoint V8, we will also roll it out using this method.