kingoftheworld
-
Posts
191 -
Joined
-
Days Won
1
Posts posted by kingoftheworld
-
-
8 hours ago, Marcos said:
You can contact your local ESET support for instructions how to avoid the notification.
I already have, and they pretty much gave me the option of hiding the GUI entirely or upgrading. I just hope the feedback received makes the decision makers behind these decisions re-think this next time.
-
9 hours ago, Marcos said:
Note that the message does not cause any pop-up notifications and does not draw users' attention until they open the main gui which is something that common users in companies should not do on a regular basis.
This is not accurate. The current notification causes a Windows notification and alert sound upon logging into the machine which draws attention to the GUI.
-
9 hours ago, Marcos said:
Actually without upgrading agent it would stop working after Windows 10 21H1 update.
You are assuming that I plan to deploy 21H1 in the near future. The users in my environment will actually never have access to 21H1.
-
On 10/7/2020 at 3:49 PM, Marcos said:
There is no easy way to accomplish that and not without the help of technical support that would need to create and convey a special policy and a new Config Engine module.
We'd like to understand what is the problem with the notification because it merely changes the protection status to yellow and no notification window pops up on the screen, ie. it should be unnoticed by users working on workstations.
At least for me, the issue with the notification is causing me to receive un-necessary support tickets from my end-users thinking there is an issue with their computer when in fact there is nothing wrong.
-
On 10/6/2020 at 10:14 AM, Marcos said:
It is an in-product message that could be configurable via the advanced setup but it's delivered via a module update, ie. the product is unaware of the message after installation. And upgrading to the latest version is quite urgent so admins should not hesitate with upgrade for long.
Tomorrow we will be releasing a module that will remove the notification about outdated agent after upgrading it. It will be removed with the next update attempt.
That's not the point. This was not well executed by ESET. This message should have been displayed to the admins in the console and not on all endpoints without the ability to control it.
-
3 hours ago, speakerbox said:
Hi Marcos,
Will ESET Endpoint Anti-Virus version 8 be out any time soon?
We are about to update 1000+ 7.2 clients to 7.3 to support the latest changes and stop our users calling us every minute about the warning but if V8 is around the corner should we hold off spending days rolling out 7.3 updates only to do it all again for V8?
Cheers
On a similar note, can I ask why there isn't a way to hide this message on the client via policy? There is an option to disable every other alert message on the client but this one. In my environment, the end-users need to not worry about the agent/product being out of date as that is handled by IT. We are actively working on it and don't need users calling and telling us.
-
On 3/16/2020 at 12:22 PM, Marcos said:
On Mac OS you specify privileged users who can modify settings.
I seriously don't understand why these settings cannot be the same between platforms. There are those that prefer to use the simple password protect settings mechanism on macOS.
-
I know many are reporting widespread issues, but I have seen this exact error message when the HDD fills up.
-
I am interested in getting a copy! Is this product geared towards file servers, linux desktops, or both? Also, would I need to have ESMC 7 deployed to manage it? We are running 6.5 and planning our upgrade to 7 for later this year.
-
11 hours ago, Heath said:
I realize this is a very old thread but I'm trying to research a fix for this...
I have this same issue, but moving the license does NOT help in a situation where I want to have multiple users who can only see their 'home' folder group like I would like to have?
Moving the license fixes the issue for the regional user login you move the license file to, but breaks it for all other regional users who are set to only see their own regional 'home' folder?
Is there a way to have 1 ERA license file, distributed between many 'regional site admins' who should only have visibility of their own 'home' folder static group?
The way that I have gotten around this is to make a "Shared Permissions" static group. Then, give the permissions to both user groups that need to access the license.
-
19 minutes ago, Peter Randziak said:
It´s been some time, we were slowly teasing you about the upcoming version of ESET Remote Administrator.
Under a completely new name (ESET Security Management Center) lies the next step in the ERA evolution. Version 7.
And you now have the unique change to get your hands on it, before anybody else. We have achieved „GA readiness“, and our marketing teams are now getting ready for the release soon.
But as we value you our active forum members, and your feedback we would like to give you access to this version in advance of the official release as result of our gratitude and appreciation.
What you are going to get, is GA version of our product, tested, and approved for the release. There is a huge change log (that you will get once we approve you to see the dedicated section in the forum). You can use your existing licenses, to operate. Last but not least, you will be also able to upgrade your production environments to this version, as we will ship you a custom repository link, that will include the latest components for ESMC, upgrade configuration and also latest builds of the new Endpoint V7.
If you are interested, and we bet you are, please let us know in the comments below!
PS: Please note, that we will not be providing access to anyone newly registered, and users with less than 5 relevant posts related to ERA usage in the past.
Please include me!
-
It looks like you provided full access to only a select few Static Groups and the license it probably in the top-level (All) access group which this account doesn't have access to. You will either need to provide access to the static group that the license is at, or move the license to a static group that this account has access to.
-
On 6/26/2018 at 1:54 AM, Peter Randziak said:
Any ETA on a fix for this issue? Yesterday, I experienced this popup no less than five times throughout the day without any interacting with the ESET GUI.
-
Not necessarily related to ERA, but for the enterprise A/V products
Description: Consistent handling of update profiles between Windows and macOS
Detail: I would think that two products that are essentially branded the same should operate the same between platforms, ESET Endpoint A/V 6.* for Windows and macOS. When configuring update profiles to pull from an internal mirror on a PC, you essentially have to go in an update the the task for the update to use your internal mirror first, then use ESET's servers second. However, when you manually trigger the update now using the GUI, this fails at doesn't know to use a secondary profile and only uses the primary. In my mind, the macOS behavior is ideal method where you specify a primary and secondary server. It attempts the first, if it doesn't connect, it fails to the second. P.S. I am not interested in using the caching proxy that has been recommended me more times than I can remember. I am confused on why these products from a administrative standpoint are so very different. Another example is the ability to password protect the settings on Windows, but a horrible method of using groups/accounts on macOS. I simply want to apply a password before dropping into the settings panel. I am forced to mark all of the settings as Forced on my macOS policy to prevent users from modifying them which is a real pain if I have to have a technician troubleshoot something with an end-user. -
3 hours ago, MichalJ said:
Hello, this functionality will be added in upcoming version 7
Any timeframe or beta for v7?
-
On 6/11/2018 at 9:59 AM, pps said:
Hello kingoftheworld there are options only for computer extinction not for disabled ones:
• Computer extinction handling - If a computer no longer exists, you can either Remove this computer or Skip it. • Group extinction handling - If a group no longer exists, you can either Remove this group or Skip it. @pps @MichalJ It is currently available under the sync task. See screenshot below
-
1 hour ago, pps said:
Hello,
Description: Exclude disabled computers in AD sync
Detail: Exclude disabled computers when running task with Active Directory sync or give the choice inside the task to include or exclude disabled computers
This is already an option in the task settings. I believe you can choose the behavior.
-
15 hours ago, Tim Jones said:
One more thing if you could locally run a command against ERAAgent to regen guid would be nice
eg
eraagent --regenguid
and that just does an UPDATE key_value_table SET value = '%randomguid%' WHERE key = 'local_peer_uuid'
in C:\ProgramData\ESET\RemoteAdministrator\Agent\EraAgentApplicationData\Data\data.db
and updates the reg keys as well
REG delete HKEY_LOCAL_MACHINE\SOFTWARE\ESET\RemoteAdministrator\Agent\CurrentVersion\Info /v ProductInstanceID /f
REG add HKEY_LOCAL_MACHINE\SOFTWARE\ESET\RemoteAdministrator\Agent\CurrentVersion\Info /v ProductInstanceID /t REG_SZ /d %randomguid% /fotherwise you end up having to do it with sqlite3 with a bunch of scripts and hacks to crash the service modify it then start it again it works but would be nice if i didn't have to and it could just do it out of the box,
PS I know its wrong, and I only do this when the guys forget to tell me when they deployed an image without telling me first and somehow included it in the image, would be even better if this was supported so i could just tell the guys to do what they like as long as they run the command at the end of an imaging task
Tim
+1 for this request. Or some other way of accomplishing this
-
4 hours ago, santoso said:
Hello,
You can do this. create new policy for Eset Remote Administrator Agent
Go to Servers to connect to - Edit server list
Add new IP address on the top
Add old IP address bellowSave It and apply fo all group
https://help.eset.com/era_install/65/en-US/index.html?change_era_server_ip_hostname.htm
I would just do this ASAP well ahead of when you plan to make the change. Any clients that are not on or otherwise don't receive this policy will require manually changing them.
-
6 hours ago, MichalJ said:
Yes, we will be announcing V7 release around RSA, with the actual availability being most probably by the end of Q2 (due to getting all related stuff ready). Beta of Endpoint 7 is going to start in few days, and we should have a build of ERA to share by April (my guess). If you are interested to get it, please let me know.
Also, out of curiosity, which particular problems are you reffering to?
Yes, please sign me up for any beta releases. I am ready to get it installed on my dev server.
-
When can we expect v7? It has been promised for far too long, and we have many existing problems that are promised to be fixed in this version. I was originally told we should have it available Q1 of 2018, but it doesn't appear to be the case. Should we expect some type of release to be around the RSA conference, or are we still a long ways out?
-
12 minutes ago, j-gray said:
Scheduled only has the regular update task set by policy, which runs every 60 minutes.
I have experienced this on my mac as well. I believe I have the stock update policies set as well.
-
4 hours ago, plittlefield said:
I have this error now on one of our Windows Server 2012 Standard computers with ESET File Security 6.5.12014.1
As you can see from the attached screenshot, the network ERA has pushed the Policy out to the Server.
Interestingly enough, we have 3 other 2012 servers with the previous version ESET File Security 6.5.12014.0 which do not have this error!
I can confirm that I have a server that is behaving in the same manner. Configured exactly the same as three others, and only one has the alert.
-
2 hours ago, Marcos said:
If I remember correctly, Filezilla is bundled with Fusioncore PUA. When it comes to PUA detection, the user is asked for action selection. Besides selecting "No action", one can expand advanced options and select exclude from detection.
That is correct. However, if you click Download from the menu bar on the left side, then click on "Show Additional Download options", there are different binaries that do not include the Fusioncore PUA. I guess they probably receive some type of revenue for having the bundled one on their home page. You will notice the one on the homepage has "bundled" in the filename as well.
MacOS 11 Update Issues
in ESET Endpoint Products
Posted
Yes, I can confirm this behavior on at least macOS Big Sur devices. I opened a ticket with support and was essentially told that ESET support for Big Sur is not fully available even though their public facing support page says it is fully supported minus the firewall and device control. I was told full support is coming in March with a new version that I hope fixes this. It is rather annoying to have to uninstall ESET to install critical OS patches.