Begin NDS Migration

1. In the Project Window, click Begin NDS Migration.

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

   • Make sure all volume data migrated successfully.
   • Make sure all critical errors from the file copy are resolved.
   • Make sure the servers in your source NDS tree are in time sync and that NDS is synchronized. For more information, see Step 2.

3. Click Next.

4. Insert the licensing diskette, browse to or enter the path to the licensing file, and 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.

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

   If you select No, by default the Yes radio button is enabled, 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. Before continuing, verify that you have run the DSREPAIR procedures in Step 2 to verify that the NDS tree containing the source server is functioning correctly, click Yes or No to acknowledge that your tree is healthy, and 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. If you are migrating from NetWare 4 running Border Manager, NetWare 5, or NetWare 6, you will be prompted to copy and transfer the NICI configuration files from the source server to the destination server. Just follow the on-screen instructions and when the NICI configuration is complete, continue with the next step.

   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 NICI Errors.

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 NDS Migration for 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.

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

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

Continue with the next section, "Finish NDS Migration."