| Novell ZENworks for Servers 3 requires some changes to your directory tree structure (namely, new objects and attributes in the schema) and installs the latest ConsoleOne along with the snap-in extensions to ConsoleOne that ZENworks for Servers 3 requires. Additionally, several components are required on your servers if they are to be able to use the system. This section details the changes that are needed to implement ZENworks for Servers 3 into your network. Learning about ZENworks for Servers 3 Objects When you install ZENworks for Servers 3 into your tree, it not only copies the executable files necessary to run the software, but it also extends the schema in your tree. The schema extension in your tree introduces several new objects and attributes to your system. The following is a high-level list of the changes to your schema. Container package object. This object collects for your administration all the policies that are available to be associated with a container. You create one of these objects when you want to affect a container policy. One such policy is the search policy, which affects the limit and order of searching for all ZENworks services in and below the container. Database object. This object represents the database in the network where you are storing such information as logs of ZENworks activity and events, as well as hardware and software inventory information. The service location package object refers to this object and can represent the same database used by ZENworks for Desktops. ZENworks for Desktops and ZENworks for Servers share the same database object; however, they each have their individual configuration parameters that can be independently configured for each product. This object has separate configuration attributes. You get to the configuration by pressing the Properties button. MW account object. This object contains the username and password that the services use to retrieve information from the management domain. MW domain object. This object represents the management domain of information (that is, the database that contains the discovered components in the network). All queries and reports against management information are referenced relative to this domain. MW scope object. This object holds a SQL query that retrieves out of the domain (database) the set of devices that a particular associated user may view and manage. MW service object. This object is an extension of the SAS object and contains additional information to identify the specific ZENworks for Servers 3 management service and relationships with the domain and other management objects. The services on the various servers, which need access to the system, log in to eDirectory by using this object. NT server object. This object is being introduced to represent an NT/2000 server in the network. Other eDirectory objects can then reference this NT/2000 server object to identify the server that has their service. Currently, this object stores the DNS name of the server along with the other traditional server fields. Policy objects. Several policy objects are introduced into the tree, representing policies that are contained in the Server policy packages. Currently in ZENworks for Servers 3, over seven different policies, such as workstation policies, are created and used in the ZENworks for Servers system. RBS module object. This object is a container object that can contain task objects. This is basically a grouping of task objects. RBS role object. This role object identifies the set of tasks that a role can perform. The set of tasks is referenced to the task object or to a module object that contains a set of tasks. Remote Web Console object. This object controls the configuration for the Remote Web Console used in communicating via a browser to the policy and distribution services such as a distributor and a subscriber. The object can specify such items as requiring SSL for the connection. SAS service object. This object may already be in the tree if you have SAS installed (which is normal for NetWare 5 and above, but not in NetWare 4). This object provides a Directory Services authentication method for the agents and services that are running on the servers. The agents and services log in to the directory via these objects. It is discussed here because it will be new for some systems. Server group object. This object enables the creation of a group of servers. This is useful when you want to apply a Server Policy package to a group of servers. Service location package object. This package collects the policies that are in the system that are related to locating services in the network. Currently these policies include the ZENworks Database Location Policy, ZENworks License Policy, TED Policy, and others. You can create them by selecting File NewPolicy Package in ConsoleOne. Server package object. This object collects all the policies that are available for servers. The policies for servers in the ZENworks for Servers 3 product include such policies as the Server Downing Policy, the Scheduled Down Policy, and the Set Server Parameters Policy. Other server policies that are compatible with this object are also included in the ZENworks for Desktops 4 product. TED channel object. This object represents and holds configuration parameters for the channel, which is a logical grouping of distributions. A subscriber subscribes to a channel to receive distributions that are placed into the channel. TED distribution object. This object represents and holds information about the files to transmit through the network. The channel object refers to this object to identify the distributions that are sent. In a distribution object, you must identify the distributor that is performing the transmission. TED distributor object. This object represents and holds configuration parameters for the distributor on the specified server. As the distributor activates, it retrieves information from its object in the tree to autoconfigure itself. The distributor is responsible for sending files from itself to any subscribers specified in the system. TED external subscriber object. This object represents a subscriber that is not an integral part of the tree. This is a subscriber that is governed by an object in another tree. This object stores the IP address of the remote subscriber. TED subscriber group object. This object represents and holds configuration information for a group of specified TED subscriber objects. TED subscriber object. This object represents and holds configuration information for the subscriber that is running on the specified server. The subscriber receives its configuration information out of this object through the distributor. The subscriber itself does not authenticate and retrieve this information from the Directory.
Existing Objects Modified in the Tree Installing ZENworks for Servers 3 modifies the following objects that are already in your tree to enable the new attribute zenpolPolicy to be part of these objects: country, locality, organization, organizational unit, group, server, and server group. The zenpolPolicy attribute enables each of these objects to be associated with a ZENworks for Servers 3 policy or policy package. These changes should not increase these objects more than 128 bytes. In addition to these changes, the server object is modified to also contain a group membership attribute. This enables the server to be associated with groups and maintain links from the server object back to the various groups with which it has membership. Depending on the number of groups with which the server is associated, this attribute consumes approximately 128 bytes for each group membership. The server object is also extended so that it may contain a new attribute to associate it with an SAS service object. This attribute should take only about 128 bytes. Discussing Policy Packages and Policies To help in the administration of all the features and policies of ZENworks for Servers 3, the various policies are conveniently grouped into policy packages. These policy packages are logical groupings of policies that are valuable for a server or service. Policy packages may be associated with the various appropriate objects. Server packages, for example, may be associated with a single server, a group of servers, or a container. A single policy package may also be associated with several servers, groups, and containers. Because each ZFS service looks for policies by searching up the tree from its corresponding object in the directory, it is desirable to keep this search from proceeding too far up the tree. Therefore, ZENworks for Servers 3 (along with its companion ZENworks for Desktops 4) includes a search policy found in the Container policy package. This policy limits the number of container levels and the search order that all ZENworks for Servers 3 systems use to discover and apply policies. Various services are used by the ZENworks for Servers 3 system, and these services are located by the Service Location Policy package. This package is associated with a container and identifies where SNMP traps and the database are located, for example. The applications in the system then use the database that is specified in the location policy. |
