5.3 Policy-Enabled Server Management

This section contains the minimum server requirements for Policy and Distribution Services, Server Inventory, and Remote Management:

5.3.1 General Server Requirements

The following sections provide general requirements information:

Mixed eDirectory Environments

ZENworks Server Management can run in a mixed eDirectory environment. For example, your network might have both eDirectory 8.x and NDS® 6.x or 7.x installed. However, ZENworks Server Management cannot run in a mixed NetWare environment in a cluster (see Section F.3.1, Meeting System Requirements for Clustering).

eDirectory 8.6.2 or 8.7.1 or later is required for ZENworks Server Management so that its objects can be placed in the tree during installation of the product. eDirectory must be installed with the master replica somewhere in your network, but not necessarily on a server where you are installing the ZENworks Server Management software.

The only requirement for any Policy and Distributions Services server is that it can communicate with the server where the eDirectory master replica (of the partition where its NCP Server object resides) is installed. Therefore, you do not need to install eDirectory on each server where you want to install Policy and Distributions Services. However, Server Inventory requires eDirectory to be running on each Inventory server.

NetWare Support Packs

To determine the current Support Pack version on a NetWare server, enter version at the server’s main console prompt.

You can download Support Packs from Novell Support.

Windows Service Packs

To determine the Service Pack level on a Windows server, right-click My Computer > Properties.

You can download Service Packs from Microsoft.

5.3.2 NetWare Server Requirements

Following are the common NetWare minimum requirements for Policy and Distribution Services and Server Inventory:

Table 5-3 Common Minimum NetWare Requirements for Policy and Distribution Services and Server Inventory

Requirement

Policy and Distribution Services

Inventory Server

Inventory Agent Server

Novell eDirectory

8.6.2 or 8.7.1 1

8.6.2 or 8.7.1

8.6.2 or 8.7.1

Cache for the Policy and Distribution database file

32 MB

N/A

N/A

Free Disk Space

35 MB for Policy and Distribution Services files

100 MB for Inventory with database; 25 MB for Inventory alone

N/A

Disk Space for ConsoleOne® Snap-Ins

70 MB

70 MB

N/A

Database File Location

Any volume other than sys:

Any volume other than sys:

N/A

IP Address

N/A

Valid IP address and IP Services installed

Valid address

Subscriber

N/A

N/A

Object and software only (Server Inventory, Inventory Agent, and Remote Management)

For more information, see Section 6.1, Installation on NetWare and Windows Servers.

Server CPU Type

Pentium III 2

To enhance Policy and Distribution Services efficiency, it is more important to increase the amount of RAM than to increase the processor speed.

Pentium III

Pentium III

1 For more information, see Section 3.2, Novell eDirectory Requirement.

2 Wherever Pentium is mentioned in these requirements, all Pentium-compatible processors are included.

Following are the platform-specific NetWare minimum requirements for Policy and Distribution Services and Server Inventory:

Table 5-4 Platform-Specific Minimum NetWare Requirements for Policy and Distribution Services and Server Inventory

Requirement

Policy and Distribution Services

Server Inventory

NetWare 5.1: Support Pack Version

5

5 1

NetWare 6: Support Pack Version

4

4

NetWare 6.5: Support Pack Version

1a

1a

NetWare 5.1: Server RAM

Policy/Distribution: 384 MB; 512 MB is recommended for larger deployments of Policy and Distribution Services.

384 MB; 512 MB is recommended

NetWare 6/6.5: Server RAM

512 MB

512 MB

1 Only for the Inventory Agent.

5.3.3 Windows Server Requirements

The following information applies to all Windows versions:

  • DNS:  All target Windows servers should have fully qualified DNS names. For more information, see Section 3.4, DNS Requirement.

    IMPORTANT:For Windows servers, the server’s DNS short name must be the same as the server’s name. Either rename Windows servers where the server’s name does not match its DNS short name before running the installation, or do not select these servers for installing Server Inventory.

  • Windows-centric network environment:  You can run Policy and Distribution Services in a Windows-centric network when you install eDirectory 8.7.1 on at least one Windows 2000 server, such as a Distributor server. To install eDirectory on a Windows Server 2003 server, eDirectory 8.7.3 is required.

    Installing eDirectory on a Windows server allows you to manage the ZENworks eDirectory objects in a Windows-centric network. All of the Windows servers in your network do not require eDirectory, just one server.

  • Local Windows server installation:  In order to install locally on a Windows 2000/2003 server, that server must have the required Novell Client running. Otherwise, the installation program does not run on that instance of Windows.

    However, you can install to a Windows server that does not have Novell Client running on it, but not locally. Just run the installation program on a workstation that does have the client running, then on the Server Selection page, browse for and select the Windows server that doesn’t have the client so that you can install ZENworks 7 Server Management to it.

  • Mixed network environment:  ZENworks Server Management can run in a mixed eDirectory environment. For example, your network might have both eDirectory 8.x and NDS 6.x or 7.x installed.

    eDirectory 8.6.2 or 8.7.1 or later is required for ZENworks Server Management so that its objects can be placed in the tree during installation of the product. eDirectory must be installed with the master replica somewhere in your network, but not necessarily on a server where you are installing the ZENworks Server Management software. However, Server Inventory requires eDirectory to be running on each Inventory server.

    The only requirement for any Policy and Distributions Services server is that it can communicate with the server where the eDirectory master replica (of the partition where its NCP Server object resides) is installed.

Following are the common Windows minimum requirements for Policy and Distribution Services and Server Inventory:

Table 5-5 Common Minimum Windows Requirements for Policy and Distribution Services and Server Inventory

Requirement

Policy and Distribution Services

Server Inventory

Server CPU Type

Pentium III

Pentium III

Server RAM

512 MB

512 MB

Free Disk Space

35 MB

100 MB for inventory with database; 25 MB for inventory alone

Disk Space for ConsoleOne Snap-Ins

50 MB

50 MB

eDirectory

N/A

N/A

Subscriber

N/A

Object and software only (Server Inventory, Inventory Agent, and Remote Management)

For more information, see Section 6.1, Installation on NetWare and Windows Servers.

Following are the platform-specific minimum requirements for the Server Management components:

Table 5-6 Platform-Specific Minimum Windows Requirements for Policy and Distribution Services and Server Inventory

Requirement

Policy and Distribution Services

Server Inventory

Windows 2000 Service Pack Version 1

4

4

1 No service pack is required for Windows Server 2003.

5.3.4 Linux and Solaris Server Requirements

Meet the following requirements before running the installation script:

Hardware and Software Requirements

Following are the minimum system requirements for Policy and Distribution Services on Linux or Solaris servers. Server Inventory and Remote Management cannot be installed on Linux or Solaris.

Table 5-7 Minimum Linux or Solaris Requirements for Policy and Distribution Services

Requirement

Linux

Solaris

Operating System Version

Distributions supported:

  • SLES 8
  • SLES 9
  • SLES 10
  • SLSS 8
  • SLSS 9
  • Red Hat Advanced Server 2.1
  • Red Hat Enterprise Server 2.1
  • Red Hat Enterprise Linux AS 3
  • Red Hat Enterprise Linux ES 3

9 (the release level Is displayed by the uname -r command)

Machine Type

IBM* compatible PC

Sun* Microsystems

Supported Processors

Intel* for Linux

SPARC* for Solaris

Server RAM

128 MB minimum; 256 MB recommended

256 MB minimum

Server CPU Type

200 MHz Pentium or faster

N/A

Free Space for Policy and Distribution Services Files

150 MB

195 MB

IMPORTANT:The hostname of the Linux or Solaris server where you install Policy and Distribution Services must be the same as its DNS short name.

Server Accessibility Requirements

The following might need to be set up for accessing a Linux or Solaris server:

Samba

Samba is not needed for installing Policy and Distribution Services to a Linux or Solaris server. However, if you plan to access the Linux or Solaris Subscriber server from a Windows client via a mapped drive, you must configure Samba on the Subscriber server to provide the shared folders.

For information concerning the Samba usage for Desktop Application Distributions, see Client Access in Linux in the Novell ZENworks 7 Server Management Administration Guide.

DNS Hostname

If you edit the tednode.properties configuration file, the installation script used to install Policy and Distribution Services on Linux and Solaris servers (see Section 6.3, Installation on Linux and Solaris Servers) displays the fully qualified DNS hostname of the local Linux or Solaris server as obtained from one of the following locations, depending on your system search order:

  • DNS (Domain Name System)

  • NIS (Network Information Service)

  • /etc/hosts file on the Linux or Solaris server

The installation script requests confirmation of the displayed information. Without the correct DNS information, Policy and Distribution Services does not function properly on the server. Do one of the following:

  • If the DNS entry is correct, type y, then press Enter.

  • If the DNS entry is incorrect:

    1. Type n, then press Enter.

    2. Specify the correct fully qualified DNS hostname, then press Enter.

    3. Type y to confirm the modified DNS hostname, then press Enter.

After the DNS entry is correct, the installation script next prompts for the password corresponding to the user you supplied for the user_Name parameter.

The installation script logs its actions in the following file:

/var/opt/novell/log/zenworks/zfs-pds-install.log

If the installation does not complete successfully, you can print this log file. To look up installation errors, see Section H.0, Installation Error Messages. Resolve the problem and perform a successful installation.

Management Requirements

In addition to fulfilling the server requirements for the Linux or Solaris server where you are installing Policy and Distribution Services, the following requirements must be met somewhere in your network:

  • Novell eDirectory 8.6.2 or 8.7.1 or later must be running on at least one server (NetWare, Windows, Linux, or Solaris) in your network. This is required for installing and managing the Distributor and Subscriber objects that are created for your Linux or Solaris servers.

    For more information, see Section 3.2, Novell eDirectory Requirement.

  • At least one NetWare or Windows server is required in your network to support the Server Management database. The Server Management database currently cannot be created on a Linux or Solaris server. The database is optional, but is recommended for historical reporting and for reporting on policies distributed to multiple servers.

    The Server Management database stores log messages for reporting purposes, detailing the successes and failures of Distribution processing and policy statuses. The server where it resides must meet the system requirements listed in Section 5.0, Server Requirements.

  • To administer Policy and Distribution Services on Linux or Solaris servers using ConsoleOne, version 1.3.6 or later must be installed on a Windows workstation. ConsoleOne is required for managing ZENworks Server Management. For information on installing ConsoleOne, see Section 4.4, Installing ConsoleOne 1.3.6e.

  • To administer Policy and Distribution Services on Linux or Solaris servers using iManager, version 2.5 or 2.6 must be installed on a Windows or NetWare server and be accessible from a Windows workstation, or installed on a Linux server where it can be run. iManager is optional, but recommended for managing Distributions using the Tiered Distribution view.

    For more information on installing iManager, see Section 4.3, Management-Specific Workstation Requirements.

5.3.5 Role-Specific Server Requirements

Some servers might require additional configuration specific to their Server Management role:

Inventory Database Server

Following are the minimum requirements for the Inventory Database server only:

Table 5-8 Minimum Inventory Database Server Requirements

Component

Minimum Hardware and Software Requirements

Database Requirements

  • Sybase ASA 8.0.2 is installed automatically when you choose to install the inventory database.

    NetWare 6 SP3

    NetWare 6.5

    Windows 2000 Server SP4

    Windows Server 2003 Standard Edition

    Windows Server 2003 Enterprise Edition

  • Oracle* can be used as an alternative to Sybase. Oracle 9.2.0.6 or Oracle 10g R1 on:

    Windows 2000 Server SP4

    Windows Server 2003 Standard Edition

    Windows Server 2003 Enterprise Edition

    SLES 9 SP1 or Solaris versions supported by Oracle

  • MS SQL can be used as an alternative to Sybase:

    (Recommended) MS SQL version 2000 SP3a

RAM Requirements

  • Recommended minimum memory on the database is 512 MB with minimum cache size of 128 MB

  • 768 is minimum and 1 GB or higher is recommended at the Root Server level with a cache size of 256 MB

Hard Disk Requirements

  • Recommended minimum hard disk space on a lowest level server with 10,000 servers is 5 GB.

  • The minimum hard disk space on the topmost level server (Root Server) is 20 GB.

  • Depending on the number of servers attached, the hard disk size might vary from 1 GB to 25 GB.

IMPORTANT:Inventory database files should not be installed on an NFS-mounted volume of a NetWare server.

Remote Management Servers

For Remote Management servers, in addition to the basic ZENworks Server Management installation requirements, the following requirements must be met for full Remote Management functionality:

Table 5-9 Minimum Remote Management Server Requirements

Requirement

Minimum Hardware and Software Requirements

Management Server

See Section 5.0, Server Requirements.

Managed Server

  • NetWare 5.1/6/6.5

  • Windows 2000/2003

  • 2 MB hard disk space on the drive where Windows is installed

  • Internet Explorer 5.x

  • If you want to install the policy enforcer, you must have the required support pack installed (that contains the required JVM*) and Policy and Distribution Services on your managed server

We recommend that you install Remote Management from the Novell ZENworks 7 Server Management with Support Pack 1 Program CD. However, if you need to copy the CD structure to a hard drive, the path between the root of the hard drive and the first CD directory can contain only directory names that conform to the 8.3-character DOS file naming convention. If any long directory names exist in the path, the installation program does not work.

Before you can install ZENworks Server Management Remote Management, you must perform the following tasks:

Determining and Preparing the Management Server

After determining the Management Server, you must perform the following task:

Determining and Preparing the Managed Server

After determining which servers you want to remotely manage, you must perform the following tasks:

  • Make sure that you have uninstalled the Remote Management component that ships with the NetWare client, if installed.

  • If you want to set up Remote Management for Windows 2000/2003 servers through using the Server Remote Management policy, make sure that you have installed the Subscriber on the managed servers. To install the Subscriber, see Section 6.1, Installation on NetWare and Windows Servers.

    IMPORTANT:For Windows servers, the server’s DNS short name must be the same as the server’s name. Either rename Windows servers where the server’s name does not match its DNS short name before running the installation, or do not select these servers for installing Remote Management.