The Location Closest Servers panel in ZENworks Control Center lets you assign ZENworks Primary Servers and Satellites to the location. When a device detects that it is within the location, it contacts the defined servers. By defining the closest servers for the location, you can reduce wide area network traffic and increase ZENworks performance.
In ZENworks Control Center, click
> .In the Locations panel, click the location to display its details.
Click the
tab.Click
to override the closest server settings from the location.(Conditional) If you do not want the Closest Server Default Rule to be used in determining closest servers, select the
option.Closest servers can also be configured on network environments and in the Closest Server Default Rule. When a managed device requests its list of closest server, the ZENworks system combines the server lists from the network environment, location, and default rule (in that order) and passes the combined list to the device. The managed device contacts the first server in the list and continues down the list until it is able to connect.
NOTE:If you choose to exclude the Closest Server Default Rule for a location that does not have any closest server rule configured, then the location is considered as a disconnected location.
Configure the closest servers:
Manage individual servers in any of the server lists (Collection, Content, Configuration, Imaging and Authentication):
Task |
Steps |
Additional Details |
---|---|---|
Add a server to a list |
|
By default, ZENworks Servers support all functions (Collection, Content, Configuration, and Authentication). Therefore, all ZENworks Servers are available for selection in any of the server lists. Satellites, however, can be configured for specific roles (Collection, Content, Imaging, and Authentication). This has the following implications:
Satellite roles are configured in the Server Hierarchy panel on the Configuration tab. |
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 a server from a list |
|
|
Manage server groups in any of the server lists (Collection, Content, Configuration, Imaging and Authentication).
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. |
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.
Manage L4 switches in any of the server lists (Collection, Content, Configuration, and Authentication):
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
to save your changes.