[Automatic deployment of agent only on unknown computers]

This is unlikely to happen.

• If there is no Agent on the client, it can not be evaluated and assigned under a dynamic group. Therefor you have no triggering mechanism on those computers. (It is not possible to trigger a task when a new computer joins a static group)
• Other problem is, that you would need to have the same Administrator password on each client (so the Server task's settings are working on each).

[MySQL Error message]

Hi RandyWang, I am not sure if this could help to you, but for certain cases of failed database migration 6.4->6.5 there is a process how to fix it: http://help.eset.com/era_install/65/en-US/index.html?crashed_database.htm

This is rather experimental/advanced process, so be careful and do not forget to backup your database before.

[Mac Firewall VNC issue]

Hi, ::ffff: is a subnet prefix for IPv4  addresses inside the IPv6 network. (32bit in 128bit space), basically it is repleacing 0000:0000:ffff:0000, and it is helping the IPv6 processor understand the IPv4 address, that is why it is working only with that prefix.

[ERA server behind reverse proxy (ARR)]

Hi, to route ERA Agent requests on port 2222 you need to use ERA Proxy component. It is designed to forward Agent/Server communication.

Have a look at the documentation:

http://help.eset.com/era_install/65/en-US/index.html?arch_proxy.htm

http://support.eset.com/kb3639/

 

[Make sure that Agent runs with Administrator privileges]

You are welcome, it is mentioned in the documentation (along with other info here: https://help.eset.com/era_admin/65/en-US/index.html?client_tasks_run_command.htm)

If you want to ask more, you can start a new thread or find one that is similar to your question and join the discussion.

[Make sure that Agent runs with Administrator privileges]

Hi ewong, agent is running on windows as Local System user and this can not be changed. Can you be more specific about your issue?

[Certificate error after resote database ERA server]

Hi, you can do it in the same way you did it, because if hardware is crashed, certificates are not revoked. When the certificate is revoked, it is put on blacklist. If there is software or hardware crash, revoke is not happening, so db restore would work.

[Certificate error after resote database ERA server]

Hi, Clients which got the information about the revoke, those are not working, others are. You should not revoke the certificate which you are planning to use in the future.

Even in the manual, https://help.eset.com/era_admin/65/en-US/index.html?admin_cert_peers.htm

there is information about that:

Quote

The revoke action is irreversible, you will not be able to use a certificate that has been revoked. Make sure there are no ERA Agents left using this certificate before you revoke it.

 

[Certificate error after resote database ERA server]

Hi, I think the problem is, that you deleted (revoked) your peer certificate (agent), this was however replicated to only few agents and after db restore, you can not connect those agents which were revoked.

Solution would be, do not revoke the peer certificate, just restore the db.

[Certificate error after resote database ERA server]

Hi hungtt, what about original ERA server, did you removed it? Or you have just switched it off and created a new one? What about IP address?

[Clean Installation - same IP address ERA server]

Hi Hungtt, in the guide you used, there is no notion of importing peer certificates, only:

Import all CAs that you have exported from your old ERA Server. To do so, follow the instructions for importing a public key.

Where CAs are Certifiaction Authorities, so as MichalJ wrote, there is no need to import peer certificates.

If you have imported CAs and changed the server certificate (in Server settings) to use the exported one, it should work.

[Certificate error after resote database ERA server]

Hi hungtt,

according to your log, you have a problem with certificates.

• Why did you backup DB and  then deleted certificates?
• Was that agent different from others?

 

[Apply ERA policies to AD groups?]

Did you try running Static Group Synchronization?

https://help.eset.com/era_admin/65/en-US/index.html?sg_server_tasks_synch.htm

[ERA Administration Guide]

Thank you for suggestions,

I would not expect big changes in current version of the documentation, however we will consider your ideas and work on them to deliver better documentation for next major release.

Regards

J.

 

[ERA Administration Guide]

Hello bbahes,

The documentation is growing together with the product so sometimes there can be an inconsistency. Thank you for pointing this out, we will try to improve it.

I agree, if you read the PDF document from start to end, some topics may look inconsistent. This is because we did not intended it to be read like that. The PDF document you have is exported from Online Help which has a different conception.

What would you suggest to change in the documentation? (except those chapters 3.3.2/3.3.1)

[migrate from ERA 6 on Windows to ERA VA]

Hi MaxW, there is a KB article about migration from Windows Server to ERA Virtual Appliance.

hxxp://support.eset.com/kb6355/

[Deployment agent via .bat]

Hello, I am not sure what do you mean by

 

on the site of Eset by a road network on the server.

 

This chapter in Online Help (hxxp://help.eset.com/era_admin/64/en-US/index.html?agent_live_installer.htm) describes how you can modify the source path for installer in the .bat file.

Is that what you need?

[ERA 6.1 clients not updating from server]

More about MySQL configuration for ERA:

• for Windows
• for Linux

[ESET Remote Administrator on Debian, installation issue]

Hi, I would recommend you to:

1. backup your database (if you have any)
2. uninstall mysql-server and uninstall ODBC connector (unixodbc libmyodbc)
3. download and install mysql-server from official MySQL page hxxp://dev.mysql.com/downloads/repo/apt/
4. download and install latest Generic Linux ODBC connector from hxxp://dev.mysql.com/downloads/connector/odbc/

• Look at MySQL official documentation 
• Look at this article, it is similar to your problem. Do not follow it exactly, it is for other Linux distribution.

[Error: Admin connection not working. Unable to continue]

Hi, try to follow the installation process of ERA Server on SLES described in the KB article.

[Eset remote administrator change name server]

I would recommend to try this, it may be cleaner way than editing tables.

[Error 1603 on Windows Server 2012 Standard]

I had similar experience when installing ERA All in one installer (6.3) x64 on Windows Server 2012 r2. Installation crashed during the Agent installation. I was installing from a shared directory. After the installation failed, I copied files to local folder, installed rest of the components separately (manually), then ERA was working properly.