Jump to content

wind-e

Members
  • Content Count

    20
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    USA
  1. Does anyone have any ideas on how to clear the server log queue?
  2. We recently upgraded our ERA instance (and half of our end user agents) to version 6.4, and about a month later to version 6.5. Most agents are on currently on 6.5, but there are still some lingering 6.4 and 6.1 end user agents. We used to use the “Remote Administrator Agent – Application Reporting – Report all installed” policy in ESET Remote Administrator to report all applications on our endpoints (see first screenshot) in version 6.1. This policy is no longer being applied to any computers (see second screenshot) in version 6.5. While we upgraded
  3. Hey hey, what do you know? "--silent" and "--accepteula" runs the install in it's entirety (albeit installer is seen during the entire run)! I'll play with it some more next week and see if there's any other combinations that might work to get it silent. Thanks @MartinK -- if you come across a way to make it please silent let me know.
  4. I've created a few different all-in-one installation packages from the ERA Web Console (some with policies specified, some without, some with parent group specified, others without) and I can't seem to figure out why the silent installation of these packages aren't working. I can run them normally (non-silently) and they run and complete just fine. I've followed the steps here on how to run a silent install using the "--silent" and "--silent --avr-disable" parameters, but while the installation appears to start (the ESET package wizard actually appears), it ends after only a few se
  5. hxxp://support.eset.com/kb5949/#ERA Technically not in upgrade instructions, but it's still documented. ....I didn't read this either beforehand.
  6. @CraigB Just finished trying to upgrade to 6.5 again. This time it was a success! Took about 1 hour.
  7. I plan on trying again tomorrow or Friday and will share results. Do you know if ERA was actively running a task at the time of your upgrade? I believe mine was (whether or not that matters, I'm not sure), and that's really the only thing I'm going to do differently this time (besides waiting a day for it to complete).
  8. Thanks @MartinK. The database was large (this was due to a configuration mistake in which there were 2 Agent tasks to report installed applications). It seems we did not wait long enough for the database to complete it's upgrade and we corrupted it. Fortunately, we were able to restore both the 6.4 ERA server and the DB (hosted separately) successfully. We will try upgrading again and have more patience this time (we now see not waiting long enough is a known issue )
  9. Hello, We've upgraded ERA from 6.4.29.0 to 6.5.522.0 using the ERA Component Upgrade task. Everything went fine during the upgrade and seemed to go smoothly, however, after trying to log into the Web Console afterwards we received "Login failed: Connection has failed with state 'Not connected'" after providing our credentials. We gave it 30 minutes to connect to the database (which is hosted on SQL Server 2008 R2 instance on a different VM) and still received the error. We then tried restarting the ESET Remote Administrator Server service, but it just hung on "Stopping" indefi
  10. I wonder if choosing an IP address will be available in ERA 6.5? Any beta testers know?
  11. Following up to post install of hotfix. It's been 3 weeks (21 days) and have not experienced hanging issue. We plan on rebooting server tonight for unrelated reasons for the first time since hotfix was applied.
  12. Installed hotfix from Microsoft as mentioned by @pesphil in post #12 over the weekend. Though it's only been a couple of days, so far so good. I will follow up 2 or 3 times over the next few weeks and post status. Hopefully this resolves the issue. @czechoto, are you having the same issue on Server 2012 R2? Please keep up posted, thanks!
  13. We too are experiencing random hangs (every few days to couple weeks) on Server 2008R2 server using version 6.0.120.25. No event logs, no memory dumps generated, and no ESET logs provide any kind of clue. Does anyone have any updates/fixes yet? I'm debating if I should even upgrade to 6.0.12035 as it seems this version has the same issue. @czechoto, any feedback from Polish support team? @tomha, any crashes after disabling Protocol Filtering yet? I may give this a try as it seems to be the only suggestion other than completely uninstalling.
  14. My situation is almost the same as yours and I found a way to make the LiveAgent silent and download from your own source. Silent install of Agent Open the batch file created by the Live Agent Installer. Do a search for /qr and and change it to /qn. This will make the MSI install in quiet mode with no GUI. Redirect source of Agent Secondly, within the same batch file, find the links that point to the online ESET repository. Simply change the URLs to your UNC paths.
×
×
  • Create New...