Problem with my own zones in rules editor

[Remulus 0]

Hello,

I've created my own zones via Rule setup -> Zones but I can't select them in rules editor. I only see default zones.
It worked in Eset version 4x but it doesn't work in 5.x


Greets
Remulus

 

[marty_c 30]

I assume that you are using ESET Endpoint Security (you posted under ERA). If so, did you create your zones according to these instructions?

[Remulus 0]

I'm using Eset Configuration Editor (5.0.511) from Eset Remote Administrator Console.

I've noticed that on PC  I can select my own zones in rules editor but not in Eset Configuration Editor.

[marty_c 30]

To be clear:

 

When you access the Zones and Rules editor on your client worktstation (endpoint) you can select your own rules.

 

When you try to access your user-created zones via Configuration Editor, they are not available.

 

Is this accurate?

[Remulus 0]

That's right.

[Peter Randziak 1,081]

Hello Remulus,

 

make sure, that you are editing correct settings. It depends on version of the product (line v.3 and line v.4 VS. Endpoint line v.5).

So edit settings in Windows product live v2 and v4 when you are changing configuration of ESET Smart Security / NOD 32 Antivirus Business edition and edit settings in Windows desktop v5 when you are changing configuration of ESET Endpoint Security / ESET Endpoint Antivirus.

 

Regards,

[Remulus 0]

I edit under "Windows desktop v5". Please check attached screens.

 

 

 

[Marcos 4,909]

Try the following:

1, create a new zone and push the configuration to clients

2, download the configuration from a client and create a new rule. I assume the new zone will appear in the list then.

[Bart 4]

Or just press F4 on client who have Your correct cfg and select "use downloaded cfg in new cfg task" -  in this case You will work on real cfg of client - typical "new task" will not show You previously changed cfg

Edited June 3, 2013 by Bart

[Remulus 0]

Try the following:

1, create a new zone and push the configuration to clients

2, download the configuration from a client and create a new rule. I assume the new zone will appear in the list then.

 

It worked but it is very annoying. Each time I add new zone I have to import and export configuration on client :/

 

Thanks for help.

 

.

[Marcos 4,909]

We actually plan to change the system of rule identification in future versions so that newly created custom zones can be used immediately for rules.