In ZENworks Control Center, click the tab.
Click the underlined link for the desired bundle to display the bundle’s Summary page.
Click the tab.
Click , select a filter condition from the drop-down list, then fill in the fields.
As you construct filters, you need to know the conditions you can use and how to organize the filters to achieve the desired results. For more information, see Section 10.1.1, Filter Conditions and Section 10.1.2, Filter Logic.
(Conditional) Add additional filters and filter sets.
Click to save the settings.
NOTE:After defining a bundle’s system requirements, you can copy its requirements and apply it to other bundles or policies. To do so, click the tab, select the check box in front of the bundle, click , click , select or , then click to select the bundles or policies to which you want to copy the selected bundle’s system requirements.
You can choose from any of the following conditions when creating a filter. Place your mouse pointer over fields that require input to display a tooltip containing example usage.
Architecture: Determines the architecture of Windows* running on the device. The condition you use to set the requirement includes a property, an operator, and a property value. The possible operators are equals () and does not equal (). For example, if you set the condition to architecture = 32, the device’s Windows operating system must be 32-bit to meet the requirement.
Bundle Installed: Determines if a specific bundle is installed. After specifying the bundle, the two conditions you can use to set the requirement are and . If you select , the specified bundle must already be installed to meet the requirement. If you select , the bundle must not be installed.
Configuration Location: Determines if the bundle is applicable to a specific location. The condition you use to set the requirement includes an operator and a value. The possible operators are equals () and does not equal (). The values are the existing locations in the Management Zone. For example, if you set the condition to =location_name, the selected location must match the device’s location to meet the requirement.
Configuration Network Environment: Determines if the bundle is applicable to a specific network environment. The condition you use to set the requirement includes an operator and a value. The possible operators are equals () and does not equal (). The values are the existing network environments in the Management Zone. For example, if you set the condition to =network_environment_name, the selected network environment must match the device’s current network environment to meet the requirement.
Connected: Determines if the device is connected to the network. The two conditions you can use to set the requirement are and . If you select , the device must be connected to the network to meet the requirement. If you select , it must not be connected.
Connection Speed: Determines the speed of the device’s connection to the network. The condition you use to set the requirement includes an operator and a value. 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 values are bits per second (), kilobits per second (), megabits per second (), and gigabits per second (). For example, if you set the condition to >= 100 Mbps, the connection speed must be greater than or equal to 100 megabits per second to meet the requirement.
Disk Space Free: Determines the amount of free disk space on the device. The condition you use to set the requirement includes a disk designation, an operator, and a value. The disk designation can be a local drive map (for example, c: or d:). 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 values are bytes (), kilobytes (), megabytes (), and gigabytes (). For example, if you set the condition to c: >= 80 MB, the free disk space must be greater than or equal to 80 megabytes to meet the requirement.
Disk Space Total: Determines the amount of total disk space on the device. The condition you use to set the requirement includes a disk designation, an operator, and a value. The disk designation can be a local drive map (for example, c: or d:). 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 values are bytes (), kilobytes (), megabytes (), and gigabytes (). For example, if you set the condition to c: >= 40 GB, the total disk space must be greater than or equal to 40 gigabytes to meet the requirement.
Disk Space Used: Determines the amount of used disk space on the device. The condition you use to set the requirement includes a disk designation, an operator, and a value. The disk designation can be a local drive map (for example, c: or d:). 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 values are bytes (), kilobytes (), megabytes (), and gigabytes (). For example, if you set the condition to c: <= 10 GB, the used disk space must be less than or equal to 10 gigabytes to meet the requirement.
Environment Variable Exists: Determines if a specific environment variable exists on the device. After specifying the environment variable, the two conditions you can use to set the requirement are and . If you select , the environment variable must exist on the device to meet the requirement. If you select , it must not exist.
Environment Variable Value: Determines if an environment variable value exists on the device. The condition you use to set the requirement includes the environment variable, an operator, and a variable value. The environment variable can be any operating system supported environment variable. The possible operators are , , , and . The possible variable values are determined by the environment variable. For example, if you set the condition to Path contains c:\windows\system32, the Path environment variable must contain the c:\windows\system32 path to meet the requirement.
File Date: Determines the date of a file. The condition you use to set the requirement includes the filename, an operator, and a date. The filename can be any filename supported by the operating system. The possible operators are , , , , and . The possible dates are any valid dates. For example, if you set the condition to app1.msi on or after 6/15/07, the app1.msi file must be dated 6/15/2007 or later to meet the requirement.
File Exists: Determines if a file exists. After specifying the filename, the two conditions you can use to set the requirement are and . If you select , the specified file must exist to meet the requirement. If you select , the file must not exist.
File Size: Determines the size of a file. The condition you use to set the requirement includes the filename, an operator, and a size. The filename can be any file name supported by the operating system. 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 sizes are designated in bytes (), kilobytes (), megabytes (), and gigabytes (). For example, if you set the condition to doc1.pdf <= 3 MB, the doc1.pdf file must be less than or equal to 3 megabytes to meet the requirement.
File Version: Determines the version of a file. The condition you use to set the requirement includes the filename, an operator, and a version. The filename can be any file name supported by the operating system. 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 ().
Be aware that file version numbers contain four components: Major, Minor, Revision, and Build. For example, the file version for calc.exe might be 5.1.2600.0. Each component is treated independently. For this reason, the system requirements that you set might not provide your expected results. If you do not specify all four components, wildcards are assumed.
For example, if you set the condition to calc.exe <= 5, you are specifying only the first component of the version number (Major). As a result, versions 5.0.5, 5.1, and 5.1.1.1 also meet the condition.
However, because each component is independent, if you set the condition to calc.exe <= 5.1, the calc.exe file must be less than or equal to version 5.1 to meet the requirement.
IP Segment: Determines the device’s IP address. After specifying the IP segment name using CIDR (Classless Inter-Domain Routing) format, the two conditions you can use to set the requirement are and . If you select , the device’s IP address must match the IP segment. If you select , the IP address must not match the IP segment.
You must specify the IP address using CIDR format. With CIDR, the dotted decimal portion of the IP address is interpreted as a 32-bit binary number that has been broken into four 8-bit bytes. The number following the slash (/n) is the prefix length, which is the number of shared initial bits, counting from the left side of the address. The /n number can range from 0 to 32, with 8, 16, 24, and 32 being commonly used numbers. Examples:
123.45.67.12/16: Matches all IP addresses that start with 123.45.
123.45.67.12/24: Matches all IP addresses that start with 123.45.67.
Logged on to Primary Workstation: Determines whether the user is logged on to his or her primary workstation. The two conditions you can use to set the requirement are and . If you select , the user must be logged on to his or her primary workstation to meet the requirement. If you select , if no user is logged on to the workstation, the requirement is not met. However, if a user other than the primary user is logged on to the workstation, the requirement is met.
Memory: Determines the amount of memory on the device. The condition you use to set the requirement includes an operator and a memory amount. 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 memory amounts are designated in megabytes () and gigabytes (). For example, if you set the condition to >= 2 GB, the device must have at least 2 gigabytes of memory to meet the requirement.
Novell Client Installed: Determines if the device is using the Novell Client for its network connection. The two conditions you can use to set the requirement are and . If you select , the device must be using the Novell Client to meet the requirement. If you select , it must not be using the Novell Client.
Operating System - Windows: Determines the service pack level, server type, and version of Windows* running on the device. The condition you use to set the requirement includes a property, an operator, and a property value. The possible properties are , , and . 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 property values vary depending on the property. For example, if you set the condition to version = Windows XP Versions, the device’s Windows version must be XP to meet the requirement.
NOTE:Be aware that operating system version numbers contain four components: Major, Minor, Revision, and Build. For example, the Windows 2000 SP4 release’s number might be 5.0.2159.262144. Each component is treated independently. For this reason, the system requirements that you set might not provide your expected results.
For example, if you specify in the first field, in the second field, in the third field, and in the last field, you are specifying only the first two components of the version number: Major (Windows) and Minor (5.0). As a result, for the requirement evaluated to true, the OS will have to be at least 5.1 (Windows XP). Windows 2003 is version 5.2, so specifying > 5.2 will also evaluate to true.
However, because each component is independent, if you specify the version > 5.0, Windows 2000 SP4 evaluates to false because the actual version number might be 5.0.2159.262144. You can type 5.0.0 to make the requirement evaluate as true because the actual revision component is greater than 0.
When you select the OS version from the drop-down, the Major and Minor components are populated. The Revision and Build components must be typed in manually.
Primary User Is Logged In: Determines if the device’s primary user is logged in. The two conditions you can use to set the requirement are and . If you select , the primary user must be logged in to meet the requirement. If you select , the user must not be logged in.
Processor Family: Determines the device’s processor type. The condition you use to set the requirement includes an operator and a processor family. The possible operators are equals () and does not equal (). The possible processor families are , , , , , , , , , , and . For example, if you set the condition to <> Celeron, the device’s processor can be any processor family other than Celeron to meet the requirement.
Processor Speed: Determines the device’s processor speed. The condition you use to set the requirement includes an operator and a processor speed. 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 processor speeds are hertz (), kilohertz (), megahertz (), and gigahertz (). For example, if you set the condition to >= 2 GHz, the device’s speed must be at least 2 gigahertz meet the requirement.
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 and . If you select , the specified key must exist to meet the requirement. If you select , the key must not exist. For example, if you specify HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Messenger\Login and set the requirement to , the specified registry key must exist to meet the requirement.
Registry Key Value: Determines if a registry key value meets a defined condition. 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 (specify a decimal value) and . The possible value data is determined by the key, value name, and value type.
If the value type is , ZCM compares only those values in the registry if the actual type in the registry is REG_STRING or REG_EXPANDED_STRING.
If the value type is , ZCM compares only those values in the registry if the actual type in the registry is REG_DWORD.
Leave the key value field blank to use the default value. The default value of a registry key has no name and is displayed in regedit as (Default).
For example, if you specify HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Messenger\Login as the key name, Port as the value name, select as the operator, select as the value type, and specify 443 as the value data, the port specified as the value data must match with the port specified in the registry key to meet the requirement.
If the value type is , ZCM compares only those values in the registry if the actual type in the registry is REG_STRING.
NOTE:The filter condition is available only for Windows bundles. The value type for Registry Key Value is applicable only in VDI environments (VMwareVDI and CitrixVDI).
If you have set the condition to and selected as the value type, then the two conditions that you can use to set the requirements are and . If you select , then the thin-client IP address of the device must be within a specific subnet. If you select , then the thin-client IP address of the device must be outside the subnet.
Specify the following in the text fields:
Path of the registry key that should be compared
Name of the registry value, for example: ViewClient_IP_Address
IP Address of the network and a subnet mask to compare in order to determine if the device is within the segment (Example: 10.0.0.0/24)
For the VMware-VDI Environment
If you are connected to a VMware desktop from any thin client, the following registry key will be created automatically in the VMware desktop, indicating the thin-client IP address through which it is connected. You can use the same Registry key as a filter to specify the filter requirement.
Example 10-1 Example:
Registry key Path: HKEY_CURRENT_USER\Volatile Environment
Registry key Name: ViewClient_IP_Address
Value: This specifies the thin-client IP address through which you are connected to the VMware desktop. This value should be in the CIDR format for both and (Example: 10.0.0.0/24).
For the Citrix- VDI Environment
If you are connected to a Citrix desktop from any thin client, the following registry key will be created automatically in the Citrix desktop, indicating the thin-client IP address through which it is connected. You can use the same registry key as a filter to specify the filter requirement.
Example 10-2 Example:
Registry key path: HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Ica\Session
Registry key name: ClientAddress
Value: This specifies the thin client address through which you are connected to the Citrix desktop (Example: 10.0.0.0/24).
Registry Key and Value Exists: Determines if a registry key and value exist. After specifying the key name and value, the two conditions you can use to set the requirement are and . If you select , the specified key and value must exist to meet the requirement. If you select , the key and value must not exist.
For example, if you specify HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Messenger\Login as the key name, Port as the value name, and set the requirement to , then the HKEY_LOCAL_MACHINE\SOFTWARE\Novell\Messenger\Login key having Port as its value, must exist to meet the requirement.
Service Exists: Determines if a service with the given name exists in the list of the system. Specify a service name and ensure that the service name is not enclosed in quotes. After specifying the service name, the two conditions you can use to set the requirement are and . If you select , the service must exist to meet the requirement. If you select , 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 and . If you select , the device must be included in the specified devices list to meet the requirement (an inclusion list). If you select , the device must not be included in the list (an exclusion list).
You can use one or more filters to determine whether the bundle should be distributed to a device. A device must match the entire filter list (as determined by the logical operators that are explained below) for the bundle 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
You can add filters individually or in sets. Logical operators, either or , are used to combine each filter and filter set. By default, filters are combined using (as determined by the field) and filter sets are combined using . You can change the default and use to combined filters, in which case filter sets are automatically combined using . 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 and options a few times each to create a few filter sets, then switch between and in the 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 ) separate the filters within the parentheses, and the operators are used to separate the parentheticals.
For example, “(u AND v AND w) OR (x AND y AND z)” means “match either uvw or xyz.” In the filter list, this looks like:
u AND v AND w OR x AND y AND z
Filters and filter sets cannot be nested. You can only enter them in series, and the first filter or filter set to match the device is used. Therefore, the order in which they are listed does not matter. You are simply looking for a match to cause the bundle to be applied to the device.