Jump to content

tomha

Members
  • Posts

    41
  • Joined

  • Last visited

About tomha

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Austria

Recent Profile Visitors

833 profile views
  1. Description: Performance exclusion in-path wildcard support Detail: Possibility to use wildcards for performance exclusions in the middle of the given path, not only at the end For example: Exclusion: C:\Users\*\myFolder\* Reason: Software writing to the actual users %appdata% folder is compromised by realtime scanning. Multiple users are alternately working on the computer. So we need to set an exclusion for each users %appdata% path and do so if new users are added (especially problematic in Domain environments). We agree, that such exclusions are potentially unsafe, but to exclude C:\Users\*\myFolder\* is more secure than excluding C:\Users\*, what we have to do now.
  2. You mean for example C:\Users\*\AppData\myFolder\* will work as performance exclusion. I believe to remember, that * in the middle of an exclusion path will not work.
  3. We need a possibility to exclude %appdata% respective a subfolder of %appdata% from realtime scanning for all users eventually using this computer(s). For explanation: A Software running on the computer creates and accesses temporary files in a subfolder of the users %appdata% folder and sometimes crashes when it tries to read or write the temporary files. When i set a realtime scanning exclusion for the actual logged in users %appdata% folder no more crashes occur, so it seems to be a timing issue. The error occurs very rarely(1time a week), but never occured when the logged on users %appdata% was excluded from realtime scan( We did this manually for the specific user). But the computers are in a domain environment and used by different users, so we need to set a exclusion for all domain users %appdata% folder. Any hints?
  4. Problem solved - I once again removed the Agent, rebooted and reinstalled the agent, after some minutes both agents connected to the Server. Status.html did not show any error (all green but no last replication). The trace. log showed the error i pasted in my initial posting.
  5. Two clients stopped connecting to the ESMC Server after upgrading the Agent to V7. I tried to remove the Agent and reinstall but unfortunately there see,s to be no way to get the clients to connect. There is a suspicious entry in the trace.log: 2018-09-01 08:31:03 Information: Kernel [Thread 880]: Initializing module ERAG1ClientConnector 2018-09-01 08:31:03 Information: ERAG1ClientConnector [Thread 880]: <CONNECTOR_MODULE> exception class Era::Connectors::G1ClientConnector::no_installed_product occurred at ProductOfflineConfiguration\WindowsProducts.cpp:56. Product not installed. 2018-09-01 08:31:03 Error: ERAG1ClientConnector [Thread 880]: <CONNECTOR_MODULE> No module is subscribed for message StatusLog_APPLIEDPOLICYPRODUCTS_STATUS (10405) 2018-09-01 08:31:03 Error: ERAG1ClientConnector [Thread 880]: <CONNECTOR_MODULE> Publish msg of type StatusLog_APPLIEDPOLICYPRODUCTS_STATUS failed 2018-09-01 08:31:03 Information: ERAG1ClientConnector [Thread 880]: Connector was deactivated. No tasks will be processed and no logs will be produced.
  6. sorry Marcos, i failed: Component Upgrade Task now works to upgrade Clients agents from 6.5 to 7.0 Congrats to eset for the very fast correction of this issue.
  7. I can confirm, that "ESMC component upgrade task" now, was successful to upgrade a clients Agent from 6.5 to 7.0
  8. @ Marcos: ru sure: "Agent can be upgraded by sending an ESMC component upgrade task to clients. "?? This didn't work on any client at our site. We had to create a "run command" Task to download and upgrade the agents at client side.
  9. @Marveltec: Please specify why a "run command" task mentioned in https://support.eset.com/KB6819/ "III. Agent upgrade using Run Command Client task" does not work.
  10. Yes i already upgraded the agents using "run command" tasks, Just wondering what the ESMC component upgrade task is for?
  11. Steven, i can confirm, that the Eset Plugin for Automate seems to be broken. We also cannot create or edit ERA Policies because the policy editor shows a blank screen. We are on ESMC 7.0.553.0 , Automate 12 Patch 8, Eset Plugin 2.5.2.0 The ERA Plugin logs do not show any relevant entries. We do not use the Automate Plugin often, because we manage our clients via ERA/ESMC, so i cannot tell when it got broken. Regards Thomas
  12. I did an upgrade of my ERA Server to ESMC7 which went flawless. After upgrading i tried to upgrade the agent of the Server itself and a clients agent to V7 using a ESMC Component upgrade Task. The task finished successful but the agent version stayed at 6.5.522.0. A manual execution of the agent installer msi at the server itself installed the V7 Agent. So does anyone know, how to get the ESMC upgrade task working on Client side to upgrade the agents, since updating the agents manually is no option?
  13. The Eset Support Team seems to have fond a glitch with parsing of lnk files. I was told, this problem will be solved by a module update.
  14. @ Peter Thanks for your reply. I ran Procmon while doing a startupscan and it seems ekrn.exe tries to access all entries of the systems path variable wit some "\..\" added and then the "C:\Windows\syswow64\reserver30\" added. - Screenshot attached. No clue why ekrn.exe does this, where it gets the path from and why it seems to find a file under this strange path. As you suggested i opened a ticket at the local Eset support and provided the logs. Regards, Thomas
×
×
  • Create New...