Before you install ZfD3, you should be aware of the Novell^® software products that are required by ZfD3 and the new features that ship with ZfD3. The following sections contain more information:

Before you can install ZfD3 and use it as the basis of your migration, you should be aware of some new Novell products that you will be required to use with ZfD3. These include:

While ZfD2 and earlier versions of the product required the NetWare^® Administrator console to administer its policies, packages, and Application objects, ZfD3 requires ConsoleOne^TM 1.2c.6. ConsoleOne is the Java*-based management console that is now the standard for all Novell administrative products. ConsoleOne 1.2c.6 is available on the Companion CD that ships with ZfD3.

NIS Installation

ZfD3 installation is accomplished with the Novell Installation Service (NIS), which allows each discrete software component or component group to be separately installed. NIS is automatically launched from the ZfD3 Program CD.

Novell Clients

ZfD3 requires the use of the Novell Clients that ship with ZfD3 on the Novell Client CD. The following client versions are required:

The New Automatic Workstation Import/Removal Component

Before a workstation could be imported in a ZfD2 environment, it first had to be registered, a cookie for it placed in NDS, then the system administrator had to manually run a tool to actually import it. The import process would create a workstation object in NDS and the workstation could log on as a workstation entity. Much of this manual work required in ZfD2 is now accomplished in ZfD3 when the workstation is logged in to the network: a one-step automatic process.

The Automatic Workstation Import service creates the Workstation object in NDS. The object can then be viewed from ConsoleOne the first time the workstation is registered. Subsequent workstation registration updates the Workstation object's properties, freeing the import service from the Workstation object unless the object is renamed, moved, or deleted.

Automatic Workstation Removal is just as simplified. You set a policy and unused Workstation objects are automatically removed from the tree.

New Features in Workstation/Policy Management

Policies for ZfD3 are organized into fewer policy packages than in ZfD2. This design lets you manage new platforms more easily because they are under a package's umbrella. For example, all of the platforms under a User Package can benefit from the general user policies.

Most of the ZfD2 policies now exist in either the User Package or in the Workstation Package.

The new policy packages for ZfD3 include:

This package is the same as for ZENworks for Servers (ZfS).

The Container Package holds only the Search policy. The Search policy is used to minimize tree walking.

Server Package

Although ZfS also has a Server Package, the policies for ZfD2 are different.

The Server Package has four policies:

This package is the same as for ZfS.

The Service Location Package has three policies:

The User Package has 9 policies found on various platform pages:

The Workstation Package has ten policies found on various platform pages:

ZfD3 includes new Application Management features to make the management and use of software applications easier. The new features include:

Caching Applications and Running in Disconnected Mode

Application caching enables users to install, run, and verify (repair) applications while they are disconnected from NDS.

ZfD3 Application Management creates a hidden cache directory (NALCACHE) on the root of each user's workstation. This cache directory contains the NDS information required to run an application when the workstation is disconnected from NDS. If the application has already been installed to the workstation and the user disconnects from NDS, the application will continue to run just as if the user were still connected.

The cache directory can also contain the application source files and other information required to install the application or verify (repair) problems that may occur with the application while in disconnected mode. For example, if a user does not install the application before disconnecting from NDS, he or she can still install it, provided the application has been cached to the workstation's cache directory.

To ensure that users will always have mission-critical applications when disconnected, you can configure Application objects to be cached automatically when you associate the Application objects with users. In addition, you can configure Novell Application Launcher^TM/Explorer to display the Application Management dialog box. This dialog box, which is turned off by default, enables users to select which applications they want to cache to their workstations' local drives.

To save disk space, application files are compressed before being stored in the cache direct.

Uninstalling Applications

Any application that was distributed through ZfD2 or ZfD3 Application Management can be uninstalled. All files, INI entries, and registry entries associated with the application are deleted. Shared DLL references are observed.

Managing Microsoft Windows Installer (.MSI) Applications

In addition to being able to manage applications that use snAppShot (.AOT) installation packages, Application Management can now manage applications that use Microsoft* Windows Installer (.MSI) packages. When creating an Application object, you simply choose what type of installation package (.AOT or .MSI) will be used. All new ZfD3 functionality, including application distribution, application uninstall, caching, imaging, and disconnected mode, is supported for .MSI applications.

Distributing Applications During the Imaging of a Workstation

Workstation Imaging lets you create base images to apply to workstations. Using Application Management, you can take any Application object and create an add-on image. Once you associate the add-on image with one or more base images, any time the base image is applied to a workstation, the add-on image will be used to automatically distribute the application to the workstation during the imaging process.

Reporting on Application Management Events

Application Management reporting has been improved to provide information about a variety of events, including the success or failure of the following events:

• Distributing an application
• Launching an application
• Uninstalling an application
• Caching an application's source files to the local cache directory

In addition to still being able to report events through SNMP traps or a log file, you can now save events to any ODBC-compatible database.

The New Workstation Imaging Component

ZfD3 includes a workstation imaging component that lets you take images of workstation hard disks and then use the network to put them on other workstations. You can perform imaging tasks manually (by physically visiting workstations) or automatically through NDS.

New Features in Remote Management

ZfD3 includes several new Remote Management features, including:

Remote Wake Up

You can remotely power up a powered-down node in your network if the network card on the node is Wake On LAN enabled. This feature lets the administrator manage nodes during off-hours to minimize the downtime that end users may otherwise experience for system maintenance and upgrades. It also facilitates power savings while keeping systems available for maintenance.

Screen Blanking

This option lets the administrator blank the managed workstation screen, making it possible to perform remote management operations unobserved by the end user.

User Control Locking

This feature lets the administrator lock the keyboard and mouse at the managed workstation, making it impossible for the end user to use these controls.

Wallpaper Suppression

When a Remote Control or Remote View session is initiated, this feature lets the administrator suppress the wallpaper displayed on the desktop of the managed workstation.

Time-Out Configuration

This feature lets the administrator set waiting time for connecting with the managed workstation prior to starting a Remote Control or a Remote View session.

New Features in Workstation Inventory

The ZfD3 Workstation Inventory component offers the following new features:

Sybase/Oracle Database Support

In ZfD3, the database is a RDMS that can be maintained either in Sybase* Active Server Anywhere* version 7.0, which ships with ZfD3, or the Oracle* 8i or 8.0.4 databases, which are native on many servers.

Inventory Data Roll-Up Support

ZfD3 supports roll-up of inventory information across servers, so you can choose the inventory deployment configuration that best suits your requirements, whether your network environment is large or small.

In large networks, ZfD3 inventory data is rolled up or accumulated, and sent to a centralized database. Beginning at the leaf server level, changes in inventory data are first sent to intermediate servers (if deployed) and finally to the highest level server, which also holds the Inventory database. The roll-up of scan data in ZfD3 can handle problems such as the WAN link being down.

New Inventory Tools

ZfD3 has a Backup tool to help you back up the Inventory database, a Synchronization tool to help you maintain the database in a consistent state with NDS, a Map Server tool to provide a unified view of all the servers and database servers deployed on your network, and a DataExport Tool to store the inventory data from the Inventory database in a Comma Separated Value (.CSV) file format (a format that is usable by most third-party reporting programs).