-
Posts
2,377 -
Joined
-
Days Won
70
Kudos
-
MichalJ received kudos from MartinK in What happens to local ERA and licensing after migrating from On-Prem to Cloud
Hello. The licensing is the same for cloud and on prem. So when you have upgraded your license, it has upgraded it on all active endpoints, regardless if they are connected to the cloud version or on premises version. Even if you uninstall ERA from the on-prem server, but do not remove ESET from those other 11 machines, they will continue being counted. The best thing would be to login to EBA, deactivate all devices, and reactivate only the ones connected to ESET PROTECT Cloud, using the console activation task. Unless you have some more machines to migrate.
-
-
MichalJ received kudos from Peter Randziak in What happens to local ERA and licensing after migrating from On-Prem to Cloud
Hello. The licensing is the same for cloud and on prem. So when you have upgraded your license, it has upgraded it on all active endpoints, regardless if they are connected to the cloud version or on premises version. Even if you uninstall ERA from the on-prem server, but do not remove ESET from those other 11 machines, they will continue being counted. The best thing would be to login to EBA, deactivate all devices, and reactivate only the ones connected to ESET PROTECT Cloud, using the console activation task. Unless you have some more machines to migrate.
-
MichalJ received kudos from Peter Randziak in CentOS 7
Hello, there will be soon a new version of the virtual appliance, that will be based on the Rocky Linux 9.
-
MichalJ received kudos from rmdir32 in Future changes to ESET PROTECT (formerly ESET Security Management Center / ESET Remote Administrator)
@ludolf In ESMC V7 you can configure "monitored static group" as a part of the notification. So if the alert happens in the Group1 and Group1 is configured as monitored, only the recipients set in this notification will get it. Concerning the auditlog issue, we are tracking improvement for a more granular filtering (it was actually existent before).
-
MichalJ received kudos from j-gray in Dynamic template for Product Not Activated
For such behavior, you need to create two different dynamic groups.
One for the Endpoint, one for the Inspect Connector. For ESET Inspect the below example should work, for standard Endpoint just change the "source" to "security product".
Hope that this helps.
-
-
MichalJ received kudos from igi008 in Make a locked option editable
Hello @LesRMed
I have opened this up with our QA department and this is what they came up with:
In case you enable the setting that allows appending the globally set exclusions to the local list, it will enable you to add the local ones. However, what you need to do first on the endpoint side, is to adjust the "combo box" to "show local exclusions". Once this is done, the add button will enable, and allow you to enter the exclusion locally.
I have filed an improvement request, to change this behavior, as it is considered as not intuitive.
-
MichalJ received kudos from Aryeh Goretsky in Error installing Endpoint Security in Windows Server 2012 R2 - Compatible package not found
Hello, when you navigate to "installers" and attempt to generate a new installer, you need to click on "customize installer" and in "product setup" click on the blue line under "security product" and in the popup choose the "ESET Server Security for Microsoft Windows Server" as seen on the screenshot below.
-
MichalJ received kudos from Peter Randziak in ESET PROTECT 9.1.18.1
Yes, you are right. This behavior is considered to be a bug, and should be fixed in the future versions. To update the agent on the machine where the ESET PROTECT Server is running, you need to install it either manually (download the standalone MSI) or using the All in One Installer as pointed out above.
-
MichalJ gave kudos to APM in Licence count exceeded but actual number of managed clients below count
Thanks for the reply Marcos. Unfortunately I'd already tried the steps you outlined and this didn't work.
However, I managed to resolve this once I gave the EBA time to update (after adding the licence to it). Around 30 minutes after adding the licence, the count reset to 0/40 used. Another 30 or so minutes later, the devices started to show up. I could see that many devices were double activated with two versions of the endpoint security, 6.5 and 8/9. I believe this is due to the forced, manual uninstalls that had to be performed back in 6.5 when a certificate problem occurred and affected certain builds.
After deactivating all the clients with double activations in the EBA, then reactivating them via the Protect appliance, the numbers now marry up and are back where they should be and within the licence limit.
Moral of the story is: give it an hour after adding a licence to the EBA and everything makes more sense.
-
MichalJ received kudos from Trooper in ESET INSPECT Connector Agent Installation
Hello @Trooper - Yes, exactly. We have unified the wording, and behavior among all of the modules / components of ESET PROTECT Platform.
-
MichalJ gave kudos to Marcos in Client not connecting to ESMC
ESET PROTECT (v8, v9) is the last version of ESMC (v7). Upgrades to newer versions are included in your license and are available for no additional cost. You can upgrade to ESET PROTECT by:
1, sending an ESMC component upgrade task to the server (this will, however, upgrade only ESET components and not the 3rd party components like MySQL, Tomcat, etc.
2, using the all-in-one installer (Windows only)
3, by deploying the latest ESET PROTECT virtual appliance and migrating the server db there.
Please refer to https://help.eset.com/protect_install/90/en-US/upgrade_procedures.html for the upgrade procedure.
As for the problem, are you able to ping the server hostname listed in status,html?
-
MichalJ gave kudos to Joel DeTeves in Internal Report Error after migrating database from mariadb 10.3 -> MySQL 8.0
Hi there, I discovered that the problem was a setting on the target MySQL database, specifically log_bin_trust_function_creators=1
It turns out our cloud provider does not allow us to enable that on their managed database.
So I went with a small MySQL 8 install on a VPS instead, and enabled that setting.
From there I was able to migrate off of MariaDB and perform the upgrade to version 9 without issue, and I don’t get any more errors.
Thank you,
-
MichalJ gave kudos to Krischeu in ESET Protect On-Prom - How to get rid of - Die Funktion wird nicht vom Windows-Sicherheitscenter überwacht
Solved
Thank you
It was great to use the forum
-
MichalJ received kudos from zeroexct in Bulk Removal from MDM/ESET console
You can also disable the password protection via policy. But the recommendation from Marcos should suffice as well.
For uninstallation of "ESET Management Agent" you need to perform the "stop managing task". But my recommendation would be the following:
uninstall ESET endpoint via the "software uninstall task" the way Marcos shown disable the "password protection" for ESET management agent uninstall ESET management agent using airwatch - agent itself does not interfere with anything, and once Endpoint is removed, could be easily uninstalled using 3rd party tool. Also, out of curiosity (you can also send me the response via private message) can you share the reasoning for the switch / company policy change and the vendor you are moving to? It´s always beneficial for us to understand our users / buyers behavior. Thank you.
Michal
-
MichalJ received kudos from j-gray in Issues with MacOS v7
Hello @j-gray just one idea. As the EEA V7 is a brand new product, the policy settings from older versions (V6) will not apply. Maybe, that is the reason, why they are not reflecting, as you have upgraded.
-
MichalJ received kudos from j-gray in OS X clients show 6.11.202.0 as latest available version
Yes, currently, as there is no full feature parity for Endpoint V7 with V6, we do not show the V7 as a direct successor. So the behavior is correct.
-
MichalJ received kudos from Ufoto in Export rules created by Firewall Learning Mode?
What you can do, is that you can pull the configuration from a selected client, where the learning mode was running (via computer details / configuration / request configuration) and once that is done, you can convert it into policy, and apply just the particular FW rules, that you want to apply to the rest of your network.
-
MichalJ received kudos from Peter Randziak in OS X clients show 6.11.202.0 as latest available version
Yes, currently, as there is no full feature parity for Endpoint V7 with V6, we do not show the V7 as a direct successor. So the behavior is correct.
-
MichalJ gave kudos to Brady in Deactivation Eset-Livegrid messages, etc.
Brilliant. Thanks alot!
User Interface --> Elements of User Interface --> Statuses --> Application Statuses
-
MichalJ gave kudos to Marcos in Online Banking with Business Endpoint Security
You must install ESET Endpoint Security on endpoints in order to have Bank and payment protection.
-
MichalJ gave kudos to Ryan O in Migrating from ELA to an Eset Business account
As I couldn't wait, I went through the migration process from ELA > Eset Business Account. I'll admit it was a lot easier to do then I thought/expected. The only thing that momentarily threw me was finding my "license owner" password but I was able to reset that in ELA to proceed. All in all, the whole process was pretty easy/smooth. Turns out I didn't even need migration documentation.
-
-
MichalJ gave kudos to Mark Dagley in Sever is unmanaged
Thanks, the issue must have been the way I installed it, I had not noticed that you can change the product when cratering the live installer it seems to be working now.
also the device was showing in the business account as unmanaged not protect
I can see the agent is now installed