MichalJ

Hello Said, ESA supports Office 365 via integration into AD FS 3.0If the customers has AD FS up and running in the his environment, all he has to do is just run ESA installer on the AD FS machine to install the plugin. After successful installation all 2FA enabled users will be prompted for the 2nd factor when logging into Office 365 Please check the following video: https://www.youtube.com/watch?v=vjFBVL2NGyY

However, ESET Endpoint Security allows component based installation. So you can install EFSW without the firewall functionality at all. For more details please refer to the product documentation: - local installation: hxxp://help.eset.com/ees/6/en-US/index.html?installation_username.htm - remote installation via ERA 6: hxxp://help.eset.com/ees/6/en-US/index.html?installation_via_era_command.htm

This is a known limitation of the existing ERA 6 version. We are working on a new security access model for ERA 6.5, which will ensure complete data isolation and would allow you to grant access to your customers without letting them see the objects (tasks, reports, policies) of others. 6.5 is scheduled to be ready in December.

Preliminary release date for the new ERA version was set to July 12, 2016.

It should have connection to https://edf.eset.com/edf

I have sent the logs for analysis to developers, will let you know, once I hear back from them.

You can also send me the actual status .html please. Is it all green?

The ERA Agent log file can be found here: /Library/Application Support/com.eset.remoteadministrator.agent/Logs/ or /Users/%user%/Library/Logs/EraAgentInstaller.log Have you shipped valid certificate? Does the Mac computer see the ERA server machine?

I would expect some more details. What is the status .html telling you? What are the tracelog errors?

As of now, Endpoint 6.3 is not available in the ERA repository. If you are executing the same task that refers to Endpoint 6.3, it would fail. You have to either host the installer on your network, and then install by a specific path, or install Endpoint 6.4 version instead.

That trace message means, that ESET product was not able to activate, however task was correctly delivered to the product itself. What product is installed? Have you tried the activation locally, on the affected client, using either License Key, or Security Admin account credentials? What is important, is that the client is able to contact ESET licensing servers at https://edf.eset.com/edf(you can access the link from the web browser on the target computer). If it opens the xml, then it works, if it fails, there are connection problems. Also, license should be issued for the product, you are trying to activate (or superior product / bundle, that has the rights to activate that application). Most activation issues are related to proxy server placed in the network infrastructure, which is not configured in the ESET product settings (procut can not reach the activation servers). Second largest set is related to not-updated OS, which has not the newest root certificates, which are needed in order allow client trusting ESET activation servers.

You have to create the license for a product, that you want to activate from ERA. So if you have purchased ESET Endpoint Security, you choose ESET Endpoint Security. If ESET Endpoint Antivirus, then ESET Endpoint Antivirus. Please note, that offline files are application specific so file for EES won´t activate EEA.

What you have used as security admin credentials? To use the security admin feature, you have to fist register your account at ESET License Administrator: https://ela.eset.com/SecurityAdmin/Registration Then you have to "add licenses by license key", for which you will need your license key (XXXX-XXXX-XXXX-XXXX-XXXX) and your ESET License Administrator Password (which you should have received after a license purchase or conversion). Once done, you have to make sure, your ESET Remote Administrator server machine is able to reach https://edf.eset.com/edf(it should open the page like in the screenshot attached).

The file that comes in the e-mail is the .lic format, which is not supported by ERA6. It was used in the previous generation of ESET Remote Administrator (5.x and older). To get the offline file for ERA6 you have to access ESET License Administrator, enable generation of offline files (in settings) and then generate the file as specified in my post above. Pictures can be added in the "more reply options" below the text-input field.

When you get an offline file to ERA, you can then use it in "software activation task" to activate all of your seats, which are not connected to the internet (for example). Basically, ERA agent delivers the offline file to all of the endpoints on the network. It is the same, like in case when you add an standard license using a license key, or security admin account.

Thank you for your inputs. We are discussing the possible solutions internally. We have several improvements planned, related to this topic: Offline / Local repository should be available for ERA 6.5 in Q4/2016 (you will be able to choose, which installers are there) Even when using online repository, you will be able to mark "automatically install the newest version", in case you want to, so the task won´t stop working Tasks, that will be pointing towards a non-existent package in repository, will be automatically invalidated, not executed, and notifications will be generated in the ERA UX Last but not least, we do plan to adjust the process of released / uploading the installers into repository (this one is not confirmed yet, we should have a confirmation in upcoming days) I am sorry for any inconvenience you have. We are not trying to make your life harder, we are constantly improving, to prevent issues like this in the future.

Hello. When you have created the offline license file, have you entered the correct token (token is displayed in ERA, and has to be inserted into the license file, prior to its generation). I am adding the screens from both ERA and ELA. So the order is: Open ERA on the "add license file" screen (licenses / add / offline file) Open ELA on the "generate offline file screen" Copy the server token from ERA to ELA Generate the offline file on ELA and download it Insert the offline file into ERA PS: Why have you decided to use the offline file? Are you trying to activate computers without internet connection?

Yes, they have to do it via ERA task. As the Endpoint does not have any seat name, then I really think it was activated using offline license file. I would also recommend upgrading the Endpoint client, as it is running version 6.1 which is quite old.

Hello Ryan, First of all, you have not stated, if you want to turn off the notification displayed locally (in the UI of the OS X client) or the notification displayed in ERA (in the status for the particular client). Both is possible, you just need to configure this via policy under "USER INTERFACE" / "ALERTS AND NOTIFICATIONS" / PROTECTION STATUSES - Display in protection status screen (locally) / send to ESET Remote Administrator. Please note, that OS X updates are monitored also by ERA agent. You can disable this in ERA Agent Policy, in "ADVANCED SETTINGS" / "OPERATING SYSTEM" / "Report if operating system is not up-to-date".

If the computer was activated with a offline license, then in case of a renewal / upgrade, they need to do the following: Renew the license Generate a new offline license file, and import it into ESET remote administrator Activate all of the computers with the new offline file. However, on the first screenshot, the license indicates, that 232 out of 250 seats on the license were activated "online", meaning that the license should be updated on the client automatically. The second screenshot, with the PLID 33C-4CS-AA7 is not the same license, as they have different expiration date, and also this one is for 400 seats, instead of 250. Also, it shows the correct validity for 2018, in which case it should not display the error you have posted, as there is a correct expiration date for this seat. So I am a bit confused - is it, or is it not the same instance of the client? Than you.

License should get updated automatically. There are few possible reasons: 1, you have activated this particular client via an offline lucense file (I see, that you have one generated) 2, the client is no longer possible to communicate with edf.eset.com 3, there was a problem when syncing our licensing systems (but this seems unlikely as the license in ERA shows the correct date). Can you send me the screen shot of your license screen. What is the license expiry thate there? Does this happen on all of the computers or just few (one)? Can you send me the "seatname" as listed in "about" section of Endpoint security? We will use it for troubleshooting.

Compared to ERA V5, V6 products are using a Cloud-powered licensing, where each of the seats is licensed towards ESET Licensing Authority service, which is cloud based. Computers are then syncing with the licensing authority, to get updates when license parameters are changed. ERA only displays the data from the licensing authority (which has its own portal, ESET License Administrator - https://ela.eset.com) When you remove computers from ERA, it does not decrease the license count automatically (we are going to change the behavior for the future versions of ERA, where upon deleting computers, it will ask you, if you want to de-activate them. But this is not included in ERA 6.3 & 6.4 which is about to be released soon). What you have to do (or what you should have done before deleting them), was once computers were in ERA, was to use the context action to perform "deactivate products". This would contact ESET Licensing servers, and manually deactivate the specific product instances. As of now, you have to login to ESET License Administrator, using your License Key, and ELA password (or using your security admin credentials, if you have used them) and manually deactivate the instances which are no longer connecting to ELA.

Hello, as of now, it is done in the way, that once the newer version of Endpoint is released, older ones are replaced in the repository. Meaning, since we have added 6.4 to repository, 6.3 was removed. Drawback of this is, that already created software install tasks won´t work (will fail) with a trace message that "package is no longer in repository". We are currently examining options, how to adjust this behavior, meaning either keep the older version in repository somehow, or adjust the task flow, to allow "install automatically the newest version" (however there are some legal issues, related to EULA acceptance, which is valid for a specific build only). In the ERA 6.5 (December) there will be a mechanism, that will warn you about tasks, which are no longer valid. Removal of EP 6.3 was done also due to the planned release of ERA 6.4, which will have the new functionality of creating the package installers of Agent / Endpoint, however only EP 6.4 will fully support it, so it will prevent some confusion. Maybe a question, why you want explicitly the version 6.3, respectively what is preventing you from installing the 6.4?

Then, since the Endpoint 6.4 you can configure just a one update profile, with Autoselect, and communication via proxy, with choosing the "proxy fallback" option, meaning when the proxy is not reachable, Endpoint should communicate directly. This option will be added also for other products, like ERA agent, as soon as the version 6.4 is out (should happen within a month). The same setting is also available for custom proxies in the "Update" section of settings.

If you execute the task manually, either on the client, or by the task from ERA, the currently selected profile is used. The scheduled task, which allows to configure two profiles runs automatically, and tries the first profile, then the second profile, per its configuration. Maybe a question - when you mean, that updates are downloaded from "ERA server" means that you have a local mirror tool, or use the HTTP Proxy for updating?