Jump to content

ewong

Most Valued Members
  • Content Count

    184
  • Joined

  • Last visited

  • Days Won

    1

ewong last won the day on December 13 2018

ewong had the most liked content!

Profile Information

  • Gender
    Not Telling
  • Location
    Hong Kong

Recent Profile Visitors

1,076 profile views
  1. I think it's under %PROGRAMFILES%\Apache Software Foundation\apache-tomcat-<version>\conf.
  2. ewong

    GPO policies

    I had major headaches doing the "GPO install Agent + AV" route. YMMV, of course; but, IMO, if you're going to just use GPO, it would make life easier if you'd just setup a policy that installs the Agent, and then use the ESMC 'Software Install' client task to install the necessary AV. again.. ymmv. Edmund
  3. Hi, Here are a few ideas that I have: Check if the Tomcat logs say anything. Check if the Tomcat service is running. Were there any firewall changes? You mentioned that you tried to connect to the MC and that it's not available. What exact error did you get? A 404? Cannot connect (i.e. not listening to any connections)? On the ESMC server, if you do a "netstat -na", is the port available and listening? Edmund
  4. Well, ended up the problem was twofold: 1) Java path was there, except not complete. Was missing some files. 2) Required a reboot. Edmund
  5. Hi @pctech1380, Yes, I also have encountered this though I haven't quite gotten to figuring out why it's happening. I think the logs might have something to say about it though. Edmund
  6. Hi, After suffering a system failure which took out the ESMC server, I had to install ESMC on a different server and after getting the appropriate things squared, I installed the all in one on a Windows 2012R2 system. Clicked on Ok by mistake and completely missed the URL for the webconsole. Anyway, after much searching I found it; but, upon logging in, and skimming through the welcome screens, the dashboard tries to load; but I eventually get the error "Error during dashboard has occurred". I click on OK, and am back on the screen but I've noticed that all the icons are missing. ;/ Just the text is available. I then try to go into the Server settings, but that managed to kill the ESMC instance as I'm booted out and can no longer go to the webconsole. I'm scanning the Server logs (those in the EraServerApplicationData), but I'm seeing some 'forcibly closed' messages. Tomcat has no logs stating why it's crashing. At least, not in the apache-tomcat-<??>/logs dir or in the Tomcat/logs dir. However, in the Event Viewer, I'm seeing "The Apache Tomcat 9.0 service terminated unexpectedly. It has done this 1 time(s)." Later on, I see another entry. That said, I'm suspecting I need to do a reboot as in the Event Viewer, I'm seeing a bunch of "Apache Tomcat terminating unexpectedly interspersed with some GPO warnings. Thanks Edmund
  7. Agent installation ending prematurely (which I also have encountered before... though what follows is a fuzzy recollection of what I did) tends to mean something (either in the registry, or in the eset directories) are preventing it from running. Firstly, make sure you're installing it with Admin privs. Secondly, check if the Agent is *already* installed (though if you check in the Add Programs (or Programs and Features..depending on the Windows version)), if the ESET Agent exists but with no installation date or whatever, it probably means something in the system has screwed up. The *best* thing to do is to grab the EsetUninstaller and go into Safe Mode and run it. It'll detect old installations. Just remove the installed versions with the EsetUninstaller. (can be downloaded from the ESet website). HTH Edmund
  8. Hi, I'm guessing that the DC002 is the system that the agents are trying to connect to? Do you have any agent policies set up and associated with the agents? Perhaps the agent policy setting has it on (i.e., you selected the Agent with proxy policy while creating the agent deployment packages? But IIRC, that is the default response. Have you checked that the ports on DC002 are allowing 2222? Edmund
  9. @Rami nope. I don't have a full disk; though not sure how I can find out if it is blocked. I mean, it downloads to 63% so it is downloading (*I think*); and if it was blocked (for some reason), wouldn't it have complained about it at the beginning? Going to try to do a packet tracing and see what's going on. Thanks Edmund
  10. It shouldn't be a problem since eventually, the computer's agent will reconnect with the ESMC. :ewong
  11. Well, I feel a bit dense, even with the information provided. It's my understanding that the command you ran was on the AWS instance and not your workstation (or whereever you access this AWS instance). Is the ESMC server behind a firewall? If so, do you happen to have the correct port-forwarding rules? If it's a system directly connected to the Internet requiring no firewall, then check the ESMC system's firewall. If it's a windows system, check the incoming port allowances. If it's a linux ESMC system, check for selinux and iptables rules. Edmund
  12. Just updated the MirrorTool and while the repo creation worked, the updates still fail as shown below: ============= UPDATES MODE ========== Mirror Tool, Copyright (c) ESET, spol. s r.o. 1992-2019. All rights reserved. Creating mirror for product: ep6. Mirror type changed to regular Initialization Initialization finished Perform full mirror started Update status for product 'ep6' changed to: Preparing structures and analyzing Downloading file: update.ver.signed. Downloaded: 100 % Downloading file: update.ver. Downloaded: 100 % Update status for product 'ep6' changed to: Downloading files Downloading file: em023_32_r0.dll.nup. Downloaded: 92 % Update status for product 'ep6' changed to: Updating Downloaded: 100 % Update status for product 'ep6' changed to: Finished Perform full mirror finished Uninitialization Uninitialization finished Creating mirror for product: era6. Mirror type changed to regular Initialization Initialization finished Perform full mirror started Update status for product 'era6' changed to: Preparing structures and analyzing Downloading file: update.ver.signed. Downloaded: 100 % Update status for product 'era6' changed to: Downloading files Downloading file: em045_64_n15.nup. Downloaded: 100 % Update status for product 'era6' changed to: Updating Downloaded: 38 % Update status for product 'era6' changed to: Finished Perform full mirror finished Uninitialization Uninitialization finished Error: Perform full mirror failed with error: Undocumented serious error. Error code is: 4122 Error occured.
  13. The first thing to check to see if the server's firewall has that port blocked. :ewong
  14. Hi, Where is this being shown in? The agent installation log or somewhere else? What operating system does this AWS instance run on? :ewong
  15. In theory, once the PCs have gone through the GPO software install, I believe they keep track of the agent 'version' and won't install it again unless you updated the GPO policy. Installing software from ESET's repository requires access to the internet. But since you've already gotten them deployed, I guess all's well. Edmund
×
×
  • Create New...