Closest Server Rules
When your ZENworks® Management Zone includes more than one server, devices need to know which server to contact. The Closest Server Rules panel lets you create rules that are used to determine which servers a device contacts for the collection, content, and configuration functions.
With respect to Closest Server rules, devices that are configured as Satellites are considered as servers and can be listed for selection in the , , and sections.
You can configure Closest Server rules at three levels:
-
Management Zone: The rules are inherited by all device folders and devices.
-
Device Folder: The rules are inherited by all devices contained within the folder or its subfolders. Overrides the Management Zone settings.
-
Device: The rules apply only to the device for which they are configured. Overrides the settings set at the Management Zone and folder levels.
Click the following headings for information to help you understand and create Closest Server rules.
Understanding Closest Server Rules
The following sections provide information you should understand before you start creating Closest Server rules:
Collection, Content, and Configuration Servers
There are three basic functions for which devices contact a server:
-
Collection: Inventory and message log information is collected from each device to be viewed in ZENworks Control Center and output to reports. Each ZENworks Primary Server and any Satellite can act as a collection server.
-
Content: Provides content to the managed devices. Each ZENworks Primary Server and any Satellite can act as a content server.
-
Configuration: Configuration settings and registration information must be applied to devices. Only ZENworks Primary Servers can act as a configuration server.
A device can contact the same server for all three functions, or it can contact different servers for each function.
Mapping Devices to Collection, Content, and Configuration Servers
A Closest Server rule maps devices with specific network addresses to three lists: a list, a list, and a list.
For example, assume that you want to create a rule for devices that fall within the IP address range of 123.45.678.1 to 123.45.678.100. You specify the IP address range and then create the following three lists:
|
Collection Server List |
Content Server List |
Configuration Server List |
|---|---|---|
|
Server 1 |
Server 3 |
Server 1 |
|
Server 2 |
Server 1 |
Server 3 |
|
Server 3 |
|
Server 2 |
Based on the three lists, any device whose IP address falls within the range will contact Server 1 for collection, Server 3 for content, and Server 1 for configuration. If any of these servers are unavailable, the device contacts the next server in the list.
Effective Rules
Each device can have only one Closest Server rule applied to it. A device’s effective rule is determined as follows:
-
Device settings: Evaluate all rules that are set on the device. If the device meets a rule’s criteria, that rule becomes the device’s effective rule.
-
Folder settings: If no device rule applies, evaluate all rules that are set on the device’s parent folder. If the device meets a rule’s criteria, that rule becomes the device’s effective rule. If not, evaluate the rules on the next folder up the hierarchy.
-
Management Zone: If no folder rule applies, evaluate all rules that are set in the Management Zone. If the device meets a rule’s criteria, that rule becomes the device’s effective rule. If not, apply the default rule to the device.
Creating Closest Server Rules
-
(Conditional) If you are creating Closest Server rules on a device or device folder, click to activate the Closest Server Rules panel.
-
Click to display the Rule Construction dialog box, fill in the fields, then click .
For information on creating the rule, see Rule Construction.
-
Repeat Step 2 to create additional rules.
-
If necessary, when you are finished creating rules, use the and buttons to reorder the rules in the list.
The rules are evaluated in the order they are listed. You should place the rules in the order you want them evaluated.