| After you have installed ZENworks for Servers 3 into your tree and onto your servers, you need to do some administration to get the product really rolling in your system. This section talks about the basics that you need to do to get the product working in your environment. Subsequent chapters discuss these areas in greater detail. Starting Up Management and Monitoring Services Several steps must be accomplished before you can begin the management and SNMP monitoring services for your servers in the network. The management and monitoring services require that several components of the system be up and active. These components are as follows: Management Site Services. This is the server that holds the database and receives all the discovery information and the SNMP traps. This information is stored in the database, and then other agents are activated to perform actions on the information. This must be a NetWare 5 or 6 server. This site server also holds the discovery and MIB tools. Management Console. This is the desktop that is running ConsoleOne and enables you to view the maps, statistics, data, and alarms that have been discovered in the system. ZENworks for Servers 3 installs a local copy of ConsoleOne on the administrator's workstation at installation time. This application is run on a Windows 32 desktop. Server Management. This is an agent that is responsible for monitoring the server and watching for events that warrant an SNMP trap. These traps are then sent to the management server. These agents are run on each NetWare or Windows NT/2000 server that you want to monitor. Traffic Analysis. This is an agent that can run on either a NetWare or a Windows NT/2000 Server and needs to be run on only one server for each managed segment. The data from this agent is also sent to the management server. Inventory Management. An inventory agent exists for both a NetWare and a Windows NT/2000 Server. These agents need to be installed on each server and the inventory is transmitted to the inventory database, stored on the management site server. Remote Management. This is an agent that enables you to perform remote control of the managed servers (that is, servers with the management agent on them). The Windows NT/2000 Server agent is the same as the remote control agent shipped in ZENworks for Desktops 3, and the NetWare agent is a Java remote control agent you place on your NetWare servers. Both these agents are controlled by an interface in ConsoleOne, available on your management console.
To get the basics for management and monitoring services going in your tree, follow these steps after management and monitoring has been installed: Create an SNMP Trap Target policy, if you want to manage your trap targets through policies, and associate the policy with your managed servers. Perform the discovery of the network by running the NetExplorer agent on the NetWare Management Server. Allow the system to find the devices (this usually takes hours, depending on the size of the network) and construct the topology map. Log in to the network via ConsoleOne on your Management Console workstation and drill down into the maps to view information about your servers.
See Chapters 9 and 10, which deal with management and monitoring servers, for more details and discussion on additional features. Starting Up Policy-Enabled Server Management Services Policy-enabled Server Management services enable you to control many behaviors of the server via policies that are defined in eDirectory and then associated with the servers. The TED component of Policy-enabled Server Management Services in ZENworks for Servers 3 enables you to transmit files through the network to various server destinations and have those files placed on the remote servers. The distribution is controlled via eDirectory, enabling you to easily manage the distribution services. To get policy management running in your network, follow these basic steps on each server you installed the Policy-enabled Server Management Services: Ensure that the file SYS:\ZENWORKS\PDS\SMANAGER\ZFS.NCF is part of your AUTOEXEC.NCF file so that the server starts up the policy engines on the server at each boot. Create a Server Policy Package in eDirectory by using ConsoleOne and turn on the specific policy that you want applied to your server or servers. Associate the Server Policy Package, using ConsoleOne, with the servers that enforce the activated policies.
After you have the policy package in eDirectory and have it associated with servers in your tree, these policies are enforced on those servers the next time the agents refresh their policies from eDirectory. To activate the distribution services in your tree, follow these high-level steps in your system: Install the Distribution Services from the CD. When you install the services, you can specify where you want the distributor and the subscriber for your distributions. Traditionally, you have a single distributor send the data to several subscribers. The install also creates the objects in the directory for administering the system. Make sure the distributor and the subscriber are running on the systems. The distributor and subscriber both run from the \ZENWORKS\PDS\TED\TED.NCF file on NetWare servers and as services on Windows NT/2000, Linux, and Solaris servers. Create a distribution. The distribution has a set of files that you want to have distributed across the network. When you create the distribution, you associate it with the distributor (a particular server). Create a channel. The channel contains a logical grouping of distributions to which subscribers can subscribe. Make sure to associate at least one distribution and at least one subscriber to the channel. Resolve certificates. The first time you start the distributor, it creates a public and private certificate set. The public certificate must be copied to the \ZENWORKS\PDS\TED\SECURITY directory on every subscriber that receives or passes along distributions from the distributor. This is a simple process, but very important. You can right-click the distributor object in ConsoleOne and choose Resolve Certificates to have ConsoleOne automatically copy the distributor's public certificate to all the subscribers that need it.
The system should now activate the distributor, which collects the files defined in the distribution and then sends them on to the channel's subscribers. The subscribers should then receive the distribution and unpack it on their respective servers. This happens according to the schedules for the various objects. Remember that the distributor agent needs access to a ZENworks for Servers license to function. For more information about TED, see Chapter 6, "Setting Up Tiered Electronic Distribution." |
