Mr.Gains

We're currently using Centos 7 on VA, so I don't see an issue. I did receive this, so I figure I'll share just in case others are looking. https://support-eol.eset.com/en/business_managed_remote_va_migrate_to_new.html

Bump. I'm trying to figure which Linux OS to migrate to, as I'm finding all the supported Linux OS in the list are EOL this year except for Ubuntu 20.04 which is EOL next year. Will this list be updated anytime soon? https://help.eset.com/protect_install/11.0/en-US/installation.html?linux.html

Thank you for the clarification. What if I need to enable Windows Defender for endpoints, is there any issues or configuration that can be done?

Just curious if someone could help me out here as I cannot find documentation for ESET configuration with Windows Firewall for both workstations and servers. I got confused that it was recommended that Windows is turned off with another ESET product. Could someone point me in the right direction in where I could find this in ESET Protect? I'm working on the GPOs, and would like to make sure there's no issues in trying to be in compliance and ESET working altogether. Currently on: ESET Protect 10.1.1283.0 ESET Endpoint Security 11.0.2032.0 ESET File Security 10.0.12014.0 Thanks,

Good afternoon, I notice that Rocky Linux 9 in the support OS system for ESET Protect console, but doesn't have any check marks due to not tested. Any one using this OS or how dependable is this OS to run ESET Protect? Currently using Centos 7 and EOL is June this year, so trying to explore options as this OS was mentioned by my colleague is what they preferred. If not this OS then is it better to go Debian 10 or RHEL 8 due to actually being supported?

Is there a way for this to populate in the ESET Protect dashboard under "firewall detections" or will it populate when I enable diagnostic logging?

I had a client that needed a specific port open, but I didn't see any events triggered on ESET Firewall in ESET Protect dashboard when they were trying to access the port. Is there a way I can manually change this on a specific client within a report/dashboard to see if certain ports getting blocked? Initially I thought no alerts for the client system, so it would've assume it wasn't ESET. I applied a policy to their system allowing a port between two systems, then it worked. ESET Endpoint Security 10.1.2050.0 ESET Management Agent 10.1.1292.0 ESET PROTECT Server 10.1.1283.0

It's disabled by default

Good morning, A client is having issues running their VBA macro in excel. I've tried to run an exclusion for the client to bypass ESET from scanning the file path. Whenever the client runs their VBA macro in excel, ESET consumes 30%+ CPU and excel is running 2% therefore causing the computer to run slow. What can I do to resolve this issue effectively? ESET Endpoint Security 10.0.2045.0 ESET Management Agent 10.0.1126.0

Is there a task within the console to restart the service? I had several servers not connected to the console before patching, so I was thinking they will reconnect after reboots. Now the service on those servers not connected will not restart or stop manually (they are running). I can confirm that the servers that were connected before this patching, reconnected after patching. I will attempt the agent live installers to repair those, but curious if there's a work around in the future?

Just an update here for anyone who reading this. MySQL ODBC driver was the issue, simple uninstall/reinstall fixed my issue.

I'm having an issue where I cannot login to the ESET console UI after a reboot. I search the logs and see Error code 14, which I tried to resolve by updating the console and agent to the latest version in which didn't work. What should I do next to resolve where it reboots that it will allow me to login to the console? OS: Centos7 ESET Rogue Detection Sensor 1.1.615.1 ESET Management Agent 9.1.2304.0 ESET PROTECT Server 9.1.2301.0

I'm not seeing the new feature when setting up the upgrade task to clients that a message pop up to allow them to postpone. I've tested it twice to postpone ESET Full Disk Encryption: first machine didn't show any message with the task completed within the console with a delay of 3 days to postpone, and second machine I set to 3 hours but it rebooted immediately upon completion (less than 30 minutes) without any message to postpone. I'm upgrading the system via details of the client in the console. Does "restart when needed" override the postpone option? ESET Endpoint Security 9.1.2057.0 ESET Full Disk Encryption 1.3.3.35 (pre-upgrade was v1.3.1) ESET Management Agent 9.1.1298.0 ESET PROTECT Server 9.1.1295.0 Thanks

I thought I saw somewhere we can't go above 5.x ODBC driver for MySQL? Was this recently change for ESET Protect?

I PM'd you the logs

I'm trying to better understand how the agent works. I had situations where that I can ping the client but they're not showing online in the console. The fix is usually having the user do their windows updates, dell updates, or a second reboot after being fully updated. I would like to know why the agent isn't checking in when the client is online instead of rebooting as a fix. ESET Management Agent 9.0.1141.0 ESET Full Disk Encryption 1.3.1.25 ESET Endpoint Security 9.0.2046.0 ESET Protect 9.0.1144.0

Does ESET do any validation to ensure the update finished applying?

Could I get an update before the next patching window? I noticed this in two different consoles/domains.

ESET Agent : 9.0.2141.0 ESET PROTECT: 9.0.2144.0 ESET Server Security: 8.0.12011.0 We setup tasks to trigger patching, what I've noticed is that the task are shown finished but aren't. For example we had a server complete the updates 4am in ESET console but it didn't finish applying the updates until around 8am. I'm guessing the task is marked finish after the server checks in after the reboot even though it's applying updates? Information isn't useful especially in our production environment where we need the services running. Advanced throttling is default, target local time is unchecked.

Thank you Kstainton! I will update here if I run into anymore related issues.

Surface Pro 7+ 20H2 ESET Endpoint Security 9.0.2032.6 ESET Management Agent 9.0.1141.0 ESET Full Disk Encryption 1.3.1.25 First time experiencing this error after attempting to do the "computer restart is required to initiate Safe start to check hardware and firmware compatibility and perform initialization." step after installing ESET onto the device. After the reboot, I've received a black screen with only this at the top left screen "Start PXE over IPv4", and "Couldn't find a bootable operating system. Check the boot configuration to try to fix this". We've tried the first two steps, but don't have enough time to do the 3rd step : https://support.microsoft.com/en-us/topic/surface-turns-on-and-shows-couldn-t-find-a-bootable-operating-system-b8e6c5b8-7b09-81bb-bfd9-bc118930439c .This has happened to two new devices in a row that we are trying to send out, and now resorting to use an older machine. Is there a workaround to this problem?

Just following up on this, I may just throw this in as a feature request since I'm unable to figure out how to setup the trigger in detail.

Hello, ESET Protect : 9.0.1144.0 I'm trying to see if there a way to setup triggers after 2nd Tuesday on selected day of the week automatically for each month? For example I want to setup a trigger to occur on Wednesday night after the 2nd Tuesday, then setup another trigger to occur Thursdays and so on after the 2nd Tuesday. From what I can see is that I only have the options for monthly triggers is to occur "1st(-5th) occurrence of the selected weekday(s) in a month". If I select start Wednesday night and select 2nd occurrence Tuesday of the month, will that repeat every month automatically? If that doesn't work, is there a way to setup what I want automatically for every month according to the example I provided above?

Thank you guys. It turns out the machines were updated very recently and didn't check back in the console, or users giving us the incorrect machine information for a different machine.

According to my colleague, the report I created is showing incorrect OS version of the client machines. I thought that information will update when the machine checks in the console, or maybe I'm wrong? If I'm wrong, is there a way to enforce update of the client machine's information or how often will it update itself? ESET Endpoint 8.1.2037.2 ESET Management Agent 9.0.1141.0 ESET Protect 9.0.1144.0