Novell Server Consolidation and Migration Toolkit 1.1, Administration Manual, Page: 103 / 126

no
vd
ocx
(E
NU)
9 Decem
ber
200
5
Migrating Data from NetWare Servers 103
6h
Click Next .
TIP: If you get NICI errors when eDirectory tries to load or when you copy the NICI files,
check to see if
pki.nlm
will load on the destination server. If it won’t load, see Section
12.9, “NICI Errors,” on page 110 .
7 Delete all user connections (except your own) to the source and destination servers, then click
Next .
If you want to first broadcast a logout message to any users logged in to the server, select
Broadcast Logout Message , type the message in the field, and then click OK .
8 Type the passwords for the source and destination trees, then click Next .
9 Resolve any critical errors or warnings on the Migrate NDS/eDir Verification Results screen,
then click
Next .
10 Perform the eDirectory step-by-step migration.
The eDirectory migration is divided into several steps. This is for diagnostic purposes. If the
eDirectory migration fails for any reason, you know exactly what step it failed on and can take
the appropriate measures to fix the problem.
For more information on the NDS/eDirectory migration process, including steps to restore the
source and destination servers, see
Section 12.11, “NDS/eDirectory Migration Failures,” on
page 110 .
10a Click Next .
The first step changes
autoexec.ncf
and
timesync.cfg
; modifies the server name
in
hosts
,
hostname
, and
snmp.cfg
; and renames
smdr.cfg
to
smdr.mig
. The
first step also renames
rootcert.der
in both the
sys:system
and
sys:public
directories to
rootcert.der.bak
.
At the end of 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 one stored in the source server’s
autoexec.ncf
file.
• The server ID is changed to the IPX
TM
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.
10b Click Next again.
This step backs up eDirectory and copies the eDirectory backup files to the destination
server and to
sys:system\nuw30\ndsbu
on the source server.
10c Down the source server by clicking Next .