Jump to content

Pinni3

Members
 View Profile  See their activity

  • Posts

    201

  • Joined

 Content Type 

Posts posted by Pinni3

    error HTTP 404 – Not Found afeter upgrade era 6 to 7

    in ESET PROTECT On-prem (Remote Management)

    Posted

    No. You must login into Your console and go into installers. Then You need to prepare new agent installer. When You finish (remember to hit IP adress instead of name..., if You have that server name in Your local dns You can put name) download version for linux. It will be as sh file with Your console IP and certifcate...Just launch that sh file generated from console...thats it

    HTTP ERROR 404 after Upgrade 6.5 to 7

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by Pinni3

    There is one point that says, You need to backup + restore file within webapp folder

    Quote

    C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\webapps\era\WEB-INF\classes\sk\eset\era\g2webconsole\server\modules\config\EraWebServerConfig.properties

    and more...

    Look at 5. Upgrade Apache Tomcat and install ESMC 7 Web console :

    Quote

    Restore .keystore, server.xml and EraWebServerConfig.properties to their original locations.

    I belive You did that right ?

    error HTTP 404 – Not Found afeter upgrade era 6 to 7

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by Pinni3

    I did same upgrade yesterday. All You have to do is upgrade java up to version 8.

    Then You need to :

    1) stop tomcat

    2) move Your era webapp directory to other location (there is one config file You will need after upgrade)

    Quote

    /var/lib/tomcat7/webapps/era/WEB-INF/classes/sk/eset/era/g2webconsole/server/modules/config/EraWebServerConfig.properties

    3 unpack era.war to same location as older one was (and copy there file I mentioned in point 2)

    4) run installation of era server : ./era_serv_file.sh --skip-licence

    5) start tomcat

    6) run point 9 of instruction I pasted

    7) log into console and generate new agent installer for linux, download it and install

    And You are ready to go

    Remote Administration - Info

    in ESET PROTECT On-prem (Remote Management)

    Posted

    You should know how many computers will go to Your console, as it a matter of resources. From my point of view, You should start learning new console from scratch. Install one of them on Your testing hardware, install agent on other testing computer and start to play with it. Console in version 6 is way different than it was in version 5. It's similar in some cases to active directory managing.

    Also there will be some complications :

    • are there any other local administrators or only You ?
    • do You want to have control over those environments and eset agents on those PC or not
    • and many many more

    If Your environment going to be in enterprise scale, I belive that linux version of console will better perform. There is also large KB available for download...so go check it out :)

    Unable to activate Eset Endpoint Security on Mac

    in ESET PROTECT On-prem (Remote Management)

    Posted · Edited by Pinni3

    dont worry mate :) one day I had similar problem. Our a/c in room was broken...almost 3 weeks. And it was friday, I thought : I will check console. After login I saw new package so I decided to be a good admin and I did upgrade..Problem was I have licence for endpoint antivirus. It was couple of seconds and i had over 1500 units with security and activation problems screaming on them :D so like they say : sh*t happens :)

    New Install Error 1920

    in ESET Endpoint Products

    Posted · Edited by Pinni3
    add note

    Try this :
    https://support.eset.com/kb6468/?locale=en_US&viewlocale=en_US

    and You can also check this one
     

    Quote

    Try this solution:

    Go to Start > Run > and type regedit

    Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control

    With the control folder selected, right click in the pane on the right and select new DWORD Value

    Name the new DWORD: ServicesPipeTimeout

    Right-click ServicesPipeTimeout, and then click Modify

    Click Decimal, type '180000', and then click OK

    Restart the computer

    Cause:

    The Microsoft Windows Service Control Manager controls the state (i.e., started, stopped, paused, etc.) of all installed Windows services. By default, the Service Control Manager will wait 30,000 milliseconds (30 seconds) for a service to respond. However, certain configurations, technical restrictions, or performance issues may result in the service taking longer than 30 seconds to start and report ready to the Service Control Manager.

    By editing or creating the ServicesPipeTimeout DWORD value, the Service Control Manager timeout period can be overridden, thereby giving the service more time to start up and report ready to the Service.

    Reference case:

    Reporting Server Error 1053: The service did not respond to the start or control request in a timely fashion

    and if there is still problem, provide logs like Marcos wrote

    Remote software repository list is empty

    in ESET PROTECT On-prem (Remote Management)

    Posted

    30 minutes ago, russell_t said:

    Working again for me as well.  I know this has happened in the past once or twice as well but usually it came back quicker.

    Is there any suggested remediation when/if this occurs again?  Are you changing the DNS entry of the repo server so we should flush DNS caches or is it some other internal issue where we can't do anything that would help? :)

    From what I know, ESET servers have static IP's so dns entry wont change nothing. I suggest to stick with autoselect but Im not crew member so I can be wrong. From my point of view I can tell You that Im with ERA 6 almost from first release date, I use ERA as my daily task and I monitor it all the time and from my memory I can read 3 fails of repository (almost 3 years of using it). So its not as bad ..... :)

×
×
  • Create New...