MichalJ
-
Posts
2,377 -
Joined
-
Days Won
70
Posts posted by MichalJ
-
-
Hi Edmond, your configuration is correct and should result in a behavior when:
- there is no warning shown in the endpoint local UI
- if updates are missing on the machine, machine will be "yellow" and alert / problem "Windows updates available" will be shown.
If this does not work, it might indicate either a bug in our configuration module, or you might have another policy, that might be in conflict and overruled the one you configured. Maybe @Marcos will have smore more details recommendation.
PS: You can monitor status of "windows updates" also via "ESET Management Agent". In policy for the agent, you can configure that it will monitor windows update status.
-
ESET Inspect will regularly sync with ESET Protect, to check, if there are no "permission changes" and no new user was added to the system. When you was installing ESET Inspect, it was asking you to enter an ESET PROTECT user, with administrative privileges. Maybe this "EI_Admin" does not have the rights required, to perform such operation, and that might be a reason why this task fails (it´s just my random guess).
-
Hello, This seems to be posted in a incorrect section, as you are obviously talking about task in "ESET PROTECT". EI_ADMIN might be related to the fact, that you have installed "ESET INSPECT"? This task would synchronize users between PROTECT and INSPECT.
-
Hello,
Hotfixes were only related to new version of agent (9.1.18.1) and new version of Apache HTTP Proxy (9.1.18.2).
If you trigger the upgrade using the task, it will install the version components according to current availability, meaning the latest server / webconsole (from the original 9.1 release) and agent. If you will do the appliance redeploy, it will include all of the latest components. There is no reason to wait with the upgrade.
-
@AlexB Please specify the platform. Given the term "terminal" I would expect it is a Mac. Also, which version you have attempted to install / activate. If V7, then it is possible to be activated only using ESET PROTECT as it is "managed only" application, that does not support "non managed" setup.
-
You should be able to use the task. The "dashboard" action does not do anything else, just triggers the task. This agent is referenced internally with the server version you have installed. Server will stay, agents will be updated to the latest version if you direct the task to group "all". Just the agent on the machine where protect is installed will have to be upgraded manually.
-
Hello @mars_ots
- The policy to "disable windows security center firewall notification" - this one disables the alert that will be show in the ESET PROTECT Console in case the FW component of the OS is disabled and Windows reports this over WMI. Agents then takes this message and interprets it.
- Policy for "HTTP Proxy Usage" is enabled / assigned by default if you have installed your "ESET PROTECT Server" with "Apache HTTP PROXY" component enabled. It basically configures every agent / endpoint to communicate with "outside world" via this proxy, which allows better network utilization, caching of update files, etc.
-
1 minute ago, antoineL said:
There seems to be a catch-22 problem. My server runs Server version 9.1.0.1295 and Agent version 9.1.0.1295. I am seeing everywhere (dashboard, machine details etc) that the agent is out-of-date, and I understand why. However, the automatic update task does not seem to apply to that machine; and when I select that particular machine and press Update ESET Products, I am told: "No ESET products that can be updated automatically have been found."
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.
-
Hello @mars_ots
ESET PROTECT Server is the management component only and on its own does not provide any protection capabilities. In order to have the server itself actually protected, you need to install ESET Server Security on it.
-
Hello, this version only includes following changes:
- New version of ESET Management Agent
- New version of Microsoft SQL Express DB, including the latest CU update, packed in the AIO.
Therefore, ESET PROTECT will not show you the popup to upgrade. You can upgrade the machine where the server is running by running the AIO installer on it. For the rest, you can update the agents by choosing a corresponding option in the main dashboard, where it should indicate that the agents are out of date.
-
Hello,
After you select a particular installer, you will see a checkbox that will allow you to choose the "latest version" of the installation package within the software install task.
-
15 hours ago, Glitch said:
And if you don't use ESET protect? Because offline so why should we use it?
We have many customers, that have "air gapped" environments, but setup in a way, that the entire environment is air gapped. So in such case, it would make sense to have the management console. I understood that in your case, the individual machines have no network connectivity, so they can´t connect even to the management server.
-
Hello, in the latest version of ESET PROTECT, you can download an installer with the full set of modules. You can configure that in the "more details" section of the installer creation.
-
Hello, they are consolidated to some level of extent. Always, the first two numbers, are valid - 9.1.xxx.x
The rest, is a bit tricky, as every component might have its own lifecycle, with regards to number of build / test cycles needed to reach release readiness. So at this moment, although It might sound like a good idea, there are some technical challenges that prevents us from realizing your suggestion.
Also, especially the management agent - that one is shared for Protect and Protect cloud, and might be released outside of the regular "on premises" release windows.
-
Hello @kapela86
You have spotted an error in the mentioned KB article. Article was published with previously intended version numbers, however due to a last moment discovery, installers have been rebuilt. Now the KB was updated, and the correct versions are listed. You are running indeed the latest version of ESET PROTECT 9.1 (server / webconsole). Sorry for any inconvenience caused.
-
Hello @Pavol_postlabs the only way to "disable" the notification is by updating the server components to the ones, that are natively compatible with your ESET PROTECT version.
-
Hello, so far, I can see that you have just suspended a customer.
- You need to "remove" such customer from EMA (you will be prompted to enter your password / 2FA if enabled)
- Once done, you need to synchronize your licenses in ESET PROTECT and then you will be able to "remove" corresponding customer group.
-
Hello, all the details are available in EBA documentation: https://help.eset.com/eba/en-US/?two-factor-authentication.html
-
Hello @Ted Join, most likely nobody from our community has enough experience with the case you wanted to follow up on. Only thing I can recommend is to contact official ESET support, they might be able to help you.
-
Simply said, you should do the following:
- choose a report you want to execute
- Duplicate the report template, with the "customer name" in it
- Apply the filter per Marcos suggestion
For the future, we are planning to improve the reporting system, that you will be able to choose a particular customer (in case of MSP setup) during report generation. Like, do this report for this customer. You will not have to edit report template, and duplicate it for each customer, which is a case as of now. You can use "tags" to make your life simpler, and use "tag search" to them filter out templates per particular customer.
-
Hello, @JeremyStantiall Thank you for your feedback. You should have posted it in the "Future Changes for ESET PROTECT", but rest assured that you feedback has been seen, and forwarded to our product management team for proper tracking.
Thank you,
Michal
-
Hello,
You can specify a "mapped domain security group", (synced from the AD). and those users will be able to use their domain credentials, when accessing ESET PROTECT.
https://help.eset.com/protect_admin/90/en-US/fs_login_screen.html?zoom_highlightsub=domain+login
-
Hello,
This would indicate, that the license is being used on computers that do not connect to ESET PROTECT / PROTECT Cloud.
You should login to your ESET Business Account, where under "Activated devices" you will find the ones. If those are not your computers, you can deactivate them (as that would indicate license leakage), and I would suggest to contact your ESET representative to reset license credentials.
Regards,
Michal
-
The best thing would be to uninstall the "ESET PROTECT Management Agent" from the affected machine, and generate a new installer with just the agent, which will be then installed. Such computer will then appear in "Lost and found" static group.
MSP - Automatic Licence based on group
in ESET PROTECT
Posted
Hello,
The only solution how to automate it currently would be to create a dynamic group with a specific "product activation task", pointing to a customer license (triggers set to "DG join / regular, incase of any activation hiccups). If I do understand your request correctly, you would simply trigger "re-activation" / "activation" the moment you drag/drop/move the particular device into it´s company group. Correct? I will discuss this with my colleagues from product management, whether it would be possible, but on the first sounding it seems to be a good idea. @igi008