Monge

Version 5.3.39.0 Changelog: Fixed: Remote client update task now supports .msi-installers with updated digital signatures and allows seamless client upgrade to version 5.0.2260.x and later. Fixed: With any other than blank password for the administrator account, the User Manager will refuse to create new users. Added: Updated copyright statement for all product components. For me it fixed a bug, while creating a remote installer for Endpoint Security 64bits, due to installer bigger than 100MB. Thank ESET for keeping support for ERA 5.

I could invest time and write bad things in v5 that are still there even after all these years. Profile corruption even in latest v5 version...for example. I could invest time and write bad things in v6 but there are people here doing awesome job in reporting bad things and requesting features. However I am single system administrator for 120 workstations and time is luxury. However, since you asked what specific problems are in place, here are some that pop out first: 1. Main problem you have is with documentation. After 6.3 release you have updated documentation and it's better, however it still does not answer many questions... 2. Full mirror integration in ERA is something we expect to be built in product for us to consider migration. Don't start proxy story. 3. Authentication server built in virtual appliance. We use it in v5 for zone authentication. 4. And finally, build desktop application for managing ERA. Just like v5 had. We expect this for consider staying with ESET. No, web interface is not cool thing I have tested third party products with "only web interface" and all I can say is that people who develop security products like antivirus management in web should be forced to use that product in real life company. Then they would understand that having cool interface does not mean it's god for real life use. You could sell it to manager...for example. At the moment my decision is rather than moving to v6 we are looking for other options. Since it will cost us time anyway. Regards. I fell the same as you. Desktop application and full mirror integration in ERA is a must to continue with ESET. I'm just watching how versions changes, studying new options until the end of life of version 5. BTW Until when ERA 5 will be supported?

Hello, I'm trying to set a scheduler to run an external application in a remote network location(Actually is the einstaller.exe). I Could not find any documentation about it. I probably also need to run this as an administrator. Is it possible?

Has anyone got errors like that? Event Viewer: Error Source: ERA_SERVER Event ID: 502. Error: "KernelProcessRequestFull: Some ThreatSense.Net errors (4) occurred"

Same suggestion as bbahes, go for latest ERA V5, you will see were ESET shines.

How many users requests? I didn't ask for this. It's is a great NAC like feature, but ESET should not have turned ERA into a 'duck' on the process. In my case: Everything works with ERA 5 for the 6k+ clients in 16 places. ERA 6 didn't hit 10 success implementations. I know that is your job to calm things down, but really, ESET should admit failure on releasing this before it's time. At least in my country ESET ended not recommending to use ERA 6 until further notice. Which country? It certainly looks as unfinished product. I think they saw competition moving their solutions to web based management at faster rate and sadly they thought they should move to web too. But they did it at quality cost. Cloud and web are cool. But my suggestion to ESET would be to design hybrid solution. Cloud ERA as backup in case of disaster, virtual applicance or server beeing brought down for various reasons. We are still on v5 and now in plan to test latest release 6.2 to check is it improved over 6.1 release. Brazil.

How many users requests? I didn't ask for this. It's is a great NAC like feature, but ESET should not have turned ERA into a 'duck' on the process. In my case: Everything works with ERA 5 for the 6k+ clients in 16 places. ERA 6 didn't hit 10 success implementations. I know that is your job to calm things down, but really, ESET should admit failure on releasing this before it's time. At least in my country ESET ended not recommending to use ERA 6 until further notice.

In my opinion, ERA 6 is not ready to clients. Like Batman: Arkham Knight for PC, sales should suspended until is fixed(and improved).

Amen to that

That sound really nice. But for my company almost nothing worked. From activation to detect agents and so on. ESET lab engineers even tried to make it work without success(remote access).

Like in many other cases, your frustration seems to be stemming from not understanding the new concept of ERA v6. ERA v6 does not support creation of a local mirror. The feature was replaced by Apache HTTP Proxy which caches downloaded installers and update files. You may choose not to install it if you plan to use another http proxy or create a mirror using ESET Endpoint Antivirus, ESET Endpoint Security or another v6 ESET product, such as ESET File Security. Let us know what you'd need to help with specifically. As of ERA v6, it's not possible to create custom packages. Basically you need to: 1, Create a dynamic group that will contain computers that don't have ESET Endpoint installed (e.g. create a rule based on application's name). 2, Bind a software install task to that dynamic group that will install Endpoint (point the task to use a locally stored msi if you don't want agent to be downloaded from ESET's repository). 3, Bind an activation task to the dynamic group with non-activated clients. 4, Deploy agent on clients. You can deploy Agent Live installer through GPO for instance, with the path to the msi installer set to point to a locally stored agent msi installer. Let us know if you need to clarify something, add some screen shots for better understanding, etc. You don't need to use Apache HTTP Proxy that is bundled in the ERA v6 all-in-one installer. You can use your existing proxy server and existing database. ERA 6.2 with further improvements is going to be available within a couple of weeks so you could consider waiting with upgrade to ERA v6 until then. As always, we recommend testing ERA v6 in a testing environment first to get familiar with the new concept of how ERA v6 works. Marcos, He and most of us did understand the new concept, the problem is that we cannot believe why key features like custom installation is gone and accept that now we need to do multiple tasks just to do what once were one click away. In my option this is a screaming sign that ESET should plan to implement what Never should have been removed in the first place.

Please be more specific as to what issues you've run into while deploying ERA v6, what features or information you lack, etc. We listed to our customers and continually improve the product and also create new KB content and videos to cover topics that our users demand. Marcos, this thread sum almost all problems that we had. Some was solved. The interface, the way you handle it in the web is not as functional as in the windows application. The only way to list all the problem is doing a video comparison, maybe for someone who never used ERA before may like version 6. If you compare how easy is to create a simple einstaller.exe and deploy silently, and compere for that .bat in Era6, where the user may cancel it.

I work in a company with more than 6k installed ESET. This a big step back for ERA. In my experience, some interfaces should never go to WEB. It's like comparing checkpoint client to admin the firewall and the web admin interface from fortigate which lacks many features. I used this thread as an exemple to ESET representatives my disapproval on the Era 6. As long as ERA 5 is supported and updated as it's clients, i will remain using ESET solution, but i am starting to look for alternatives.