Novell ZENWORKS HANDELD MANAGEMENT 7 SP1 IR4 - ADMINISTRATION Administration Manual page 23

Hide thumbs Also See for ZENWORKS HANDELD MANAGEMENT 7 SP1 IR4 - ADMINISTRATION:
Table of Contents

Advertisement

The search order that ZENworks Handheld Management uses is consistent with standard eDirectory
behavior and any search policies that are in the tree. By default, ZENworks Handheld Management
starts at the handheld device or user object, followed by any Handheld groups or User groups that
the device is a member of, and then starts walking up the tree looking for policies to enforce. All
handheld policies are merged and the culmination is applied to the handheld device. If any conflicts
occur, such as two Palm Configuration policies (one associated directly to the handheld device
object and the other associated to a parent container of the handheld device object), the first policy
found is enforced. In this case, the Palm Configuration policy directly associated to the handheld
device object is enforced.
If a policy contained in a Handheld User Package and another policy in the Handheld Package
conflict, the settings in the Handheld User Package are enforced. For example, if you configure and
enable the Palm Configuration policy in the Handheld User Package, but you also have an enabled
Palm Configuration policy in the Handheld Package, the policy is the Handheld User Package takes
precedence.
The File Retrieval policies (Palm File Retrieval and WinCE File Retrieval) present exceptions to
rule that the first policy found is enforced. These policies are both plural (meaning they can be
added many times to a policy package) and cumulative (meaning that many different File Retrieval
policies with different settings can be effective for a single handheld device object, handheld group
object, or container object). Because the File Retrieval policies are plural and cumulative, no
conflicts occur when ZENworks Handheld Management encounters multiple File Retrieval policies:
every effective File Retrieval policy is enforced.
The Search policy is used to limit how far up the tree ZENworks Handheld Management searches
for the effective policies. In addition to limiting how far up the tree ZENworks Handheld
Management searches for policies, both policies let you determine the searching order (object,
group, container) that ZENworks Handheld Management uses as it searches for policies. The search
order is significant because the first policy found is enforced (except for the File Retrieval policies,
as explained previously).
The Handheld Application Search policy is used to limit how far up the tree ZENworks Handheld
Management searches for handheld application objects.
If your directory contains many objects, ZENworks Handheld Management performs significant
tree-walking if no search policies are enabled. For this reason, you should make use of both the
Search policy and the Handheld Application Search policy.
The Search policy and the Handheld Application Search policy provide the following benefits
Improved security
The ability to reorder a search
Better search performance by limiting the search levels traversed in eDirectory and by avoiding
unnecessary LAN traffic
The Search policy specifies how ZENworks Handheld Management determines which policies are
associated with handheld device objects. The Handheld Application Search policy specifies how
ZENworks Handheld Management determines which handheld application objects are associated
with handheld device objects. To make either search policy effective, you associate it with a
container. Both search policies apply to handheld device or user objects within or beneath a given
container.
You can specify the number of levels above or below the location to begin the search:
Using ZENworks Handheld Management Policies
23

Advertisement

Table of Contents
loading

Table of Contents