For more information on how to enable the Supervisor right, see the ConsoleOne® documentation.
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.
Make sure that your client workstation has an IPX connection to your source server and destination tree.
The source server is the existing server that contains the data that will be copied to the destination NDS tree.
Load one of the following NLMTM programs at the server console of each NetWare 3 source server that you are planning to migrate:
The destination NDS tree is the NDS tree that contains the servers that will receive the data migrated from the NetWare 3 source server. After data is copied from the source server, it appears in the destination NDS tree.
Make sure that all the servers that you are migrating data to in the destination NDS tree have the following:
NetWare Migration Wizard 6.5 does not migrate to NetWare 4.10 servers.
IMPORTANT: If IPX is not bound and running on the destination server, the file migration will fail. To check whether IPX is bound, enter CONFIG at the server console of the destination server.
Continue with the next section, "Creating a Template Object ."
This is an optional prerequisite task. A Template object is used to define additional NDS user attributes to NetWare 3 users during the migration. We recommend that you use a Template object because it is an organized way to migrate your NetWare 3 users to the NDS tree and manage them after they are there.
If there is a conflict between the properties of a Template object and properties of a NetWare 3 user, the properties of the Template object will, in most cases, take priority. For example, if a minimum password length of seven characters is specified for the NetWare 3 user, Jeff, and a minimum password length of nine characters is specified in the Template object, then when Jeff's object is migrated, the object will be created in NDS with a password length of nine characters.
If you want to know what additional NDS attributes can be defined in a Template object, run ConsoleOne and double-click a Template object to view all of the existing properties.
The last name, full name, and description of every NetWare 3 object are always migrated, and their corresponding properties from the Template object are overwritten.
If you decide to use a Template object, you can create one in ConsoleOne by clicking File > New > Object > Template.
Continue with the next section, "Run Migration Wizard ."