The Closest Server Default rule lets you define the rule that is used by a device to determine the closest authentication, collection, content, and configuration servers when no Closest Server rules have been defined or when none apply. This rule is simply a listing of the servers in the order you want devices to contact them. You cannot add or remove servers from the lists.
The Closest Server Default rule is applicable for ZENworks Configuration Management 10.2.x/10.3.x and ZENworks 11 devices. If you do not want the Closest Server Default Rule to be used to determine the closest servers for devices, you can create customized Closest Server rules. You can create the Closest Server rules for ZENworks Configuration 10.2.x/10.3.x devices at three levels: Management zone, device folder, and device. These settings are disabled when you baseline your Management Zone to ZENworks 11. For a ZENworks 11 device, the customized closest servers are configured on locations. For detailed information, see Section 12.0, Location Awareness.
For Closest Server Default rules, devices that are Satellites are considered as servers and can be listed for selection in the appropriate lists.
By default, all ZENworks Servers function as authentication, collection, content, and configuration servers and are displayed in the appropriate lists. In addition, any devices that are defined with the Content or Imaging roles are also displayed in the Content Servers list, any devices that are defined with the Collection role are also displayed in the Collection Servers list, and any devices that are defined with the Authentication role are also displayed in the Authentication Servers list.
To configure a Closest Server Default rule:
In ZENworks Control Center, click the Configuration tab, click Infrastructure Management (in the Management Zone Settings panel), then click Closest Server Default Rule.
To configure the servers listed in the any section, do any of the following:
(Conditional) You can perform the following tasks to manage individual servers in any of the server lists (Collection, Content, Configuration, and Authentication):
Task |
Steps |
Additional Details |
---|---|---|
Reorder the list |
|
Placement in the list determines the order in which servers are contacted. The first list item (server, group, or L4 switch) is contacted first, then the second, and so forth. You can order the items in the lists differently. This allows you to spread the workload initiated by devices by placing different servers higher in one list than in the other lists. For example:
|
(Conditional) You can use a group to randomize connections to servers. Each time the server list is sent to a device, it is randomized so that not all devices receive the same ordered list.
For example, assume the server list contains the following:
Server 1
Group 1 (Server 2, Server 3, Server 4)
Server 5
One device might receive the following list: Server 1, Server 3, Server 2, Server 4, Server 5.
Another device might receive a different list: Server 1, Server 4, Server 3, Server 2, Server 5.
In all cases, Server 1 is listed first and Server 5 is listed last, but the order of the servers in Group 1 is randomized.
You can perform the following tasks to manage server groups in any of the server lists (Collection, Content, Configuration, and Authentication):
Task |
Steps |
Additional Details |
---|---|---|
Create a server group |
|
|
Add servers to a group |
|
|
Reorder the list |
|
Placement in the list determines the order in which servers are contacted. The first list item (server, group, or L4 switch) is contacted first, then the second, and so forth. You can order the items in the lists differently. This allows you to spread the workload initiated by devices by placing different servers higher in one list than in the other lists. For example:
|
Copy a group from one list to another list |
|
If you copy a group to a list that does not already contain the group’s servers, the unlisted servers are removed from the group. For example, if Group1 includes Server1 and Server2 and you copy Group1 to a list that does not include Server1, Server1 is removed from the group. |
Remove servers from a group |
|
The servers are not removed from the server list, only from the group. |
Remove a group |
|
The group’s servers are not removed, only the group. |
(Conditional) If you have ZENworks Servers that are clustered behind an L4 switch, you can define the L4 switch and add the servers to the definition. This enables the L4 switch to continue to balance the traffic among those servers.
Task |
Steps |
Additional Details |
---|---|---|
Create an L4 switch definition |
|
|
Add servers to an L4 switch definition |
|
|
Reorder the list |
|
Placement in the list determines the order in which servers are contacted. The first list item (server, group, or L4 switch) is contacted first, then the second, and so forth. You can order the items in the lists differently. This allows you to spread the workload initiated by devices by placing different servers higher in one list than in the other lists. For example:
|
Remove servers from an L4 switch definition |
|
The servers are not removed from the server list, only from the L4 switch definition. |
Remove an L4 switch definition |
|
The L4 switch definition's servers are not removed, only the definition. |
Click OK or Apply to save the changes.