Once a policy package is created, you can associate it with a variety of NDS^TM objects in order to set policies for Workstations or for the objects associated with them.

See the following sections:

Policy package associations flow down a tree, much like the NDS Inherited Rights. When you choose to view the associated policy packages for an object, the system (by default) starts at the object and searches up the tree for all associated policy packages: first, with the object; second, with any Group that the object belongs to; and third, with any of the Container objects where the object resides up to [Root].

Just like assigning different rights for different users in NDS, you can set a general policy for most users, and a unique policy for a unique user. Unless otherwise specified in a Search policy, when the system starts searching for the associated policy packages for an object, it starts at the object and works its way up the tree. Any enabled policy in a policy package associated directly with an object takes control, even if a contradicting policy in a policy package is higher in the tree.

You can use the procedures here to create and associate policy packages with objects. You can also associate policy packages with objects from each object's Associated Packages page.

An enabled policy in a policy package is not effective unless the policy package is associated with an object. Policy packages can be associated with User or Workstation objects using one of three methods:

• Create or modify a policy package
• Create or modify a User or Workstation
• Associate a policy package with a Group, Workstation Group or Container object in which the User or Workstation object is a member

An enabled policy in a policy package is not effective unless the policy package is associated with an object. You can associate policy packages with Users, Groups, Workstations, Workstation Groups, or containers, depending on the type of policy package. As your Workstation Management needs change, so might your associations between policy packages and objects.

Just like assigning different rights for different users in NDS, you can set a general policy for most users, and a unique policy for a unique user. Unless otherwise specified in a Search policy, when the system starts searching for the associated policy packages for an object, it starts at the object and works its way up the tree. Any enabled policy in a policy package associated directly with an object takes control, even if a contradicting policy in a policy package is higher in the tree.

A policy package can be associated with an object when

• The object is created
• The policy package is created
• You modify either the object or the policy package

An enabled policy in a policy package is not effective unless the policy package is associated with an object (such as User, Group, Workstation, Workstation Group, or Container objects, depending on the type of policy package). As your Workstation Management needs change, you might also need to change associations between policy packages and objects.

You must have the Write right to both the policy package and the object in order to associate them with one another.

You can associate a policy package with an object when

• The object is created
• The policy package is created
• You modify either the object or policy package