Novell NETWARE 6-DOCUMENTATION Manual page 388

30
NetWare Migration Wizard 6 Aministration Guide
IMPORTANT:
If you are getting NICI errors when NDS is trying to load or when
you are copying the NICI files, you should first check and see if PKI.NLM will load
on the destination server. If PKI.NLM won't load, see
8
Delete all user connections (except your own) to the source and
destination servers, and then click Next.
9
Enter the passwords for the source and destination trees, and then click
Next.
10
Resolve any critical errors or warnings on the Migrate NDS Verification
Results screen, and then click Next.
11
Click Migrate to begin the NDS migration.
At the end of this the migration process, the source server is brought down
and the destination server reboots and takes over the name and identity of
the source server.
Migration Wizard automatically modifies the following items in the
destination server's AUTOEXEC.NCF file:
The file server name is changed to the name of the source server
The time zone is changed to the time zone stored in the source
server's AUTOEXEC.NCF file
The server ID is changed to the IPX internal net value or server ID
stored in the source server's AUTOEXEC.NCF file
The default time server type is changed to the value stored in the
source server's AUTOEXEC.NCF file
The bindery context is changed to the bindery context stored in
source server's AUTOEXEC.NCF file
IMPORTANT:
During the migration, the source server's timesync information is
not automatically migrated.
12
View the Error and Success logs, and then click Done.
Use the Error Log to see a listing of all errors that occurred during the
migration. If there were errors, use the Success Log to determine how far
the migration got before the error occurred.
If the NDS migration failed, see
instructions on how to restore your servers to their original configuration.
13
Check the former destination server and verify that it has restarted and
taken on the name of the source server.
"NICI Errors" on page
"NDS Migration" on page 56
55.
for