I am having some problems with deploying zones and rules within Eset using Administrator and Console versions 5.2.2
I am experiencing the same issue which is described here - https://forum.eset.com/topic/251-problem-with-my-own-zones-in-rules-editor/?hl=zone which doesn't seem to have been fixed yet, but I can work around that. The biggest problem seems to be that when you import zones and associated firewall rules through either manually importing an XML configuration file, or through centralised deployment, Eset alters the zone IDs, which breaks the firewall rule.
As an example, I have installed Endpoint Security and created two new custom zones. I've then created a firewall rule which refers to these two zones. When I export the configuration and look at the XML, these two new zones have the IDs 2 and 4 and are referred to in the firewall rule by those IDs.
If I then subsequently import that configuration into another Endpoint Security installation which already had several custom zones created, it imports my two custom zones, but gives them completely new IDs (in this case 8 and 9). The firewall rule is imported too, but still refers to zones 2 and 4, thus requiring me to manually intervene to re-point it to the zones. The same thing happens if I deploy the policy from the console. I have even tried altering the XML file to give the zones IDs which are not in use, but importing the zones always changes the IDs to the next sequentially available numbers.
So my question is how can I centrally deploy these custom zones and the firewall rule without having to manually intervene, and without having to delete any pre-existing zones from the client? Hopefully I'm missing something really obvious.
Thanks in advance for any help.