ZfD 3.x and ZfD 4.x Coexistence

With a few exceptions, ZfD 4.x is backward-compatible with ZfD 3.x features. However, you will notice a difference in the way ZfD 4.x handles some functionality. The following sections explain the differences that you need to be aware of.

• Workstation Import
• Policy Management
• Application Management
• Workstation Imaging
• Remote Management
• Workstation Inventory

Workstation Import

If the Import Service is upgraded to ZfD 4.x on a server, the ZfD 3.x workstations will register in the same way and the ZfD 4.x Import Service will import them. Both ZfD 3.x and ZfD 4.x workstations can be imported by a ZfD 4.x Import Server.

Policy Management

After you install ZfD 4.x, ZfD 4.x agents and policies will coexist with ZfD 3.x agents and policies in the following ways:

• The ZfD 4.x agents installed on a workstation will first look for ZfD 4.x policies. If the agents do not find ZfD 4.x policies, they will use ZfD 3.x policies as needed.
• ZfD 3.x agents cannot use ZfD 4.x policies or new features.
• ZfD 3.x policies can continue to be managed from ConsoleOne^® upgraded with ZfD 4.x functionality.
• Search policies that stop on a partition boundary are not supported and are not functional with ZfD 4.x agents. For more information, see Updating Search Policies .

ZfD 4.x does not support Windows 95, Windows 98 without the SE upgrade, Novell eDirectory^TM versions before NDS^® 8, NetWare^® 4.x, or NetWare 5.0. If these workstation and network server platforms are part of your network infrastructure and you cannot convert all of the workstations or servers at one time, you might want to purchase ZENworks for Desktops 3.2. ZfD 3.2 supports Windows 95/98 workstations and will install into the same DS tree as ZENworks for Desktops 4.x. This will let you deliver best-of-breed management to all your workstations while you upgrade to supported platforms.

For more information, see Upgrading Policies .

Application Management

With ZfD 4.x, either the Application Window or the Application Launcher is launched from the local machine (usually from c:\program files\novell\zenworks). With ZfD 3.x, either nal.exe or nalexpld.exe was launched from the server. If you are going to start the Application Launcher from the login script, make sure that every container's login script in your environment has built-in logic to determine whether the ZfD 4.x agent exists, then run the Application Launcher from the appropriate location. For more information, see Updating the Application Launcher Startup Method .

Even if you are migrating only one site at a time to ZfD 4.x, this login script change needs to happen everywhere at the beginning of the migration process to accompany roaming users.

Workstation Imaging

When you upgrade Workstation Imaging from ZfD 3.x, make sure to use the same boot disk version as the version on the ZfD Server. For example, if you upgrade the Imaging server to ZfD 4.x, make sure to use a ZfD 4.x boot CD when you manually invoke imaging.

Remote Management

Use the ZfD 4.x Remote Management Console to control ZfD 3.x and ZfD 4.x workstations (a workstation becomes a ZfD 4.x workstation when the ZfD 4.x Management Agent is installed).

Workstation Inventory

After you install ZfD 4.x, ZfD 4.x Workstation Inventory pieces and ZfD 3 SP1 or ZfD 3.2 agents and policies will coexist in the following ways:

• Inventory data from ZfD 4.x agents cannot be sent to a ZfD 3 SP1 or ZfD 3.2 inventory server and placed in a ZfD 3 SP1 or ZfD 3.2 database. A ZfD 3 SP1 or ZfD 3.2 Inventory Agent cannot send its inventory data to a new ZfD 4.x Inventory server. It can send its inventory data only to a ZfD 3 SP1 or ZfD 3.2 Inventory server or to a ZfD 4.x Inventory server that has been upgraded from ZfD 3 SP1 or ZfD 3.2.
• ZfD 3 SP1 or ZfD 3.2 inventory servers can roll up their databases to a ZfD 4.x inventory server, but a ZfD 4.x inventory server cannot roll up its database to a ZfD 3 SP1 or ZfD 3.2 server.
• Any ZfD 3 SP1 or ZfD 3.2 inventory servers that roll up their data to a ZfD 4.x inventory server must be patched in order to function properly.
• A ZfD 3 SP1 or ZfD 3.2 inventory server cannot roll up its data to a ZfD 3 SP1, ZfD 3.2, or ZfD 4.x inventory server in another eDirectory tree.

In order for your network to support both ZfD 3 SP1 or ZfD 3.2 and ZfD 4.x, you must first install ZfD 3 SP1 or ZfD 3.2 into your network. Installing ZfD 4.x without first installing ZfD 3 SP1 or ZfD 3.2 will not have the Novell eDirectory schema or ConsoleOne plug-in support for ZfD 3 SP1 or ZfD 3.2 policies. On the other hand, installing ZfD 3 SP1 or ZfD 3.2 first places the ZfD 3 SP1 or ZfD 3.2 schema and the plug-ins into ConsoleOne. When you install ZfD 4.x after ZfD 3 SP1 or ZfD 3.2, the ZfD 3 SP1 or ZfD 3.2 schema and plug-ins remain.