If running on a Windows 2000 workstation, Service Pack 2 or later must be installed.
The Migration Wizard Utility does not work with Windows XP Home Edition or Windows 95/98.
Windows NT/2000/XP workstations must be running Novell Client for Windows NT/2000/XP version 4.83 or later.
IMPORTANT: If the destination server is running NetWare 6.5 and the Universal Password feature is enabled, you must run the Migration Wizard Utility on a workstation running the Novell Client for Windows NT/2000/XP version 4.9 or later. Universal Password is disabled by default on NetWare 6.5.
To check the Novell Client version, right-click the N icon on the workstation toolbar, then click Novell Client Properties > Client. To download the latest client, see the Novell Software Downloads site.
If Microsoft Jet Database drivers are not installed on your NT 4.0 workstation, they can be downloaded from www.microsoft.com/downloads by searching for the Jet 4.0 Service Pack 3 Update.
If MDAC 2.7 is not installed on your workstation, it can be downloaded from www.microsoft.com/downloads.
The source server is the NetWare server that contains the files, volumes, and NDS objects that will be copied to the NetWare destination server. Valid source servers can be running NetWare 4.11, 4.2, 5.0, 5.1, 6.0, or 6.5. Migrations to a NetWare 6.5 destination server can be successfully completed from a NetWare 4.11, 4.2, 5.0, 5.1, 6.0, or 6.5 source server. However, migrating from NetWare 6.0 to NetWare 6.5 must be done in one of two ways:
Updates are available at the Consolidated Support Pack home page.
To add long name space support to a NetWare 4.11 or NetWare 4.2 volume, enter the following at the server console:
LOAD LONG
ADD NAME SPACE LONG TO volume_name
To load clibaux.nlm on a NetWare 4.11 or 4.2 server, enter the following at the server console:
load clibaux
Make sure that these finish with no errors.
The destination server is the new computer that will receive the data from the source server. This server must be installed into a temporary tree.
After data is migrated from the source server to the destination server, the destination server reboots and Migration Wizard automatically modifies the destination server's autoexec.ncf file to include the source server's name and internal IPX number/server ID. You don't have to modify these manually.
Valid destination servers can be running NetWare 5.1, 6.0, and 6.5. Migration Wizard does not migrate to NetWare 4 destination servers. If migrating from NetWare 6.0, valid destination servers must be running NetWare 6.0. Migrations from NetWare 6.0 to NetWare 6.5 can be accomplished in one of two ways:
Make sure that you select the custom option on the Installation Options screen during the NetWare 5.1 installation, and deselect all deselectable products except SMS. Don't worry about any default products that you can't deselect.
Make sure that you select the Pre-migration Server option described in Selecting the Type of Installation in the NetWare 6 Overview and Installation Guide during the NetWare 6 installation. And then select the custom option so that you can verify that you have enough room on your destination server to accommodate your source server data.
Make sure that you select the Pre-migration Server pattern described in the NetWare 6.5 Overview and Installation Guide under the Choosing the Server Type heading during the NetWare 6.5 installation.
Universal Password is disabled by default on NetWare 6.5.
IMPORTANT: The temporary name and temporary NDS tree name must not be the same as the source server's name or NDS tree name; otherwise, the destination server will not assume the identity of the source server after the migration.
After the migration completes and the source server is taken offline, you can change the destination server's IP address to match what had been assigned to the source server.
To generate GUIDs on NetWare 4 servers in your tree, launch the Deployment Manager (nwdeploy.exe) on a workstation in your tree and click the Generate GUIDs on NetWare 4 Servers link. Follow the instructions in the Deployment Manager.
NOTE: Always run the Deployment Manager before installing NetWare 6.5 servers, including NetWare 6.5 pre-migration servers.
The GUID generator in Deployment Manager does not work with NetWare 4.10 servers, only with 4.11 or 4.2 servers. If there is a NetWare 4.10 server in your tree, it must be removed or you cannot migrate.
The IPX protocol must be bound to the destination server for the migration to work. (You can remove IPX after completing the migration.)
IMPORTANT: IP addresses for the source server will not be migrated. For more information on changing your IP addresses, see Step 3.
Continue with the next section, "Run Migration Wizard ."