Moving, Creating, Or Importing Edirectory Users - Novell OPEN ENTERPRISE SERVER 2.0 SP2 - UPGRADING TO OES-PLANNING AND IMPLEMENTATION GUIDE 12-2009 Implementation Manual

The single biggest issue in many organizations is that NetWare and eDirectory haven't been patched,
so starting fresh is the easier option. This is true of file and print as well. Most customers who use
this strategy are moving to OES 2 SP2 from NetWare 5 and NDS 6 (which is limited to 1500 users).
Adding a branch to an existing tree
Some Novell customers transfer objects to a new OES 2 SP2 branch and then gradually retire the
older NetWare branch. By adding a branch, it's easier to drag and drop users and login scripts,
certificates, and PKI so they don't need to be re-created.
Manual Upgrade Using Replicas
If all you want to do is copy the existing eDirectory information from a NetWare server to a new
OES 2 SP2 server, without the OES server assuming the NetWare server's identity, you can move
objects to a new OES 2 SP2 branch and then gradually retire the older NetWare branch. When
you've added a branch, it's easy to drag and drop users and login scripts, certificates, and PKI so they
don't need to be re-created.
1 Create a new OES 2 SP2 server with a new eDirectory 8.8 tree.
2 Create an eDirectory replica on the target OES server by attaching it to the same replica ring as
the source NetWare server.
This creates two instances of eDirectory in the environment. The OES Migration Tool does a
non-destructive move of all services, and it needs both servers with their respective directories
up and running.
3 Allow the OES eDirectory installation to synchronize.
If necessary, you can rework the layout of your tree structure, remap the location of all user
objects in your new tree, and delete any user objects that are no longer needed.
4 When eDirectory synchronization of the replica is complete, move the impacted services with
the OES 2 SP2 Migration Tool.
5 Retire the older NetWare server.
Except where dependencies exist, there is no required order for moving services in the same tree. An
example of a dependency would be that the Archive and Versioning service depends on the file
system.

3.3.3 Moving, Creating, or Importing eDirectory Users

If you have opted to create a new tree, you need to decide how to move user objects from one tree to
another. Several options are available:
"Using Novell Identity Manager" on page 45
"Creating and Importing an LDIF file" on page 46
"Using the OES 2 SP2 Migration Tool" on page 46
Using Novell Identity Manager
One method is setting up a Novell Identity Manager connection between your old tree and your new
one. This lets you easily synchronize user objects to the new tree. You can also use Identity Manager
to remap the location of all user objects in your new tree.
Upgrading eDirectory to OES 45