john_White24778 1 Posted July 7 Share Posted July 7 Hi Dear ESET Admins. There is many issue in Configuration module 2127.4 Again we find another issue that When we install V9 and V10 EES with AIO installer , No policy will be applied to Clients ! if we upgrade V9 , V10 to V11 then all Policies will Apply. Temporary Agent installation with server assistant will work ! but AIO and ini will cause Agent to not applying policies. ESET PROTECT on-prem (Server), Version 11.0 (11.0.199.0) ESET PROTECT on-prem (Web Console), Version 11.0 (11.0.193.0) Update module 1041 (20240610) Translation support module 2013 (20240625) SysInspector module 1283 (20220614) SSL module 1086 (20240328) Push Notification Service module 1139 (20240603) Configuration module 2127.4 (20240628) On Client Side We have Win7 with these versions: ESET Endpoint Security 9.1.2063.0 ESET Management Agent 10.1.1292.0 ESET log collector of Console and client is attached. Clinet.zip Console.zip Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,273 Posted July 7 Administrators Share Posted July 7 The latest version of the Configuration module is 2127.6. Please try to update from the pre-release update channel to see if it makes a difference. Quote Link to comment Share on other sites More sharing options...
john_White24778 1 Posted July 8 Author Share Posted July 8 17 hours ago, Marcos said: The latest version of the Configuration module is 2127.6. Please try to update from the pre-release update channel to see if it makes a difference. Configuration module 2127.6 is released for EES , Mentioned issue happen in new and clean installation when AV has no Modules and no Updates are don yet ! It means than this problem occurred from Console configuration module ! Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,273 Posted July 8 Administrators Share Posted July 8 How did you perform the installation? Did you create a new All-in-one installer of agent (or agent+security product) with the Configuration module 2127.6 installed in ESET PROTECT? Quote Link to comment Share on other sites More sharing options...
john_White24778 1 Posted July 8 Author Share Posted July 8 54 minutes ago, Marcos said: How did you perform the installation? Did you create a new All-in-one installer of agent (or agent+security product) with the Configuration module 2127.6 installed in ESET PROTECT? Yes Exactly . But if we use AIO or ini , Installed versions will not apply any policy . Removing the agent and install it without any INI will solve the issue and policies will apply ! Quote Link to comment Share on other sites More sharing options...
tedib63028 0 Posted July 8 Share Posted July 8 Hi ESET Admins, We're facing issues with Configuration module 2127.4. When installing V9 and V10 EES with the AIO installer, policies aren't applied to clients. Upgrading to V11 resolves this issue. Temporary agent installation with server assistant works, but AIO and ini prevent policy application. Our setup: - ESET PROTECT on-prem (Server), Version 11.0 (11.0.199.0) - ESET PROTECT on-prem (Web Console), Version 11.0 (11.0.193.0) - Configuration module 2127.4 (20240628) Client setup: - ESET Endpoint Security 9.1.2063.0 - ESET Management Agent 10.1.1292.0 Logs are attached. Thanks for your help. Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,273 Posted July 8 Administrators Share Posted July 8 Is there any reason why you can't use the latest version 11 except the case when installing on Windows 7? As for older versions, the old installers would need to be re-packed so that they contain a recent Configuration module. Quote Link to comment Share on other sites More sharing options...
john_White24778 1 Posted July 8 Author Share Posted July 8 2 hours ago, Marcos said: Is there any reason why you can't use the latest version 11 except the case when installing on Windows 7? As for older versions, the old installers would need to be re-packed so that they contain a recent Configuration module. Win 7 and non-Supported Azure OS can not use V11 , We have many Old systems that are still using win7 and win 10 NonAzure. Re-packing not work even with Configuration Module 2127.6 ! Quote Link to comment Share on other sites More sharing options...
Administrators Marcos 5,273 Posted July 8 Administrators Share Posted July 8 31 minutes ago, john_White24778 said: Re-packing not work even with Configuration Module 2127.6 ! We have not re-packed older installers in the repository yet. It's an option that we are currently considering. Quote Link to comment Share on other sites More sharing options...
john_White24778 1 Posted July 9 Author Share Posted July 9 19 hours ago, Marcos said: Is there any reason why you can't use the latest version 11 except the case when installing on Windows 7? As for older versions, the old installers would need to be re-packed so that they contain a recent Configuration module. FYI dear @Marcos in some networks over 35% of system has not Azure Supported and unfortunately ESET Developers did not pretest modules for nonAzure OS and this will cause many issue for our customers. Right now we are fully analyze the issue in our test environment and we will send you any useful reports : This is the latest news : Non-Azure Version that are new installed with ini or AIO did not receive policy from ESET Protect Console with configuration module 2127.6 (20240702) !!! Even if the AIO installer was generated 1 Year ago !!! it show that the issue is from ESET Protect Console Configuration Module ! Manual upgrading EES/ESS to Azure Supported version will solve the issue without any changing in ESET Agent ! ( It show that ESET Protect Console can not apply Policy to nonAzure Versions. We are analyzing the issue and will send new reports soon. Best regards. Quote Link to comment Share on other sites More sharing options...
john_White24778 1 Posted July 9 Author Share Posted July 9 On 7/8/2024 at 11:53 AM, Marcos said: How did you perform the installation? Did you create a new All-in-one installer of agent (or agent+security product) with the Configuration module 2127.6 installed in ESET PROTECT? This is the exact Issue as our multiple testings : Not Applying Policy Issue is accrued in this circumstances : New Installation of EES 9.1.2063.0 or ESS 10.0.12012.0 ( By ini ot AIO ) at Clients and servers that have no Internet Connection ! In this situation no configuration module is exist or if we use full msi configuration modules are very old. So Agent can not apply any policies and ESS or ESS will not have proxy setting or any other settings so it can not be update , But if we set proxy setting manually and update AV , Policies will be applied after first update ( Perhaps because configuration module is updated ) upgrading to EES 10.1.2050.0 / ESS 10.0.12015.2 will apply policies , but EES 10.1.2050 will not install on Win7 Quote Link to comment Share on other sites More sharing options...
john_White24778 1 Posted July 9 Author Share Posted July 9 On 7/8/2024 at 4:59 PM, Marcos said: We have not re-packed older installers in the repository yet. It's an option that we are currently considering. Dear @Marcos we test manual re-packing these versions with Configuration module 2127.6 , So the first policy apply issue was resolved : EES 6.5.2132.6 EES 9.1.2063.0 ESS 10.0.12012.0 It means that old configuration module in msi is the cause of these problems ! Maybe a ESET Protect configuration module update that support First apply policy for legacy version will help these issues. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.