The minimum hardware requirements for a NetWare 6 server are listed here. Remember that these are just minimum requirements—the recommended values are considerably higher (as shown in parentheses):

If you aren’t satisfied with meeting the minimum requirements for your hardware, you should consider some upgrades. Keep the following in mind:

If you’re considering hardware upgrades, Table 2.1 might point you in the right direction.

TABLE 2.1 Hardware Upgrades

The minimum software requirements for NetWare 6 include some or all of the following, depending on your network configuration:

To run an upgrade of your network, the servers must be running one of the following operating systems:

The minimum configuration requirements for NetWare 6 include one or all of the following, depending on your network configuration:

After all hardware, software, and configuration requirements have been met, you’re just about ready to roll. But first, you must back up your source server and prepare the network for NetWare 6. In the next two sections, you’ll learn how to back up servers and prepare the network for eDirectory 8.6.

Before you back up your NetWare 5 server by using SMS, you should ensure that your system meets (or exceeds) all the SBACKUP system requirements, including NetWare 5 server with SMS installed, 3MB of available RAM (minimum), a host server with enough memory to run NetWare and connected clients, a target server, and, ultimately, a backup device. To use SMS to back up data on a NetWare 5 server, perform these steps:

To restore backed up data to a NetWare 5 server, perform these steps:

Before you use SMS to backup your NetWare 4 server, you should ensure that your system meets (or exceeds) all the SBACKUP system requirements, including NetWare 4 server with SMS installed, 3MB of available RAM (minimum), a host server with enough memory to run NetWare and connected clients, a target server, and, ultimately, a backup device.

To use SMS to back up data on a NetWare 4 server, perform these steps:

Before you attempt to restore data to a NetWare 4 server by using SBACKUP, you should ensure that you’ve met all the prerequisite system requirements: You must have Supervisor (or equivalent) rights, you need to know the username and password for the target server (or workstation) that you want to restore the data to, and you must be intimately familiar with the file structure of the data you’re restoring.

To restore backed-up data to a NetWare 4 server, perform these steps:

Good job. Your safety nets are now complete. With multiple server backups in a safe place, it’s time to shift your focus to network preparation. Next stop, eDirectory schema.

To use NetWare Deployment Manager, you must have the latest Novell Client and NICI client on both your primary and secondary administrative workstations. The following are the steps for installing the Novell Client for Windows:

1.   Exit any applications that you’re running to clear off your workstation. Then, download the appropriate Novell Client from the Novell Web site at download.novell.com.

2.   Next, select the appropriate Novell Client file from the Novell Web site. Make sure to create a Novell eLogin account for future downloads. Refer to Figure 2.1 for more information. When you’ve finished saving the file, expand it and continue with the next step.

FIGURE 2.1 Downloading Novell Client software using eLogin.

3.   To install the Novell Client, locate and execute the appropriate Windows setup file. When the Novell Client for Windows License Agreement appears, review the agreement, and then select Yes to agree to its terms and conditions. Then select Custom at the Welcome to Novell Client for Windows Install screen (as shown in Figure 2.2) and click Next.

FIGURE 2.2 Selecting an installation option during Novell Client installation.

4.   When the Protocol Preference window appears (as seen in Figure 2.3), verify that IP and IPX is selected, and then select Next.

FIGURE 2.3 Selecting a network protocol option during Novell Client installation.

5.   When the Login Authenticator window appears, verify that NDS (NetWare 4.x or Later) is selected, and then select Next. At the Novell Client for Windows Optional Components window (see Figure 2.4), verify that no products are selected, and then select Install. Wait while the installation program builds a driver information database.

FIGURE 2.4 Selecting optional components during Novell Client installation.

6.   At this point, the installation program will ask you to insert the Windows Operating System CD into your workstation. Then a series of Copying Files dialog boxes will appear. Each time you’re prompted for the location of a file, indicate the appropriate location, and then select OK.

7.   Finally, wait while the installation program removes the existing Novell Client (if one exists), builds the driver information database, and installs the new Novell Client. Then, when the Control Panel Network dialog box appears (as shown in Figure 2.5), verify that the Novell Client has been installed, and then select OK to close the Network dialog box.

FIGURE 2.5 Configuring the Novell Client in Windows 95/98.

In addition to the Novell Client, you’ll be required to activate NICI strong encryption on your workstation in order to use NetWare Deployment Manager. This is required to ensure that your data files are secure as they traverse the network from source to target server.

Follow these short and simple steps to install the appropriate NICI client on both of your administrative workstations:

Now it’s time for NetWare Deployment Manager—a fabulous tool! Before you can upgrade a server to NetWare 6 in an existing network, you must update eDirectory and prepare the network. All this magic is accomplished using NetWare Deployment Manager.

Follow these steps to update eDirectory using Deployment Manager:

1.   Insert the NetWare 6 Operating System CD into the workstation’s CD-ROM drive, and log in to your network from a Windows workstation as a user with Supervisor rights.

2.   Execute NetWare Deployment Manager (NWDEPLOY.EXE) from the root of the CD-ROM and select the Network Preparation folder to expand it. Choose Step 2: View and Update NDS Versions (as shown in Figure 2.6).

FIGURE 2.6 Updating NDS versions in Deployment Manager.

3.   Select Browse when the Update NDS window appears. Then navigate to your tree and select the topmost container under your tree (such as ACME, shown in Figure 2.7). Select OK to continue.

FIGURE 2.7 Selecting the topmost container in Deployment Manager.

4.   If a Login Dialog window appears, authenticate as a user with Supervisor rights. Then, when the Update NDS window appears, select Include Subordinate Containers (as shown in Figure 2.8). At this point, you’ll notice that eDirectory detects which servers need to be updated and lists them in the Server column. Select the servers you want to update, and then select Next. Wait while the files are copied. Then, when you are prompted to reload eDirectory for the changes to take effect, select Next. Finally, click Exit to complete the update process.

FIGURE 2.8 Searching the tree for servers to be updated in Deployment Manager.

During the NetWare 6 upgrade process, you’ll need to install a new version of eDirectory. However, before you can do that, you’ll need to modify the existing network schema. This way, when a new NetWare 6 server is installed, the same version of eDirectory will be used throughout the network.

To update the schema to eDirectory 8.6, you must have Administrative rights to the eDirectory tree. Follow these steps to prepare the network for eDirectory 8.6:

1.   Insert the NetWare 6 Operating System CD into the workstation’s CD-ROM drive, and log in to your network from a Windows workstation as a user with Supervisor rights.

2.   Execute NetWare Deployment Manager (NWDEPLOY.EXE) from the root of the CD-ROM and select the Network Preparation folder to expand it. Choose Step 3: Prepare for NDS eDirectory (as shown in Figure 2.9).

FIGURE 2.9 Preparing the network for eDirectory 8.6 in Deployment Manager.

3.   Select Browse when the Update NDS window appears. Then navigate to your tree, select it, and click Next. When the Available Servers field appears, select a server that contains a Master or Read/Write replica of the root partition (as shown in Figure 2.10). Then select Next. Finally, click Exit to complete your eDirectory preparation.

FIGURE 2.10 Selecting a replica server in Deployment Manager.

That’s it! All finished. You’ve successfully prepared the network for NetWare 6 installation, upgrade, and/or migration. In this section, you learned how to update the eDirectory schema using NetWare Deployment Manager. Now let’s complete our network preparation tasks by updating the Certificate Authority (CA) object.

The Novell Certificate Server ensures secure data transmissions between servers and workstations over your network. This NetWare 6 service is required for Web-related products such as Novell Lightweight Directory Access Protocol (LDAP), NetWare Web Server, and the NetWare Management Portal. It also enables you to mint, issue, and manage digital certificates by creating a Security container object and an Organizational Certificate Authority (CA) object.

If the network doesn’t already have an Organizational CA object, the first NetWare 6 server automatically creates and physically stores the Security container object and Organizational CA object for the entire eDirectory tree. Both objects are created at, and must remain at, the tree root of the eDirectory tree.

Novell delivered a base-level PKI (public key cryptography) with NetWare 5.0. As such, you must update your NetWare 5.0 PKI Services to a Novell Certificate Server CA object. Fortunately, this applies only to NetWare 5.0 servers. The NetWare 5.1 CA is updated during the NetWare 6 Upgrade process.

To update your network to use the new Novell Certificate Server, you must satisfy these minimum requirements:

Follow these steps to update your network for the new Novell Certificate Server:

Well, there you have it! We’ve satisfied the minimum system requirements, backed up our source and destination servers, prepared the network, and updated the Certification Authority (CA). Now can we get started?! Not yet. First we need a plan.

Before you do anything, you must back up all the data from your source upgrade computer to an offline storage media. Also, make sure that you install the latest NetWare service pack. Refer to the “Before You Begin” section earlier for more information.

NetWare 6 can be upgraded from the server’s local CD drive or from upgrade files located elsewhere on the network. To access the NetWare 6 upgrade files, perform these steps:

The following NetWare applications also require that you prepare their files prior to upgrading:

Finally, be sure your DOS partition is large enough to hold both the system files and a memory core dump (200MB recommended). If the DOS partition doesn’t have enough space, you cannot upgrade.

To begin the NetWare 6 upgrade process, insert the NetWare 6 Operating System CD into the CD drive (or log in to the network if you’ve stored the NetWare 6 upgrade files on an existing server), and enter the following command at the prompt:

Notice that the upgrade program displays the initial screens in text mode. Auto-detected and/or default settings appear on each screen. You can either accept the auto-detected and default settings or modify them to meet your requirements. To navigate a text screen, use the arrow keys on your keyboard. To select a menu choice, highlight the desired option and press Enter. To toggle between predetermined values in a field, highlight the field, and then press Enter to toggle to the next value. See the bottom of each screen for further information.

At the beginning of the upgrade process, you’re asked to agree to the terms and conditions contained in the NetWare 6 Novell Software License Agreement. Press F10 or select Accept License Agreement, as appropriate, to indicate that you’ve read the agreement and accept its terms and conditions. The appropriate choice will depend on the method you used to start the upgrade program.

The upgrade program then checks the server’s first hard disk to verify that it has a valid boot partition and adequate disk space. When a screen appears indicating that a valid boot partition has been found, select Continue with Existing Partition.

When the JReport Runtime License Agreement screen appears, press F10 to indicate that you’ve read the agreement and accept its terms and conditions.

When the Welcome to the NetWare Server Installation screen appears, you’re given the opportunity to select the installation type (express or custom) and the installation method (new server, upgrade, or pre-migration). The default installation type is express and the default installation method is upgrade. Let’s take a closer look at each of these options.

The NetWare 6 installation methods available on the screen include

Review the values listed on this screen and modify them as necessary. In Lab Exercise 2.1, you’ll perform a NetWare 6 custom upgrade.

The Server Settings screen appears next, listing the following default values:

Some information you might want to keep in mind regarding these options includes

The Regional Settings screen appears next, as shown in Figure 2.11. Regional settings are used to customize server language and keyboard settings. If you’re located in the United States, the default values are as follows:

FIGURE 2.11 Selecting regional settings during NetWare 6 upgrade.

The upgrade program then copies a number of server boot files from the CD to the C:NWSERVER startup directory. These include files such as SERVER.EXE, disk drivers, NWCONFIG.NLM, NWSNUT.NLM, VREPAIR.NLM, and other NetWare loadable modules (NLMs).

This completes the first five steps of NetWare 6 upgrade and phase I. Now, we will continue with platform support and NetWare storage in phase II.

Figure 2.12 shows the first of three driver screens. This one lists the platform and support modules (which have been auto-detected wherever possible):

FIGURE 2.12 Selecting platform support during NetWare 6 upgrade.

The second driver screen lists storage devices. Storage devices require a software driver, called a custom device module (CDM) to communicate with the storage adapter that controls it. Each type of storage device requires a separate CDM. The Upgrade Wizard auto-detects many types of storage devices, such as SCSI/IDE drives, CD-ROM drives, and tape drives. If a storage device is not detected, choose the appropriate driver from the list provided or load it from a manufacturer-provided disk. Custom device modules typically have a .CDM extension.

The third driver screen lists the network drivers and a plethora of NLMs:

When you select Continue, the Upgrade Wizard copies system files to the SYS: volume.

This completes the next three steps of NetWare 6 upgrade and phase II. Now, we’ll venture into a whole new world: GUI installation screens and phase III.

Some technologies (such as SSL and certificate generation) require the use of cryptography. If the Encryption screen appears, insert the NetWare 6 License/Cryptography disk into the computer’s disk drive. On the disk, browse to the License directory, select the .NFK file, and then select OK.

If the Encryption screen appears and you don’t select an .NFK file, you won’t be able to install NetWare 6! Fortunately, the .NFK included with this CNE Study Guide will keep you running for several months.

The NetWare 6 file system consists of partitions, volumes, and free space. In this step, you’re given the option of creating additional NetWare partitions and volumes using available free space. For example, you can divide a large disk into two or more volumes or distribute a single volume over more than one disk.

You can create two different types of NetWare 6 volumes:

If a Configure File System dialog box appears, review the information listed. To create an additional volume, choose one of the displayed free space icons and select Create.

If the New Volume dialog box appears, type the name of the new volume in the Volume Name field, provide a size in the Space to Use field, and select Apply to Volume. When you’ve finished, select OK. The Configure File System screen then reappears, listing the new volume. Repeat the process, as necessary, to create additional volumes.

In addition, the size of an existing volume can be increased, but not decreased, by using the Free Space option within the Configure File System screen. In the Space to Use field, enter the new size of the volume, select Apply to Volume, and select OK. To decrease the size of an existing volume, you must delete and re-create it. To delete a volume, highlight it in the Configure File System screen and then choose Delete.

If the Mount Volumes dialog box appears, indicate whether to mount all volumes when the server reboots at the end of the upgrade process or whether to mount all volumes now. The default choice (Yes) establishes that all volumes will be mounted when the server reboots. You would typically need to mount all volumes now only if you plan to install additional products and services (such as documentation) on volumes other than SYS:.

At this point, the Protocols dialog box appears. This screen displays the network protocols that are currently configured.

NetWare 6 can be configured to process IP network packets and/or traditional IPX packets. If desired, both protocols can be assigned to a single network board. This allows the server to communicate using both IP and IPX. In fact, your NetWare 6 server can be configured in any of the following ways:

This completes the middle three steps of NetWare 6 upgrade and phase III. Now, it’s time to venture outside the cozy confines of our server and into the exciting world of Domain Name Service and eDirectory.

Earlier, I mentioned that the IP protocol identifies servers and workstations by their unique four-part IP addresses. These addresses are complex and difficult for humans to track. Fortunately, your NetWare 6 server can maintain a list of simple, readable names that match all the IP addressed devices on your network. This capability is known as Domain Name Service, and the corresponding NetWare 6 application is called DNS Server.

To provide DNS services from your NetWare 6 server, you must configure the following information in Figure 2.13:

FIGURE 2.13 Configuring Domain Name Service during NetWare 6 upgrade.

When the Login to NDS screen appears, log in to the tree as Admin, using the full distinguished name and password.

At this point, the Upgrade Wizard checks for duplicate tree names and installs NDS/eDirectory. When the NDS Summary screen appears (see Figure 2.14), write the values you supplied for the following parameters and store it in a safe place for future reference:

FIGURE 2.14 Viewing the NDS Summary screen during NetWare 6 upgrade.

Novell Licensing Services has been enhanced in NetWare 6 to support two different models for distributing valid license certificates to network users and services:

When you install or upgrade to NetWare 6, the wizard installs the UAL model by default. To add license certificates and/or upgrade to UAL, you must use iManager after the installation or upgrade. Fortunately, UAL and SCL can coexist on the same network. In this scenario, NetWare delivers the appropriate license certificate type based on the location of the resource—NetWare 6 servers share a single UAL certificate, whereas NetWare 5 servers deliver an SCL certificate for each server.

We’ll use the NetWare 6 Upgrade Wizard to license the NetWare 6 server (as shown in Figure 2.15). When the Licenses dialog box appears, insert the NetWare license disk in the floppy drive and select the appropriate license file. Be sure to use a unique license disk, and make sure that you actually browse to and select the license file, instead of just listing the drive letter (a common mistake).

FIGURE 2.15 Licensing the server during NetWare 6 upgrade.

When you select the license file, you’ll notice that the type of license appears in the Description section, such as NetWare 6 Server, Plus Fifty User Connections. Select OK to return to the Licenses screen, and Next to continue to step 15.

NetWare 6 must have a valid software license in order to function as a server. You can install the license from the NetWare 6 License/Cryptography disk or browse to a directory that contains a valid NetWare 6 license. In addition, you can choose to install NetWare 6 without a license by marking the Install without Licenses check box in Figure 2.15. In this scenario, the unlicensed server will allow only two user connections.

If an MLA License Certificate context screen appears, select the NDS context where you would like the MLA server-based license certificate and connection license certificate installed. These MLA certificates are valid for all servers and users located at the selected eDirectory context and below. You might want to install these MLA license certificates high in the tree so that they will be available to more servers and users.

This completes the three trickiest steps of NetWare 6 upgrade and phase IV. Now, it’s time for the home stretch: completing the upgrade in phase V.

Near the end of the upgrade process, you’ll be given the opportunity to install a variety of additional network products. These products provide enhanced server and network functionality, including Internet printing, Web access services, Domain Name Service, and advanced Novell auditing.

Toward the end of the NetWare 6 upgrade process, the Components dialog box appears, enabling you to select from the following list of additional network products (see Figure 2.16):

FIGURE 2.16 Selecting components to install during NetWare 6 upgrade.

If you rest your cursor on an installation option, a description of the accompanying product is displayed at the bottom of the screen. Mark the check box of each product you want to install. If a product requires a supporting component, the check box of the supporting product will be selected automatically. Also, always be sure that your server has enough disk space and system memory to accommodate the products you want to install.

Novell Certificate Server ensures secure data transmissions between servers and workstations over your network. Only one Organizational CA object can exist in an eDirectory tree. After the Organizational CA object has been created on a server, it cannot be moved to another server. Deleting and re-creating an Organizational CA object will invalidate any certificates associated with the Organizational CA—so you must make sure that the server hosting the Organizational CA object is very reliable.

To create the Security container and Organizational CA objects, you must be logged in as a user with the Supervisor right to the tree root of the eDirectory tree. In the Novell Certificate Server Objects installation screen (shown in Figure 2.17), mark the appropriate check boxes. The Upgrade Wizard will give the Organizational CA a default name based on the server name. Select Next to create the Novell Certificate Server objects and continue.

FIGURE 2.17 Configuring Novell Certificate Server during NetWare 6 upgrade.

When the Summary screen appears (as shown in Figure 2.18), review the NetWare 6 products that are ready to be installed. When you’re satisfied with the list of products, select Customize to access the upgrade customization screen. Check it out.

FIGURE 2.18 Viewing the Summary screen during NetWare 6 upgrade.

You can enhance the basic NetWare 6 upgrade with some additional configurations by using the Product Customization dialog box. As you can see in Figure 2.19, the NetWare 6 upgrade process provides you with a plethora of customizable categories, including the core NetWare operating system, file system, protocols, time synchronization, Novell Directory Services, and additional products and services.

FIGURE 2.19 Customizing Novell products during NetWare 6 upgrade.

To customize your upgrade, browse the tree to find the first NetWare 6 component that you want to modify, select the component, and select Configure. When you’ve finished customizing your selections, select OK to return to the Summary screen.

On the Summary screen, select Finish to complete the upgrade process. Yeah!

The Upgrade Wizard then performs the main file copy. (This step might take a while.) When the file copy finishes, the Installation Complete window appears. Select View Log or View Readme, if desired. Next, remove the NetWare 6 License/Cryptography disk from the floppy disk drive (if you used one), the NetWare 6 Operating System CD from the CD-ROM drive (if applicable), and select Yes to restart your server (as shown in Figure 2.20).

FIGURE 2.20 Completing the NetWare 6 upgrade process.

Congratulations—you’ve done it! You’ve successfully traversed the five phases and 18 steps of NetWare 6 upgrade! Now it’s time to use your new server to help save the Net! Check out the step-by-step challenges awaiting you in Lab Exercise 2.1.

NetWare 6 migration requires two types of preparation: Source and Destination. In the Source server preparation phase, you’ll perform a variety of server housekeeping tasks on the NetWare 4 or 5 server that hosts all your valuable files, volumes, and eDirectory information.

Let’s start with a closer look at the source-server preparation checklist:

Next, you must prepare the destination server. This machine is the new computer that will receive the data from the source server. As such, it must be installed into a temporary, separate eDirectory tree. After the data has been migrated from the source server to the destination server, the destination server reboots and the Migration Wizard modifies the destination server’s AUTOEXEC.NCF file to include the source server’s name and internal IPX number or server ID. You don’t have to modify these manually.

Let’s continue with a closer look at the destination server preparation checklist:

Finally, you’ll need to verify the Novell Client version that is running on your migration client. The NetWare Migration Wizard can run from either a Windows 98 or Windows NT/2000/XP workstation. If you’re using a Windows 98 workstation, be sure that it’s running the Novell Client for Windows 98 version 3.3 (or higher).

You can determine which version of the client software is running on your Windows 98 workstation by using any of these three methods:

A Windows NT/2000 client must be running the Novell Client for Windows NT version 4.8 (or higher). The client version should be listed on the title bar of the Login dialog box. If these methods don’t work, you’ll probably need to upgrade your client software. Refer to the first lesson of this chapter for detailed steps.

That’s all there is to it. Consider your three migration machines prepared. Now it’s time to move on to the actual migration process, beginning with the Migration Project.

First, in the Migration Project Window, you’ll click the Copy Volumes button. When you do, the Migration Wizard backs up your directory and file trustees and saves them in files located on the source and the destination server. Once the migration is complete, the Wizard restores the trustee rights.

To start the volume copying process, simply choose each volume name from the list provided and then select Yes or No (see Figure 2.28). If you have big volumes or slow LAN connections, or if you want to reconfigure your data by putting existing directories into different folders on the destination server, consider using a backup tape to copy your volumes. However, don’t restore the source server’s SYS directories because these were already created during the destination server’s NetWare 6 installation process.

FIGURE 2.28 Selecting a source volume in the NetWare 6 Migration Wizard.

Next, you’ll need to decide whether you want to copy the source server’s SYS directories to the destination server’s SYS:SYS.MIG directory. For safety reasons, Migration Wizard never overwrites the SYS directories on the destination server. If there are files in the source server’s SYS directories that you want to use on the destination server, copy them from SYS:SYS.MIG into the appropriate SYS directory on the destination server at the end of the migration.

At this point, the Migration Wizard will ask you how you want to resolve duplicate filenames between the source and destination servers. You can choose one of the following options (also shown in Figure 2.29):

FIGURE 2.29 Configuring file copy parameters in the NetWare 6 Migration Wizard.

Now it’s time for action. Next, the Migration Wizard will ask whether you want to copy volumes while users are logged in. Remember, the wizard cannot copy open files. Therefore, you might want to choose Disable Login to ensure that all your users’ data are available for copying. Finally, the wizard will prompt you to authenticate with your source and destination username and password (as shown in Figure 2.30) to resolve any critical (denoted by a red circle with a white X) and noncritical (denoted by a yellow triangle) errors. When you’ve performed all the volume copying configuration tasks, you can actually perform the data migration by clicking the Migrate button. Yeah!

FIGURE 2.30 Authenticating to the source and destination trees in the NetWare 6 Migration Wizard.

In the second task to be done from the Migration Project Window, you’ll click the Edit Configuration Files button. When you do, the Migration Wizard displays the source server and destination server configuration files (with .NCF and .CFG extensions). These files contain default LOAD statements and parameters. If you’re editing the AUTOEXEC.NCF file, make sure that the file is closed before you migrate your eDirectory database.

To edit a specific configuration file, simply choose it and select Edit File. Then copy and paste the commands from the configuration file on the source server to the corresponding configuration file on the destination server. When you’ve finished modifying your configuration file, select Save & Close.

Now you’ve completed the first half of the Project Migration journey. And, your life is about to get a lot more interesting. Next, we’ll migrate the most critical NetWare 6 component of all: eDirectory. Go team!

Your third task using the Migration Project Window is to click the Begin NDS Migration button. When you do, the Migration Wizard requests licensing information and then updates the source server’s schema to include the eDirectory classes of the default applications that are installed on the destination server. If you select No to update the schema, Migration Wizard will compare the source and destination schemas instead. This comparison helps you to determine how to extend your schema manually. Click Yes to continue.

Next, the wizard will ask you whether your eDirectory tree is healthy. This screen is a simple reminder to run DSREPAIR prior to migration. The Migration Wizard does not prevent you from continuing if you haven’t run DSREPAIR; however, the migration might not complete successfully if your eDirectory tree is unhealthy. Click Yes to continue.

If you’re migrating from NetWare 4 running Border Manager, or NetWare 5, or NetWare 6, you’ll be prompted to copy and transfer the NICI configuration files from the source server to the destination server. Begin this process by selecting Copy NLM. When you see the confirmation message, click OK to continue. Then NICI will be automatically configured.

Now it’s time for action. Next, the Migration Wizard will delete all user connections (except yours) to the source and destination servers. Click Next to continue. Finally, the wizard will prompt you to authenticate with your source and destination username and password and resolve any critical (denoted by a red circle with a white X) and noncritical (denoted by a yellow triangle) errors. When you’ve performed all the eDirectory migration tasks, you can actually perform the migration by clicking the Migrate button.

Next, you’ll click the Finish NDS Migration button in the Migration Project Window. When you do, the Migration Wizard displays the Continue NDS Migration window. Make sure to validate that the former destination server has restarted, that it has the identity of the source server, and that licensing is installed before you continue.

Next, you must ensure that eDirectory is synchronized on all servers in the tree. To check eDirectory synchronization status, enter DSREPAIR at the server console and run the Report Synchronization Status and Time Synchronization options. If the destination server does not contain a read/write or master replica, you must check eDirectory synchronization by running DSREPAIR on another server in the eDirectory tree that has one of these replicas.

Then, at the end of the NetWare 6 Migration, verify that you’ve completed these tasks by selecting Yes. Finally, authenticate to the source tree, resolve any critical and/or noncritical errors, and, complete the migration by clicking Continue.

At this point, the Migration Complete dialog box appears. Click View Success Log and review the information listed. Click the close button (X) to close the window. Again, the Migration Complete dialog box reappears. Click Done.

That’s all there is to it!

Perform these tasks on your primary administrative workstation:

Perform these tasks at the WHITE-SRV2 (destination) server console:

1.   Use ConsoleOne to verify that the admin User object will have Supervisor rights to the source Server object (that is, WHITE-SRV2) and its file system.

2.   Use the parameters in Table 2.4 to install NetWare 6 on the WHITESRV2 server. During the installation process

TABLE 2.4 Preparing the Destination Server

If you wanted to edit any configuration files, you could select Edit Configuration files in the Project window. Because you don’t want to edit any configuration files, just skip this step.