Make a locked option editable

[LesRMed 22]

I know it's there, but I'm just overlooking it. Where in the policy can I make these "locked" options editable?

[Marcos 5,070]

You must first enable Override mode via a policy:

[LesRMed 22]

I did that, and applied the policy, but they're still showing locked.

 

In particular, I'm trying to make the exclusions editable (for admins), but Add is grayed out.

Edited August 24, 2022 by LesRMed
Add image

[Marcos 5,070]

I've tested it with real-time protection; after activating override mode the padlock symbol disappeared and I was able to pause real-time protection then:

As for detection exclusions, make sure to enable this setting in a policy first:

[LesRMed 22]

Well it doesn't work on my end. You can see my settings. What else can I check?

[Marcos 5,070]

3 hours ago, LesRMed said:

Well it doesn't work on my end. You can see my settings. What else can I check?

Are you positive that you have this setting in a policy enabled? It's not in your screenshots above.

This should make the Add button in Detection exclusions available on clients.

[MichalJ 434]

Hello @LesRMed

The behavior with regards to policies is like this: 

• when a setting is "set by policy" (by set means, the blue dot / red flash are shown) the setting is NOT editable on the client.  If setting is not "set by policy" if the user locally has admin rights / knows the password to settings, he can change the local configuration freely. 
• only way how to temporarily override the policy settings which are set by ESET PROTECT is by enabling the override mode. Override mode set to "on" and set by policy. On your screenshot, the override mode is neither enabled, neither configured to be reflecting the policy settings. However, once the override mode ends, the settings will revert to the previous state. 
• In order to allow "local exclusions", you need to follow the recommendation from Marcos above. If you allow them being "appended", endpoint will take into consideration exclusions set centrally, and also the ones that are set locally. 

Edited August 25, 2022 by MichalJ

[LesRMed 22]

That made no difference. I give up. I added the exclusion from the console.

[MichalJ 434]

Hello @LesRMed

I have opened this up with our QA department and this is what they came up with: 

In case you enable the setting that allows appending the globally set exclusions to the local list, it will enable you to add the local ones. However, what you need to do first on the endpoint side, is to adjust the "combo box" to "show local exclusions". Once this is done, the add button will enable, and allow you to enter the exclusion locally. 

I have filed an improvement request, to change this behavior, as it is considered as not intuitive. 

 

Edited August 31, 2022 by MichalJ

[LesRMed 22]

Thank you @MichalJ! That's what I needed! Not intuitive is an understatement. LOL