Installation manual
55
HAS IP Range (specify) – if client belongs to the group defined by the IP range…
HAS (NOT) Defined Policy (specify) – if client does (or does not) adopt the policy…
Product Name (NOT) IN - if product name is...
Product Version IS (NOT) - if product version is...
Client Custom Info Mask (NOT) IN - if Client Custom Info contains...
HAS (NOT) Protection Status (specify) - if client´s protection status is...
Virus Signature DB Version IS (NOT) - if virus signature database is...
Last Connection IS (NOT) older than (specify) - if last connection is older than...
IS (NOT) Waiting For Restart - if client is waiting for restart
Policy rules can be imported/exported from/to an .xml file and they can also be created automatically by using the Policy
Rules Wizard, which allows you to create a policy structure based on the existing group structure and map created
policies to groups by creating correspondent policy rules. For more information on importing/exporting policy rules see
chapter titled Importing/Exporting policies .
To remove a policy rule, click the Delete button from the Policy Manager window. Click Run Policy Rules Now if you
want to immediately apply all rules.
5.3.8 Deleting policies
As with rule creation, deleting is only possible for policies located on the server you are currently connected to. To delete
policies from other servers, you must directly connect to them with the ERAC.
NOTE: A policy may be linked to other servers or policies (as a parent policy, as a default policy for lower servers, as
a default policy for primary clients, etc.), therefore, in some cases it would need to be replaced rather than deleted. To see
options for deleting and replacing, click the Delete Policy button. The options described below may or may not be
available, depending on the position of the given policy in the policy hierarchy.
New policy for primary clients with the currently deleted policy – Allows you to select a new policy for primary clients
to substitute the one you are deleting. Primary clients can adopt the Default policy for primary clients, as well as other
policies from the same server (either assigned manually – Add Clients or forced by Policy Rules). As a replacement you
can use any policy from the given server or a replicated policy.
New parent policy for the currently deleted policy’s children policies (if existing) – If a policy to be deleted served as
a parent policy for other child policies, it must also be substituted. It can be substituted by a policy from that server, by
a policy replicated from upper servers, or by the N/A flag, which means that child policies will be assigned no substitute
policy. We highly recommend that you assign a substitute even if no child policy exists. Another user assigning a child
policy to that policy during the deletion process would cause a conflict.
New policy for replicated clients with the currently deleted or modified policy – Here you can select a new policy for
clients replicated from lower servers – those that were applied to the one you are currently deleting. As a replacement you
can use any policy from the given server or a replicated policy.
New default policy for lower servers – If the deleted policy serves as a virtual policy (see section Global Policy Settings),
it must be substituted by another one (for more information, see chapter Virtual policies ). As a replacement you can
use any policy from the given server or the N/A flag.
New default policy for primary clients – If the deleted policy serves as a virtual policy (see section Global Policy
Settings), it must be substituted by another one (for more information, see chapter Virtual policies ). You can use a
policy from the same server as a replacement.
The same dialog will also open if you disable the Down replicable option for a policy and click OK, Apply or if you select
another policy from the Policy Tree. This will activate the items New policy for replicated clients with the currently
deleted or modified policy or New default policy for lower servers.
53
52
52










