rbrookbanks

I've found a couple of issues upgrading Remote Administration/Management from V6 to V7 that may help someone in future. Firstly the install fails with an error message "localsystem is not a valid user or group" if the service is running on a DC as in SBS. Change the service account to the DOMAIN\administrator account, restart the service and you can run the upgrade. (.\Administrator didn't seem to work) Secondly if you follow the instructions here https://support.eset.com/kb6925/ The upgrade will fail if your existing Apache is the x86 version as the new version is x64. When you replace the files in the new x64 version you'll have to edit server.xml to reflect the new path to .keystore C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\.keystoreC:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\conf\server.xmlC:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\webapps\era\WEB-INF\classes\sk\eset\era\g2webconsole\server\modules\config\EraWebServerConfig.properties It can be edited with Notepad, just remove the " (x86)" and it should work. No other files needed editing. Hopefully this is useful.

I've got an issue, it might be my lack of familiarity with the new product or a minor bug. When I look at the mail reports it seems as if only one of my servers is reporting it's spam statistics. If I look locally on the servers i can see the spam being blocked, yet if I look at the report in the RA it doesn't tally. Only one of my remote servers has ever reported. I've checked the filter and it's set to Mail Servers but I can't see anywhere in the RA console to verify which servers are included in that category. The servers are all reporting viruses found, but only one appears to be reporting spam. What settings do I need to check so that I can see all spam senders across all of my customer's servers in our RA console?

I've been stuck in the old can't install it, can't uninstall it loop for a couple of hours. I think I've finally got to the bottom of this one. There was an entry relating to the initial failed install in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\InProgress Prior to this I've run the uninstaller in /nosafemode (it's a production server on a remote site which can't be rebooted) emptied any temp files and manually checked the registry for any ESET entries and deleted them. Renaming the InProgress key allowed me to run a fresh install which seems to have cured it.

I'm just on my second upgrade of EMSX and both have failed. I've downloaded the installer, moved it out of downloads and unblocked it but both ended with "installation has ended prematurely." I followed the upgrade guide, it has fallen over both times immediately after the restart. Surely this should work? The only thing that may be non-standard is I installed the 6.2 agent on both servers prior to the upgrade. Unfortunately I can't keep testing this on live customer servers!