Jump to content

st3fan

Members
  • Posts

    78
  • Joined

  • Last visited

About st3fan

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    South Africa

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. We have not used the "Check for product update" task in all our branches yet, as we prefer to roll this out in stages. Yesterday I noticed that all branches had already received the Endpoint Antivirus version 10.1.2063.0 - so even branches where we never ran the new task. It seems the auto-update deployment started working again in the last few days. We have not made any changes to any policies. The only change we made was the upgrade to PROTECT 11.0.14.0. Very strange.
  2. I am not sure unfortunately and Support did not spend any time on troubleshooting. It might be a bug. Or maybe this update has not been fully released yet. It just does not make sense to me that auto-updates work for the servers but not for the endpoints, and that a manual "check for product update" is required now.
  3. Support suggested upgrading ESET PROTECT to version 11.0.14.0. And then we were able use the new "Check for product update" task (https://help.eset.com/protect_admin/11.0/en-US/check_for_product_update.html) in order to force the auto-update for Endpoint Antivirus.
  4. We configured the PROTECT server as the proxy server for all endpoints. And all endpoints have direct connectivity to the ESET services too. Unfortunately it is still not working for us. Servers where Server Security is installed are configured the same way. And here we are receiving the uPCU version 10.0.12015.2, without having to do a manual check for updates. I will open a ticket.
  5. And I noticed that this does not affect the uPCU 10.0.12015.2 for Server Security. No problem there. Our servers are receiving this update automatically. However, uPCU 10.1.2063.0 for Endpoint Antivirus is still a problem. None of our endpoints are receiving this update, unless we check manually. @Sec-C, are you still having this problem or does it work for you now? @Peter Randziak, is there anything else that we can try?
  6. I checked again today but it is still not working unfortunately. Only a manual check for updates works in my case.
  7. Hmm strange. It does not work for me yet. I just sent an "update modules" task to one of the endpoints (currently on 10.1.2058.0) but it has not downloaded the 10.1.2063.0 update yet. Auto-updates are allowed on all endpoints and I selected "Stop updates at 10.1.2063.0" in our auto-updates policy. I will try again later today.
  8. Thanks a lot for clarifying this @Peter Randziak Out of interest, do you know when the throttling will be removed? Or is there a way to deploy the uPCU remotely, without having to do the manual check for updates?
  9. Does anyone know when Endpoint Antivirus version 10.1.2063.0 will be available via the auto-update mechanism? We would like to upgrade to this version due to the reported vulnerability (CVE-2024-0353) but our endpoints are not receiving this update yet (auto-update policies are applied). The update is only downloaded if a manual "check for updates" is done but it is not automatically deployed via the auto-update option yet. Thanks, Stefan
  10. We sometimes get the below warning. So far we noticed this on Endpoint Antivirus 10.1.2050.0 and 10.1.2058.0. It is an intermittent problem, so we can't reproduce this, and it seems to affect random devices... never the same ones. It always happens after a notebook is started and the message always clears after a reboot. All our notebooks are on Windows 10 22H2. This is a new phenomenon that only started recently (November/December). I can't really say much about v11 yet as we only have a handful of devices on that version. Is anyone else seeing this? What can be done to prevent this? Is there a way to fix this without having to reboot the endpoint? Thank you.
  11. We had to uninstall ESET on all affected servers that were rebooted. I can confirm that this is definitely not related to the December Windows updates. In most cases we had to remove ESET using the uninstaller in safe mode as the ESET service could not be stopped/removed properly anymore. Before you reboot any other servers, make sure that you install a more recent ESET version. I doubt this problem is caused by this (which I believe is what Marcos meant). This should not affect existing installations according to the article.
  12. Assuming the above article was the one that you were referring to @Marcos, I am not sure if this applies in our case but please correct me in case I misunderstood. What is described in this article should only impact new installations or upgrades (“Existing installations of ESET products will not be affected and will keep receiving module updates.”). In our case, only existing installations were affected. Our issues did not start after any upgrades etc. The issues started after a simple server reboot, without any other changes. Our Windows servers are up-to-date and they should support ACS (still checking). If this was not the case, I assume we would not be able to do a fresh install of version 10.0.12014.0 (includes an installation block if the OS does not support ACS).
  13. Are you referring to this @Marcos? https://support-eol.eset.com/en/trending_weol2023_10_2022.html
  14. A few more updates on this: I have prepared the auto-update for version 10.0.12014.0 for all 9.0.12013.0 servers that have not been rebooted yet. Afterwards I rebooted a few servers for testing purposes. All good. The 9.0.12013.0 servers that have been rebooted before the auto-update was prepared are broken. I had to remove ESET in Safe Mode and reinstall it. All other upgrade attempts were unsuccessful. So to summarise for any other ESET admin who might run into this: Do not reboot your Windows servers if you are still running ESET Server Security 9.0.12013.0. @Marcos, surely we can't be the only ones who still use ESET v9. I am curious what the plan is for all other customers who might run into this problem. And I am assuming there will be a lot of problems this week, when Windows servers are rebooted after Patch Tuesday.
×
×
  • Create New...