96
ZENworks 10 Configuration Management System Administration Reference
n
ov
do
cx (e
n)
16
Ap
ril 20
10
The following sections contain more information:
Section 8.2.1, “Authentication Role Sever Relationships,” on page 96
Section 8.2.2, “Content Role Server Relationships,” on page 96
Section 8.2.3, “Collection Role Server Relationships,” on page 96
Section 8.2.4, “Imaging Role Server Relationships,” on page 96
8.2.1 Authentication Role Sever Relationships
An Authentication role identifies a managed device that is able to authenticate devices to the
ZENworks Management Zone. When you set up a device to function with a Authentication role, you
must specify a Primary Server as its parent.
8.2.2 Content Role Server Relationships
A Content role identifies a managed device that is able to distribute content (bundles, policies,
system updates, and patches) to other devices. When you set up a device to function with a Content
role, you must specify a Primary Server as its parent. The device with the Content role receives all
content from its parent Primary Server.
8.2.3 Collection Role Server Relationships
A Collection role causes a managed device to collect inventory information, messages (errors,
warning, informational, and so forth), and policy and bundle statuses, then rolls that information up
to its parent Primary Server, which in turn either writes to the database directly or passes the
information on to its parent Primary Server, which does the database writing.
8.2.4 Imaging Role Server Relationships
An Imaging role causes a managed device to take and restore images within as well as across
subnets by using unicast or multicast imaging.
8.3 Changing the Parent-Child Relationships of
Primary Servers
You can move a Primary Server to be a peer or child of other Primary Servers:
Section 8.3.1, “Making a Primary Server a Child,” on page 96
Section 8.3.2, “Making a Primary Server a Peer,” on page 97
8.3.1 Making a Primary Server a Child
You can place a Primary Server as a child of another Primary Server. This child Primary Server no
longer writes collection data directly to the ZENworks database; instead, it passes its information on
to its parent Primary Server, which does the database writing. However, the child Primary Server
still retrieves configuration information from the database and passes configuration information
back up to the database. For this reason, the child Primary Server must have a direct connection to
the ZENworks database
