Jump to content

Thomas F.

  • Posts

  • Joined

  • Last visited

About Thomas F.

  • Rank

Profile Information

  • Gender
  • Location
  • Interests

Recent Profile Visitors

558 profile views
  1. Hi. Today I noticed that 100% of our ESET clients are no longer up to date. I thought I read here once that from 8.x on, updates are performed after an optional reboot and automatic. However, that does not seem to be the case. After doing the update manually on two clients (from v8.1.2031.0 to v8.1.2037.2), I see a message that I should reboot the PC "to remain protected". I thought this should not happen anymore? A test with EICAR showed that downloads and also saving an EICAR file created using an editor are prevented. So, why this message? If I run the update in general, I get dozens of messages and calls again from people asking if they really need to restart their PCs. Regards, Thomas
  2. Hello. I tried to download https://download.mozilla.org/?product=thunderbird-78.12.0-SSL&os=win&lang=de. After completion, ESET Endpoint Antivirus showed a warning for a very short time and deleted the file. I could not find any log entry for that. This happened on two different Windows 10 clients. VirusTotal says that this file is clean. Regards, Thomas
  3. I like this idea. Does this app run on every client? Then I would like to test it. Regards, Thomas
  4. Thanks, I created the task and will see what will happen.
  5. We have reached the license limit at our ESMC. So, I checked the entries and found that some clients were listed twice, some with e.g. old and new IP address, others with completely identical data. I deleted these entries, but after that, the number of used licenses did not decrease. Is there anything else I need to do? Regards, Thomas
  6. If a restart is required, why not put a big flashing icon on the desktop that alerts the user, pops up again every hour after clicking away, and performs a forced restart after a configurable time? It takes several days to get our colleagues to reboot because they don't notice it. A small dot on one of several icons in the taskbar is not enough. Regards, Thomas
  7. I have got a similar problem. I upgraded ESMC to 7.2, created a task to do an update ("upgrade of Security Management Center Components"), and let it run for all clients. The report tells me that all went good, but I still have all sorts of versions and some clients tell the users that they are outdated. I don't understand why it is so difficult to keep the clients up-to-date. This should be an easy, as-automatic-as-possible process. This micromanagement takes hours to find out what went wrong this time. Last hour I installed a Windows 10 Pro PC with ESET and the client tells me that it is an outdated version even after I remotely updated it. When I try to update the client locally it tells me that it is up-to-date. Another thing is the much too inconspicuous warning that the PC should be restarted after the update. None of my colleagues notice the small mark in the icon. Can't you bring a repeating big message? The recognition quality is excellent, but the operation leaves much to be desired. Regards Thomas
  8. Hi. My colleague created an internal CA (Certifying Authority) for our local servers. How do we tell ESET that his CA is valid? Importing the keys into ERA returned an error. I hope this is at all possible without touching every client? Regards Thomas
  9. I guess you are right. For that reason MS does automatic updates. I really wonder though why there are so many Russian clients and (web)servers that are not patched and therefore used as zombies. Any idea?
  10. Are you serious? Those cannot be official IT personell. We know of every patch for every system we use and would never say "I don't care" as this would be our last action in our jobs before we get fired.
  11. Hi. Yesterday I upgraded ESET from 6. to 7.x on our Windows Server 2012 R2 and all seemed to work well. Today I could not connect to the web console from my Windows 10 client, it gave me a timeout. Only thing that changed besides the upgrade was a fresh installation of Dameware. So I checked all kind of things like open ports, running services etc. Locally I could reach https://localhost/era without any problems. I stopped the Dameware services, but no change. Then I looked at the firewall settings, although we didn't touch them for years. First I didn't see it but then I could not believe my eyes. "ESET Remote Administrator rule (Tomcat7)" was set to private and public, but not domain! All our machines are in a domain and all other rules only have domain activated. I guess that must have been changed by the upgrade because it worked for some years, until today. Does anyone have a clue why this happened? Regards Thomas
  12. When ESET told me that our WSUS server has updates available but the server itself didn't know of any I checked the last syncs and they all failed with: WebException: Die zugrunde liegende Verbindung wurde geschlossen: Für den geschützten SSL/TLS-Kanal konnte keine Vertrauensstellung hergestellt werden.. ---> System.Security.Authentication.AuthenticationException: Das Remotezertifikat ist laut Validierungsverfahren ungültig. After a bit of researching I found that ESET file security "hacks" into the HTTPS connection to the windows server, making the certificate invalid. Why does a tool that is called "file security" and especially is used for servers do this?! This surely cannot be unknown by ESET and I would expect a clear warning during installation that this will happen, especially if the WSUS service is already installed and running. Here is a quick fix in case other people have this problem:
  13. ESET Antivirus puts Thunderbird data files of a collueague (> 120 GB by now) in quarantine because it found bad Emails in them I guess. How can I prevent this from happening? This is a serious bug. Regards Thomas
  14. All machines update from ESET's servers. I found out that this error shows when I try to directly install over v5. For the rest of the PCs I first uninstalled antivirus v5, rebooted and then installed v6 together with the agent. This works everytime. Regards Thomas
  15. Hi there. I am upgrading from endpoint antivirus v5 to v6. On some machines (all Win 10 Pro) installing the software is very strange: Upgrading from v5 via websonsole or locally, rebooting -> module update failed". Uninstalling, rebooting, reinstalling, rebooting -> module update failed". Uninstalling, rebooting, reinstalling, rebooting -> everything works fine. I have to enter the license, then everything works fine. Does anybody have an explanation for this? Regards Thomas
  • Create New...