Run DSRepair on the destination server and select Unattended Full Repair to ensure that eDirectory is functioning properly.
Using ConsoleOne®, verify that the user information migrated successfully.
HINT:During the migration, the standard sys: directory from the source server is saved in the sys.mig directory on the destination server.
Run > to verify that your source server is synchronized with the rest of your servers.
Verify that the correct IP address is assigned to the new server in all appropriate files.
For example, check autoexec.ncf, sys:\etc\hosts, and sys:\etc\hostname, or type config at the server console.
IMPORTANT:Failure to have the correct IP address in the hosts or hostname files causes the post-installation of some products to fail.
(Conditional) If you have performed a migration to a NetWare 6.0 destination server, verify that sys:\public\rootcert.der exists.
If it does not exist, copy the file from an existing server on the network, or create a new one following the instructions in TID #10066860.
If the rootcert.der file does not exist, a post-migration install of applications could fail.
(Conditional) If you haven’t already done so, install the latest NetWare Support Pack on the destination server.
This ensures that you get the latest code for the applications that you are reinstalling. The latest Support Packs are available at the Novell Support Web site.
Reinstall any server applications.
IMPORTANT:Because the source server’s eDirectory database replaces the destination server’s eDirectory database, all eDirectory objects on the destination server before the migration, including those representing applications, are replaced by the eDirectory objects that exist on the source server. However, the NLM programs associated with the destination server's applications still exist. Because you cannot manage applications without their corresponding eDirectory objects, you must reinstall the applications to restore their eDirectory objects to the tree.
You can reinstall these network products and services using either of two methods:
Go to the destination server, load the GUI interface if necessary by typing startx, and click the Novell icon in the lower-left corner of the servertop. Then click > to install products.
To install products remotely, run the Novell Deployment Manager utility (nwdeploy.exe, or nwdeploynobrowser.exe for a nonbrowser-based version) located on NetWare 6.5 CD 1 (Operating System). Under Post-Install tasks, select and follow the on-screen instructions to run the Remote Product Install utility.
If needed, after completing a NetWare 6.5-to-NetWare 6.5 migration using the Migration Wizard, complete the following steps to ensure that Tomcat installs correctly:
Copy sys:\sys.mig\java to sys:\java, overwriting all existing files.
Copy sys:\sys.mig\adminsrv to sys:\adminsrv, overwriting all existing files.
Copy sys:\sys.mig\system\ipconf to sys:\system\ipconf, overwriting all existing files.
After completing a NetWare 6.5-to-NetWare 6.5 migration using the Migration Wizard, complete the following steps to ensure that exteNd™ Application Server installs correctly:
Copy sys:\sys.mig\java to sys:\java, overwriting all existing files.
Copy sys:\sys.mig\etc\my.cnf to sys:\etc\my.cnf.
If needed, after completing a NetWare 5.1-to-NetWare 6.5 migration using the Migration Wizard, complete the following steps to ensure that Native File Access for UNIX installs correctly:
Delete the NFAU User object.
Run the schinst utility by entering
schinst -n -w
SCHINST takes the administrator’s FDN and password as input for extending the schema.
Run nisinst.
Execute nfsstart.