labynko 5 Posted April 30 Share Posted April 30 Hello. In EESET PROTECT 11.0.14.0, you cannot enable a disabled firewall rule in policies. Rec 0004.mp4 Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted May 1 Administrators Share Posted May 1 Thank you for the heads-up, the issue has been reported to developers. P_EESW-11483 Link to comment Share on other sites More sharing options...
Opapa 2 Posted May 2 Share Posted May 2 Hello Marcos, can you confirm that this problem also exists in other rule editors (e.g. notification settings in Device Control rules, network connection profiles (removal of trusted addresses, and more)? Thank you! Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted May 2 Administrators Share Posted May 2 Yes, it seems to concern policies with rules in general. Link to comment Share on other sites More sharing options...
labynko 5 Posted May 10 Author Share Posted May 10 A terrible bug, you can’t normally change the settings of many policies, you have to create them again. When is this issue expected to be fixed? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted May 10 Administrators Share Posted May 10 There is no ETA yet but it's treated with high priority. Link to comment Share on other sites More sharing options...
Abdou14 0 Posted May 12 Share Posted May 12 hello, same problem (bug) here, in ESET Version 11.0 (11.0.199.0) can't change settings for all the policies rules (e.g. HIPS.....). Link to comment Share on other sites More sharing options...
ESET Staff JozefG 10 Posted May 16 ESET Staff Share Posted May 16 Configuration module 2116.4 with fix is on Prerelease channel. It will be fully released next Wednesday. Link to comment Share on other sites More sharing options...
KaewCYJ 0 Posted May 23 Share Posted May 23 How can we update the configuration module at the ESET PROTECT On-Prem console? Because the issues we encountered are found in the Policies menu. Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted May 23 Administrators Share Posted May 23 3 hours ago, KaewCYJ said: How can we update the configuration module at the ESET PROTECT On-Prem console? Because the issues we encountered are found in the Policies menu. You could change to the pre-release update channel but that's probably not what you would like to do if it's a production ESET PROTECT server and not one intended for testing with a smaller number of endpoints connecting to it. The module should be fully released next week and then you will receive it automatically. Link to comment Share on other sites More sharing options...
KaewCYJ 0 Posted May 23 Share Posted May 23 3 hours ago, Marcos said: You could change to the pre-release update channel but that's probably not what you would like to do if it's a production ESET PROTECT server and not one intended for testing with a smaller number of endpoints connecting to it. The module should be fully released next week and then you will receive it automatically. Thank you for your reply. Can you tell me what day it is next week? Link to comment Share on other sites More sharing options...
Administrators Marcos 5,231 Posted May 23 Administrators Share Posted May 23 We usually release most module updates on Monday but there are many variables that may affect it. Link to comment Share on other sites More sharing options...
KaewCYJ 0 Posted May 31 Share Posted May 31 On 5/23/2024 at 5:05 PM, Marcos said: We usually release most module updates on Monday but there are many variables that may affect it. Sorry, I'm not sure right now. Is configuration module 2116.4 updated in the ESET PROTECT On-Prem console yet? We have been waiting for a long time and we have not received the convenience of using it. Or can we change the update to Pre-release update? Link to comment Share on other sites More sharing options...
ESET Staff JozefG 10 Posted May 31 ESET Staff Share Posted May 31 Configuration module 2116.4 was pulled at the last moment due to regression that the fix in it caused. It is currently being replaced by 2116.5. It is on prerelease update channel and will be fully released on Monday. Sorry for the inconvenience. Link to comment Share on other sites More sharing options...
Recommended Posts