This chapter covers the following testing objectives for Novell Course 3000:

Transcription

1 1HW:DUH8SJUDGHDQG0LJUDWLRQ Content provided in partnership with Que, from the book CNE Update for Netware 6 STudy Guide by David Clarkeà This chapter covers the following testing objectives for Novell Course 3000: Upgrading to NetWare 6.. Use Deployment Manager to Update Your Directory Schema.. Upgrade or Migrate to NetWare 6.. Troubleshoot Your NetWare 6 Migration. In the first leg of our exciting NetWare 6 CNE Update journey, we explored the top 20 features of Novell s most Internet-savvy network operating system to date. We also strolled through the five phases of NetWare 6 Installation. If you learned anything in Chapter 1, you should have learned If you build it, they will come! But what if you are already running NetWare 4 or 5? I m sure a lot of you are. Then what? Fortunately, NetWare 6 includes two cool options for you:. NetWare 6 Upgrade You can install NetWare 6 on the same machine without losing any existing files. This type of upgrade is called an inplace upgrade. You can upgrade to NetWare 6 from either NetWare 5.x or NetWare 4.x.. NetWare 6 Migration NetWare 6 includes an elaborate migration utility, not surprisingly called the NetWare Migration Wizard. This GUI migration tool enables you to upgrade NetWare 4, 5, or 6 servers across-the-wire to NetWare 6. However, the destination server must be running NetWare 5.0, 5.1, or 6. Furthermore, you can even migrate Windows NT 3.51 or 4 servers to NetWare 6 very cool! In %X\7KLV%RRN)URPLQIRUP,7 About Us Advertise On InformIT Contact US Site Map Book Registration 2003 Pearson Education, Inc. InformIT Division. All rights reserved. Legal NoticeÃ_ÃPrivacy PolicyÃ

2 66 CHAPTER 2 Netware 6 Upgrade and Migration this case, Windows NT Users and Groups are added to edirectory, and shared folders are placed in the NetWare 6 file system (with rights intact). Cool, huh?! So, which NetWare 6 upgrade option is best for you? Your choice depends on a number of factors such as the operating system you re currently running, the hardware you have, and which NetWare 6 features you plan to use (such as iprint, imanager, and Novell Cluster Services). Of course, you could always choose to install NetWare 6 using the from-scratch installation process covered in the previous chapter. That was fun! In this chapter, we will explore the detailed steps of NetWare 6 Upgrade and Migration. Before we do, however, we must take a quick look at some important upgrade setup tasks namely, minimum system requirements and network preparation with Deployment Manager. It s time to begin... REAL WORLD In addition to In-Place Upgrade and Across-the-Wire Migration, NetWare 6 includes a third, more advanced, upgrade tool called NetWare Accelerated Upgrade (NAU). This utility is for network administrators who are skilled at troubleshooting and installing NetWare networks. Because NetWare Accelerated Upgrade runs from a Windows workstation, you don t have to have physical access to the server console, and it doesn t require the server to have a CD-ROM drive installed. This is ideal for new highperformance rack-mounted and/or blade servers. Of course, you can still run NAU from the server using NWCONFIG if you prefer. NetWare Accelerated Upgrade relies on a staging server (where the installation files are stored) and network access to the source and target servers. To run the Accelerated Upgrade, launch ACCUPG.EXE from the root directory of the NetWare 6 Operating System CD-ROM. Then, log into both the source and target servers. Next, the utility compares the target server s properties with an ideal NetWare 6 setup. Based on the results, the Accelerated Upgrade configures the target machine accordingly. Think of NetWare Accelerated Upgrade as a turbocharged installation. Vroom!! Before You Begin Test Objective Covered: 1. Use Deployment Manager to update your directory schema. Variety is the spice of life!

3 Netware 6 Upgrade and Migration CHAPTER 2 67 NetWare 6 can be installed, upgraded, and migrated in a variety of different ways by using a plethora of different tools. In Chapter 1, we discovered the NetWare 6 installation method. Now, we will explore NetWare 6 upgrade and migration. Before you begin upgrading and migrating to NetWare 6, you ll need to perform a variety of preliminary tasks including identifying (and satisfying) any minimum system requirements, backing up your existing servers, preparing the network for edirectory 8.6, and updating the Certificate Authority (CA) object. In this section, we will cover the following pre-upgrade tasks:. Minimum System Requirements. Data Backup. Network Preparation. Certificate Authority (CA) Update It always pays to be prepared! When performing the lab exercises in this guide, it is imperative that you use a nonproduction server (that is, a practice server) in an isolated edirectory tree. You should use nonproduction workstations as well. Remember that we are here to help improve your life, not to make it more difficult!... TIP Minimum System Requirements Before you upgrade or migrate to NetWare 6, you should ensure that minimum hardware, software, and configuration requirements have been met (or exceeded). Following is a detailed review of each of these NetWare 6 system requirements. (We also discussed these in depth in Chapter 1.) Hardware Requirements 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).

4 68 CHAPTER 2 Netware 6 Upgrade and Migration. A server-class PC with a Pentium II or later processor (Two-way Pentium III 700 MHz or later processor is recommended for multiple processor machines. In fact, NetWare 6 supports up to 32 processors. Wow!). A Super VGA (or higher) resolution display adapter. 256MB of RAM (512MB recommended). A DOS partition of at least 200MB and 200MB of available space (1GB recommended)... TIP A quick method for calculating the appropriate size of the DOS partition is to add the total amount of server RAM to the minimum amount of disk space required. Because 200MB is the minimum amount of available disk space required, a server with 2048MB of RAM would theoretically have an optimum DOS partition size of 2248MB (2048MB + 200MB = 2248MB). Using this strategy allows you to do a core dump to the disk drive if required for troubleshooting purposes.. 2GB available space outside the DOS partition for the SYS: volume (4GB recommended). One (or more) network boards. A bootable CD drive. (Optional) A USB, PS/2, or serial mouse (a mouse is recommended)... REAL WORLD Although NetWare 6 will run if the minimum requirements are met, you should ensure that your system meets or exceeds the recommended requirements for optimum performance. For example, when determining your system requirements, you will want to ensure that your server has sufficient RAM and hard disk space for any additional Novell products and services you want to install, as well as for any third-party applications, documentation, and the file system. You will also want to ensure that your server has sufficient processor speed to provide the level of server performance required by your organization. Finally, don t forget other hardware that may be required such as routers, hubs, cabling, uninterruptible power supplies, and so on. Software Requirements The minimum software requirements for NetWare 6 include some or all of the following, depending on your network configuration:. A NetWare 6 Operating System CD. A NetWare 6 License/Cryptography disk

5 Netware 6 Upgrade and Migration CHAPTER (Conditional) DOS 3.3 or later (if the server does not boot from CD). (Conditional) DOS CD drivers (if the server does not boot from CD). (Conditional) Client connection utilities (optional; for installing from a network):. (Conditional) Novell Client for DOS and Windows 3.1x (optional; for installing from a NetWare server running Internetwork Packet exchange (IPX)). (Conditional) IP Server Connection utility (optional; for installing from a NetWare server running IP only) Configuration Requirements The minimum configuration requirements for NetWare 6 include one or all of the following, depending on your network configuration:. The Supervisor right at the [Root] of the edirectory tree. The Supervisor right to the container where the server will be installed. The Read right to the Security container object for the edirectory tree. Network communication parameters required for connecting to the Internet:. IP address. IP address of a domain name server. Name of your domain. Default Gateway/Router IP Address. Network board and storage device properties (such as interrupt and port address, if not included with NetWare) For IP addresses and domain names, contact your system administrator and/or Internet Service Provider (ISP). For network board and storage device information, contact the hardware manufacturer. Finally, there are nifty tools available for gathering this network configuration data yourself. Check them out in Novell s CNE Study Guide for NetWare TIP After all hardware, software, and configuration requirements have been met, you re just about ready to roll. But first, you must backup your source server and prepare the network for NetWare 6. In the next two sections, you will learn how to backup your server and how to prepare the network for edirectory 8.6.

6 70 CHAPTER 2 Netware 6 Upgrade and Migration Data Backup Before upgrading to a new version of NetWare, you should always make two or more complete, verified backups of both edirectory data and file system data on your server. You can either use a NetWare solution or a third-party solution to back up the data.... TIP Before using a third-party backup program, verify that it is fully SMS-compliant. (If you use an SMS-compliant backup program such as ARCserve, trustee information will be backed up.) NetWare 6 contains a server backup feature called Storage Management Services (SMS). SMS consists of a set of programs that are both operating system independent and hardware independent. These programs allow you to back up and restore data across the network by using SBACKUP. SBACKUP can back up servers, workstations, or other services to media (such as tape, optical disk, or jukebox) for offsite storage. Examples of targets that can be backed up by using SBACKUP include edirectory, binderies, the file system, cluster-enabled pools, or hard disks on individual workstations. SBACKUP takes a snapshot copy of the data you select, stores a copy on tape (or other media), and then allows you to retrieve the data at a later time in case of a natural disaster, hardware failure, corrupted data, accidentally deleted data, and/or incorrectly changed data. Even if you plan to use a third-party program to back up your data, you should be familiar with the procedures for using SBACKUP to back up (and restore) data on NetWare 4 and NetWare 5 servers. Backing Up and Restoring a NetWare 5 Server Before you backup 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:

7 Netware 6 Upgrade and Migration CHAPTER Start at the server console. Load the device drivers for your controller and storage devices. If you load HAM drivers or add an external device, enter the following at the server console prompt: LIST DEVICES. Then, load the appropriate Target Service Agents (TSAs). For more detailed information, refer to the section titled Before Running the Backup Software in the SMS manual at TIP Load the Storage Management Engine and backup software on the server. Begin by entering LOAD SMDR at the console. Accept the default or add an SMDR context by pressing Enter. Then, enter the full context of your username and provide your administrative password. 3. Type the following commands at the console to activate SBACKUP: LOAD TSA500 LOAD SMSDI LOAD QMAN LOAD SBSC LOAD SBCON 4. After the NLMs are loaded, select Main Menu, Job Administration, Backup at the main menu. Next, choose the NetWare server running your backup or restore TSA by selecting Target Service. Enter the target username and password (if prompted) for the target. 5. You will need to select what you want to back up. To do so, press Insert. On the NetWare server screen, select the volumes and files you want to back up, and then press Esc. In the Description field, enter a descriptive name for the backup session, and select Device/Media Name. Then, choose Advanced Options, Append Session. Finally, save your options and continue with the backup by pressing Enter. You can return to the main Menu by pressing Esc repeatedly. To restore backed up data to a NetWare 5 server, perform these steps: 1. Start at the server console. Load the device drivers for your controller and storage devices. Next, load the appropriate TSAs. Finally, load Enhanced SBACKUP. 2. At the Main Menu, select Job Administration, Restore. Then, choose Target Service, NetWare Server Running Your Backup and Restore

8 72 CHAPTER 2 Netware 6 Upgrade and Migration Target Service Agent. When you are prompted for the target username, enter your network administrator username and context (if required) for the target. If prompted, enter the password for the target. 3. In the Description field, enter a descriptive name for the session. Select the device and media to restore. In the Device/Media Name field, press Enter and decide where you want to restore from. Then, select the session to restore. 4. Finally, to make the selected restore, select Advanced Options, and complete the Advanced Restore Options form. Press Esc and answer the prompt at the Submit Job screen to begin the restore session. To view the activity log screen, press Alt+Esc. To return to the Main Menu, press Esc repeatedly. Backing Up and Restoring a NetWare 4 Server 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: 1. Start at the server console. Load the device drivers for controller and storage devices. Then, load SBACKUP.NLM and the appropriate TSA files. On the host server, load the SBACKUP.NLM. 2. From the Main Menu, choose Backup. Select a target for the data you want to back up. Next, choose the Backup/Restore Target Services Running on <Target Name> listing. Select the TSA you want to use. Then, provide the username and password for the target you want to back up. 3. Select the device that you want to back up. Choose Type of Backup and highlight the type of backup you want to perform. Enter a description of the backup session. Save the description and continue with the backup by pressing F Finally, specify when you want the backup to start by setting the date and time for the backup to begin. Press F10, and save your changes by pressing Enter.

9 Netware 6 Upgrade and Migration CHAPTER 2 73 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 are restoring. To restore backed up data to a NetWare 4 server, perform these steps: 1. At the server console, load SBACKUP. From the Main menu, select Restore. Select the target that you want to restore the data to, and enter the appropriate username and password. 2. Specify how you want the date to restore. Then, start the restore by pressing F10. When you are done, you can view the error log to determine whether any files were not restored. For more information, refer to the NetWare 4 documentation at TIP Network Preparation Before you can install, upgrade, or migrate NetWare 6 and edirectory 8.6 to any servers in an existing network, you must update the edirectory schema. A convenient way to do so is to use NetWare Deployment Manager, which is located in the root of the NetWare 6 Operating System CD. This utility helps you to ensure that the latest version of edirectory is running on all your servers. The following is a summary of the steps required to prepare your network to use NetWare Deployment Manager to install, upgrade, or migrate NetWare 6. This process only needs to be performed once per network: 1. Install the Novell Client for Windows 95/ Install the NICI Client. 3. Update edirectory with Deployment Manager. 4. Prepare the Network for edirectory 8.6. Ready, set, deploy!

10 74 CHAPTER 2 Netware 6 Upgrade and Migration Step 1: Install the Novell Client for Windows 95/98 To use NetWare Deployment Manager, you must have the latest Novell Client and NICI client on both your primary and secondary administrative workstations. Following are the steps for installing the Novell Client for Windows 95/98: 1. Exit any applications that you are running to clear off your workstation. Then, download the appropriate Novell Client from the Novell web site at 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 are done 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 SETUP.EXE. (For example, if you downloaded the Novell Client for Windows 98, it may be located in the \WIN95\ENU folder under the temporary folder you created.) When the Novell Client for Windows 95/98 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 95/98 Install screen (as shown in Figure 2.2) and click Next.

11 Netware 6 Upgrade and Migration CHAPTER 2 75 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 95/98 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. 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 are 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,

12 76 CHAPTER 2 Netware 6 Upgrade and Migration 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.4 Selecting optional components during Novell Client installation. FIGURE 2.5 Configuring the Novell Client in Windows 95/ TIP If you encounter any errors during the Novell Client installation process, you can install the client manually on the Configuration tab of the Network icon in the Windows Control Panel. Step 2: Install the NICI Client In addition to the Novell Client, you will 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.

13 Netware 6 Upgrade and Migration CHAPTER 2 77 Follow these short and simple steps to install the appropriate NICI client on both of your administrative workstations: 1. Exit any applications that you are running to clear off your workstation. Then, download the appropriate NICI Client from the Novell web site at 2. Next, select the appropriate NICI Client file (Version or later) from the Novell web site. Make sure to use your new elogin account (as shown in Figure 2.1). When you are done saving the file, expand it and continue with the next step. 3. To install the NICI Client, follow the prompts on the screen. Step 3: Update edirectory with Deployment Manager 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 into your network from a Windows 95/98 or Windows NT/2000 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). 3. Select Browse when the Update NDS window appears. Then, navigate to your tree and select the top-most container under your tree (such as ACME shown in Figure 2.7). Select OK to continue.

14 78 CHAPTER 2 Netware 6 Upgrade and Migration FIGURE 2.6 Updating NDS versions in Deployment Manager. FIGURE 2.7 Selecting the top-most 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. Step 4: Prepare the Network for edirectory 8.6 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.

15 Netware 6 Upgrade and Migration CHAPTER 2 79 FIGURE 2.8 Searching the tree for servers to be updated in Deployment Manager. 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 into your network from a Windows 95/98 or Windows NT/2000 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 NDS 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. That s it! All finished. You have successfully prepared the network for NetWare 6 installation, upgrade, and/or migration. In this section, we learned how to update the edirectory schema using NetWare Deployment Manager. Now let s check the Certificate Authority (CA) object before we start upgrading.

16 80 CHAPTER 2 Netware 6 Upgrade and Migration FIGURE 2.10 Selecting a replica server in Deployment Manager. Certificate Authority Update 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 LDAP (Lightweight Directory Access Protocol), NetWare Web Server, and the NetWare Management Portal. It also allows you to mint, issue, and manage digital certificates by creating a Security container object and an Organizational Certificate Authority (CA) object. If the network does not 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 [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 only applies 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:. You must install the most recent version of Novell Certificate Server.. To create the organizational CA and complete the NetWare Upgrade, you must have the Supervisor right at the [Root] of the edirectory tree. You must also have the Supervisor right in the Security container, or at the [Root] of the tree if the Security container does not exist.

17 Netware 6 Upgrade and Migration CHAPTER If you plan to use the Novell Certificate Server 2.20 ConsoleOne snapin (available with NetWare 6) you need client NICI (or later) installed on the workstation where you run ConsoleOne. Refer to the Network preparation section earlier in this chapter for more details. Follow these steps to update your network for the new Novell Certificate Server: 1. First, determine which server in your network is acting as the Organizational CA. By default, the Organizational CA s object is stored in the Security container. Using ConsoleOne, double-click the Organizational CA object, and choose the General tab. 2. On the server acting as the CA, verify that it is running Novell Certificate Server 2.0 or later. From the server console, enter NWCONFIG, and select Product Options. Next, choose VIEW/Configure/Remove Installed Products. Look for the PKIS entry; if there is no entry, or if you do not see or later, install Novell Certificate Server 2.0 (or later) before continuing. You can find it on Novell s website. 3. Check for the existence of security-related objects and establish the proper edirectory rights for creating and operating the CA. If the KAP container or the W0 object do not exist (the KAP container is in the Security container, and the W0 object is in the KAP container), the installation of the first NetWare 6 (or NetWare 5.1) server will create them for you. Furthermore, the first NetWare 6 installation or upgrade will create the Organizational CA as well. The server acting as the CA must remain operational during the installation or upgrade other NetWare 5.1 or NetWare 6 servers into this tree. Furthermore, if the CA object, KAP container, and the W0 object exist, you will need the following edirectory rights to upgrade NetWare:. Read entry rights to the NDSPKI:Private Key attribute of the Organizational CA s object.. Supervisor right to the W0 object. Supervisor right to the server s container... REAL WORLD 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?! Yes!

18 82 CHAPTER 2 Netware 6 Upgrade and Migration Now that you ve satisfied all the NetWare 6 Upgrade and Migration requirements, it s time to begin building the NetWare 6 server. In the rest of this chapter, we explore the detailed steps of both of these advanced NetWare 6 installation options Upgrade and Migration. Upgrading to NetWare 6 Test Objective Covered: 2. Upgrade or migrate to NetWare 6. I have good news and I have bad news:. Good News The NetWare 6 Upgrade process closely resembles the NetWare 6 Installation steps we covered in the previous chapter.. Bad News The NetWare 6 Upgrade process occurs on an existing Novell server with all of its edirectory information, shared data, and internal problems. Fortunately, you are a CNE (Certified Novell Engineer), and therefore you are trained to handle the ups and downs of NetWare 6 Upgrade. The inplace nature of NetWare 6 s Upgrade process is both a benefit and a curse. It s a benefit in that it allows you to upgrade existing edirectory and user files to NetWare 6 on the same machine. It s a curse in that it provides limited recovery if (or when) something goes wrong. In this section, we re going to explore all 18 steps of the NetWare 6 Upgrade process in great depth. Please follow this discussion carefully, because it could mean the difference between a speedy NetWare 6 server and a useless hunk of silicon. And, if this journey isn t enough for you, you can always check out the detailed step-by-step ACME walk-through at the end of this section it s called Exercise 2.1: Upgrade NetWare 5.1 to NetWare 6. Here is a brief roadmap of the major steps that occur during each of the five upgrade phases:. Phase I: Choosing the Correct NetWare 6 Settings You will prepare the server, execute the INSTALL.BAT file, accept the license agreements, and load the core NetWare operating system. Then, you will select a plethora of general NetWare 6 settings, including upgrade type, server settings, and regional settings.

19 Netware 6 Upgrade and Migration CHAPTER Phase II: Upgrading Storage to NetWare 6 You will install and configure NetWare 6 storage devices by selecting an appropriate platform support module and/or HotPlug support module (if applicable), and configuring storage adapter(s), storage device(s), and network board(s).. Phase III: Upgrading the Server and Network You will configure the file system and review existing network protocols.. Phase IV: Setting Up DNS and edirectory You will expand beyond the server to establish Domain Name settings and to configure your Directory tree. This phase encompasses the following three steps: configure Domain Name Service (DNS), configure edirectory, and license the NetWare 6 server.. Phase V: Completing the Upgrade You will complete the NetWare 6 upgrade process by (optionally) installing additional network products, installing the Novell Certificate Server, and customizing final upgrade parameters. Every great adventure begins with a single step yours starts with Phase I. Phase I: Choosing the Correct NetWare 6 Settings In Phase I, you will prepare the server, execute the INSTALL.BAT file, accept the license agreements, and load the core NetWare operating system. Then, you will select a plethora of general NetWare 6 settings, including upgrade type, server settings, and regional settings. Let s get started. Step 1: Prepare the Server 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:

20 84 CHAPTER 2 Netware 6 Upgrade and Migration 1. Install the DOS CD driver for the computer s CD drive onto the DOS partition. (The DOS CD driver should be obtained from the CD drive manufacturer.) After you install the driver, verify that the logical filename of the CD drive specified in the computer s CONFIG.SYS and AUTOEXEC.BAT files is not CDROM or CDINST. 2. Verify that the CONFIG.SYS file contains the following parameters: FILES=50 and BUFFERS= (Conditional) If you plan to upgrade NetWare 6 from upgrade files located on a network, install the Novell Client for DOS and Windows 3.1x or IP Server Connection utility located on the NetWare 6 Novell Client CD, as appropriate. 4. (Conditional) If you plan to upgrade NetWare 6 from upgrade files located on a network, don t forget to copy the files to the desired server. Also, verify that you have the appropriate security rights to access them. Step 2: Begin the Upgrade To begin the NetWare 6 upgrade process, insert the NetWare 6 Operating System CD into the CD drive (or log into the network if you have stored the NetWare 6 upgrade files on an existing server), and enter the following command at the prompt: INSTALL... REAL WORLD The INSTALL.BAT file is located in the root directory of the NetWare 6 Operating System CD. If you have a bootable CD drive that meets the El Torito specification, you can boot off the CD to load the upgrade program automatically rather than manually executing the INSTALL.BAT program as indicated above. Notice that the upgrade program displays the initial screens in text mode. Autodetected and/or default settings appear on each screen. You can either accept the autodetected 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.

21 Netware 6 Upgrade and Migration CHAPTER 2 85 At the beginning of the upgrade process, you are 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 have 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 have read the agreement and accept its terms and conditions. Step 3: Select the Upgrade Type When the Welcome to the NetWare Server Installation screen appears, you are 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. New Server Installs a new server from scratch. Creates a new NetWare partition for the SYS: volume but does not delete system partitions or other partitions (such as DOS, Unix, or Windows). See Chapter 1 for more details.. Upgrade Upgrades a NetWare 4 or NetWare 5 server to NetWare 6. This option retains all original server data such as partitions, volumes, directory structures, and files.. Pre-Migration Uses the Migration Wizard to migrate data from an existing (source) server to a new (destination) NetWare 6 server. Review the values listed on this screen and modify them as necessary. In Lab Exercise 2.1, you will perform a NetWare 6 custom upgrade.

22 86 CHAPTER 2 Netware 6 Upgrade and Migration Step 4: Specify the Server Settings The Server Settings screen appears next, listing the following default values:. Load Server at Reboot: Yes. Server Set Parameters: Edit. Backup Startup Directory (Optional): C:\NWSERVER.OLD Some information you might want to keep in mind regarding these options includes. Load Server at Reboot If you select Yes (default), the AUTOEXEC.BAT and CONFIG.SYS files are copied and renamed with a.00x extension. The original AUTOEXEC.BAT and CONFIG.SYS files are then updated so that the NetWare operating system automatically loads when the server boots. If you select No, the AUTOEXEC.BAT and CONFIG.SYS files are not updated.. Server SET Parameters SET parameters might need to be modified for device drivers such as network boards or storage devices in order to complete the installation. SET parameters are saved in the server s STARTUP.NCF file.. Backup Startup Directory (Optional): C:\NWSERVER.OLD Location to save old C:\NWSERVER startup files.... REAL WORLD If you attempt to access the NetWare 6 upgrade files from a server on a different network segment, you may discover that you are unable to reconnect to the server to complete the upgrade until you specify an unfiltered server ID number. Step 5: Select the Regional Settings The Regional Settings screen appears next, as shown in Figure Regional settings are used to customize server language and keyboard settings. If you are located in the United States, the default values are as follows:. Country: 001 (USA). Code Page: 437 (United States English). Keyboard: United States

23 Netware 6 Upgrade and Migration CHAPTER 2 87 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. Phase II: Upgrading Storage to NetWare 6 In Phase II, you will install and configure NetWare 6 storage devices by selecting an appropriate platform support module and/or HotPlug support module (if applicable), and configuring storage adapter(s), storage device(s), and network board(s). Step 6: Select Platform Support 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):. Platform Support Module A platform support module (PSM) driver can be loaded to optimize the performance of servers with multiple processors and other configurations. If a PSM is not detected, your computer probably does not need one. If a platform support module driver is detected on a computer that does not contain multiple processors, the driver can be allowed to load without adversely affecting performance. Platform support modules typically have a.psm filename extension.

24 88 CHAPTER 2 Netware 6 Upgrade and Migration. HotPlug Support Module PCI HotPlug technology allows storage adapters and network boards to be inserted and removed while the computer is powered on. If a PCI HotPlug module is not detected, your computer probably does support the technology (and thus, does not need one). PCI HotPlug modules typically have an.nlm extension.. Storage Adapters Storage adapters require a software driver called a host adapter module (HAM) to communicate with the computer (host). Because a single storage adapter can control more than one type of storage device, only one HAM may be required. Various types of storage adapters, such as Integrated Drive Electronics (IDE) and Small Computer System Interface (SCSI), maybe autodetected. If a particular storage adapter is not detected, choose the appropriate driver from the list, or load it from a manufacturer-provided disk. Verify that properties such as interrupt, port value, and slot do not conflict with any other device in the computer. Host adapter modules typically have a.ham extension. FIGURE 2.12 Selecting platform support during NetWare 6 upgrade.... REAL WORLD To add, change, or delete a device driver in any of the three driver screens discussed here, follow these simple steps: 1. In the Options box, select Modify. 2. Select the device type that you want to work with and press Enter. 3. To add a driver, press Insert, specify the location of the driver, and press Enter. To delete a driver, select it from the list and press Enter. To modify a driver, select it from the list, choose the property to modify, and press Enter. Step 7: Select Storage Devices 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

25 Netware 6 Upgrade and Migration CHAPTER 2 89 separate CDM. The Upgrade Wizard autodetects 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. Because a single adapter can control more than one type of storage device, your computer may require only one HAM, but have multiple types of storage devices, and thus, multiple CDMs.... TIP Step 8: Select Network Boards and NLMs The third driver screen lists these storage drivers:. Network Boards Network boards require a software driver called a LAN driver to communicate with the network. The upgrade program autodetects many types of network boards. If a particular network board is not detected, choose the appropriate driver from the list provided, or load it from a manufacturer-provided disk. To edit the properties of the network board, it must be installed and configured properly. Verify that properties such as interrupt, port value, and slot do not conflict with any other device in your server. LAN drivers typically have a.lan extension.. NetWare Loadable Modules Some servers and network configurations require that you load an NLM before completing the server upgrade. (For example, if you are installing the server in a Token Ring environment, you may need to load ROUTE.NLM.) If required, add the appropriate NLM to the NetWare Loadable Modules field. When you select Continue the Upgrade Wizard copies system files to the SYS: volume. If you are installing NetWare 6 from the network, you will be prompted to reconnect to the network. To continue the upgrade, you must authenticate with the same User object and password that you used at the beginning of the upgrade process.... TIP This completes the next three steps of NetWare 6 upgrade, and Phase II. Now, we will venture into a whole new world GUI installation screens.

26 90 CHAPTER 2 Netware 6 Upgrade and Migration Phase III: Upgrading the Server and Network Welcome to the Java portion of NetWare 6 upgrade! In Phase III, you will review existing network protocols. In this stage, you will leave the boring text-mode world and switch to a Java interface. Although a mouse is recommended, you can use keystrokes to navigate through the upgrade program screens. Remember that the NumLock (number lock) key must be activated in order for cursor movements to be enabled on the keypad. At this point, the Upgrade Wizard copies a number of files to the server hard drive (called the preparatory file copy process). A Java Virtual Machine (JVM) is created on the server and the GUI portion of the Upgrade Wizard is loaded. This step may take a while, so feel free to go have a cup of java while you wait. Step 9: Enable Cryptography (Conditional) 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, 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! Step 10: Configure the NetWare Server File System The NetWare 6 file system consists of partitions, volumes, and free space. In this step, you are 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:. NSS Volumes NSS is an advanced file system technology that is designed for the management of large volumes, large files, name spaces, and complex storage devices. It significantly reduces the

27 Netware 6 Upgrade and Migration CHAPTER 2 91 amount of time required to mount large volumes. This is the default volume type.. Traditional Volumes Traditional volumes are not recommended and should only be used if you require the use of technologies such as block suballocation, NFS (Network File System), FTP, VREPAIR, or file locks. 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. Although an NSS SYS: volume is recommended for most server installations, you can create a traditional SYS: volume by pressing F5 during step 10. If all available space has been allocated to the SYS: volume, you will not be prompted for additional NetWare server file system information. If this is the case, skip to Step 11: View Network Protocols.... TIP 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 are done, 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. Volume names can consist of 2 to 15 characters. Valid characters include A through Z, 0 through 9, and!, #, $, %, &, (, and ). A volume name cannot begin with an underscore (_) or contain two or more consecutive underscores.... TIP 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 only need to mount all volumes now if you plan to install additional products and services (such as documentation) on volumes other than SYS:.

28 92 CHAPTER 2 Netware 6 Upgrade and Migration Step 11: View Network Protocols 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:. IP Only The IP Only protocol configuration forces your NetWare 6 server and all its workstations to communicate using IP only. The IP protocol choice also causes the server to automatically bind the ETHERNET_II frame type to the corresponding internal NIC.. IP with IPX Compatibility Mode When the IP protocol is selected, passive support for IPX is also provided. If an IPX request arrives at the server, NetWare 6 processes the request. This passive support for IPX is called Compatibility Mode and it must be enabled manually using the Advanced tab.. IPX Only You can also configure your NetWare 6 server for IPX (Novell s traditional communications protocol) to facilitate legacy NetWare IPX applications. If IPX, but not IP, is installed on your server, it will actively process IPX packets and ignore packets using other protocols, such as IP. This is not a good idea because many new NetWare 6 network features require the more advanced IP protocol.. IP and IPX If you have network clients or applications that require both IP and IPX, you can install multiple protocols simultaneously. Fortunately, both IP and IPX protocols can be bound to a single server NIC. In this configuration, the server processes IP requests using IP, and IPX requests using IPX. This solution is elegant in its simplicity!... TIP To configure the IP protocol, you must be familiar with and know the IP address, the subnet address, and the router (gateway) address. The Upgrade utility uses default frame types of ETHERNET_802.2 (if no frame types are detected while installing IPX) and ETHERNET_II (for IP). 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 Services and edirectory.

29 Netware 6 Upgrade and Migration CHAPTER 2 Phase IV: Setting Up DNS and edirectory In Phase IV, you will expand beyond the server to establish Domain Name settings and configure the edirectory tree. This stage encompassed the following three steps: configure Domain Name Service (DNS), configure edirectory, and license the NetWare 6 server. Let s start with enhanced IP address management via the Domain Name Service. Step 12: Configure DNS Earlier, we 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 Services, 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:. Host Computer The simple, readable name on the DNS server that matches your NetWare server s name (or the name you have bound to the internal server NIC). You can set up the host computer name on the DNS server to use the NetWare server name.. Domain Name The hierarchical name that represents the organization of your network, such as acme.com. Typically, you should use the information provided by your network administrator. In many cases it is the name of the server s host Organization object in the NDS tree.. Domain Name Server The IP address of the DNS server that maintains the list containing this NetWare server s simple, readable name and IP address. For more information, contact your network administrator or ISP. If your NetWare 6 server is providing DNS services, this would be its own IP address. 93 If you see an error message at this point, it means that you don t have an A-record on your DNS server for the hostname you supplied. Be sure to go back later and add the appropriate record.... TIP......

30 94 CHAPTER 2 Netware 6 Upgrade and Migration FIGURE 2.13 Configuring Domain Name Services during NetWare 6 upgrade. Step 13: Configure edirectory When the Login to NDS screen appears, log into 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. 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:. NDS Tree Name. Server Context. Administrator name. Administrator password you entered on previous screen FIGURE 2.14 Viewing the NDS Summary screen during NetWare 6 upgrade.

31 Step 14: License the NetWare 6 Server Netware 6 Upgrade and Migration CHAPTER 2 Novell Licensing Services has been enhanced in NetWare 6 to support two different models for distributing valid license certificates to network users and services:. Server Connection License (SCL) Model In the SCL model, users are granted access to network resources and services based on the server they are logged into. This means that each user must obtain an available license for every server that hosts a resource that they need.. User Access License (UAL) Model In NetWare 6, Novell Licensing has evolved beyond the server to focus on the network as a whole. This new model is known as User Access Licensing (UAL). In the UAL model, User objects receive a permanent license unit that allows them to access network services at any time and from any workstation attached to the network. This greatly simplifies Novell license management. When you install or upgrade to NetWare 6, the Wizard installs the SCL 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, while NetWare 5 servers deliver an SCL certificate for each server. We will 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). 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

32 96 CHAPTER 2 Netware 6 Upgrade and Migration FIGURE 2.15 Licensing the server during NetWare 6 upgrade. 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 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 may wish to install these MLA license certificates high in the tree so that they will be available to more servers and users.... TIP If you are using a demo version of the NetWare 6 Operating System CD (that is, one that does not have an associated license disk), use the license file in the preselected directory on the CD. If you can t locate the license file, mark the Install without Licenses check box, although you may experience problems with features such as Novell Distributed Print Services (NDPS), which use multiple connections. 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. Phase V: Completing the Upgrade Finally, in Phase V, you will complete the NetWare 6 upgrade adventure by installing additional network products, installing the Novell Certificate Server, and customizing final upgrade parameters.

33 Netware 6 Upgrade and Migration CHAPTER 2 97 Let s continue by installing some additional network products. Some of my personal favorites are Novell Native File Access Pack (NFAP), NetWare Web Access, and iprint. Step 15: Install Additional Network Products Near the end of the upgrade process, you will 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 Names Services, and advanced Novell auditing. Some products can only be installed using the NetWare Deployment Manager after the server upgrade is complete.... TIP 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):. iprint/ndps. NetWare Enterprise Web Server. NetWare FTP Server. NetWare Web Search. Novell DNS/DHCP Services. WAN Traffic Manager Services. Novell Native File Access Pack (selected by default). Novell Advanced Audit Service (selected by default). NetWare Web Access 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 automatically be selected. Also, always be sure your server has enough disk space and system memory to accommodate the products you want to install.

34 98 CHAPTER 2 Netware 6 Upgrade and Migration FIGURE 2.16 Selecting components to install during NetWare 6 upgrade.... TIP In this study guide, we will explore each of the additional network products listed above. However, we won t cover their installation and configuration in this chapter. Because many of these products are complex, we will devote entire sections of the guide to their proper configuration in subsequent chapters. Stay tuned! Step 16: Install Novell Certificate Server The 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. Once the Organizational CA object is created on a server, it cannot be moved to another server. Deleting and recreating 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 [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.... TIP If the Organizational CA object already exists on the network, the installation program finds and references the server that holds it. The installation program then accesses the Security container and creates a Server Certificate object. To access the Security container and create a Server Certificate object, you must be logged in as a user with the Read right to the existing Security container object.

35 Netware 6 Upgrade and Migration CHAPTER 2 99 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. Once you are 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. Step 17: Customize the 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. 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 have finished customizing your selections, select OK to return to the Summary screen.

36 100 CHAPTER 2 Netware 6 Upgrade and Migration FIGURE 2.19 Customizing Novell products during NetWare 6 upgrade. Step 18: Complete the Server Upgrade On the Summary screen, select Finish to complete the upgrade process. Yeah! The Upgrade Wizard then performs the main file copy. (This step may take a while.) When the file copy is finished, 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.... REAL WORLD NetWare 6 automatically reloads when the server restarts, provided that you did not change default settings during the upgrade process. You can also load the NetWare 6 operating system manually by performing the following three steps: 1. When prompted that the upgrade is complete, restart the server by selecting Yes. 2. Change to the startup directory containing the NetWare server files (C:\NWSERVER). 3. Type SERVER and press Enter.

37 101 Netware 6 Upgrade and Migration CHAPTER 2 Congratulations you ve done it! You have successfully traversed the 5 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.

38 102 CHAPTER 2 Netware 6 Upgrade and Migration Lab Exercise 2.1: Upgrade NetWare 5.1 to NetWare 6 In this lab exercise, you will perform these tasks:. Part I: Install NetWare 5.1 on WHITE-SRV1. Part II: Install the Latest NetWare 5.1 Support Pack. Part III: Prepare the Source Server. Part IV: Perform an In-Place Upgrade to NetWare 6 In this lab exercise, you will need the following components:. The server hardware used in Lab Exercise 1.1. (In this exercise, you will overwrite the NetWare 6 operating system with NetWare 5.1.). Two workstations running Windows 95/98 or Windows NT/2000 that (meet or exceed) the minimum hardware requirements for a NetWare 6 administrative workstation. (These should be the workstations that you plan to use as your primary administrative workstations for the lab exercises in this book.). A Microsoft Windows Operating System CD-ROM (that matches the Windows operating system that is running on the primary administrative workstation).. A Microsoft Windows Operating System CD-ROM (that matches the Windows operating system that is running on the secondary administrative workstation).. Internet access for the workstations.. A NetWare 6 Operating System CD.. (Optional) A NetWare 5.1 License/Cryptography disk containing a server license.. A NetWare 6 License/Cryptography disk containing both server and user licenses. (This is the one you used in Lab Exercise 1.1.)

39 103 Netware 6 Upgrade and Migration CHAPTER 2 Part I: Install NetWare 5.1 on WHITE-SRV1 Perform the following tasks at the WHITE-SRV1 server console: 1. Using the parameters in Table 2.1, install NetWare 5.1 on the WHITE- SRV1 server. During the installation process:. Install the server as a new server, not as an upgrade! (In other words, you are going to overwrite the NetWare 6 operating system with NetWare 5.1.). Do remove and re-create the DOS partition.. Do remove and re-create the NetWare partition and SYS: volume.. Overwrite any newer files (even though you would not normally do so in real life ). Novell s CNE Study Guide for NetWare 5.1 contains a demo version of NetWare 5.1 that can be used to install NetWare 5.1. If you don t have access to a NetWare 5.1 Operating System CD, you ll have to just pretend that your NetWare 6 server is a NetWare 5.1 server and upgrade it anyway.... TIP Installation Parameters PARAMETER VALUE TABLE 2.1 Installation Type New Server (not upgrade!) Server Name WHITE-SRV1 NetWare Partition Not to exceed 4 GB Default Volume SYS: (Not to exceed 4 GB) IP Address Subnet Mask Hostname WHITE-SRV1 Domain acme.com edirectory Tree New tree (not existing tree!) edirectory Tree Name ACME-TREE Server Context OU=WHITE.OU=CRIME.OU=TOKYO.O=ACME Admin Context OU=WHITE.OU=CRIME.OU=TOKYO.O=ACME Admin Password ACME

40 104 CHAPTER 2 Netware 6 Upgrade and Migration Part II: Install the Latest NetWare 5.1 Support Pack Perform the following step on your primary administrative workstation: 1. Download the Latest NetWare 5.1 Support Pack You will not be allowed to upgrade your NetWare 5.1 server to NetWare 6 unless the NetWare 5.1 Support Pack 2 or later is installed on your server. In this lab exercise, we ll use the most recent Support Pack provided by Novell at the time of printing. It is okay for you to use the most recent Support Pack at the time of reading. a. Normally, you would carefully back up any existing data on the server. Because you are using a practice (that is, nonproduction) server for this lab exercise, however, you can skip this step. b. Log into your network as Admin. c. Create a directory on WHITE-SRV1 volume SYS called SP. d. Create a drive mapping that maps S: to the SP directory. e. Next, launch Internet Explorer, and access the Novell web site at nw51sp4.exe/. f. Download the nw51sp4.exe file from the web site to the SP directory on your server. g. Access a DOS prompt on your workstation.. Select Start, Programs, MS-DOS Prompt.. When the DOS prompt appears, switch to the S: drive.. At the DOS prompt, explode the file by entering nw51sp4. (Note: It might take a while for the file extraction to begin. It will be even longer for the files to be extracted. Feel free to take a break at this point.). When the files explosion process is complete, enter EXIT to exit the DOS prompt. Perform the following step at the WHITE-SRV1 server console: 2. Install the Latest NetWare 5.1 Support Pack. a. At the WHITE-SRV1 prompt, launch NWCONFIG.

41 105 Netware 6 Upgrade and Migration CHAPTER 2 b. When the Configuration Options window appears, select Product Options, Install a Product Not Listed. c. To specify the source path, press F3. d. When the Specify a Directory Path field appears, specify the following path: SYS:\SP\NW51SP4 e. Wait while the support pack files are installed. f. When the Novell Terms and Conditions screen appears, read the information on the screen, and then press Esc. g. When the Do You Accept the License Agreement window appears, select Yes. h. When the License Agreement for JReport Runtime screen appears, read the information on the screen, then press Esc. i. When the Do You Accept the ConsoleOne Reporting Tool License Agreement window appears, select Yes. j. When a message appears indicating that the NetWare Support Pack Version is about to be installed, press Enter to continue. (Note: It may take a while for the support pack files to be installed. Feel free to take a break at this point.) k. When the Backup Files Replaced by NetWare Support Pack window appears, select Yes. l. When the Do you Want to Update the Storage/LAN/PSM/WAN Drivers Currently in Use window appears, select Yes. m. When the Reboot the Server After Copying Files window appears, select Yes. n. When a warning screen appears, indicating that the Installed Products and Services will now be shut down, press Enter. Then, wait for the files to copy. o. When the Enter Destination Path for Backup Files window appears, leave the default of SYS:\SYSTEM\BACKSP4 and press Enter. Then, wait for the files to copy. p. A message will appear indicating that the system is backing up files and that it can take approximately 5 to 15 minutes. Wait while this occurs.

42 106 CHAPTER 2 Netware 6 Upgrade and Migration q. After the support pack installation is complete, allow the server to reboot. r. If the Auto Purge feature is not set on your server, you might want to manually purge the volume to free disk space. Part III: Prepare the Source Server Perform the following step at the WHITE-SRV1 server console: 1. Run DSREPAIR. a. At the server prompt, enter DSREPAIR.. In the Available Options menu, select Unattended Full Repair. Wait until the repair process is complete. Note the number of errors, and then press Enter to acknowledge the message. If any errors occurred, review the log file that appears on the screen, press Esc to exit the log file, and then repeat the process until it runs without errors.. In Available Options menu, select Time Synchronization. When the log file appears, review the log file to determine if any errors occurred, then press Esc. If any errors occur, attempt to troubleshoot the problems.. In the Available Options menu, select Report Synchronization Status. When the log file appears, review the log file to determine if any errors occurred, then press Esc. If any errors occur, attempt to troubleshoot the problems. b. Exit DSREPAIR. Perform the following step on your primary administrative workstation: 2. Run Deployment Manager: a. Insert the NetWare 6 Operating System CD into the workstation s CD drive. b. Log into the network as admin. c. Launch NetWare Deployment Manager (NWDEPLOY.EXE), which is located in the root of the NetWare 6 Operating System CD.. Select Start, Run.. When the Run dialog box appears, select Browse.

43 107 Netware 6 Upgrade and Migration CHAPTER 2. When the Browse dialog box appears, browse to the NetWare 6 Operating System CD.. Select NWDEPLOY (which is located in the root of the CD), and then select Open.. When the Run dialog box reappears, select OK. d. When the Select Product window appears, double-click the Network Preparation folder to expand it. e. Under Network Preparation, select Step 3: Prepare for NDS edirectory 8.6. f. When the Update NDS window appears, select the Browse button to the right of the text field. g. When the NDS Tree Browser window appears. Expand Novell Network.. Expand Novell Directory Services.. Select ACME-TREE.. Select OK. h. If a Login Dialog window appears, authenticate as admin.. In the Username field, enter admin.. In the User Password field, enter acme.. In the Tree field, verify that ACME-TREE is listed.. In the User Context field, enter WHITE.CRIME.TOKYO.ACME.. Select OK. i. When the Update NDS window appears, verify that netware://trees/acme-tree is listed, and then select Next. j. When the next Update NDS window appears, both of your servers should be listed. Verify that the WHITE-SRV1 server appears in both the Available Servers and Selected Server fields, then select Next. k. When the next Update NDS window appears, verify that it indicates that the edirectory tree is prepared for edirectory 8.6. If so, select Exit.

44 108 CHAPTER 2 Netware 6 Upgrade and Migration l. On WHITE-SRV1, wait until the following message appears at the console prompt: NDSEM : Process Completed. (Be patient. It may take a while for this message to appear!) This also verifies that edirectory on WHITE-SRV1 was prepared for edirectory 8.6. m. On your workstation, close Deployment Manager by selecting Cancel. n. When the Exit window appears, select Yes. Part IV: Perform an In-Place Upgrade to NetWare 6 Perform the following steps at the WHITE-SRV1 server console: 1. Prepare the Server. Ensure that the source Upgrade server is prepared for NetWare Begin the upgrade. a. Insert the NetWare 6 Operating System CD into the server s CD drive. b. At the server console prompt, enter RESET SERVER. Watch the server console screen while the server reboots. c. When prompted, select one of the following:. To install IDE CD drivers, press I.. To install SCSI CD drivers, press S.. To install both IDE and SCSI drivers, press B. d. When the Welcome to NetWare Server Installation screen appears, select Accept License Agreement. This indicates that you have read the agreement and accept its terms and conditions. Num Lock (number lock) must be on in order for cursor movements to be enabled on the keypad. e. When a screen appears indicating that a valid boot partition was detected on the computer s hard disk, select Continue with Existing Partition. f. When the JReport Runtime License Agreement screen appears, press F10 to indicate that you have read the agreement and accept its terms and conditions.

45 109 Netware 6 Upgrade and Migration CHAPTER 2 3. Select the Upgrade Type. When the Welcome to the NetWare Server Installation screen appears, perform these tasks:. In the Is This an Express Install or a Custom Install? field, press Enter to switch the value from Express to Custom.. In the Is This a New Server, Upgrade, or Pre-Migration? field, verify that Upgrade is selected.. Select Continue. 4. Specify the Server Settings. When the Server Settings screen appears, you ll notice that the following default values are listed:. Load Server at Reboot: Yes. Server Set Parameters: Edit. Backup Startup Directory (Optional): C:\NWSERVER.OLD Select Continue. 5. Select the Regional Settings. When the Regional Settings screen appears, you ll notice that default values are listed for the country code, code page, and keyboard type. If you are located in the United States, the default values are. Country: 001 (USA). Code Page: 437 (United States English). Keyboard: United States Review the values listed on this screen and modify them if necessary. Then, select Continue. Allow the files to copy. If advised that a target file is newer than the one on the CD, select Never Overwrite Newer Files. 6. Select Platform Support. A device driver screen appears, listing autodetected drivers for the following parameters:. Platform Support Module. HotPlug Support Module. Storage Adapters Review the values listed on this screen and modify them if necessary. Then, select Continue. Allow the files to copy.

46 110 CHAPTER 2 Netware 6 Upgrade and Migration 7. Select Storage Devices. A device driver screen appears, listing autodetected drivers for storage devices. Review the values listed on this screen and modify them if necessary. Then, select Continue. Allow the files to copy. 8. Select Network Boards and NLMs. A device driver screen appears, listing autodetected drivers for network board(s) and allowing you to (optionally) specify NLMs. Review the values listed on this screen and modify them if necessary. Then, select Continue. Next, the installation program copies a number of files to the server (called the preparatory file copy process). The installation program then loads the GUI-based Installation Wizard, at which point the installation interface switches from being text based to graphic based. 9. Enable Cryptography (Conditional). 10. Configure the NetWare Server File System. When the Configure File System screen appears, review the information on the screen, and then click Next. 11. View Network Protocols. When the Protocols screen appears, you ll notice that the existing IP Address and Subnet Mask values are displayed. Review the values listed on this screen and modify them if necessary. Then, select Next. 12. Configure DNS. a. When the Domain Name Service screen appears, perform these tasks:. In the Host Name field, verify that WHITE-SRV1 is listed.. In the Domain field, enter acme.com.. Leave the Name Server fields empty.. Select Next. b. When the Warning screen appears, perform these tasks:

47 111 Netware 6 Upgrade and Migration CHAPTER 2. Read the warning indicating that because you have not configured Domain Name Service, you will obtain limited functionality from products that require this service.. Select OK to acknowledge the warning. c. When the Login to NDS screen appears, perform these tasks:. Select Browse.. When the Browse Users dialog box appears, navigate to and select the admin User object, and then select OK. d. When the Login to NDS screen reappears. In the Name (Full NDS Context) field, verify that the full distinguished name of the admin User object is listed.. In the Password field, enter acme.. Select OK. e. When the Summary screen appears, review the information on the screen, and then select Next. 13. Configure edirectory (Conditional). Note: This screen will probably not appear, because edirectory already exists on the source server. 14. License the NetWare 6 Server. a. When the Licenses screen appears, perform one of the following tasks:. Insert the NetWare 6 Cryptography/License disk into the floppy drive. (Be sure to use a unique license disk.) Select the appropriate server license file. Make sure you actually browse to and select the server license file, instead of just listing the drive letter (a common mistake). If you click the filename, you ll notice that the type of license appears in the Description section.. If you are using a demo version of the NetWare 6 Operating System CD (that is, a version that does not have an associated license disk), use the license file in the NETWARE6/LICENSE/DEMO directory on the CD. If you can t locate a license file, mark the Install without Licenses check box. Unfortunately, you may experience problems with features like NDPS, which use multiple connections. b. Click Next.

48 112 CHAPTER 2 Netware 6 Upgrade and Migration 15. Install Additional Network Products. When the Components screen appears, select Clear All, and then select Next. 16. Install Novell Certificate Server. a. When the Novell Certificate Server 2.21 Objects screen appears, review the information on the screen, then select Next. b. When the LDAP Configuration screen appears, select Allow Clear Text Passwords, and then select Next. c. When the edirectory imanage Install Options screen appears, select Next. 17. Customize the upgrade and finish. a. When the Summary screen appears, review the list of NetWare 6 products to be installed, and then select Finish to complete the upgrade process. b. The Installation program then performs the main file copy and displays the server console screen. (This step may take a while.) c. When the copying is complete, the Installation Complete window appears. Follow these steps:. Remove any CDs or floppy disks from your computer drives.. Select Yes to reboot the computer. Phase IV: Postupgrade Tasks Perform the following steps at the WHITE-SRV1 server console: 1. To ensure that all your trustees are restored, manually run the backlink process at WHITE-SRV1 server prompt: SET DSTRACE=ON SET DSTRACE=+BLINK SET DSTRACE=*B 2. Switch to Directory Services screen and verify that backlink has completed. 3. Enter RESET SERVER. Wait while the WHITE-SRV1 server restarts.

49 113 Netware 6 Upgrade and Migration CHAPTER 2 Perform the following steps on your primary administrative workstation: 4. Log into the network as admin. 5. Insert the NetWare 6 License/Cryptography CD into the workstation s floppy disk drive. 6. Launch NetWare Administrator: a. Select Start, Run. b. When the Run dialog box appears, select Browse. c. When the Browse dialog box appears, browse to WHITE-SRV1\SYS:PUBLIC\WIN32. d. Select NWADMIN32, and then select Open. e. When the Run dialog box reappears, select OK. 7. Install user licenses on WHITE-SRV1. a. When the Welcome to NetWare Administrator window appears, select Close. b. Verify that the WHITE Organizational object is selected. c. In the main menu, select Tools, Novell Licensing Services, Add Licenses. d. When the Add a License Certificate dialog box appears, verify that License File is selected, then select OK. e. When the Select a License Certificate file dialog box appears, browse to your license disk. f. In the root of your (WHITE-SRV1) License/Cryptography disk, select the user license (.nlf), then select Open. For example, A:license-number.NLF. g. When the Add Certificates from an Envelope dialog box appears, select Add. h. When the License Installation Report dialog box appears, verify that the user licenses were successfully installed, then select Close.

50 114 CHAPTER 2 Netware 6 Upgrade and Migration Migrating to NetWare 6 Test Objectives Covered: 2. Upgrade or migrate to NetWare Troubleshoot your NetWare 6 migration. NetWare 6 Migration is the ultimate achievement in nerdiness. It s probably the most popular installation method for NetWare 6. After all, there are already millions of NetWare servers out there no one wants to start from scratch. With migration, existing CNEs can simply transfer NDS information and data files to the new NetWare 6 edirectory village. The beauty of this system is that you don t have to repopulate it. The NetWare 6 Migration uses an across-the-wire method for transferring edirectory information and data from one server to another across the LAN. It requires three machines, each with specific hardware/software requirements:. A source server running NetWare 4.11, 4.2, 5.0, 5.1, and/or 6.. A destination server running NetWare 5.0, 5.1, and/or 6.. A Windows 98 or Windows NT/2000 workstation running the appropriate Novell Client. The NetWare 6 Migration method is the safest upgrade/migration option because the source server also known as an escape pod remains intact. You can also use it to migrate all or selected information (which is particularly useful when dealing with sensitive data files). Furthermore, this multifaceted migration option allows you to consolidate multiple source servers to a single NetWare 6 machine. So, how does it work? Good question. All of this fancy across-the-wire footwork is made possible by the NetWare Migration Wizard. Here s a quick preview of the NetWare 6 migration steps we ll explore in this section: 1. Getting Started 2. Create a Migration Project 3. Volume and Configuration File Migration 4. edirectory Migration 5. Migration Cleanup

51 115 Netware 6 Upgrade and Migration CHAPTER 2 In step 1, you jump-start the migration process by preparing the source/target servers and installing the NetWare Migration Wizard. Then, in step 2, you can create your Migration Project. The Migration Project is a database wizard that stores your migration configuration settings. In steps 3 and 4, you will actually perform the across-the-wire migration using the data you configured in the Migration Project database. Finally, the migration ends with some simple housekeeping cleanup chores in step 5. Now, that wasn t so bad, was it? So, let s migrate our old, cranky NetWare 5.1 server into a NetWare 6 supermachine. Step 1: Getting Started NetWare 6 migration is serious business. As such, it requires some careful preparation and you ll need to accomplish some important premigration preparation tasks before you can get started (floppy diskette required). Here s a quick preview:. Source Server Preparation The NetWare 6 Migration process requires that you prepare both the source and destination servers in unique ways. In this first step, we will learn how to prepare the source server with ConsoleOne, name space, and DSREPAIR.. Destination Server Preparation Then, we will shift our focus to the destination server. This server must be installed into a temporary edirectory tree and prepared for all the exciting new information it is about to receive.. Verify the Migration Client Finally, you ll need to verify the Novell Client version running on your migration client. This can be accomplished in a number of ways. Let s explore step 1 in more detail. Ready, set, prepare! Source Server Preparation NetWare 6 Migration requires two types of preparation: Source and Destination. In the Source server preparation phase, you will perform a variety of server housekeeping tasks on the NetWare 4 or 5 server that hosts all your valuable files, volumes, and edirectory information.

52 116 CHAPTER 2 Netware 6 Upgrade and Migration Let s start with a closer look at the source-server preparation checklist:. Use ConsoleOne to verify that you have the Supervisor right to the source server s file system and to the source server itself.. Update the source server with the latest NetWare support pack. Updates are available at (Conditional) If you are migrating data from NetWare 4, make sure the source server s volumes are running long-name space support on all volumes to be copied. To add long-name space support to a NetWare 4.11 or NetWare 4.2 volume, enter the following at the server console: LOAD LONG ADD NAME SPACE LONG TO volume name.. Load DSREPAIR and run the following options:. Unattended Full Repair. Time Synchronization. Report Synchronization Status. Back up edirectory and all data. Destination Server Preparation 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 that data is 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:. Use ConsoleOne to verify that you have the Supervisor right to the destination server s file system and to the server itself.. Be sure you have created a temporary edirectory tree with a temporary edirectory tree name. The temporary name and temporary edirectory tree name must not be the same as the source server s name or edirectory tree name; otherwise, the destination server cannot assume the identity of the source server after the migration.

53 117 Netware 6 Upgrade and Migration CHAPTER 2. During installation, create volumes on the destination server that are the same size as, or larger than, volumes on the source server. Volume names on the destination server must be the same as the volume names on the source server.. If migrating from NetWare 4, install and configure IPX. IPX must be bound to the destination server for the migration to work. (You can remove IPX after completing the migration.) IP addresses for the source server are not migrated. Instead, you manually change them during migration.. Install the destination server with the NetWare operating system that you are migrating to, and make sure you ve installed the Pre-Migration installation type. In this case, you are probably migrating to NetWare 6.. Make sure the destination server s time is equal to or later than the source server s time. This prevents critical time synchronization errors during migration. Migration Wizard migrates compressed volumes. If you are migrating compressed volumes to uncompressed volumes, Migration Wizard decompresses the volumes during migration. The decompression process is CPU and time intensive, so allow enough time to complete the operation. Make sure you have room on the uncompressed volume to accommodate the source volumes after they are decompressed.... TIP Verify the Migration Client 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 workstation. If you are using a Windows 98 workstation, be sure it is 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:. Hold down the Alt key while double-clicking the Windows 98 Network Neighborhood icon. Select the Novell Client, and then click Properties.. Double-click the Network icon in the Windows 98 Control Panel. Select the Novell Client, and then click Properties.

54 118 CHAPTER 2 Netware 6 Upgrade and Migration. If you re running the Novell NetWare 6 Client, right-click the N icon near the right end of the Windows 98 toolbar, which is located at the bottom of your screen, by default. Select the Novell Client Properties option from the popup window that appears. 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 also known as creating and implementing the Migration Project. Step 2: Create a Migration Project During the first few steps of the NetWare 6 Migration process, you ll need to create and implement a Migration Project. The Migration Project is a database wizard that stores your migration configuration settings. First, we will create a Migration Project using the NetWare Migration Wizard. Download and install Migration Wizard from the NetWare 6 operating system CD or from the NetWare section of the Novell Software Downloads web site. You can also gain valuable migration knowledge at the NetWare 6 Migration Wizard documentation site (as shown in Figure 2.21). Then, run Migration Wizard on your migration workstation from the following default location Start, Programs, Novell, NetWare Migration Wizard, NetWare Migration Wizard. Next, read the Welcome screen, click OK, and select Create a New Project from the Novell NetWare Migration Wizard Startup window (as shown in Figure 2.22).

55 119 Netware 6 Upgrade and Migration CHAPTER 2 FIGURE 2.21 Using the NetWare 6 Migration Wizard documentation on the web. FIGURE 2.22 Creating a new project in the NetWare 6 Migration Wizard. After you have launched a new migration project, you must select the source-server type. You have a variety of choices (as shown in Figure 2.23) from NetWare 4 to Windows NT 4. Click OK when you are ready to continue. Next, name the project something descriptive (such as WHITE-SRV1 Migration in our example in Figure 2.24). The filename should follow Windows 98 and Windows NT/2000 long filename conventions. In other words, it can be up to 255 characters long and can include any character but these: \ : *? < > /. In addition, you will need to choose a place to save the project database. By default, Migration Wizard saves all projects to C:\PROGRAM FILES\NOVELL\NETWARE MIGRATION WIZARD (as shown in Figure 2.24). FIGURE 2.23 Selecting the source-server type in the NetWare 6 Migration Wizard.

56 120 CHAPTER 2 Netware 6 Upgrade and Migration FIGURE 2.24 Naming your project file in the NetWare 6 Migration Wizard. Now it s time to select your source and destination migration servers. First, navigate to the correct tree, and select your source server from the graphical window in Figure Then, select your destination server in the same way (as shown in Figure 2.26). In our example, the source server is WHITE- SRV1 and the destination server is WHITE-SRV2. FIGURE 2.25 Selecting a source server in the NetWare 6 Migration Wizard. FIGURE 2.26 Selecting a destination server in the NetWare 6 Migration Wizard. Finally, save your project and access the Project Window by selecting Create. All finished. That was easy. Now let s jump into action by implementing our new project starting with volumes and configuration files.

57 Step 3: Volume and Configuration File Migration 121 Netware 6 Upgrade and Migration CHAPTER 2 After you have created your NetWare 6 Migration Project, the Project Window magically appears. Check it out in Figure The Project Window is a checklist (with associated buttons) for the four main tasks of NetWare 6 Migration:. Copy Volumes Copy volumes from the source server to the destination server. You can copy a volume as many times as needed.. Edit Configuration Files Compare the configuration files between the source and destination servers. You can edit the destination configuration files.. Begin NDS Migration After you complete the tasks above, migrate NDS file from the source server to the destination server. The source server will be brought down and the destination server restarted.. Finish NDS Migration Upgrade the Schema, fix volume objects, and restore trustees to the destination server after it has restarted. FIGURE 2.27 Viewing the migration task list in the NetWare 6 Migration Wizard. Let s continue our migration journey with the first two tasks: copying volumes and editing configuration files. Copying Volumes During NetWare 6 Migration First, in the Migration Project Window, you will 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

58 122 CHAPTER 2 Netware 6 Upgrade and Migration server. Once the migration is complete, the Wizard restores the trustee rights.... TIP When you are copying volumes during migration, you don t need to copy all volumes at the same time. The Migration Wizard allows you to select volumes to copy now and then you can copy other volumes later by reopening the project file. Remember that open files are not migrated. To start the volume copying process, simply choose each volume name from the list provided and then select Yes or No (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 will 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):

59 123 Netware 6 Upgrade and Migration CHAPTER 2. Don t copy over existing files.. Copy the source file if it is newer.. Always copy the source file. 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 may 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 have performed all of 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.