kingoftheworld

Great news! Thank you. May be good to update that KB I linked above to reflect that information because that is a link provided when you click the top banner in ESET Protect v9 regarding the enabling of Automatic Product Updates.

Thank you! Any update from your colleagues @Marcos?

@Marcos So I guess this statement is false based on https://support.eset.com/en/kb8129-autoupdate-for-business-products.... A little disappointing considering I have spent months planning and working to update my clients to v8.... Enabling auto-updates in ESET PROTECT will only work if you have the supported version of the endpoint security product installed. For example, ESET Endpoint Security 8.x will not auto-update to version 9.x. After the endpoint security product is manually updated to version 9.x, it will then auto-update to later versions when they are available.

Thank you for the response and I will test that. I understand the importance of updates, but without the option to disable these notifications will likely be a deal breaker for my organization. We manage device restarts no less than once per week. The red system tray icon will only result in my users calling in a support ticket. If what you suggested doesn't disable these, please add this feature in ASAP.

@Marcos Will there be a way to suppress these notifications on the endpoint via policy? I am fine with them reporting the status to the console, but I also don't need 5k people opening support tickets asking why their system tray is red.

Great. Thank you!

I have been directed to post feature requests here as that seems to be the only option for accepting customer feedback. I would like to request that ESET Protect, at least the on-premise version, to be able to use use of the many OTP MFA apps available such as Google Authenticator, Authy, etc. The login to ESET Business Account already allows you to use any app of your choosing, but for some reason, this feature was never added to ESET Protect. Being forced to use only the ESET Secure Authentication app for only this is a little annoying, and I am sure I am not alone.

@MartinK Any word on my last question?

Great thank you! One follow up question, if I opt to delay the server upgrade to ESET Protect to v9 until a much later date, will the agents upgrade to v9 with the server on v8.1, or is the server upgrade a pre-req for the auto-upgrade of the agents?

With the recent release of ESET Protect v9, I would like some information on the upgrade process of the agent. If I remember correctly, the release notes for v8.1 included automatic updating of the agents as a feature. If that is accurate, will I just need to update the ESET Protect server to v9, and the agents will automatically begin updating? Or will I need to update them via tasks as I have done for past upgrades?

A related question to this is will this process eventually work to upgrade v8 endpoint to v9 endpoint once it is ready for primetime? Or will we need to plan to upgrade those using the old methods?

This machine updated some time in the last couple of days to v8.1.2037

Thank you. So to confirm there will NOT be an PCU update to version 8.1.2031 that was released at the start of July?

Good morning, I am trying to check on the PCU update status. I have a Windows 10 PC that has been running ESET Endpoint AV 8.0.2039.0 since about the day it was released. The machine has a policy to allow automatic program updates, the EULA was accepted via the ESET protect console, and the machine is restarted at least once per week. It doesn't seem to update past that point. Versions of 8.1 have been around now for greater than two months which I believe was the delay that these updates would operate on.

If ping is correctly sending ICMP between the networks, it is likely not a routing issue. I would check to make sure port 2222 (or whatever you configured) is allowed between the two networks and also on the host firewall for the ESET protect server. A screenshot that Marcos requested will also help identify any potential issue.

Any word on this, I have purposely left a test machine on EEA v8.0, accepted the EULA prompt in ESET Protect, verified policies are set to automatically handle program updates, and nothing has changed to bring it to v8.1.

Sounds like this may be an issue with a firewall somewhere in between or a routing issue. I would check to make sure traffic is passing between the two networks.

I am aware of MSFT's offering for this, but I think this requires MS Defender to be deployed and running on the endpoint. I expect that would cause issues running ESET side by side.

While I know this isn't a current feature, this is something that I think would be a great addition to the product. Something that monitors a key set of 3rd party apps and specific OS patches that are missing reporting back to the console.

If you are simply changing the IP, you could do an DNS record, edit your policy to use the DNS name, then change the DNS record to your new IP.

When is this next service release due out?

Any update on the release after 8.1?

Since ESET Protect 8.1 was just released, Is the next service release coming in the near future? I have the upgrade scheduled and planned but determining if I need to delay pending this next service release.

Can you provide documentation on how to approve the EULA via the console? I searched through the KB and couldn't find anything to show me where to look or what to do.

I would download a fresh copy of the WAR file from ESET's website, move the era.bak and era.new folders to a 2nd location as a backup, then restart the Tomcat service. That should re-create the ERA folders and restore access. This should get you operational again unless you have a special distributed setup.