Jump to content

Thomas F.

Members
  • Content Count

    13
  • Joined

  • Last visited

Profile Information

  • Gender
    Male
  • Location
    Germany
  • Interests
    VR

Recent Profile Visitors

403 profile views
  1. Thanks, I created the task and will see what will happen.
  2. 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
  3. 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
  4. 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 m
  5. 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
  6. 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?
  7. 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.
  8. 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
  9. 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
  10. 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
  11. 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
  12. 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
  13. Hi there. I am upgrading from v5 to v6 in my company. The problem is that we use several subnets e.g. 192.168.150.0 and 192.168.178.0. Only the first subnet is scanned because the server is located there and the clients in the second subnet are not in the domain. I found no quick way to tell the remote administrator to scan/add another network. I had to add them all manually. Is it possible to install another rogue sensor and to add it to the remote administrator? Or is there another way? Regards Thomas
×
×
  • Create New...