Timos

There should be no problems when 6.5 comes out. These versions are compatible. You can check it also in future versions: hxxp://support.eset.com/kb3690/

I recommend this: Short version: Backup your tomcat installation or whole machine Uninstall tomcat/webconsole Install tomcat/webconsole using Setup.exe Apply again your custom changes you did in tomcat earlier (SSL cert, ...) Long version: Use Setup.exe (according version to server, 6.4 in your case) to uninstall webconsole/tomcat. Tomcat uninstaller will ask you if you want to delete webapps directory, accept it. Run Setup.exe again Setup.exe now lets you to install webconsole/tomcat only. Tomcat is now hardened by Setup.exe: selfsigned ssl cert, sslProtocol, ... Tomcat is up and running now. Try to login into webconsole, it should work. You have to apply your custom changes, your custom ssl cert. You know better what was your changes. If you did not applied custom changes to tomcat/webconsole, you can skip step 6, and it is easy I use this quite a lot when testing ERA, you shouldn't get in any big troubles.

Releases of ERA always contains newest Tomcat 7, but upgrade task applies only to webconsole, not to Tomcat. Your 7.0.55 is from your first installation. For more security I recommend to use another machine which will serve only webconsole: You have installed ERA Server on machine A. Install webconsole+tomcat on some machine B with all-in-one installer. (Possible if you run Setup.exe from commandline with parameters: Setup.exe --mode webconsole). Before install, you can substitute tomcat installer with newer version of Tomcat 7. You must use all-in-installer with same version as the server is, because webconsole and server wouldn't work together. Set up tomcat to your needs (you mentioned ssl cert). Set up webconsole to connect to ERA Server on machine A. It is possible by configuration file located in C:\Program Files (x86)\Apache Software Foundation\Tomcat 7.0\webapps\era\WEB-INF\classes\sk\eset\era\g2webconsole\server\modules\config\EraWebServerConfig.properties (default: localhost 2223). For more security, you can set here public key of ERA Cert Authority which signed server certificate. Webconsole would then connect only to servers, which authenticates by certificates signed with this CA. Set firewall to allow tcp connections from machine B to machine A on incoming port 2223. Advantages are: On internet is exposed only machine B with tomcat/webconsole. If some attacks it, there is less chance, they will get to ERA database, where are all data are stored. Machine A still exposes to internet only port 2222, where agents connect. You do not have to backup machine A when setting this up. All of the setup is performed on machine B.

You can create policy for Security Product with disabled firewall, and then assign it to clients or groups.

Googling for the error gave me this result hxxp://databasebestpractices.com/sql-server-configuration-manager-access-denied/

I think it requires SQL Server 2008 R2. If it's possible I'd recommend you to install SQL Server 2014. Follow the instructions hxxp://support.eset.com/kb3671/ Be careful. If you are installing 2 different versions on same machine: https://msdn.microsoft.com/en-us/library/ms143694.aspx You should be careful, another SQL Server can interfere with applications already using the 2008 SQL Server. Backup your data before major changes like this. I recommend you to install on some clean system, Setup.exe will install SQL Server without user interaction a and set it up for ERA packages.

Hi vanroy, Because of limitation of Microsoft SQL Server 2014 Installer, it is unable to install it from folder path with special characters (the wider characters than 16 bits). To resolve your problem, please copy contents of ESET All in one installer (Setup.exe and files in the same directory) to some folder path with simple characters (for example C:\EsetInstaller\) and run Setup.exe from there.

If above doesn't help: 1. Start notepad (or whatever text editor you are using) As Administrator and open server.xml 2. There should be line with <Connector and port="8080", change that port to something else, for example port="9080" 3. Webconsole should be accessible on https://localhost:9080/era

Please try access webconsole on hxxp://localhost:8080/era

Better solution for step 5 is: Rename era.war to era.zip. Rename "era" in webapps to "era_backup". Extract era.zip in to "era" in webapps Why? If Apache Tomcat is installed by All in one installer (Setup.exe), Tomcat runs as network service, so it cannot write to disk, thus it cannot extract era.war package into webapps.

Try restart the services or machine. Try CTRL+F5 in browser. I have no other ideas for now.

Importing CA that signed Agent certificates into the Trusted Root Certificates on server machine should work. Server will accept these certificates. (It must be in Computer account, not My User nor Service account) BUT, agents will still reject server certificate unless they have CA that signed Server certificate. If they get this CA in installation, they should accept Server certificate.

Ensure SQL Server is listening on port 1433. If it did not help, try using database type "MS SQL Server via Windows Authentication" on port 1433 instead of "MS SQL Server"

Everything you need can be set in server's Generate Report task - How can I get report by date interval / monthly Set trigger in task- How can I export/save the report Select Save to file or Send email.- How can I export Client list as HTML/TXT/CSV Set this setting in task, choices are PDF, Postscript or csv. We have also help page for reports hxxp://help.eset.com/era/6/en-US/index.html?reports.htm

This will be fixed in new version. Apache HTTP Proxy will be installed, but configured access to ESET servers only.