avielc

Just emphasizing the point that matters for this solution usually sudo apt install -y gcc-12 should resolve it - possible to do so as a task from the EP console.

Which means if nothing changes with the scheduled EOL of EES v6, EES v8 should appear before hand in order to replace it. Can we escalate to emphasize how dependant clients may be on EES? This is to put the EOL of v6 in a better perspective. I'm not sure how "bad" it is to be with a product that has reached EOL, I rather not find out. it's definitely not a good thing if EOL is at August and the product is released on December (H2 can be anywhere until 25H1) Thank you.

Hi. I'm looking to know if there's anything in the roadmap for EES on mac. Our organization needs the device control and firewall features, and we can't move to v7 under any circumstances due to that. EESv6 EOL has been pushed back from last year till August this year. Is there anything in the roadmap that mentions a new EES version for macOS? Something that will contain the features mentioned above? Thanks

Same as Sec-C - most machines are on v10 (or v6 on Mac) and I get mixed messages of EPNS. Waiting for an update or a clear on the endpoints. Thank you for working on it.

Have you figured that part out? Sounds to me like there should be an offline installer option (which I can't find on the "Installer" page on EP on prem. How about defining HTTP Proxy on creating new installer, would that work?

Thanks Peter, I meant to show that both EEI and EEA installations are missing previous versions. I understand that the minor versions usually means no major new features are introduced, However, in the past I have noticed specific minor version works while another don't. That's why all versions are being tested before mass-deployed. In any case, both the repo and the main site did not have versions available except the latest. This is the issue I experienced, on both EP and the website. That's kinda major, isn't it?

Adding another note: EEI is also missing. This is serious. how can we have only 1 released copy with no ability to go back a version if there's a problem\haven't tested it in our environment??

Hi EEA for Linux is missing the specified version to download. This is the previous version to the current 10.2.2.0 I tried downloading from ESET main page, but even in the previous version there's only a single version for v10 and v9. Can we please push out 10.1.8.0? I can't start pushing to endpoints an untested version. Thanks.

Joining Nightowl - Forticlient is one of the more widespread VPN used (specifically used by our company + 2 clients I recommended using ESET too. Thanks

I will open a ticket, however screenshot says otherwise.

I should have mentioned before, This was my first go to, which I cleared, it doesn't work for ESET Inspect. (Also, Inspect on Mac/Linux) Seems the policy for Inspect doesn't include "Application Status" selection.

Hi I am receiving a license expires soon status from ESET Inspect from all computers in the organization a month ahead of time. This colors the entire board with Yellow-Warning and makes it hard to filter out what's important and what's not. Can We remove that status like we an do for EEA/EES? Thanks

I Removed the auto upgrade feature just now, thanks for mentioning as it helped me understand it can be removed (or better yet, unassigned)

You are using the wrong quotes. JJ mentioned escape quotes that will make "uname -r" to run as a command and insert the reply in place. to skip it to the actual results you need run "uname -r" alone, get the information and paste it instead of the mention of that in the yum command. e.g. : the command should be yum install kernel-devel-3.10.0-1160.83.1.el7.x86_64 kernel-headers-3.10.0-1160.83.1.el7.x86_64 This is what I get, hope it helps.

@Peter Randziak Hi Peter, I'm writing here to make sure others will be aware of it. I have passed 2-3 version updates that aren't reported in the RSS feed I will choose the most recent example - Ubuntu EEA had an update, nothing is reported, not on the RSS feed, nor on the EC dashboard. Same goes for EESv6 for macOS being updated to 6.11.616.0 for macOS Sonoma support. This is causing all the dev machines running Ubuntu to be automatically updated to 10.1.8.0 and then receive a task to automatically downgrade back as there are rules\dynamic folder-tasks in place to make sure everyone are on a certain version. WIthout me knowing about it, this will throw them into that loop. Also, if the version is broken, I won't know about it until I hear the devs scream in agony that things aren't working for them. - I can't have that. Please escalate that as well. with some urgency and priority. If you have an address i can reach out to, to be heard better as a customer, feel free to message me, I'll be sure to use it. Thank you.

In our case we use WIndows machine, so it's well supported, and most agents have been updated successfully. It's a single machine issue at the moment. something to do with a Module Error: ApplyCustomPolicy: ModuleManager: Unable to load module MODULE_ID_CONFENG2_ERA. Reason: 7001

Yes, however the OS On the server doesn't matter. Agents are able to connect from any platform to any platform the server can be installed on - Linux based or WIndows based. The problem is the installation of the agent fails. need to understand the cause of it. In any case, Thanks, I'll contact support hopefully they will raise a ticket for solution.

the client is installed on macOS Big Sur 11.7.6. it seems when I tried to upgrade the agent from 10.0.xxx to 10.1.3267 the installation failed and the client stopped responding. This only happened on one machine though, so I can't be certain why it happened.

@Grzegorz M - did you resolve it? I"m running into the exact same issue

Thank you for that Peter. Wish the dev-team would invest just a little more in providing proper change log instead of the anonymous "Fixed: Performance / Reliability issues"

Thank you for that mate, really appreciate your answer. I have not changed anything in that part. I'll give it a restart next week as currently i'm deploying 2050 update on windows machine. Thanks again. *quick edit* Inspect on Mac (check release log on the link you provided): 🙃 *second edit* If you change the Operating system type to macos it would have the write package available (at least UI wise) Changelog remains the same.

Hi @Peter Randziak This is a follow up on that I noticed lately few new versions drop out and not appear in the RSS feed. I have new versions for Inspect EEA and ERA and no notification when that happens Can we get something going and escalated - I need release logs to be delivered to my mail as soon as a new version is out or earlier Screenshot of RSS Feed today: Screenshot of new versions out in the Console: (First is Mac, second is windows) ESET Inspect connector for Mac is outdated even though the latest version is only 1.11.2882.0, the version in the screenshot doesn't appear on the list of available versions: (see below) While at it. suggestion, Can we add "Latest" tag to the package versions (on all products) to make sure I don't need to edit task every time a new version sneaks in? (If I feel sure for a certain version, e.g. Inspect) Thanks.

This is great! Thank you very much Peter, I'll definitely add that to my feed and follow up there Kudos!

Hey Peter, Can we ask the Dev Team \ product to provide some release notes prior or when a new version is out? I don't mind being listed for a spam of emails for every minor version that comes out. but I want to know. To give a small analogy from a "small" company (Blizzard) when they messed up their first update, they decided to publish release notes almost a week prior to actually patching. This is extremely important for any client base and community, ESET should be no different. Another option I thought about: We have RSS feed in the web Console. I'm sure there are other options to make sure admins can receive information in a visible and clear manner. Thanks

Yea, I noticed today too. Basically computers were with 2878 and the newest version was 2872. This meant that these installed machines (29 of them) would receive consecutive tasks from the dynamic directory where they are "outdated" just because their version mismatch the latest which used to be 2872. (I am not going to look at the logs to know how much data was sent out over that. I rather sleep at night 😅)