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 server or servers 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 Remote Management installed

2 MB

Disk space available on the drive where Windows is installed

ZENworks server without ZENworks database installed

160 MB

NetWare® 4.11, 4.2, or 5.x 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, or 5.x servers with 40 MB free

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


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

ConsoleOneTM 1.2c.6 (or later) included on the Zfd Companion CD shipping with ZENworks for Desktops --- must be installed after NetWare patch

NetWare 4.x
  • NetWare 4.11 (SFTIIITM or SMP not supported) or NetWare 4.2; NW4SP8A.EXE patch (or later) applied
  • JVM 1.1.7b with JAVA.NLM (dated April 11, 2000 or later) available in JVM.EXE shipping on the ZfD Companion CD --- must be installed after NetWare patch
  • ORB.EXE shipping on the ZfD Companion CD --- must be installed after the latest NetWare Support Pack
  • IP Protocol Stack bound and available on the server

NetWare 5.0
  • NW5SP5.EXE (or later) patch applied
  • IP Protocol Stack bound and available on the server

NetWare 5.1
  • NW51SP1.EXE (or later) patch applied
  • IP Protocol Stack 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 eDirectoryTM on Windows 2000 update
  • IP Protocol Stack bound and available on the server

Novell® ClientTM for Windows 95/98

Version 3.3 or later

HINT:  Check the Novell Client Documenation Web site for minimum requirements.

Novell Client for Windows NT/2000

Version 4.8 or later

HINT:  Check the Novell Client Documenation Web site for minimum requirements.

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


Obtaining NetWare Support Packs

Support Pack files for NetWare are available from the Minimum Patch List at the Novell Support Connection® Web site.


Obtaining and Installing the JVM

If you plan to install ZfD on a NetWare 4.x server, we recommend that you also install the JVM for NetWare from the Companion CD (JVM directory) that ships with ZfD. Using this version will help you avoid errors when loading Automatic Workstation Import. If you install ZfD on a NetWare 5.x server, make sure you have installed the appropriate NetWare patch first. For more information on which NetWare patches to apply, see the Overall Software Requirements.

HINT:  To avoid a prolonged install of the JVM caused by extensive file version checking, rename the JAVA directory at the root of the SYS: volume before you run JVM.EXE.


Obtaining and Installing ConsoleOne

We recommend that you use ConsoleOne 1.2c.6 from the Companion CD that ships with ZfD rather than a version of ConsoleOne shipping with NetWare. Using version 1.2c.6 (or later) will help you avoid errors when using context-sensitive JavaHelp for the ZfD snap-ins.

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.2c.6 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.2c.6 on a network server. When you install, make sure that you specify the install path with a mapped drive letter rather than with a UNC path.

IMPORTANT:   ZfD snap-ins do not load properly on the NetWare server console. After installation, do not run ConsoleOne 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

If you install ConsoleOne on a NetWare server volume, the installation program automatically installs the ConsoleOne files to the PUBLIC\MGMT\CONSOLEONE\1.2 directory on that volume, because it assumes the drive is mapped to the root of the volume.

If you have map-rooted the drive to a subfolder under the volume, the installation program creates the default path and appends it to the map-rooted path. This will cause the ConsoleOne snap-ins that are subsequently installed (such as ZfD) to be ignored by ConsoleOne, because they will not be installed to the path from which ConsoleOne is running.


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 whatever 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 (like 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 ZfD3 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 documentation Web site.


Obtaining and Installing Novell Clients

You can obtain the Novell Clients from the Novell Software Download Web site or from the Client CD that ships with ZfD.

For more information about installing the Novell Clients optimized for ZfD, see the Novell Client Documentation Web site.