Hardware and Software Requirements

This section includes the hardware and software specifications necessary for a successful installation of ZfD, including:


Overall Hardware Requirements

For full functionality and performance, ZfD requires the following minimum amounts of processing power, disk space, and RAM on the servers and workstations where it will be installed:

Resource Minimum Disk Space Minimum Hardware Requirement

User workstation; complete ZfD installation

5 MB

A Pentium* (or higher) personal computer, 75 MHz, 16 MB of RAM

User workstation with ZfD Preboot Services installed

0 MB

A Pentium (or higher) personal computer, 75 MHz, 16 MB of RAM; Preboot Execution Environment (PXE) -enabled network adapter or PXE-On-Disk boot diskette

User workstation with ZfD Remote Management installed

2 MB

Available disk space on the drive where Windows* is installed

ZENworks server without ZENworks database installed

160 MB

NetWare® 4.11, 4.2, 5.x, or 6 servers: 128 MB of RAM (minimum) with 7 MB free

ZENworks server with ZENworks database installed

220 MB (database will expand)

256 MB of RAM on NetWare 4.11, 4.2, 5.x, or 6 servers with 40 MB free

ZENworks server with ZENworks Preboot Services installed

10 MB

128 MB of RAM with 8 MB free

IMPORTANT:  ZfD is not supported on the NEC* 9800 (also known as PC98) series of personal computers.


Overall Software Requirements

The requirements table in this section lists the software that is required to be installed on the server where you install ZfD. In addition, this section includes the following software accessibility information:

Platform Minimum Software Requirement

Management Console

ConsoleOne® 1.3.2 (or later) included on the ZfD Companion CD shipping with ZENworks for Desktops --- must be installed after any NetWare Support Packs are applied

NetWare 4.x
  • NetWare 4.11 with NW4SP9.EXE applied (SFTIIITM or SMP not supported); NetWare 4.2 with NW4SP8A.EXE patch (or later) applied
  • JVM (Java* Virtual Machine) 1.1.7b (dated January 2001 or later) included on the ZfD Companion CD shipping with ZENworks for Desktops --- must be installed after any NetWare Support Packs are applied
  • ORB.EXE shipping on the ZfD Companion CD --- must be installed after any NetWare Support Packs are applied
  • IP Protocol Stack bound and available on the server

IMPORTANT:  ZfD 3.2 Preboot Services are not supported on NetWare 4.x.

NetWare 5.0
  • NW5SP6.EXE (or later) patch applied
  • JVM 1.1.7b (dated January 2001 or later) included on the ZfD Companion CD shipping with ZENworks for Desktops --- must be installed after any NetWare Support Packs are applied
  • IP Protocol Stack bound and available on the server

NetWare 5.1
  • NW51SP2A.EXE (or later) patch applied
  • JVM 1.1.7b (dated January 2001 or later) included on the ZfD Companion CD shipping with ZENworks for Desktops --- must be installed after any NetWare Support Packs are applied
  • IP Protocol Stack bound and available on the server

NetWare 6

NOTE:  NetWare 6 is supported with ZfD 3.2 SP1 or later
  • Support Pack 3 (recommended)
  • Novell eDirectory (8.6.0 minimum, 8.7 recommended)
  • JVM 1.3.1 (minimum) with JAVA.NLM must be installed
  • IP Protocol Stack must be bound and available on the server

Windows NT* server
  • NDS® Corporate Edition or NDS eDirectoryTM
  • IP Protocol Stack bound and available on the server

Windows 2000 server
  • NDS eDirectory 8 or NDS eDirectory 8.5.
  • IP Protocol Stack bound and available on the server

Novell ClientTM for Windows 95/98

Version 3.3 with the SP4 patch. The basic version of the client is available from the Novell Software Downloads Web site. The SP4 patch is available from the \CLIENT directory of the Companion CD shipping with ZfD 3.2 (English only version).

or

Version 3.31, which is available on the \CLIENT directory on the ZfD 3.2 Companion CD (English, French, German version).

Check the Novell Client Documentation Web site for minimum requirements.

Novell Client for Windows NT/2000/XP

Version 4.83 with the SP4 patch. The basic version of the client is available from the Novell Software Downloads Web site. The SP4 patch is available from the \CLIENT directory of the Companion CD shipping with ZfD 3.2 (English only version).

or

Version 4.81, which is available on the \CLIENT directory of the ZfD 3.2 Companion CD (English, French, German version).

Check the Novell Client Documentation Web site for minimum requirements.

Support for ZfD in an IPX Environment

ZfD functions correctly when the IP protocol stack is loaded or bound to the network interface card (NIC) on the workstation. This is possible in a pure IP or IP/IPXTM environment using the NetWare Core ProtocolTM (NCPTM), but not in a pure IPX environment without NCP and when the IP stack is not bound.

The following table lists several network protocol configurations and their support for ZfD.

Network Protocol ZfD Support

Pure IPX (no IP stack loaded or bound to the NIC on the workstation).
  • Automatic Workstation Import will not work
  • Some parts of Remote Management will not work
  • Policies are supported
  • Application Launcher is supported

IPX for NCP (IP stack for the Internet, host, etc.)

Fully supported

IP/IPX for NCP

Fully supported

Pure IP for NCP

Fully supported

IMPORTANT:  ZfD will not function in an IP-to-IP gateway or in an IPX-to-IP gateway environment.


Obtaining NetWare Support Packs

If you install ZfD on a NetWare 5.x or NetWare 6 server, make sure you have installed the appropriate NetWare patch first. Support Pack files for NetWare are available from the Minimum Patch List at the Novell Support Connection® Web site.


Obtaining and Installing the JVM for Your NetWare Server

To determine the version of the NetWare JVM on your NetWare server, show the date of the JAVA.NLM by entering the following command at the system console:

modules java

You can also determine the version by entering the following command at the system console:

java -version

If you plan to install ZfD on a NetWare 4.x server, you should install the JVM for NetWare version 1.1.7b available from the Companion CD that ships with ZfD. Using this version will help you avoid errors when loading Automatic Workstation Import. It is fully compatible with ZENworks for Desktops 3.2 and ZENworks for Servers 2.0 (or higher).

In some circumstances, the time to run Auto Workstation Import may take a very long time to run on a NetWare 5.1 server. If this is the case, you can use the JVM for NetWare version 1.2.2 from the Companion CD that ships with ZfD.

WARNING:  

If you are using ZENworks for Servers 2.0 Tiered Electronic Distribution (TED) in a mixed JVM environment, you must disable subscriber security. For more information, see TID 10060307 at the Novell Knowledgebase Web site.


Obtaining and Installing ConsoleOne

We recommend that you use ConsoleOne 1.3.2 from the Companion CD that ships with ZfD. Using version 1.3.2 (or later) will help you avoid errors when using context-sensitive JavaHelp for the ZfD snap-ins. You can also obtain this version of ConsoleOne from the Novell Software Downloads Web site.

WARNING:  

If you have previously installed ConsoleOne on your server, check the version number. If your installed ConsoleOne is a newer version than the 1.3.2 version that ships on the Companion CD, do not attempt to install the older version over the newer version.

From the Companion CD, you should browse to and install ConsoleOne 1.3.2 on a network server.

IMPORTANT:   ZfD snap-ins do not load properly on the NetWare server console. After installation, do not run ConsoleOne directly from the server console to administer ZfD snap-ins. Instead, run ConsoleOne from a Windows workstation with a shortcut to the network server where you installed it.

This section includes the following topics:


Installing ConsoleOne on a NetWare Server

Use the following steps if you install ConsoleOne on a NetWare server volume:

  1. Bring down Java* and any Java applications that are running on the server, including the server GUI. You can do this by entering the following command at the server console:

    java -exit

  2. Ask all users who are currently running ConsoleOne remotely through a network connection exit their ConsoleOne sessions.

  3. At a Windows workstation, insert the Companion CD > browse to the \CONSOLEONE directory > run C1.EXE.

  4. Follow the prompts in the installation program. When asked to specify an installation path, enter \\SERVER_NAME\SYS\PUBLIC\MGMT\CONSOLEONE\1.2.

  5. At the Summary screen, click Finish.

  6. If you receive a prompt asking how to handle overwriting newer files, select Never Overwrite Newer files > click OK.

  7. After the installation, an Installation Complete message appears. Click Close.


Installing ConsoleOne and ZfD on a Windows NT Server

NDS for NT servers must have a share name to install to. Normally, when NDS for NT is installed, if you install the admin programs, the share name is created for you. To establish a valid connection to a Windows NT server, map a drive to the NT SYS share and log in as Administrator.

If you have not installed the admin programs, you must create a share for the C:\NOVELL (or whichever drive where NDS for NT is installed) directory named SYS.

If the SYS share name does not exist, an error is displayed indicating that ConsoleOne cannot be found. ConsoleOne snap-ins (such as ZfD) cannot be installed under this condition.


Installing ConsoleOne to a Workstation Hard Drive

Although the ConsoleOne installation program lets you install ConsoleOne files to a local hard drive, and though minor performance enhancements can be achieved by doing so, such an installation will not include the ZfD snap-ins.

Instead of using the ConsoleOne installation program to get a local installation, we recommend the following:

  1. Install ConsoleOne and ZfD to the server, including all of the components you plan to use.

  2. From the PUBLIC\MGMT\CONSOLEONE directory on the server, copy the 1.2 folder > paste it to a clean area on your local drive.

  3. Create a shortcut on your desktop to the 1.2\BIN\CONSOLEONE.EXE file in your local installation.

Another alternative is to use snAppShotTM to create your own application object (.AOT file) for ConsoleOne snap-ins or to use the pre-packaged ConsoleOne Application object (created during ZfD installation) to distribute the ConsoleOne snap-ins to other workstations.

You can configure the pre-packaged Application object by running the C1UPDATE.EXE program from SYS\PUBLIC\ZENWORKS on the server where you have installed ZfD. This utility helps you configure the object with the path to ConsoleOne on the server (usually SYS\PUBLIC\MGMT\CONSOLEONE\1.2). Configuring with this path ensures that all of ConsoleOne and the ZfD snap-ins will be available. The program also lets you configure a path for local installation of ConsoleOne (usually C:\NOVELL\CONSOLEONE\1.2).

When the update is executed, it prepares the ConsoleOne Update object for association and distribution to a workstation or a user. For information about distributing a pre-defined .AOT object, see "Application Management" in Administration at the ZENworks for Desktops 3.2 documentation Web site.


Obtaining and Installing the Novell Client

All versions of ZfD, including ZfD 3.2, require the appropriate version of the Novell Client. Both the the International (English, French, German) and the English-only version of ZfD 3.2 can use client version 3.31 for Windows 9x workstations or version 4.81 for Windows NT/2000 workstations or servers. You can obtain the Novell Client from the Companion CD (English, French, German) or download from the Novell Software Downloads Web site.

To install the Windows 95/98 client, run SETUP.EXE from the CLIENT\PRODUCTS\WIN95\IBM_language directory.

To install the Windows NT/2000 client, run SETUPNW.EXE from the CLIENT\PRODUCTS\I386 directory.

For more information about installing a Novell Client, particularly in a ZfD environment, see the Novell Client documentation Web site.