QuickSilverST250 0 Posted November 28, 2023 Share Posted November 28, 2023 Hi, We saw the version 1.4.50.0 was available, we only update a couple to test. Not long after we saw that all our devices were up 2 date but then saw the new version wasn't showing and went back to 1.3.4.39. What was the reason for the pull back? To many issues? Link to comment Share on other sites More sharing options...
ESET Staff Kstainton 31 Posted November 29, 2023 ESET Staff Share Posted November 29, 2023 Hi @QuickSilverST250, Nothing major, we noticed a file within the product was not signed, anyone who has updated to EFDE v1.4.50.0 before we pulled it are in no way at risk, we just rather have it out there with everything signed properly. Thank you. Link to comment Share on other sites More sharing options...
mkrupa 0 Posted November 29, 2023 Share Posted November 29, 2023 We were trying to encrypt 10 new devices with version 1.4.50 yesterday via our on-prem Protect server but the product faild to activate on the clients. We had to manually uninstall this version of FDE on the clients and roll out the previous version again, which activated fine. Link to comment Share on other sites More sharing options...
ESET Staff Kstainton 31 Posted November 29, 2023 ESET Staff Share Posted November 29, 2023 Hi @mkrupa, If you run into this issue again with EFDE v1.4.51.0 when released, please do report this to us https://www.eset.com/int/support/contact/ as we would be interested to grab some logs and work out why this might be. Thank you. Link to comment Share on other sites More sharing options...
mkrupa 0 Posted November 29, 2023 Share Posted November 29, 2023 Actually the problem got worse. Since ESET pulled back version 1.4.50 we cannot activate newly installed clients with the older version anymore. Our licence is for 320 instances and only 72 are in use now.. From the log of the client: [2023-11-29 13:17:42.629] [agent] [info] [5300] Received Activation task from Agent [2023-11-29 13:18:03.693] [licence] [error] [5300] Cannot send message "association" : 20003 [2023-11-29 13:18:03.693] [licence] [error] [5300] ecp::Result::HttpRetryAfter [2023-11-29 13:18:03.695] [licence] [error] [5300] Association Failed : result 3 resultcode 20003 [2023-11-29 13:18:03.695] [licence] [error] [5300] Activation Failed 0 : 0x00004E23 [2023-11-29 13:18:03.695] [agent] [error] [5300] Activation task has failed Link to comment Share on other sites More sharing options...
ESET Staff Kstainton 31 Posted November 29, 2023 ESET Staff Share Posted November 29, 2023 Can you submit a ticket with the following logs please: https://support.eset.com/en/kb3466-collect-logs-with-eset-log-collector-for-windows Thank you @mkrupa Link to comment Share on other sites More sharing options...
ESET Staff JozefG 9 Posted December 4, 2023 ESET Staff Share Posted December 4, 2023 (edited) @mkrupa do you have by any chance a couple years old FDE policy containing proxy password and applying it together with some newly created one? If so could you try to recreate that policy from scratch and see if it helps? We noticed some issue in Agents with latest Configuration module. Edited December 4, 2023 by JozefG Kstainton 1 Link to comment Share on other sites More sharing options...
mkrupa 0 Posted December 5, 2023 Share Posted December 5, 2023 (edited) @JozefG We have configured a proxy (eset bridge) but the policy is only a few months old and there is no proxy password Edited December 5, 2023 by mkrupa Link to comment Share on other sites More sharing options...
Recommended Posts