Oliver

MDM generates a list of enrollment tokens that are required for the mobile enrollment process after the installation is completed, or in case all the enrollment tokens are used. This can mean 2 things : a) a freshly installed MDM did not have enough time to generate the list of enrollment tokens for itself. b) All the enrollment tokens that were available for the MDM were used and the MDM need to generate another list of enrollment tokens for itself. Solution: wait a few minutes and try the enrollment again.

As mentioned in the relevant product documentation for ESET NOD 32 Antivirus - Business Edition for Linux -> 1.1 System requirements- > the antivirus requires: GTK+ 2.6 or newer. Which is absent in the CentOS.

Hello, this is not possible in the current ERA v6.5 (so I am not sure how you configured the notification for a static group). However, it will be possible in the next release (v7). But there is a workaround for this scenario. You can create a user with access rights for only computers in StaticGroup1 and another user with access right for only computers in StaticGroup2. and Create the Threat detection notification under each of them. This way the notification will report the events only for computers available to the user.

Hello, you can find the full list of variables here: http://help.eset.com/ees/6/en-US/?idh_config_notice.htm but the %URL% variable is not available. Can you please describe the scenario in which you would like to have such option?

Hello, Can you please specify a version of ERA? If it is Windows server based or ERA_VA? And also if you are the Administrator or if it was deployed for you?

Hello, what is the version of your ERA? Also, are you the administrator with full access rights? Or was it set for you by some MSP Administrator? If ERA 6.5 than you can see the notifications in Admin -> Notifications section. But ERA does not send any notifications on its own, only those that are set in the Notifications section.

Hello, bbahes. What exactly are you missing in the documentation of v6?

Hello, policies in ERA can be merged / combined in way that you will not replace the list on the client device , just add another setting to the existing configuration on specific device . Please follow this link for more information : http://help.eset.com/era_admin/65/en-US/admin_pol_how_policies_are_applied.htm

Hello, can you please describe what scenario do you have in mind ?

Hello Miami just to be sure: the certificate that is part of MDC Policy -> you exported it from ERA -> and imported according to the steps mentioned above. and than restart the MDC service ? If the troubleshooting steps above do not solve your problem, collect the logs with ESET Log Collector (according to these steps) and contact ESET Support.

Ok. So that is just a "visual bug" and everything else is working correctly. But if you want to "fix" it, there is a way. You can create a new ERA CA -> Generate(create) a new set of certificates and sign them with this NEW ERA CA and than , replace all those "old" certificates with those shiny new ones ( use these new signed certificates in respective policy and use the "force" option and assign this policy to all required devices). After you verify that the CA and certificates are working correctly and every device is using the new certificate-> you can revoke all other (not-so-shiny) certificates and CA.

Hello, Just to verify. Your issue is that the certificates are present twice and the column "CA is present" is under status "no" ? Or is there an issue with Agent connection due to the certificate duplicity? (you can see that in "status.html" on client device)

Can you please provide more information ? Is this a fresh ERA 6.5 installation or an upgrade from 6.4 to 6.5 ? What is the status of MDM component in webconsole ? are there any Warning / Error messages ? Are you using ERA CA + ERA-generated certificate or a 3rd party CA and a certificate signed by 3rd party CA ?

Hello, You need to import your HTTPS certificate into the certificate store on the MDM host device according to these steps : http://help.eset.com/era_install/65/en-US/index.html?certificate_mdm_https.htm

Hello, Can you please be more specific ? Do you want to run the all-in-one installation of ERA (http://help.eset.com/era_install/64/en-US/index.html?install_win.htm) in silent mode ? Or just the ERA server component (http://help.eset.com/era_install/64/en-US/index.html?component_installation_server_windows.htm) ?

Hello, can you please post the lines from the tracelog loop ? Also, just to be on the same page: you are using ERA CA ?

Hello, regarding the " ParsePkcs12: Could not verify password (invalid password or corrupted pkcs12 structure " you need to use for the Certification Authority Passphrase the password you used for ERA Server VA that you setup during configuration. (as mentioned here : http://help.eset.com/era_deploy_va/64/en-US/index.html?config_server_va.htm ) From your description, I am not usre if you use the ERA https certificate for MDM or if you use your 3rd party https certificate. Also, as mentioned in the KB5771.the hostname in the HTTPS certificate and the hostname in the MDC policy must match. (so if you use the IP address of MDC device in https certificate you must use the IP address also in MDC policy. the same applies for hostname) Also , you do not mention which version of ERA you are using, (6.3/6.4) but: the hostname must be the same doring the whole process (MDC certificate, APN certifcate, MDC policy, iOS enrollement ) , and if hostname, of https certificate are changed, in one of the mentioned , you need to also update the rest. For the Profile Installation Failed error: try to troubleshoot according to this KB : http://support.eset.com/kb6011/

Hello, this can work for you : set Reports : Computers : Rogue Computers : with Daily Schedule and Delivery set to Email and un-check the Send Email If Report Is Empty checkbox. -> This will generate the report every day and deliver to your specified email address when a new computer will appear in Rogue Detection Senzor Report.

Hello, please check if the required ports for ERA are accessible or if there is any port conflict. Also , if you are using firewall, please also check if these ports and addresses are allowed.

Instructions for CentOS6 can be found in ERA_VA help : http://help.eset.com/era_deploy_va/64/en-US/index.html?enable_apache_http_proxy.htm

Hello, you can see all reported files / firewall events , etc in Threats section, http://help.eset.com/era_admin/64/en-US/index.html?threats.htm or for a specific client under Computers -> Details -> Threats and Quarantine. http://help.eset.com/era_admin/64/en-US/index.html?computer_details.htm