Kanenas 0 Posted August 20, 2018 Share Posted August 20, 2018 Hi everybody, I just upgrade my ESET ERA 6.5 to ESET SMC 7 and everything went perfect during installation. After this, i navigate the new settings of eset, and i noticed that there are some differences in policy settings. I edited an policy which migrated from era 6.5 and i noticed that there are missing many settings. If you try to create new policy all settings are there. Do i have to recreate my policies for the new ESMC7? I tried to export the policy and re-import it, but i got same results (many settings are still missing). For example a section that is missing is "Network attack protection". It will be very difficult to recreate so many policies and some of them are very complex. Any ideas? Thanks in advance Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted August 20, 2018 ESET Staff Share Posted August 20, 2018 @Kanenas What do you mean by "missing settings"? We have released a new version of CE module, which not reflects the state of the advanced setup of Endpoint clients V7 (I assume, you are talking about Endpoint policies). Network attack protection has changed location within the advanced setup tree. Can you maybe post a screenshots of the problem you are having? Link to comment Share on other sites More sharing options...
Kanenas 0 Posted August 20, 2018 Author Share Posted August 20, 2018 (edited) Hi MichalJ Yes, i forgot to mention product family i use. ESET Endpoint Security 1st Image is create new policy from ESMC 7 2nd image is edit policy migrated from ERA 6.5 As you can see, there is not any option "Network attack protection" in migrated policy Edited August 20, 2018 by Kanenas Link to comment Share on other sites More sharing options...
ESET Staff MichalJ 434 Posted August 20, 2018 ESET Staff Share Posted August 20, 2018 (edited) If possible, can you please send us the exported "migrated" policy for analysis? If it does not include any sensitive data, of course. You can send it via private message. Also, recommendation from the developers was to open such policy, save it again, and then open it again, whether the issue still persists. Thank you. Edited August 21, 2018 by MichalJ Link to comment Share on other sites More sharing options...
Recommended Posts