Filter Logic - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - POLICY MANAGEMENT REFERENCE 10.3 30-03-2010 Management Manual

Registry Key Exists: Determines if a registry key exists. After specifying the key name, the two
conditions you can use to set the requirement are Yes and No. If you select Yes, the specified key
must exist to meet the requirement. If you select No, the key must not exist.
Registry Key Value: Determines if a registry key value exists on the device. The condition you use
to set the requirement includes the key name, the value name, an operator, a value type, and a value
data. The key and value names must identify the key value you want to check. The possible
operators are equals (=), does not equal (<>), is greater than (>), is greater than or equal to (>=), is
less than (<), and is less than or equal to (<=). The possible value types are INT_TYPE and
STR_TYPE. The possible value data is determined by the key, value name, and value type.
Registry Key and Value Exists: Determines if a registry key and value exists. After specifying the
key name and value, the two conditions you can use to set the requirement are Yes and No. If you
select Yes, the specified key and value must exist to meet the requirement. If you select No, the key
and value must not exist.
Service Exists: Determines if a service exists. After specifying the service name, the two conditions
you can use to set the requirement are Yes and No. If you select Yes, the service must exist to meet
the requirement. If you select No, the service must not exist.
Specified Devices: Determines if the device is one of the specified devices. After specifying the
devices, the two conditions you can use to set the requirement are Yes and No. If you select Yes, the
device must be included in the specified devices list to meet the requirement (an inclusion list). If
you select No, the device must not be included in the list (an exclusion list).

3.11.2 Filter Logic

You can use one or more filters to determine whether the policy should be applied to a device. A
device must match the entire filter list (as determined by the logical operators that are explained
below) for the policy to be applied to the device.
There is no technical limit to the number of filters you can use, but there are practical limits, such as:
Designing a filter structure that is easy to understand
Organizing the filters so that you do not create conflicting filters
Filters, Filter Sets, and Logical Operators
You can add filters individually or in sets. Logical operators, either AND or OR, are used to combine
each filter and filter set. By default, filters are combined using OR (as determined by the Combine
Filters Using field) and filter sets are combined using AND. You can change the default and use
AND to combined filters, in which case filter sets are automatically combined using OR. In other
words, the logical operator that is to combine individual filters (within in a set) must be the opposite
of the operator that is used between filter sets.
You can easily view how these logical operators work. Click both the Add Filter and Add Filter Set
options a few times each to create a few filter sets, then switch between AND and OR in the
Combine Filters Using field and observe how the operators change.
As you construct filters and filter sets, you can think in terms of algebraic notation parentheticals,
where filters are contained within parentheses, and sets are separated into a series of parenthetical
groups. Logical operators (AND and OR) separate the filters within the parentheses, and the
operators are used to separate the parentheticals.
54 ZENworks 10 Configuration Management Policy Management Reference