ronmanp
-
Posts
64 -
Joined
Posts posted by ronmanp
-
-
The first screenshot is from the application statuses setup
-
Hi, since ESET File Security for Windows Servers 6.5 we are having issues with unwanted alerts. We get Anti-Phishing alerts even though we don't enable them.
I attached screenshots of our settings.
Anybody else shares the same issue?
-
I'd love to have more details on the issues you are having with 6.4. We are on 6.3 and planning to upgrade too. 2500 systems.
6.0 was a total nightmare but since 6.2 it's starting to get better.
-
Great news. Thanks for the update.
-
I totally agree. I created a support ticket some time ago and they acknowledged it's not possible so I had them create a feature request.
In my case it was ESET Mail Security for Exchange 6.3.
-
ERA should support application version branches. For instance in McAfee ePolicy Orchestrator there's the "previous", "current" and "evaluation" branch.
This way you get to decide which version is the "current" after going through an evaluation stage and with that you also get the option to rollback if needed.
I don't experience that issue since I use SCCM to deploy ESET but I can understand that a relatively big company can't decide overnight to switch all new machines to a new build without proper testing. Companies often need to have everyone on the same build too.
Just my 2 cents.
-
Or provide another way to force a server/client sync from the client.
-
+1
Was useful to force a sync with the ERA server.
-
Is it possible to share which new features and bug fixes we can expect from 6.3?
-
-
Scratch that I wasn't deploying it to the right dynamic group.
-
Is there a way to remotely upgrade the ESET Agent on MacOS?
I'm on ERA 6.2 but all I see in the Remote Administrator Components Upgrade client task is the upgrade for Windows machines.
Thanks
-
Sounds good, thank you.
-
I know it is not your product but ERA depends on JRE so the official answer shouldn't be "just try it".
Recently wasn't there a change in the way JRE displays its version in the registry that required some tweaks to make ERA 6.1 work?
That's the kind of issues I'm trying to avoid by asking you first.
I would expect ESET to have a list of requirement to run ERA with the supported version of each requirement.
That being said, by your answer I assume no bugs have been raised with JRE 8u60 so I'll try it.
Thanks
-
Hi, I'm running ERA 6.2 with JRE 8u45 and I wonder what is the process to update JRE.
Is JRE 8u60 supported? What is the recommended method to update JRE?
Is it just a matter of stopping the ERA service, updating JRE and then restart the ERA service?
Is there a document I can refer to?
Thanks
-
Hi, I'm running ESET Uninstaller in safe mode and I've successfully removed ESET from there.
But it also listed "SEP" in the installed AV products list.
I never had Symantec installed on that server. How could it detect Symantec then?
-
-
-
-
-
That happens all the time for me too. Apparently 6.2 will fix that.
-
-
-
Glad to hear that, but to be honest even if ERA was on-par with SCCM for software deployment I wouldn't use it because it wouldn't make sense to build additional servers at each site when we have a solution for software deployment already.
I'm not trying to convince anyone. Each environment has different needs.
Thanks for the help. I can confirm the parameter works.
Application Statuses
in ESET Products for Windows Servers
Posted
Hi Marcos, I get this problem only with version 6.5.12007.0. Previous builds didn't have that issue (same EFSW policy via ERA 6.5.522.0)
I'll try 6.5.12010.0 and let you know.
Thanks,