MKHAI
-
Posts
5 -
Joined
-
Last visited
-
Days Won
2
Kudos
-
MKHAI gave kudos to ma77y88 in Updating ESET Endpoint via ESET PROTECT Console
OK, so when is the support in ESET Protect due?
It seems bizarre to announce a feature but not allow the capability within the console!
-
MKHAI received kudos from TvM in Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
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.
-
MKHAI received kudos from Zen11t in Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
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.
-
MKHAI received kudos from Tomasz Trynkowski in Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
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.
-
MKHAI gave kudos to Peter Randziak in The ekrn service failed to start / Patch Tuesday Windows Updates
Hello @karsayor and @st3fan,
I apologize for the confusion.
We ere checking it internally and it seems that the statement
"In order to speed up the process and receive update right after the web/repository release administrators can use "Check for updates" button available in the application GUI." is not correct 😞
The Auto-updates will be available on February 13, before that manual upgrade would be required.
Such task is planned to be added to the ESET PROTECT console.
Peter
-
MKHAI gave kudos to Peter Randziak in The ekrn service failed to start / Patch Tuesday Windows Updates
Hello @karsayor,
The release to web/repository was on January 30 and will be followed by first phase of Auto-update/uPCU release (50%) on 13 February, while the last phase (100%) is scheduled for 27 February.
In order to speed up the process and receive update right after the web/repository release administrators can use "Check for updates" button available in the application GUI.
It is a new version and we speak of servers so for sure we need to proceed with caution...
Peter
-
MKHAI received kudos from LesRMed in Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
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.
-
MKHAI received kudos from Peter Randziak in Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
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.
-
MKHAI received kudos from karlisi in Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
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.
-
MKHAI gave kudos to Opapa in ESET Management Agent automatic upgrade
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...
-
MKHAI gave kudos to lleysan in Update to the latest version problem
Thanks! But if this process is completely automated and takes a month or more, why change the status in the administrator console that the product is outdated and an update is needed? It sounds illogical, but thanks, I will mean that the product is now updating itself. Could you tell me where I can create a support ticket? My local support is not able to solve the problem, and I don’t really want to wait months until they pass it on to the developers or someone even more competent.
-
MKHAI gave kudos to RayFlexCom B.V. - Brian in Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
Description: Checkbox 'Automaticlly Reboot when needed' default set to disabled. / off.
Detail: Currently we are executing tasks with no need for a reboot and sometimes we do. But since we also execute tasks on our servers, leaving the default setting 'checked' being quite dangerous.
See attatchment. This is the checkbox we would like to be disabled on default.
-
MKHAI gave kudos to ludolf in Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
Description: ability to export folder exclusions from ESMC policy
Detail: to migrate exclusions from one policy to another
