Peter Randziak
-
Posts
3,496 -
Joined
-
Last visited
-
Days Won
201
Posts posted by Peter Randziak
-
-
Hello @st3fan,
you are welcome.
The throttling is already removed so the endpoints will apply it if you haven't disabled and have connectivity.
The product checks for the new version once a day by default, the throttling was removed yesterday.Peter
-
Hello guys,
the build is now available via uPCU / Auto updates, currently with a throttling.
On 2/12/2024 at 11:38 AM, Sec-C said:When running the same task manually (right click -> "run now") the client suddenly finds the update. Is this expected behavior?
Yes, that is an expected behavior if the throttling is set to 0% as manual check for updates overrides it. This is usally part of the rollout.
Peter
-
Hello,
the Network Prerequisites are covered at https://help.eset.com/protect_cloud/en-US/?prerequisites.html
the full list is available at https://support.eset.com/en/kb332-ports-and-addresses-required-to-use-your-eset-product-with-a-third-party-firewall
using ESET Bridge might be an option for you as it
1. by default (when Vulnerability & Patch Management is not being used) allows traffic related to ESET's services
2. caches significant portion of the traffic to save your bandwidth
So I recommend to explore this optionPeter
-
Hello @j-gray,
I was informed that the NORAM Technical support team is in contact with you regarding the issues reported, I hope you will be able to resolve them together.
Peter
-
On 1/25/2024 at 10:31 PM, j-gray said:
No, unfortunately I don't have ECP logs for any of those.
That's a pity 😞, I hope that we will be able to move forward with it, but the logs would be helpful for sure.
Peter -
Hello @j-gray,
On 1/19/2024 at 9:14 PM, j-gray said:My case (#00521603) got auto-closed without resolution.
I asked my colleagues from the Global Support Team to check it.
On 1/19/2024 at 9:14 PM, j-gray said:While it's a prevalent issue, I can't recreate it consistently at will. So end up wasting a lot of time manually enabling ECP logging to then not have the issue occur. And we hit the end of the upgrade cycle some time ago, so I don't have much to work with until the next upgrade is released.
FWIW, support did identify the issue upgrading from v6.11 to v7.3 and identified a fix for that scenario specifically. But apparently that fix does not apply to subsequent upgrades. I'm not sure why that would be the case, though.
Sorry to hear of such issues and the trouble you experience with it😞
The development team analyzed the logs and sadly haven't found cause in it seems that the activation went fine in this particular case. Do you happen to have the ECP Activation logs available to check from this case, or from another one when you observed the issue for the subsequent upgrade i.e. not from an upgrade from the 6.th generation of the product? If yes can you please provide me with it so I can provide the Dev team with it?Thank you, Peter
Note for me: P_EECSM-5259 -
Hello,
thank you for your report.
The error is unrelated, it means that the server is unable to connect to the Repository so it might be a DNS issue or issue with the connectivity.
A senior EP developer noted, that we had such bug in the EP in the past so some versions weren't shown so it might be related. For example the 10.1.8.0 is still available in the Repository.The product management team is taking care of the issue with the download widget on the eset.com, but it will take time to fix.
The minor releases are are only Servicing updates so no new major features added, mostly fixes of issues so those should not cause issues, but rather resolve them, see details at https://support-eol.eset.com/en/policy_business/versioning_rules.html
Peter
-
Hello @j-gray,
one of our developers noticed this thread and asked us to provide him with the installation logs (the OS install.log, usually located at
/private/var/log/install.log
) from the affected machine to check for the start?Can you please provide us with it? Feel free to upload it to a file sharing service of your choice and send me the download details via a private message.
Thank you, Peter
-
Hello guys,
I can confirm that there is an issue with the quality of service of the ESET Push Notification Service (EPNS).
The teams responsible are on it.
We apologize for the inconvenience caused,
Peter -
Hello guys,
I can confirm that there is an issue with the quality of service of the ESET Push Notification Service (EPNS).
The teams responsible are on it.
We apologize for the inconvenience caused,
Peter -
Hello @ash77,
what is the version of the Configuration module on the server on which you are testing the fix?
Have you applied the policy with the pre-release update type to it?Peter
-
2 minutes ago, Krula said:
I have the same problem for 3 days now. I have already uninstalled eset, but after reinstalling to a lower version, the problem persists.
4 minutes ago, Tkaran said:Same problem here 5 pc's
"Faulting application name: ekrn.exe, version: 10.37.39.0, time stamp: 0x652903c1
Faulting module name: dbgcore.DLL, version: 10.0.19041.3636, time stamp: 0xbaff5453"Please provide us with the ekrn complete memory crash dumps, so we can analyze the root cause of the issue.
If the dumps created by the built-in diagnostics are empty i.e, 0 MB in size, please follow
-
Hello,
please enable creation of full dumps in Advanced setup, tools, diagnostics and provide us with the created crash dump to check.
Peter
-
Hello @Yafu Ji,glad to hear that it works without issues for you now, but we would like to verify the fix which we prepared.
It is available on so called pre-release update channel, updating from it can be easily enabled via the policy / in the settingsOn the screenshot you have the Detection engine of version 28246, the pre-release updates are marked with "P" i.e. it would be 28246P
Can you please try to switch to the pre-release update channel and confirm that it works fine in your environment?
Thank you, Peter
-
Hello guys,
Can you please try to verify the fix on pre-release update channel in environments, where you reproduced the issue?
In our internal tests it works well, but we would like to have it confirmed before we deploy the change on the release update channel.
Thank you in advance.Peter on behalf of the teams involved
-
Hello guys,
Can you please try to verify the fix on pre-release update channel in environments, where you reproduced the issue?
In our internal tests it works well, but we would like to have it confirmed before we deploy the change on the release update channel.
Thank you in advance.Peter on behalf of the teams involved
-
Hello guys,
On 11/14/2023 at 2:25 AM, kingoftheworld said:This is the first time I am hearing about the end of sale for ESET Protect. Since we are an existing customer, I understand our console will continue to work. However, should we expect development of the on-prem offering to cease? If so, how long should we reasonably expect to be on-prem before being forced to the cloud?
the ESET PROTECT on-prem will work, it is being actively developed and supported.
As I mentioned only sales of some of the license offerings / bundles are not anymore available.End of support of a product have to be with accordance to the ESET End of life policy, which is available at https://support-eol.eset.com/en/index.html
Even the current version of ESET PROTECT on-prem will be supported for a long time https://support-eol.eset.com/en/policy_business/product_tables.html (ESET On-premises Consoles)
Peter
-
Hello @eornate
the module updates were fully resumed at ~13:00 CET (November 14, 2023).
-
Hello @howardagoldberg
the module updates were fully resumed at ~13:00 CET (November 14, 2023).
-
Hello guys,
the module updates were fully resumed at ~13:00 CET (November 14, 2023).
-
Hello guys,
the fixed modules are available on the Update servers since ~13:00 CET (November 14, 2023).
Users affected by this issue do not need to take any steps, the module will be updated automatically and the issue will be resolved by it.
We apologize for the inconvenience caused,
Peter on behalf of the teams involved
-
Hello guys,
the fixed modules are available on the Update servers since ~13:00 CET (November 14, 2023).
Users affected by this issue do not need to take any steps, the module will be updated automatically and the issue will be resolved by it.
We apologize for the inconvenience caused,
Peter on behalf of the teams involved
-
Hello guys,
the fixed modules are available on the Update servers since ~13:00 CET (November 14, 2023).
Users affected by this issue do not need to take any steps, the module will be updated automatically and the issue will be resolved by it.
We apologize for the inconvenience caused,
Peter on behalf of the teams involved
- O S, MarcFL and Ben Partouche
- 3
-
3 minutes ago, Estrelo said:
What you have pinned in the forums is the wrong advice! Servers that haven't rebooted still have the real time protection working. If you reboot you lose malware protection. Rolling back updates does not work.
Tested with Eicar file. Please advise people NOT TO RESTART THE SERVERS until the issue is solved!
Yes I admit that the information provided in the alert was not up to date and accurate. The situation was quite dynamic and new findings were emerging...
As of now, it is up to date https://support.eset.com/en/alert8521-error-during-auto-updates-in-eset-server-security-for-microsoft-windows-server
We apologize for the inconvenience caused.
Auto-update for Endpoint Antivirus 10.1.2063.0?
in ESET Endpoint Products
Posted
Hello,
the Update modules task does not check for new product version, If I recall correctly there are some plans to make uPCU available on-demand from the ESET PROTECT in the future.
Do the endpoints have direct connectivity to ESET services or via a proxy?
If they are on every day, I assume that it will have to be investigated via a ticket...