Supported Source And Destination Server Versions - Novell SERVER CONSOLIDATION MIGRATION TOOLKIT 1.1 - ADMINISTRATION GUIDE 12-23-2005 Administration Manual

• Step 3: Begin NDS/eDirectory Migration.
• Step 4: Finish NDS/eDirectory Migration.
Before you can migrate your data, you must first install a destination NetWare server in a temporary
eDirectory tree (see
server with a pre-migration installation of NetWare and no additional products installed (other than
SMS and other products installed by default).
Figure 1-3
Migration Wizard automatically modifies the destination server's autoexec.ncf file to include
the source server's name and internal IPX
manually. Because the server's identity has been transferred from one physical server to another, you
don't need to upgrade any client applications that might be doing drive mappings or running
applications based on the server name. However, you do have to manually change the IP address of
the destination server to match that of the source server.
Migration Wizard does not migrate any products and services that are running on the source server.
After the migration is complete, you need to reinstall all applications on the destination server and
reconfigure them, if necessary.
1.3 Supported Source and Destination Server
Versions
The utilities included in this release of the Server Consolidation and Migration Toolkit support the
source and destination server configurations listed below. These minimum server versions, and all
newer versions, have been tested and are supported by Novell. Older server versions might work,
18 Novell Server Consolidation and Migration Toolkit Administration Guide
The NDS/eDirectory files are transferred from the old server to the new one without any
additional work on your part. After the migration, the eDirectory partitions that existed on the
old server will exist on the new server. This is because the Migration Wizard backs up the
entire eDirectory database on the source server and then restores it on the destination server.
After the source server's file system and NDS/eDirectory database are migrated to the
destination server, the source server is automatically brought down and the destination server
reboots and assumes the name and identity of the source server on your existing network.
Figure 1-3). A temporary eDirectory tree is simply a tree that contains one
Server Hardware Upgrade with Migration Wizard 8.1
number/server ID. You don't have to modify these
TM