Migration Modeling - Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - MIGRATION GUIDE 10.3 30-03-2010 Migration Manual

You can use the migration screen to create new folders in Configuration Management. These
folders can be nested in any fashion. You can then drag eDirectory objects into these folders no
matter where they resided in eDirectory.
You don't need to maintain the same organization in Configuration Management that you have
in eDirectory. However, because of possible associations to containers, we recommend that
when you have eDirectory objects grouped in containers, that you migrate those contexts
instead of the individual objects contained in them.
Before you drag and drop eDirectory objects into new Configuration Management folders, you
can migrate the empty folders to create the directory structure that you want in Configuration
Management. For migration purposes, this might be faster to do from the ZENworks Migration
Utility than in ZCC because of navigational differences.
When migrating image objects, the imaging information contained in the objects is migrated as
the imaging bundle information in the ZENworks Configuration Management database.
However, the actual image files (
server. You do not have control over this placement.

3.4.10 Migration Modeling

The migration screen is designed so that you can model your migration, then perform the migration
after you have refined your model. The modeling data is automatically saved on your workstation so
that you can revise it over time. Therefore, you can use the modeling capability of this utility to help
you in visually planning your migration.
To use the migration screen to model, just select the objects, contexts, and associations from your
eDirectory tree view and drag them into the Configuration Management Zone's view to queue them
for migration. These items (objects, contexts, and associations) are represented in the destination
panel's listing as Configuration Management objects, folders, and associations. Their icons and texts
are dimmed to distinguish them from items in Configuration Management that have already been
migrated (teal-colored text). Items in black text were originally created in Configuration
Management or migrated from a different workstation, because migration history files are kept on
the workstation where you run the utility.
The teal color is persistent so that you can always know what has previously been migrated from the
workstation. The listings of both your eDirectory tree and the ZENworks database content maintain
the teal color for migrated items. This can be helpful for knowing what has been migrated from the
eDirectory perspective.
To migrate, you simply use the migration screen to queue what you want migrated, resolving any
issues that the utility might identify as you queue them, then click a button to migrate your
eDirectory data to the ZENworks database. Therefore, in addition to planning your migration on
paper, you can use this modeling capability of the migration screen to visualize your migration
before actually performing it.
The migration screen works by migration task. The tasks described in
Order," on page 30 are each a migration session. A selected task is migrated when you click the
Migrate Now button. Therefore, at a minimum, you must plan to migrate your eDirectory data in
several separate clicks of the Migrate Now button. However, you can model an incremental
migration consisting of many sessions per migration task.
) are copied to an imaging directory on the imaging
.zmg
Planning Your Migration to ZENworks Configuration Management
Section 3.4.5, "Migration
33