kamiran.asia

it seems that ESET bridge catch is not working probably in version 2.0.2 Catch folder in many cases has a small size seems that update file are not saved in catch folder. Also Update.ver.signed file did not update instantly and endpoints receive old versions. Any Body has similar issues with ESET Bridge ?

Hi dears. Today we find a terrible problem that cause many Endpoints not to be updated. Endpoint on Client side show error " File Not found on server " according to our investigations , Bridge did not send fresh copy on update.ver to clients . Clearing bridge catch solved the problem and fresh copy of files received by the endpoints. How can we prevent these problems in bridge or is it a bug ?

The issue is random . We are working on but there is no rule that the issue occurred in special situation. Even when we change the static group , Policies will work and merge correctly. We will create the ESET Log Collector in the problematic endpoints,

Yes , may be you are right . because we can not reproduce the issue in every situation. We are working to find the source of problem exactly.

in this video you can see that how one Firewall Role will gone after update to 1438.2 , and just one Policy will remain after update. ESS Version 10.0.2034 PolicyGone.mp4

We reproduce the bug and this is the video : in any Version of ESS with Firewall 1438.2 , Firewall Rules will not merge , But when ESS upgrade to 10.1.2046.0 , Same policies will work and merge probably. We guess this problem will cause in new installation and after update to 1438.2 , V9 Firewall Bug.mp4

Correction : Mentioned issue is occurred just in V9 Version ( With fresh new installation ) upgrading to latest version 10.1 will solve the problem. But for windows 7 - 8 that v10 is not available , Firewall Rules can not be merged via ESET Protect Policy , Just one Policy Rules will be set at endpoint V9. PreRelease 1439 not helped. Will this issue solve at firewall module 1440 ?

This Problem accrued just in new installation v9 / V10 / V10.1 ! installed versions not involved ! just fresh installation will have this problem and two Firewall Config will not merged. PreRelease and module 1439 not helped . Other Module policy works correct in merging , For example HIPS policy merge correctly.

Hi Dears. In Many Endpoints manged with ESET Protect , Firewall Policy is not merged ( When we use two policy at same time ( Append + Prepend ) ) Just one policy will apply and second one will be ignored. Firewall module 1438.2 Configuration 2075.5 What can we do for this issue ?

Thank You dear Marcos . So as ESET mentioned in that link : Existing installations of ESET products will not be affected and will keep receiving module updates. So Windows 7 and 2008 R2 do not need to install required KB to receive module updates . Is it correct ? Just for installation of new products and upgrade the old products !

We must work on this case , But Windows 7 and 2008 need ESU for these updates , So ESET will stop update on 7 and 2008 after DEC 2023 !

We are confused ! ESET Should release a KB to solve this problem !!!

Hi dears. this week many of our servers become yellow in ESET Protect console with this alert : Your operating system is outdated You're using an outdated version of your operating system. To receive the latest product updates and stay protected in the future, upgrade your operating system. See your options: https://support-eol.eset.com As you can see at the Screenshot attache " Windows 2012 - 2019 " and this alert can not be disable in Application status !!! What can we do for these many yellow servers that most of them are in isolated network !! Why these alerts can not be off from application statuses . These are very annoying. Best Regards

Same problem in many ESET projects ...

Hi Dear @Marcos , bug still exist at EESW 9.1.2057 , Did they forgot to fix ? 🤪

Thank You dear , We will Check it out

Thank you dear Marcos . You are awesome, We are waiting for any updates.

Hi dears. is Debian 11.4 supported by latest ESET Server Security for Linux ? Installation will cause RealTime not functional.

Those 3 servers Windows was not updated because they have not Internet Connection. After Update Windows , Live-grid Error solved. May be some Ca Certificates or ... was not updated .

Thank you dear @Marcos for your rapid reply . Every 4 Mail Servers are using the same internet and same apache proxy ! Last year when we have such problem you sent us a tools called ASCloudDiag v1.0.0 is there any newer version ? and if this tool show all address and server is reachable how can we check the issue ? Is there any link or address to check live grid connectivity ? or any think like this.

Hi Dears , We have 4 Mail Server in a Project 1 - ESET Mail Security for Microsoft Exchange Server 9.0.10008.0 Win Server2016 With Internet Connection 3 Others EMS 9.0.10008.0 Server2012 R2 with out Internet Connection All Are using Apache Http proxy. 3 EMS has Live grid alert and Anti spam limit cloud connectivity Error , Even with Direct Connection and not Using Apache , Errors will not resolve ! How can we check Anti Spam Network Connectivity and Live Grid ? is it important that they are 2012 R2 ? There was a tool "ASCloudDiag_x64.exe" to check connectivity , is there any new version of this tool ? Best Regards.

As Always you're awesome @Marcos

After 5 days we did not receive any answer from Ticket #00401625 dear @Marcos

That's it ! You are awesome

It must be a bug in ESET Protect 9.1 and it may be fix in next release. ESET admins must approve it.