Begin NDS Migration

The Begin NDS Migration step migrates the NDS/eDirectory files from the source server to the destination server. The source server is brought down and the destination server is restarted during this step.

1. In the Project View dialog box, click Begin NDS/eDir Migration.

2. Back up all volumes that you are not planning to migrate and ensure the following before continuing:

   • All volume data migrated successfully
   • All critical errors from the file copy are resolved
   • The servers in your source NDS tree are in time sync and NDS is synchronized.

     For more information, see Source Server Requirements .

3. Click Next.

4. Insert the licensing diskette, browse to or type the path to the licensing file, then click Next.

   If you have an MLA, you also have the option of selecting the MLA instead of inserting the licensing diskette.

5. Select Yes or No to update the source server's schema, then click Next.

   Migration Wizard can update the source server's schema to include the NDS classes of the default applications that are installed on the destination server.

   By default, Yes is selected, which causes Migration Wizard to compare the source and destination schemas. This comparison will help you determine how to extend your schema in preparation for the migration.

6. (Optional but recommended) Verify that you have run the DSREPAIR procedures in Source Server Requirements to verify that the NDS tree containing the source server is functioning correctly, click Yes or No to acknowledge that your tree is healthy, then click Next.

   Migration Wizard does not prevent you from continuing if you have not run DSREPAIR to verify the health of your tree. However, if your tree is unhealthy before you begin the migration, the migration might not complete successfully.

7. (Conditional) If you are migrating from NetWare 4 running Border Manager^®, NetWare 5, NetWare 6, or NetWare 6.5, you are now prompted to copy and transfer the NICI configuration files from the source server to the destination server.

   To ensure the security certificate works properly on the destination server, you must copy the source server's NICI configuration files to the destination server. To facilitate the NICI file copy, nuwnici.nlm is first copied to both the source and destination servers.

   1. To copy the nuwnici.nlm to the source and destination servers, click Copy NLM.

   2. Click Next.

   3. Insert a blank formatted diskette into the floppy drive on the destination server.

   4. At the destination server console, enter load nuwnici -1.

   5. Remove the diskette from the destination server and insert it into the source server's floppy drive.

   6. At the source server console, enter load nuwnici -2.

      This copies the NICI files to the diskette.

   7. Remove the diskette from the source server and insert it into the destination server's floppy drive.

   8. At the destination server console, enter load nuwnici -3.

      This copies the NICI files to the destination server.

   9. Click Next.

   HINT:  If you get NICI errors when NDS tries to load or when you copy the NICI files, check and see if pki.nlm will load on the destination server. If it won't load, see NICI Errors .

8. 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, click Broadcast Logout Message, type the message in the field, and then click OK.

9. Type the passwords for the source and destination trees, then click Next.

10. Resolve any critical errors or warnings on the Migrate NDS Verification Results screen, then click Next.

11. Perform the eDirectory step-by-step migration.

    The eDirectory migration is broken into several steps. This is for diagnostic purposes. If the eDirectory migration fails for any reason, you will know exactly what step it failed on and can take the appropriate measures to fix the problem.

    For more information on the eDirectory/NDS migration process, including steps to restore the source and destination servers, see NDS Migration .

    1. 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 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.

    2. To begin the next step (backing up eDirectory, copying the eDirectory backup files to the destination server, and copying the eDirectory backup files to sys:system\nuw30\ndsbu on the source server), click Next.

    3. Down the source server by clicking Next.

       The Source Server Status dialog box displays.

    4. Verify that the source server is down, then click OK.

    5. To begin the next step (removing eDirectory from the destination server and deleting the client connection), click Next.

    6. To begin the next step (upgrading eDirectory on the destination server if necessary, restoring eDirectory on the destination server, and preparing to reboot the destination server), click Next.

    7. Reboot the destination server by clicking Next.

    8. If you are ready to proceed, click Yes > Finish.

12. Check the former destination server and verify that it has restarted and taken on the name of the source server.

13. Reboot your workstation and log in to the former destination server.

    This clears old connections from the workstation and establishes a clean connection to the former destination server.

    If you can't log in, refer to Workstation-to-Server Connections .

14. Restart the Migration Wizard utility.

15. Read the Welcome screen, then click OK.

16. Click Open Last Project > OK.

    The utility verifies that the first three steps of the project file are complete.

17. If you are ready to finish the migration, click Yes.