Jump to content

GCG

Members
  • Content Count

    31
  • Joined

  • Last visited

1 Follower

Profile Information

  • Gender
    Not Telling
  • Location
    USA

Recent Profile Visitors

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

  1. just give us some credit or contribution credit
  2. We are a national MSP based in Chicago and while working with ESET to test the upcoming ESET ESMC 7.X release GCG decided that we wanted to upgrade the built-in version of Tomcat 7.x (32-bit) to version 9.0.10 (64-bit). This, of course, meant that we also had to update the Tomcat configuration and update our Java install. We don't want to bore everyone with the technical details, but we felt like the overall level of documentation available was lacking so we wanted to share the Tomcat configuration we are using to make configuration and upgrade of the Tomcat install easier for others
  3. We look forward to testing the G.A. release of the upcoming version 7 release
  4. Peter, My organization is interested in being apart of your beta test group for this and other products. Robert GCG
  5. This is likely happening because proper exclusion rules have not been implemented on the server in question. I would recommend that you disable parts of the application one at a time to see if you can narrow down which part of the application is causing the high CPU usage issue in your environment. once you identify which part of the ESET application causing the high CPU usage I would recommend focusing on making sure your settings are configured properly to for your business and environment requirements.
  6. A) I would recommend restarting the server into safe mode so that you can be sure that the application is not running. B) I would then use the "SC delete" command to delete the actual service. I would then take the directory and create a password protected (make sure it is password protected) archive using WinRAR of the entire directory at the folder level of "C:\program files (x86)\common files\sys" Please note: I am recommended this for the following reasons: 1) so that you can ensure even hidden folders or files are captured in the archive and 2) so you can rest
  7. We also had an instance today of a user's laptop not startup up normally, extended windows startup time, logon process slow to respond, user desktop unresponsive after upgrading the ESET agent from 6.4.283.0 to 6.5 and after disabling HIPS completely on the machine all issues went away. We then re-enabled HIPS but left self-defense disabled and user has had no issues since.
  8. ESET ERA component upgrade iinitiated from ESET ERA web console between 15:21:49 and 15:32:36 - Result: FAILED Below are examples of blocking action taken by ESET (NO CUSTOM RULE, BUILT-IN RULES ONLY IN EFFECT) We also are investigating the possibility that HIPS is preventing Acronis backup software from working normally.
  9. Marcos, We also posted this in another thread, but we tried initiating an in place agent upgrade using ESET ERA Server 6.4. to upgrade a few test clients ESET Agent application from version 6.4.283.0 to 6.5 and the upgrade failed. The computer is pretty vanilla and doesn't have much loaded. logs show that ESET blocked installer and several other processes from modifying the ESET Agent application. Time;Application;Operation;Target;Action;Rule;Additional information 3/21/2017 3:43:36 PM;C:\Windows\System32\wbem\WmiPrvSE.exe;Get access to another application;C:\Program Fi
  10. We see our own log files is that if you have HIPS - Self-Defense enabled it shows that ESET blocks actions against its own product, even a inplace upgrade of the ESET ERA 6.x Agent initiated from the ESET ERA console. We tested this today, and captured over 100 different events in the HIPS logs (you have to manually enable logging for all blocked operations (AntiVirus Section - HIPS Section - Advanced Setup (click plus symbol) - log all blocked operations (Enable). If you do not enable this feature operations blocked by built-in rules are not logged to the HIPS log in ESET.
  11. We are seeing some potential issues with ESET HIPS self-defense and Windows during upgrades of the ESET clients or ESET ERAS components. You might try enabling logging of all blocked actions under HIPS to capture such actions that are happening behind the scenes. Here are some examples of the items we are seeing logged and being blocked by ESET HIPS. We do not have any custom HIPS rules in place so it is odd that ESET is even block itself according to the logs. it appears from the logs that HIPS could be contributing to some of the issues people are having when upgrading E
  12. Just an FYI, We manually downloaded 6.5 and pushed it out to a few test machines in our environment. We were still able to administrate it with ESET ERA 6.4 but we had to adjust the several policies as 6.5 introduces several new settings and changes how alerts are displayed on the actual machine versus the ERA server. ESET ERA server policies can be adjusted without having any ESET EFSW 6.5 clients deployed.
  13. New 6.5 documentation was released today and made available. https://download.eset.com/com/eset/apps/business/era/suite/latest/eset_era_65_era_admin_enu.pdf https://download.eset.com/com/eset/apps/business/era/suite/latest/eset_era_65_era_deploy_va_enu.pdf https://download.eset.com/com/eset/apps/business/era/suite/latest/eset_era_65_era_install_enu.pdf https://download.eset.com/com/eset/apps/business/era/suite/latest/eset_era_65_era_smb_enu.pdf In the past our experience has been relatively smooth with ERAS upgrades when you use the Built-in admin account to initiate t
  14. We wanted to let people know that we see that version 9.5 has been released and made publically available. Like many of you we also have been encountering issues with clients downloading updates since the beginning of march. Does anyone know if it is related to program or feature updates that were released?
×
×
  • Create New...