Jump to content

roga

Members
  • Content Count

    84
  • Joined

  • Last visited

Profile Information

  • Location
    U.K.

Recent Profile Visitors

785 profile views
  1. Thanks for all your help @MartinK Everything now resolved.
  2. Hi @MartinK That all worked nicely, and once the server connected to itself, the upgrade task went ahead. One last question, as I have now deleted the traceAll file in the logs directory, will the logging go back to default on next restart?
  3. OK that makes sense: it is a vm and we moved it from one host to another. A little bit annoying, we had some backup software that did the same. I'll try and follow the documentation and let you know how I get on. BTW I haven't quite got the hang of those "blue numbers" yet - when I click on them it goes to a page with lots of reports, but it is not obvious what I have to do next. Thanks for the response and going through those logs.
  4. OK service is running, and only way to restart service (after "traceAll") is to reboot computer, I'll post most recent entries of log when server come back up. See attached part of trace log since reboot and status html in zip. NB name of domain has been replaced by "organisation" Hope the attachments help diagnose the error. regards Roga sample-trace.log status.zip
  5. I have: ESET Security Management Center (Server), Version 7.0 (7.0.577.0)ESET Security Management Center (Web Console), Version 7.0 (7.0.429.0) It all functions well in general, however it has lost contact with it's own agent - last contact was in November 2019. And now of course it won't upgrade to the latest version. BTW We do have a password on the agent. Any idea of how I can get the agent to re-register?
×
×
  • Create New...