Jump to content


  • Posts

  • Joined

  • Last visited

About zackliu

  • Rank

Profile Information

  • Location
  1. Agree with everyone else, you must try v6 before consider upgrading. It's like a different product.
  2. For Reports, it would be great to have the ability to merge the default templates. For example, I want to have a daily report that includes the active threats, last scan, virus definition update info, and quarantine info, all in one report. I feel the reporting function in ESET needs some improvement and should include more out-of-box useful templates for the ease of administration. Also, when the report are generated and sent via email, the name of the report is always "report.pdf", please consider to include a timestamp and/or change the name of the file to match the type of report OR let us define the filename. It is a pain to identify the report currently with the same file name.
  3. This is what shows under ERA console. We have a policy that turns off Firewall in ESET Endpoint Security and some of my computers display the alert shown. There should be a policy that stops ESET or agents reporting these alerts.
  4. I just noticed that component upgrade task does not upgrade Tomcat and Apache proxy on the ERA server, and the documentation is not clear on whether we should manually upgrade them or not afterwards. Can ESET clarify this and make Tomcat upgrade file downloadable individually? Currently we had to extract it from the all-in-one installer.
  5. Just want to add that 2 of my clients ran into the same issue recently. Turns out the culprit is that Network.dll had not been properly upgraded. After running component upgrade from ERA 6.2 to 6.3, Network.dll is still 6.2 version, causing 6.3 service to crash. I took the dll from a working 6.3 installation, replaced it, and viola service starts working properly. Attached is the list of files in C:\Program Files\ESET\RemoteAdministrator\Server from a working 6.3 installation, might want to check this first in case someone else run into the same issue. Adding to RyanTsai's solution: Since I do not have an additional working 6.3 installation, I downloaded the ESET ERA Standalone component server installer (in my case Server 2012R2) Server_x64.msi Extracted the contents of the .msi to a folder. Example: msiexec /a C:\temp\Server_x64.msi /qb TARGETDIR=C:\temp\Extracted On the ERA server, rename the old Network.dll to Network.old Copy the newly extracted Network.dll to C:\Program Files\ESET\RemoteAdministrator\Server Started the ESET Remote Administrator Server Service Have not experienced anymore issues It's weird that network.dll was not repaired when I tried to repair the 6.3 installation with server_x64.msi. Anyways, great job for actually locating what the actual file is causing the issue. I tried to search for clues in event viewer and trace.log and nothing useful could be found.
  6. I ran into this issue today when upgrading to ERA 6.3 with Components upgrade task. After the task completed my EraServerSvc service will start and crash after 10 seconds. Had to contact ESET support and was told to remove all ERA installation and re-install. After doing that the EraServerSvc service will start without crashing....Just a heads up for you sysadmin guys..had me scratching my head for a few minutes.
  7. Same issue happened to us..End up waiting 3-4 hours for a few large inbox (1GB to 3 GB) and eventually Outlook starts to update inbox.
  8. For your WMI Service issue and ekrn.exe consuming CPU resources, we had the same issue in our environment and it turns out that HIPS filtering mode needs to be set at "Smart Mode" (Automatic Mode doesn't work), and make sure you do not "log all blocked operations" in HIPS. ESET v6 should have been tested more before released.
  9. I have a policy that turns off personal firewall, how to turn off Personal Firewall Inactive warning on clients? Some clients don't show this warning and some clients show this, they are assigned with the same policy, why is that?
  10. What I found easy to deploy for our environment is the following: 1. Setup some kind of web server in your network, copy ESET MSI installers to the web server, and get the URL. 2. Setup Proxy for ESET and setup a policy to your workstation (For activation and virus definition updates) 2. Push agent (manually install or use PDQ Deploy) 3. Perform Software Install task through ERA and choose "Install by direct package URL", and use the URL of your local web server. 4. ESET products will talk to proxy server for activation and definition update.
  11. Turns out that it is possible to put the MSI installers in our internal web servers for product installation task.
  12. Thanks Marcos, Just another question, Is it possible to have our internal web servers host MSI installers for Endpoint products and use that URL (like hxxp://ourinternalservers.local/ees_nt32_enu.msi) to perform Software Installation task? If possible, then whitelisting is not needed since I setup an Apache Proxy that can do activation and virus definition updates..... Zack
  13. Hello, We have a web content filtering system that require a user to authenticate before they can access internet. We have installed ESET Remote Administrator 6, agents, and Endpoint Security 6. I want to know what ESET's URLs to whitelist (so that no user authentication is needed to download updates, activation task and new software releases from ESET) Is hxxp://*.eset.com sufficient for virus definition update, activation, and software releases? Please advise, Zack
  • Create New...