Before You Migrate to ZfD3

To prepare for the migration to ZfD3, you must first prepare your systems with the following items:


Making a Backup of the Existing ZfD2 Installation

Before you install ZfD3, you should make sure that you have made at least two backups of the existing ZfD2 installation. For backing up a NetWare server, use Novell Storage Management Services (SMS) or another backup utility to make sure that the server has an archived backup for you to restore later should there be problems with the migration.

For more information about SMS, see the Backup and Restore documentation at the NetWare 5.1 documentation Web site.


Upgrading to ConsoleOne

Before you migrate, you must install ConsoleOne version 1.2c.6 or later. ZfD3 components and policies snap in to this java-based network administration tool. Version 1.2c.6 of ConsoleOne is included on the Companion CD that ships with ZfD3. If you try to install ZfD3 on a network server that has an older installation of ConsoleOne, you will receive the following message:

IMPORTANT: ZENworks for Desktops 3 requires ConsoleOne version 1.2c.6 or later to display all of its snap-ins. The version of CONSOLEONE.EXE currently installed on server NAME is dated 03/01/2000 1.2c, which is older than the required version.Do you want to proceed with the ZfD2 snap-in installation?

[Yes] Install ZfD3 snap-ins into the older version of ConsoleOne. I will install the required (or newer) version of ConsoleOne when this install is complete.[No] Do not install ZfD3 snap-ins. I will use the older version of ConsoleOne.

If you click Yes, you will need to install the latest ConsoleOne version to SYS:\PUBLIC\MGMT\CONSOLEONE\1.2 on a network server. For more information, see Obtaining and Installing ConsoleOne in Getting Started, or see the ConsoleOne documentation Web site.

IMPORTANT:  If you use ConsoleOne to change the properties of existing ZfD objects, save your changes, and then subsequently open the ZfD objects using NetWare Administrator (NWADMN32.EXE), some of the attributes of the ZfD object will be lost. The best practice is to remember this: if you start to administer any ZfD object with ConsoleOne, do not revert to that object with NetWare Administrator.


Editing the AUTOEXEC.NCF File

Migrating from ZfD2 will make certain commands in the AUTOEXEC.NCF configuration file obsolete. Before you migrate to ZfD3, you should edit this file and remove or comment the following lines:

SEARCH ADD SYS:\PUBLIC\ZENWORKS\JAVALOAD JAVA.NLMSYS:\SYSTEM\JVORBCFG.NCFLOAD ORBCMD.NLMLOAD OSAGENT.NLMSYS:\PUBLIC\ZENWORKS\JAVA\ALARMMGR.NCFSYS:\SYSTEM\MGMTDBS.NCFSYS:\SYSTEM\GATHERER.NCFSYS:\PUBLIC\ZENWORKS\JAVA\MASTER.NCFSYS:\PUBLIC\ZENWORKS\JAVA\STORER.NCF

IMPORTANT:  The preceding lines appear in the AUTOEXEC.NCF file after a test installation of the ZfD2 International release. Your AUTOEXEC.NCF file may or may not contain any of the lines shown, depending on the version of ZfD2 and the components installed.


Restarting the Server

When the latest version of ConsoleOne is installed and the AUTOEXEC.NCF file is edited, type the following command at the server console where you will be installing ZfD3:

restart server

Restarting the server after the configuration file is properly altered for migration will keep it from loading old ZfD2 NLMs and configuration files.


Unloading Java

You must unload Java before you begin the ZfD3 installation program. Use the following command at the server console:

unload java

If Java is running when you run the installation program, the program will display the following message:

Java is running on server Name Install may not run properly if Java is runningPlease unload Java on this server then press OK to continue.

You may still safely unload Java when this message is displayed.