55
after the name of an imported policy.
5.3.5 Viewing policies
Policies in the Policy Tree structure can be viewed directly in the Configuration Editor by clicking
View...
or
View Merged...
.
View Merged
– Displays the merged policy created as a result of inheritance (the process of inheriting applies settings
from the parent policy). This option is displayed by default, because the current policy is already a merged policy.
View
– Displays the original policy before it was merged with a parent policy.
On lower servers, the following options are available for policies inherited from upper servers:
View Merged
– Same as above
View Override Part
– This button applies for policies with the attribute Override any child policy. This option only
shows the forced part of the policy – i.e. the one which has priority over other settings in child policies.
View Non-force part
– Has opposite effect of View Override Part – only displays active items, to which Override… is
not applied.
5.3.6 Importing/Exporting policies
The Policy Manager allows you to import/export policies and policy rules. Existing policies can be imported/exported
from/to an
.xml
file by clicking the
Import Policies.../Export Policies...
button. The policies can furthermore be
imported from groups by clicking the
Import from Groups...
button. Policy rules can be imported/exported by clicking
the
Import.../Export...
button and, in addition, they can be created using the
Policy Rules Wizard
.
Name conflicts (the existing and the imported policy names are identical) are solved during the import by adding a
random string to the name of the imported policy. If a conflict cannot be resolved in this fashion (usually due to the new
name being too long) the import finishes with the warning
Unresolved policy name conflict
. The solution is to delete or
rename the conflicting policies or policy rules.
5.3.7 Assigning policies to clients
There are two main rules for assigning policies to clients:
1. Local (primary) clients can be assigned any local policy or any policy replicated from upper servers.
2. Clients replicated from lower servers can be assigned any local policy with the
Down replicable
attribute or any
policy replicated from upper servers. They cannot be forced to adopt policies from their own primary server (to do so,
you must connect to that server with ERAC).
An important feature is that each client is assigned some policy (there is no such thing as clients with no policy). Also,
you cannot take a policy away from a client. You can only replace it with another policy. If you do not want to apply
a configuration from any policy to a client, create an empty policy.
5.3.7.1 Default Primary Clients Policy
One method of assigning policies is automatic application of the Default Primary Clients Policy, a virtual policy that is
configurable in Global Policy Settings. This policy is applied to primary clients, i.e. those directly connected to that ERAS.
For more information see chapter
Virtual policies
.
5.3.7.2 Manual assigning
There are two ways to manually assign policies: Right-click a client in the
Clients
pane and select
Add Policy
from the
context menu, or click
Add Clients
>
Add/Remove
in the Policy Manager.
Clicking
Add Clients
in the Policy Manager opens the
Add/Remove
dialog window. Clients are listed on the left in the
format Server/Client. If the
Down replicable policy
is selected, the window will also list clients replicated from lower
servers. Select clients to receive the policy by using the drag-and-drop method or clicking
>>
to move them to
Selected items
. Newly selected clients will have a yellow asterisk and can still be removed from
Selected items
by
clicking the
<<
or
C
button. Click
OK
to confirm the selection.
NOTE:
After confirming, if you reopen the
Add/Remove
dialog window, clients cannot be removed from
Selected items
, you can only replace the policy.
54
