[Migrate VA from CentoOS to Rocky Linux, no errors, but can't login to web console - communication error]

I was able to configure LDAPS with help from Eset support. Same settings for Kerberos as CentOS and NTP server configured in chrony on Rocky Linux. 

[Migrated VA to Rocky Linux but cannot create new Client Task]

Do you have clients with Outdated version? If the clients are Up-to-date, that menu will not appear

[Migrate VA from CentoOS to Rocky Linux, no errors, but can't login to web console - communication error]

Thank you Marcos, the solution worked perfect!

Another situation after migrating some PCs and servers:

On all Windows Server 2016 Standard (I have few) in console appear Configuration module has malfunctions. I've tried clear cache on client side and few restarts, but the message from console still remain. On client side (Windows Server 2016 Standard with Eset Server Security) I don't have any error.

P.S. I've seen that someone posted about LDAPS integration. This is also not working, will appreciate a procedure/update for it.

 

 

[Migrate VA from CentoOS to Rocky Linux, no errors, but can't login to web console - communication error]

I've tried to migrate, I reinstalled the Rocky Linux VA 6 or 7 times without any error. I've tried with same IP and different IP methods. When I want to connect first time to Web Console with Administrator password I receive communication error. I've tried with Edge and Chrome from different computers and also with incognito mode. Searching the forum, I found that maybe it's something from Tomcat chiper config, but without success. Last time I installed Rocky Linux VA without pulling database from the other server, this is how logging in the web console works. 

 

Centos VA is up to date with the latest updates from Eset

[Endpoint Security can't connect to Push Notification Service]

I have CentOS VA as console, I updated only my laptop to version ESET Endpoint Security 9.0.2032.2   and I have also this error. The firewall permit the ports/IPs to ESET Push Notification.

[Login failed after update to ESET PROTECT 8.1.13.0]

Hello,

 

After update the VA (based on CentOS) to ESET PROTECT 8.1.13.0 I am unable to  login to console at first try. I have an AD group for ESMC administrators. Before update it worked like charm.

 

I tried with all browsers: Chrome, Firefox, Edge, IE, same behavior:

 

1.       If I login first time in a browser, or after clear cache, it works with AD user:

 

2.       If I login second time with tick on Log Into Domain, I receive this:

 

3.       If I fill any other input, also non existent local user, without tick on Log Into Domain, will give error, and after that if I tick Log Into Domain and use my domain user, it will work.

4.       Now works with domain user

 

5.       The error from log is: Error: CServerSecurityModule [Thread 7f1c41970700]: AuthenticateNativeUser: Native user login failed

[Bug after update to ESET PROTECT Console - Version 8.0.19.0]

still nothing changed

[Bug after update to ESET PROTECT Console - Version 8.0.19.0]

After update, in Widget Product version status, Mobile appear grey and devices Unknown, as in attach. In Android devices both devices apear correctly, without any problems.  The platform is VA (CentOS)

[Migrate ESMC from Windows Server to ESMC VA]

Is there any posibility to migrate ESMC installed on Windows server with MS SQL on ESMC VA based on CentOS with MySQL? I found the procedure with the certificates to migrate the agents, but if I want move the data base from MS SQL to MySQL I must install ESMC from scratch? (I dont want to keep ESMC on CentOS connected with MS SQL because I have only around 250 clients)