Jump to content

ewong

Most Valued Members
  • Content Count

    186
  • 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,167 profile views
  1. As @Martink mentioned, this isn't an issue with being blocked by a firewall. We are talking about http and not some different protocol. Furthermore, it's an indication more on the server not finding the said package. If it was a network issue, you'd see something along the lines of "Cannot find or access http://repository.eset.com". That said, the first item in the log you showed seems to point out something else. "4 Unexpected error while processing..."
  2. Hi, Using the new MirrorTool, I'm still getting an error when trying to download the updates: 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: em049_64_l1.nup. Downloaded: 0 % 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: em024_64_n7.nup. Downloaded: 100 % Update status for product 'era6' changed to: Updating Downloaded: 100 % Update status for product 'era6' changed to: Finished Perform full mirror finished Uninitialization Uninitialization finished Creating mirror for product: ep7. Mirror type changed to regular Initialization Initialization finished Perform full mirror started Update status for product 'ep7' changed to: Preparing structures and analyzing Downloading file: update.ver.signed. Downloaded: 100 % Update status for product 'ep7' changed to: Downloading files Downloading file: em049_64_n8.dll.nup. Downloaded: 58 % Update status for product 'ep7' changed to: Finished Perform full mirror finished Uninitialization Uninitialization finished Error: Perform full mirror failed with error: Error creating file. Error code is: 4118 Error occured. Though the error # is different. So perhaps a transient issue? (been trying a lot of times.. still getting that error) What does the 4118 error code mean? I've checked and I do have enough disk space. Thanks! Edmund
  3. I think it's under %PROGRAMFILES%\Apache Software Foundation\apache-tomcat-<version>\conf.
  4. 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
  5. 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
  6. Well, ended up the problem was twofold: 1) Java path was there, except not complete. Was missing some files. 2) Required a reboot. Edmund
  7. 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
  8. 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
  9. 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
  10. 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
  11. Description: - Include a REST API in ESMC so that the administrator can gather information without needing to log on to the ESMC. Detail: - The ability to run customized data-gathering scripts against the ESMC gives the administrator better ability to grab the information he/she wishes without needing to fiddle with the Report generator or in fact any aspect. (Though, tbh, I'm not sure which would be a burden.. supplying REST information or having the user generate reports..etc). Thanks!
  12. Description: Enable MirrorTool to have an 'update-repo' mode Detail: As far as I can understand the MirrorTool usage, when I run the following command: MirrorTool --intermediateRepositoryDirectory /tmp/repo --mirrortype regular --repositoryServer AUTOSELECT \ --outputRepositoryDirectory /mirror/repo --languageFilterForRepository en_US It deletes the existing /mirror/repo contents and start all over again. Perhaps include an 'update' mode such that it'll just compare the current files with those on the AUTOSELECT server and find the files that are new.
  13. Description: Remotely reset Agents' information using a 'secret key' that will reset where the Agents report to. Details: At the moment, using the GPO method of deploying agents is 'simple' enough; but if the ESMC server suffers a hiccup/goes away(for some reason), the ESMC must be installed/reinstalled; thusly the old agents won't be able to communicate with the new ESMC server. Having the ability to set up a 'secret' on the EMSC that can be used to connect to all old-agents and have them reapply the new server information would make life easier. (At this moment, I'm still recovering from a server failure and can't seem to be able to get all of the agents installed properly via gpo, even with the new 'install_config.ini' file set up.) So having this kinda trouble, I've had to go into each system, run esetuninstaller and then have they run gpupdate to get themselves updated) and even then that's not working all the time. [note: I do admit that it is possibly a PEBCAK problem.] On the flip side, this could lead to security issues (particularly since this is somewhat akin to adding a 'backdoor'), so I'm not sure if this is a good idea.
  14. Description: Showing (or downloading) debug logs when tasks fail. Detail: Somewhat similar to my previous feature request, having the debug log generated during the task (akin to trace.log) and when it fails, there is a link to download the log file for that particular process. Rationale: It's to allow the Remote Administrator to figure out what is going on within the process without needing to go into the client's workstation.
  15. Description: Running tasks progress Detail: Currently (well I'm upgrading to the latest 7.x ERA with the 6.x component upgrade task), when I go to Client Task Executions, it states that the task is running. If there is a way (particularly with the Eset product-based tasks, for some sort of progress showing (and even an ETA (but I suspect this might be a bit tough)).
×
×
  • Create New...