MichalJ
-
Posts
2,377 -
Joined
-
Days Won
70
Posts posted by MichalJ
-
-
At this moment, you can´t disable "sending them", you can only "filter them out" by configuring the "detections" screen to show only the ones, that have not been resolved (add filter for "resolved" and uncheck it). That will keep only the ones, that have not been handled / resolved in the view. But you can´t simply made them disappear.
-
Hello, You can´t adjust the connection interval. By default, it is set to be 10 minutes, but you can always initiate a wake up call, that would trigger a connection attempt out of interval for the relevant machines.
-
-
Hello,
Can you please be more specific? With regards to installation options you can either:
- create all in one installer, that combines agent + endpoint (.exe) that you can either run manually on each computer, or use any 3rd party software that is able to push software. AIO installer can be pushed using "remote deployment tool", that is able to target machines also using IP address if I am not mistaken https://help.eset.com/protect_admin/90/en-US/?fs_agent_deploy_remote.html
- create a agent only batch script, that you can as well deploy using a standard 3rd party software like SCCM / GPO
-
Hello @Krischeu
With regards to your second question - I see that you are using "ESET PROTECT" deployed on premises, not the cloud version. So to deploy "Endpoint Security" products, you have to do the following:
- Select either all of the machines or the group of computers where you want the software to be installed
- Actions => New Task => Software Install => Choose the corresponding version of the product you want to install. Choose a valid license as well, so the Endpoint will be activated upon installation.
- Installer will be downloaded and installed by the agent, silently.
-
Hello,
"component upgrade task" does not upgrade the 3rd party libraries, including Apache Tomcat. Per my information, the only way how to update those, is either manually, or using the AIO. However, the AIO you have downloaded, my still have the currently installed version in it, what is the reason, that the upgrade option is "greyed out".
Regards,
Michal -
Hello,
I am concerned that the scenario you are trying to achieve is not supported, as MariaDB was never officially supported. Maybe @MartinK will be able to provide more insight, but I am really afraid it will not work.
-
Hello, automatic updates apply only to the "ESET PROTECT Cloud", which is a cloud service, and is maintained by ESET. Currently, the automatic updates apply for Endpoints (regardless of the management server version) and Agents (agents should be automatically updated to latest version compatible with the currently running management server).
-
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.
-
-
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.
- Peter Randziak and j-gray
-
2
-
@kapela86 if you will double click on the particular entry on the endpoint site, you will actually see, that it has been detected as well 4 times, however was "aggregated" within the log entry.
-
Hello @Tad2020. Can you please share with us the screenshot of the dashboard? This Overview is supposed to be shown on the primary screen, right after login.
-
No, there is no "local override" implemented in the mac product.
-
Hello,
This is related to the internal "relations" in the PROTECT Database. Simply, not all fields could be linked together, as they do not have any common parameter. We are able to sometimes address this, but it will never be possible to have everything paired with everything. Most of the competition handles is in the way, that "custom report builder" is not even available, and they just offer you "out of the box" set of reports.
It will be interesting if you would explicitly write what kind of report you would like to build, and we can take a look, whether we can do something about it.
AFAIK, in ESET PROTECT V9, we have added a "unified HW inventory report", that looks like this:
-
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
-
You can just "enlarge" the license - increase the quantity on it. The reason why I have recommended the "mail plus" is that it includes the Dynamic threat defense (advance threat defense system, that includes cloud sandboxing option). It allows cloud management, but is as well eligible for on premises management. Price vice, it is the best option. In case you want just the pure Mail Security, then as said, the standalone Mail Security license, for the number of mailboxes you have is the way to go. You should be able to increase the quantity anytime.
-
Based on what you have said, you are missing the management agent on the mac machine. Management agent is required for the communication / management between the computer and the ESET PROTECT server. You can download the installer from your PROTECT server as a batch script (.sh) that will just install the agent itself.
-
Can you post a screenshot of your policy? Or even better, for the affected device, request a configuration (you can do this from computer (device) details / configuration / "request configuration". you can also check, what policies are really applied in the second tab. I assume, that you might have not the "apply flag" set, or that there is some conflicting policy set for the device.
-
Thanks for the response @Ryan O ELA to EBA migration does not "affect" the activation state of the endpoint. Once the endpoint is activated, it would retain the licensing info regardless of the activation method (activated by license key directly, or via EBA account / ELA account (directly, or via ESET PROTECT). Glad to hear your experience was smooth.
-
Hello, license files are still being generated. Can you please share the information about:
- Your public license ID
- Which product you are trying to generate "legacy license file" for?
You need it only for the following products:
- ESET Remote Administrator - file "unlocks" capability to manage clients remotely
- ESET Mail Security (exchange / domino)- file unlocks "mail protection" and carries information about how many mailboxes you can protect
- ESET File Security - it unlocks "mirror" functionality, otherwise it is not needed
For any other purpose, you just need "username and password" which you should be able to display, via EBA:
-
Thank you for your update @Ryan O
Out of curiosity - was the process you did the following:
- Created a new EBA account
- Added your existing license there (for that you need license key and ELA license owner password) - this one you reset using ELA (screenshots below).
- Once the license was added, it "disappeared" from ELA, and all activated devices were "moved" (you see them in EBA, the same way as you saw them in EBA, correct)?
-
As stated before, V5 generation of applications is more than 10 years old, and do not provide sufficient protection against modern threats. It´s not viable for a security / software vendor to support such broad set of application versions. We kept those apps running even when a modern replacement was available (V6+), even after Microsoft stopped supporting the operating systems it was running on (XP, Vista, 7).
As the usage of those product dropped significantly, ESET started to enforce its end of life policy, so we can invest our resources into making our modern products better, more robust, and capable of stopping modern threat types.
I would recommend you to check: https://support-eol.eset.com/en/index.html
And the following KB article, where the policy is explained, including current version support status: https://support.eset.com/en/kb3592-is-my-eset-product-supported-eset-end-of-life-policy-business-products
-
Hello, in this case, I would go for "ESET PROTECT Complete". That one allows you to use the following modules / components:
- ESET PROTECT Cloud Console
- ESET Endpoints for all platforms (including mobiles)
- ESET Full Disk Encryption
- ESET Dynamic Threat Defense (Advanced, cloud based Threat Defense platform)
- ESET Cloud Office Security (securing Exchange Online, One Drive, SharePoint)
More details could be found here: https://www.eset.com/nz/business/complete-protection-bundle/
Server Patching
in ESET PROTECT
Posted
Hello, per my understanding, the task is "finished" when it was handed over to local "WMI" Provider, that triggers the operating system update by the system. But the status "finished" from the console perspective, is not triggered by any crosschecking mechanism that the update has really been applied. That would be achieved only when the "operating system is not up to date" warning disappears (if checking enabled).