FILE NAME: 2XUPGRDE.DOC DATE: 7 June 1993 PROGRAM: 2XUPGRDE.NLM v1.10 NETWIRE: NOVLIB Library 6, file 2XTO3X.EXE ========================================================================== Chapter 5 Choose Migration or In-Place Upgrade Options for Upgrading Your Existing File Server ----------------------------------------------- To upgrade an existing NetWare v2.1x or v3.x server, use either the NetWare Migration utility or the NetWare In-Place Upgrade NLM. This section provides you with information to help you decide which utility is best for you. Table 5-1, "NetWare Upgrade Options," below gives you a brief explanation of upgrade options and the advantages of one option over another. The NetWare Migration utility may be used using one of two methods: "Across-the-Wire Migration" and "Same-Server Migration." Table 5-1 lists both methods. For a complete discussion of the NetWare Migration utility, see "What a Migration Does". For a complete discussion of the NetWare In-Place Upgrade NLM, see "What an In-Place Upgrade Does". Table 5-1 NetWare Upgrade Options ----------------------------------------------------------------------- Upgrade Options Available Advantages Disadvantages ----------------------------------------------------------------------- NetWare v2.x Across-the-Wire to No risk of data Need a v3.11 to v3.11 an installed v3.11 loss. server installed. server Can migrate many servers to one server. Can choose what data you want to migrate. Can direct data to specific volume or directory. -------------------------------------------------------- Same-Server Can choose what Some risk of data migration data you want to lost. migrate. Need a workstation (or tape backup) with enough disk space for data files. -------------------------------------------------------- In-Place Upgrade Just need one Cannot upgrade from v2.1x or v2.2 v2.1x server. from v2.0a. to v3.11 Need an 80386 or higher processor. If upgrade fails, you may have to restore your v2.1x data from backup. ----------------------------------------------------------------------- NetWare v3.x Across-the-Wire No risk of data Need a v3.11 to v3.11 migration to an loss. server installed. installed v3.11 server Can migrate many servers to one server. Can choose what data you want to migrate. Can direct data to specific volume or directory. -------------------------------------------------------- Same-Server Can choose what Some risk of data migration data you want to loss. migrate. Need a workstation (or tape backup) with enough disk space for data files. ----------------------------------------------------------------------- NetWare v3.x In-Place Upgrade Just need one Cannot upgrade to v3.11 from v3.x to v3.11 v3.x server from v3.0. --no additional hardware needed. If upgrade fails, may have to restore original data from backup. ----------------------------------------------------------------------- LAN Server or Across-the-Wire No risk of data Additional PCLP to migration procedures loss. hardware needed. NetWare v3.11 ----------------------------------------------------------------------- LAN Server or Same-Server No additional Some risk of data PCLP to migration procedures hardware needed. loss. NetWare v3.11 Need a workstation (or tape backup) with enough disk space for data files. ----------------------------------------------------------------------- What a Migration Does --------------------- (See either MIGRAT.EXE or MIGRAT.ZIP also on NetWire in NOVLIB Library 6.) What an In-Place Upgrade Does ----------------------------- An in-place upgrade allows you to upgrade a NetWare 2.1x server to v3.11 using SERVER.EXE with the 2XUPGRDE.NLM. Upgrading a NetWare v2.1x or v2.2 server includes two parts: 1. The file system is upgraded. 2. The new operating system is installed. Upgrading a NetWare v2.1x file system has four phases: 1. The file system is analyzed/inventoried. 2. The disks are analyzed. 3. The disks are modified. 4. A NetWare v3.11 bindery is created to replace the v2.1x bindery. Figure 5-3 illustrates the four phases. Figure 5-3 Phases in the Upgrade v2.1x v3.11 +------------------\-----------------\---------------------\------------+ | System Analysis > Disk Analysis > Disk Modification > Bindery | +------------------/-----------------/---------------------/------------+ Phase #1 Phase #2 Phase #3 Phase #4 Following is a discussion of what happens during each phase of the upgrade. When you run the upgrade, status messages refer to each of the actions discussed here. v2.1x +------------------\ | System Analysis > +------------------/ Phase #1 Phase 1. The NetWare v2.1x file system is analyzed. o Each disk is inventoried. o The system displays what volumes are on each disk. o This phase approximates the memory needed to successfully complete an upgrade. \-----------------\ > Disk Analysis > /-----------------/ Phase #2 Phase 2. Each NetWare v2.1x disk is analyzed. o The locations of the Hot Fix area, the system and volume areas, the Directory Entry Tables (DETs) and the File Allocation Tables (FATs) are determined. A layout of the disk for v3.11 is created from this information. o A list of disk blocks that must be moved is created. For example, if a block on VOL1: is on the disk in a location that is now assigned to VOL0:, it must be moved to a location that was assigned to VOL1: when the disk layout for v3.11 was created. o The DETs and FATs for each volume are translated. o Directory and file attributes are upgraded automatically. Macintosh folders and files are also upgraded if you are running NetWare for Macintosh. The Macintosh name space module should also be loaded (MAC.NAM). o This phase ensures the system has enough memory and free disk space to complete the upgrade. If the v2.1x disks do not have enough space for the upgrade to occur, a warning appears and the upgrade stops. (You must create more room on the disk, and then restart the upgrade.) \---------------------\ > Disk Modification > /---------------------/ Phase #3 Phase 3. Each NetWare v2.1x disk is modified. o The partition table on track 0 is updated and the v3.11 system tables are written to the system area. The DETs and FATs for each of the v3.11 volumes are duplicated. o Blocks are moved to their new locations on the disk. The v2.1x system is not functional after this phase begins. If a power failure or similar event occurs during this phase, you must restore your v2.1x system from your backup. v3.11 \------------+ > Bindery | /------------+ Phase #4 Phase 4. The NetWare v2.1x bindery is upgraded to v3.11. o Most v2.1x bindery information is upgraded to v3.11. Other information that is upgraded includes account restrictions and print queues. o NetWare v2.1x passwords are not retained in the v3.11 bindery. If you chose to assign new passwords to users, those are created and put into a file called NEW.PWD (in the SYS: SYSTEM directory). o VAPs do not get upgraded. They are unique to NetWare v2.x and do not exist in NetWare v3.x. Third-party VAP functionality is lost during this upgrade. After you upgrade to v3.11, delete VAP files. o Core printing services are not upgraded. After you finish upgrading to v3.11, delete print services and re-create them. o Volume and disk restrictions for users are not upgraded because of differences between the v2.1x and v3.x file systems. In v2.1x the restrictions were server-wide, whereas in v3.x the restrictions are only per volume. ========================================================================== Chapter 7 Upgrade Using In-Place Upgrade Overview -------- This chapter covers the procedures for upgrading an existing NetWare server using the In-Place Upgrade NLM. Use the In-Place Upgrade NLM for upgrading from an existing NetWare v2.1x or v2.2 to a v3.11 or v4.0 server. NetWare v2.1x or v2.2 Upgrade ============================= NOTE: References in this section to NetWare v2.1x include NetWare v2.2. A NetWare v2.1x server must have an 80386 or higher microprocessor to be upgraded to a v3.11 server. If your NetWare 2.1x server uses an 80286 microprocessor, see Chapter 6, "Upgrade Using Migration". NOTE: NetWare v2.0 and v2.0a are not supported by the In-Place Upgrade NLM. Necessary Resources ------------------- o A working copy of the NetWare system diskettes. o A NetWare server running versions 2.10, 2.11, 2.12, 2.15 (revisions a, b, and c), or 2.2. o A computer with an 80386 or higher microprocessor with a minimum of 4 MB of RAM. NetWare v3.x does not run on an 80286 microprocessor. Servers with large disks and a large number of directories may need more memory to complete the upgrade than they would normally need to run the server after the upgrade. o A backup device, such as a tape drive or a DOS hard drive. o Enough disk space to accommodate the v3.11 file system. Each volume should have at least 10% free disk space to accommodate the enlarged directory and file allocation tables. To store the v3.11 operating system files, we recommend you reserve 20-30 MB on volume SYS:. We also recommend that you create at least a 5MB DOS partition on the disk containing volume SYS:. Ensure that no disk has more than eight volumes on it. o The NetWare System_1 diskette which contains the 2XUPGRDE.NLM. o Sufficient time to upgrade your server. This depends on the following conditions: o The number of hard disks, not including mirrored disks o The amount of disk space in use If you have several disks, and a lot of disk space in use, this upgrade could take several hours. See the "Memory and Timing Case Study" in the README file. o (Optional) NetWare for Macintosh (to support Macintosh files on your network). Prerequisites ------------- o If you are running NetWare v2.1x on an 80286 microprocessor, upgrade your computer to an 80386 or higher microprocessor. o Back up your v2.1x system twice to ensure that you have a good backup. A backup is essential if you must restore your v2.1x system. o Make sure that all users are logged out and that all files (except bindery files) are closed during the upgrade. o Make sure all print servers are logged out. o You may need updated disk and LAN drivers to run v3.11. If you have third-party drivers, check with the manufacturer before you upgrade to see if you have compatible versions. WARNING: If you are using the IDE.DSK disk driver, you cannot add a DOS partition to an upgraded v3.11 disk. Claiming a DOS partition with FDISK on an upgraded IDE disk causes the IDE.DSK driver to get its parameters for heads, sectors, and cylinders from the CMOS tables instead of from the disk drive. The different parameters cause the DOS and NetWare partitions to overlap, resulting in data loss or data corruption. The NetWare partition will also be read from and written to erroneously with the wrong drive parameters. This problem occurs since the NetWare 2.1x IDE disk driver did not conform to the same specifications as DOS. The IDE driver is designed to check for the existence of a DOS partition. If a DOS partition exists, then the driver uses the drive parameters from the CMOS tables so that they will match what DOS is using. Otherwise, the driver will use the drive parameters from the NetWare 2.1x partition on the IDE disk drive. Boot NetWare v3.11 ------------------ Procedure --------- IMPORTANT: Keep a record of your hardware configuration information to be used at a later stage of the upgrade, as well as for future reference. NOTE: When instructed to insert a particular diskette, the diskette may be different depending upon which version of NetWare you are using, (ie: 3.11, 4.0). 1. At the NetWare v2.1x server system console prompt (:), type CONFIG 2. Copy the following information from the server screen onto the NetWare v3.11 Server Worksheet provided at the back of this manual. o Server name o LAN configuration information (including the network address) o Disk channel configuration information 3. From a workstation, run BINDFIX. NOTE: You must have rights to the SYS:SYSTEM directory to run BINDFIX. BINDFIX deletes mail subdirectories and trustee rights of users who no longer exist on the network and fixes the incorrect records in the bindery. To delete mail subdirectories and trustee rights, answer "Y" to the questions presented during BINDFIX. SUGGESTION: You may want to copy the NET$BIND.OLD and NET$BVAL.OLD files to diskette to recover the bindery later if needed. For more information on "BINDFIX", see Utilities Reference. 4. Down the NetWare v2.1x server. At the system console prompt (:), type DOWN IMPORTANT: Do not down the server simply by turning its power switch to OFF. This creates errors when upgrading to a NetWare v3.x file system. After the server responds that it is down, wait two to three minutes to be sure that all transactions to system files are complete before turning the power off. 5. Run VREPAIR. From the downed server, run the v2.1x VREPAIR utility on each volume. See the v2.1x VREPAIR documentation for further instructions. 6. Insert the bootable INSTALL diskette into drive A:. 7. Turn the server off and then on again. The computer now boots with DR DOS 6.0. NOTE: If you are creating a DOS partition on the hard drive, record the information you will enter in 8 through 13 on the worksheet at the end of this manual. You will use this information again later. 8. With the System_1 diskette in drive A:, load the v3.11 operating system by typing SERVER You receive a message similar to the following: Loading... Novell NetWare v3.11 Processor speed: 193 (Type SPEED at the command prompt for an explanation of the speed rating) File server name: NOTE: Don't type "SPEED" at this prompt (unless you want to name the server "SPEED"). For an explanation of the speed rating (which is computer-specific), wait until after you name the server and give it an internal network number before you type SPEED at the console prompt. 9. Name the server by typing servername SUGGESTION: Use your NetWare v2.1x servername so that you do not have to change any login files, map statements, or batch files. 10. Assign an IPX internal network number to the server. This number does not exist on a NetWare v2.1x network. In versions v3.0, v3.1, v3.11, and v4.0, it is a logical network number that identifies the individual file server. This number must be different from other network numbers (for cabling systems) or internal network numbers (for NetWare v3.0, v3.1, v3.11, and v4.0 file servers). The internal network number for each server must be o Unique o Hexadecimal (base 16: using numbers 0 through 9 and letters A through F) o One to eight digits 11. At the cursor prompt, type the IPX internal network number and press . The v3.11 console prompt (:) appears. The remaining steps are executed from the console prompt. 12. Load the appropriate disk driver by typing LOAD A:disk_driver Replace disk_driver with one of the v3.11 drivers. Table 1-1 NetWare v3.11 disk drivers ----------------------------------------------------------------------- Computer Disk controller type NetWare v3.11 disk driver Architecture (*.DSK) ----------------------------------------------------------------------- Industry Standard AT, MFM, RLL, ARLL, ISADISK Architecture (ISA) ESDI ISADISK /b IDE ISADISK /b /l [lowercase "L"] IDE (You cannot add a DOS partition to an upgraded v3.11 IDE disk.) Novell disk DCB coprocessor board ----------------------------------------------------------------------- Microchannel ESDI PS2ESDI MFM PS2MFM IBM SCSI PS2SCSI ----------------------------------------------------------------------- Extended Industry AT class ISADISK Standard Architecture (EISA) EISA vendor See vendor proprietary Other devices may be supported. Contact the device manufacturer to find out if it has a v3.11 supported driver. ----------------------------------------------------------------------- To decide which disk drivers to load, look at the disk channel configuration information you recorded in Step 2. Load the equivalent v3.11 disk driver. Many more third-party disk drivers are available from the disk drive manufacturers. Third-party disk driver manufacturers include Adaptec ADIC Always Technology Bus Logic Data Technology Corp. DPT Future Domain Quantum UltraStor IMPORTANT: Load the disk drivers in the order of the controller boards. Load the driver for the internal controller first, the driver for the first disk controller board second, etc. If you do not follow the correct order, system messages about your hard disks will be incorrect. 13. Answer the disk driver configuration information prompts by entering the information you recorded in Step 2. In NetWare v2.x, the interrupt number was decimal. In NetWare v3.x, the interrupt number is hexadecimal. 14. (Optional) To test third-party LAN drivers for compatibility, load them by typing LOAD A: LAN_driver Replace LAN_driver with the third-party v3.11 LAN driver. Table 7-2 lists all LAN drivers supported by Novell, Inc. WARNING: Do not upgrade if LAN drivers are not compatible. Call the manufacturer to get an updated version of the driver. IMPORTANT: If you experience problems with third-party drivers, contact the manufacturer listed in the driver description that appears when you load the driver. Table 7-2 NetWare v3.11 LAN drivers ----------------------------------------------------------------------- Cabling System Network Board NetWare v3.11 LAN Driver (*.LAN) ----------------------------------------------------------------------- ARCnet RX-Net TRXNET RX-Net II RX-Net/2 ----------------------------------------------------------------------- Ethernet Etherlink II - ASSY 2227 3C503 (3C503) EtherLink/MC 3C523 EtherLink Plus - ASSY 2012 3C505 NE/2 NE2 NE/2-32 NE2-32 NE1000 - ASSY 950-054401 NE1000 NE1000 - ASSY 810-160-001 NE2000 - ASSY 810-149 NE2000 NE3200 NE3200 ----------------------------------------------------------------------- Token-Ring 16/4 Adapter TOKEN 16/4 Adapter /A PC Adapter II PC Adapter /A ----------------------------------------------------------------------- IBM PC Network PCN baseband PCN2 PCNA baseband PCN2 broadband PCN2/A broadband ----------------------------------------------------------------------- Many more third-party LAN drivers are available from the NIC card manufacturers. Third-party LAN driver manufacturers include 3COM Cabletron Hewlett-Packard IBM Intel Madge NCR Proteon Racal Datacom Standard Microsystems Thomas-Conrad Ungermann-Bass 15. (Optional) Answer the LAN driver configuration information prompts by entering the information you recorded in Step 2. If the LAN driver loads, it can communicate with the network board and is compatible with NetWare v3.11. If the LAN driver does not load, it is either incompatible with v3.11 or the configuration is wrong. The following message appears: Module xxx.LAN not loaded. Check the configuration and try again. If you're sure the configuration is correct, find out if you have the correct driver version. 16. (Optional) Unload the third-party LAN drivers to free the memory for the upgrade by typing UNLOAD LAN_driver 17. With the System_1 diskette in drive A:, load Macintosh name space support by typing LOAD A:MAC Loading the Macintosh name space module ensures that all volumes are mounted properly at the phase 4 bindery step. 18. Continue the upgrade by determining which upgrade option to use. See "Choose In-Place Upgrade Options". Choose In-Place Upgrade Options ------------------------------- Before doing an In-Place Upgrade, decide the following: o Run the upgrade interactively? o Run the upgrade as a batch process? The following sections discuss both options to help you make your decisions and then give you instructions for completing each task. Run the Upgrade Interactively? ------------------------------ When you run the upgrade interactively, you are prompted whether to continue from one phase of the upgrade to the next, whether to create space for a DOS partition, and whether to have the NLM create and assign new passwords. Status messages and error messages are displayed. If you are a first time installer, use the interactive method so you can follow each phase of the upgrade. Run the Upgrade as a Batch Process? ----------------------------------- When you run the upgrade as a batch process, only error and status messages are displayed. The upgrade automatically proceeds through the phases without requiring input from the user. Use the optional parameters described below to create space for a DOS partition and to assign random passwords to users. If no options are specified, the defaults are used. If you are an experienced installer and have run several upgrades, use the batch process method, especially if you are upgrading several servers. Run the In-Place Upgrade ------------------------ NOTE: The optional parameters can be entered whether the upgrade is run interactively or as a batch process. Procedure --------- 1. Insert the System_1 diskette into drive A:. 2. (Conditional) To run the upgrade interactively, type LOAD A:2XUPGRDE A warning screen appears. You are asked the following question: Do you have a recent backup of your server? y Skip to Step 4. 3. (Conditional) To run the upgrade as a batch process, type LOAD A:2XUPGRDE [optional parameters] Replace [optional parameters] with any of the following: Table 7-3 In-Place Upgrade optional parameters --------------------------------------------------------------------- Parameter Explanation --------------------------------------------------------------------- B or BATCH Runs the upgrade in batch mode. BATCH2 Runs the upgrade in batch mode, not pausing for non-critical errors. BINDERY Skips to phase 4 to upgrade the 2.1x bindery only. F or FAST Skips the memory and free disk space check. H, ? or Shows a list of parameters. HELP P0 Does not create space for a DOS partition. Px Creates space for a DOS partition on volume SYS: (x = partition size in megabytes). Size range: 0 to 32 MB. Default: 5 MB. R or R+ Assigns random passwords. R- Does not assign random passwords (default). --------------------------------------------------------------------- You can enter the parameters in any order. Parameters can be separated by either a slash (/), a minus sign (-), or a space. For example, to run the upgrade as a batch process, create a 5MB DOS partition, and assign random passwords, type LOAD A:2XUPGRDE /B /P5 /R+ When the "Final Status" screen appears (Figure 7-7), continue with Step 9. 4. To proceed with the upgrade, type "Y". WARNING: If the procedure runs correctly (that is, if there are no power failures or power surges, etc.), you do not need to restore your disk from the backup. However, if a failure occurs, you may need to restore your disk to its previous condition. Table 7-4 below explains the In-Place Upgrade phases. Table 7-4 In-Place Upgrade Phases --------------------------------------------------------------------- Phase Description --------------------------------------------------------------------- 1 System Analysis Inventories each disk and each volume. Also ensures that the system has enough memory to successfully complete the upgrade. 2 Disk Analysis Analyzes each disk. An image of the new NetWare v3.11 disk is built and stored into memory. This phase is non-destructive and does not damage the existing NetWare v2.1x or v2.2 file system. 3 Disk Modification Writes the new NetWare v3.11 file system to the disk, destroying the NetWare v2.1x or v2.2 file system. A hardware failure during this phase will result in the irrecoverable loss of data on the server. 4 Bindery Updates bindery objects, properties, and values such as user accounts and passwords. In NetWare v2.1x, these were included in two files in SYS:SYSTEM: NET$BIND.SYS (for objects and properties) NET$BVAL.SYS (for property data sets) Random user passwords are assigned if requested. --------------------------------------------------------------------- The DOS partition screen (Figure 7-1) appears. Figure 7-1 DOS partition screen ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»³ ³º In-Place Upgrade from NetWare v2.1x and v2.2 to NetWare v3.1x º³ ³ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ³ ³ ³ ³ >>>>> OPTIONAL DOS PARTITION <<<<< ³ ³ ³ ³This utility can create space for a DOS partition at the beginning of ³ ³the disk containing the SYS: volume. ³ ³ ³ ³NetWare is much easier to load from a hard disk than from floppy disks. ³ ³In addition, NetWare 4.0 requires a minimum of a 5 MB DOS partition. ³ ³ ³ ³If you do NOT want a DOS partition on this hard disk, enter 0. ³ ³If you do want a DOS partition, enter the number of megabytes. ³ ³ ³ ³Enter a number between 0 and 32: 5 ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ 5. At the prompt, enter the number of megabytes you want for the DOS partition and press . NOTE: The In-Place Upgrade can create the space (between 0 and 32 MB) for a DOS partition on the disk that contains volume SYS:. We recommend a DOS partition of at least 5 MB. Booting the server from a DOS partition is significantly faster than booting from a diskette. The "0" option is available for servers that will boot from a diskette rather than from a DOS partition. If there is not enough space on your disk to create a DOS partition, the upgrade stops and displays the following:. "This NetWare server has insufficient free hard disk space to complete the upgrade. The In-Place Upgrade process is now being aborted." NOTE: Reboot the v2.1x file server, and then restart the upgrade. Delete unnecessary files to free more space on the disk. After you create the DOS partition, screens similar to the following appear. Figure 7-2, "System Analysis screen", details the System Analysis phase where each disk is scanned and inventoried. Figure 7-2 System Analysis screen ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»³ ³º In-Place Upgrade from NetWare v2.1x and v2.2 to NetWare v3.1x º³ ³ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ³ ³ ³ ³ >>>>> PHASE #1: SYSTEM ANALYSIS <<<<< ³ ³ ³ ³Scanning all disks for NetWare v2.1x and v2.2 volumes: ³ ³ ³ ³ Disk #0 (21000) (CDC WrenII/Embedded SCSI) ³ ³ Volume SYS: ³ ³ Volume VOL1: ³ ³ ³ ³This server has 12.7 MB of memory. ³ ³This upgrade will require approximately 10.2 MB of server memory. ³ ³ ³ ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Figure 7-3, "Disk Analysis screen 1", details the first portion of the Disk Analysis phase. This screen only appears if multiple disks are being upgraded. These extra phases are run to determine how much server memory and free disk space is required per volume to successfully complete the upgrade. Figure 7-3 Disk Analysis screen 1 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»³ ³º In-Place Upgrade from NetWare v2.1x and v2.2 to NetWare v3.1x º³ ³ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ³ ³ ³ ³ >>>>> PHASE #2: DISK ANALYSIS <<<<< ³ ³ ³ ³The system is now being analyzed to ensure that it has enough memory ³ ³and free disk space to successfully complete the upgrade process. High ³ ³capacity disks and disks with lots of directories may require more ³ ³server memory to upgrade. ³ ³ ³ ³Analyzing Disk #0 ³ ³Creating list of disk blocks to be moved...COMPLETE ³ ³Creating list of Hot Fix Redirection Area blocks to be moved...COMPLETE ³ ³Translating the Directory Entry Table (DET) for volume SYS:...COMPLETE ³ ³Translating the File Allocation Table (FAT) for volume SYS:...COMPLETE ³ ³Translating the Directory Entry Table (DET) for volume VOL1:...COMPLETE ³ ³Translating the File Allocation Table (FAT) for volume VOL1:...COMPLETE ³ ³Creating the Volume Segment Table...COMPLETE ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Servers with only one hard disk proceed directly to the second part of the Disk Analysis phase. See Figure 7-4. The calculations made during the first part of the Disk Analysis phase are discarded to conserve server memory. As shown in Figure 7-4, "Disk Analysis screen 2", the Disk Analysis phase analyzes each disk. An image of the new NetWare v3.11 disk is built and stored in memory. This phase is nondestructive and will not damage the existing NetWare v2.1x file system. Figure 7-4 Disk Analysis screen 2 ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»³ ³º In-Place Upgrade from NetWare v2.1x and v2.2 to NetWare v3.1x º³ ³ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ³ ³ ³ ³ >>>>> PHASE #2: DISK ANALYSIS <<<<< ³ ³ ³ ³Analyzing Disk #0 ³ ³Creating list of disk blocks to be moved . . . COMPLETE ³ ³Creating list of Hot Fix Redirection Area blocks to be moved...COMPLETE ³ ³Translating the Directory Entry Table (DET) for volume SYS:...COMPLETE ³ ³Translating the File Allocation Table (FAT) for volume SYS:...COMPLETE ³ ³Translating the Directory Entry Table (DET) for volume VOL1:...COMPLETE ³ ³Translating the File Allocation Table (FAT) for volume VOL1:...COMPLETE ³ ³Creating the Volume Segment Table...COMPLETE ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ Figure 7-5, "Disk Modification screen", details the Disk Modification phase. In this phase, the v2.1x file system is overwritten by the v3.11 file system. The Disk Modification phase is the only destructive phase of the upgrade. This phase must be completed before NetWare v3.11 can use the disk. Figure 7-5 Disk Modification screen ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»³ ³º In-Place Upgrade from NetWare v2.1x and v2.2 to NetWare v3.1x º³ ³ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ³ ³ ³ ³ >>>>> PHASE #3: DISK MODIFICATION <<<<< ³ ³ ³ ³During the next phase of the In-Place Upgrade, the disks are modified. ³ ³The v2.1x or v2.2 file system is overwritten by the v3.1x file system. ³ ³After you press 'Y', you cannot reconstruct the v2.1x or v2.2 file ³ ³system. ³ ³ ³ ³Proceed with the Disk Modification Phase? y ³ ³ ³ ³Modifying Disk #0 ³ ³Moving disk blocks to their new locations. Percent Moved: 100% ³ ³Mirroring each volume's DET and FAT tables . . . COMPLETE ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ 6. At the Disk Modification screen, type "Y" to continue with the upgrade or type "N" to quit. NOTE: If you have multiple disks, the Disk Analysis and Disk Modification process repeats itself. After all disks have been upgraded, volume SYS: is mounted and the bindery is upgraded. The v2.1x bindery is merged into the newly created v3.11 bindery. The Bindery phase updates bindery objects, properties, and values such as user accounts and passwords. Figure 7-6 Bindery screen ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»³ ³º In-Place Upgrade from NetWare v2.1x and v2.2 to NetWare v3.1x º³ ³ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ³ ³ ³ ³ >>>>> PHASE #4: BINDERY <<<<< ³ ³ ³ ³Mounting volume SYS ³ ³Initializing Transaction Tracking System ³ ³ ³ ³The In-Place Upgrade does not transfer user passwords to the v3.1x ³ ³bindery. You can choose to either leave users without passwords, or to ³ ³assign a random password to each user. The SUPERVISOR will not be given³ ³a random password. Random passwords are recorded in the file NEW.PWD in³ ³the SYS:SYSTEM directory. ³ ³ ³ ³Assign random passwords to users? y ³ ³ ³ ³Upgrading the bindery information . . . COMPLETE ³ ³ ³ ³Dismounting volume SYS ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ 7. (Conditional) In the process of assigning passwords, if you did not use the [R+] or [R-] or [B] parameters when you started the upgrade, you are prompted to assign random passwords. See Step 8 for password options. 8. Choose one of the following password options: --------------------------------------------------------------------- Password Option Description --------------------------------------------------------------------- Y (Yes) Assign random passwords. A random password for each user who originally had a password is created by the utility and stored in a file called NEW.PWD. User SUPERVISOR is not assigned a password. Only the network supervisor has access to this file. Users cannot log in until the supervisor gives them their password from this list. N (No) Assign no passwords. Users are not prompted for a password when they first log in. However, after they have logged in once, and if their accounts are set to require passwords, they are prompted to type a new password. --------------------------------------------------------------------- The Final Status screen displays how your disks and volumes were affected by the upgrade. See Figure 7-7, "Final Status screen", for an example. Figure 7-7 Final Status screen ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»³ ³º In-Place Upgrade from NetWare v2.1x and v2.2 to NetWare v3.1x º³ ³ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ³ ³ ³ ³ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿³ ³³ *** The In-Place Upgrade to the v3.1x File System is now complete ***³³ ³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ ³³ DISKS VOLUMES ³ STATUS MESSAGES ³³ ³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ ³³ Disk 0 SYS: ³ Disk successfully upgraded. ³³ ³³ VOL1: ³ ³³ ³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ ³³ Optional DOS Partition Size: 5 MB ³³ ³ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´³ ³³ Random Passwords Assigned? YES (stored in SYS:SYSTEM\NEW.PWD) ³³ ³ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ³ ³ ³ ³ ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ The NetWare v2.1x file system has been upgraded to a v3.11 file system. 9. Press any key to receive further instructions and then return to the console prompt (:). Mount Volumes ------------- Procedure --------- 1. Mount volume SYS: and other volumes by typing MOUNT ALL 2. Temporarily prevent users from logging in to the server by typing DISABLE LOGIN This prevents users from logging in as SUPERVISOR. To allow users to log in to the server when the upgrade is completed, type ENABLE LOGIN Load LAN Drivers ---------------- Procedure --------- 1. Insert the System_2 diskette in drive A:. 2. Load the appropriate LAN driver(s) by typing LOAD A:LAN_driver See Table 7-2 for a list of Novell LAN drivers. The default frame type for NetWare 4.0 is Ethernet 802.2. To user the Ethernet 802.3 frame type, used by default in NetWare v3.11 and earlier, add "frame=Ethernet_802.3" when loading the LAN driver. For example, type LOAD A:NE2000 frame=Ethernet_802.3 3. Bind LAN drivers to the server's registered protocol. For example, to bind IPX to the NE2000 LAN driver, type BIND IPX TO NE2000 Enter the network number for your cabling system. To bind the Ethernet 802.3 frame type to the LAN_driver, add "frame=Ethernet_802.3" when binding the protocol. For example, type BIND IPX to NE2000 frame=Ethernet_802.3 Copy SYSTEM and PUBLIC Files ---------------------------- Procedure --------- 1. Inser the System_1 diskette in drive A:. 2. Load INSTALL.NLM by typing LOAD A:INSTALL 3. Choose "System Options" and press . 4. From the "Available System Options" menu, choose "Copy System and Public Files" and press . 5. Insert diskettes as prompted. Create a STARTUP.NCF File ------------------------- A STARTUP.NCF file contains commands to load the disk drivers and name space support for your file server. This file is executed after SERVER.EXE and is stored on the disk you boot from (hard disk or diskette). Once this file loads the disk drivers and name space support, and mounts volume SYS:, it turns control over to AUTOEXEC.NCF to complete the boot process. Procedure --------- 1. Insert the writable System_1 diskette into drive A:. 2. Select "Create STARTUP.NCF File" from the "Available System Options" menu. 3. Enter the proper drive letter on the "Path For STARTUP.NCF File" screen. Use to make sure the drive is set to o C: to boot from hard disk. o A: to boot from drive A:. (This file can be copied to drive C: later.) 4. Press . A screen similar to the following appears: Figure 7-8 A sample STARTUP.NCF file ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³LOAD ISADISK PORT=1F0 INT=E ³ ³LOAD DCB PORT=340 INT=B ³ ³LOAD DCB PORT=348 INT=C ³ ³LOAD MAC ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ The operating system reads the information you previously entered for disk drivers and name space support. 5. From the following table, determine your system configuration and decide which additional commands you would like added to the STARTUP.NCF file. --------------------------------------------------------------------- To Add these or other commands --------------------------------------------------------------------- Load name spaces LOAD MAC.NAM for Macintosh, LOAD OS2.NAM OS/2, UNIX, or LOAD NFS.NAM FTAM LOAD FTAM.NAM (These commands must precede the command to mount the volume that stores the files using the name space.) Set server (You can add the following eight commands to the parameters STARTUP.NCF file only. You can add other SET commands to the STARTUP.NCF and to the AUTOEXEC.NCF file.) SET Maximum Physical Receive Packet Size SET Cache Buffer Size SET Reserved Buffers Below 16 Meg SET Maximum Subdirectory Tree Depth SET Concurrent Remirror Requests SET Auto TTS Backout Flag SET Minimum Packet Receive Buffers (For more on these and other SET parameters, see "SET" in Utilities Reference, or type "SET" at the server console.) Pause after each PAUSE command --------------------------------------------------------------------- 6. Type one command per line. 7. Press to save the file. Create an AUTOEXEC.NCF File --------------------------- An AUTOEXEC.NCF file contains commands to complete the boot process after SERVER.EXE and STARTUP.NCF executes. Because AUTOEXEC.NCF is saved in and runs from SYS:SYSTEM, place most boot commands (except the disk driver and name space support commands) in AUTOEXEC.NCF. Commands you can use in AUTOEXEC.NCF do the following: o Name the file server. o Assign the internal network number for the file server. o Load LAN drivers for the file server and assign the network number. o Bind LAN drivers to the file server's registered protocol. o Load other modules you want loaded when the file server boots. (See "LOAD" in System Administration.) o Execute other console commands (such as TRACK ON or VOLUMES) during the boot process. o Set other parameters for the file server. (See "SET" in System Administration.) o Mount volumes. Procedure --------- 1. From the "Available System Options" menu, select "Create AUTOEXEC.NCF File". The operating system gathers information you have previously entered at the console prompt for this file. A screen similar to the following appears, showing the commands that are automatically placed in AUTOEXEC.NCF. Figure 7-9 A sample AUTOEXEC.NCF file ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³file server name SPEEDY ³ ³ipx internal net 1993ABCD ³ ³LOAD NE1000 port=300 int=3 ³ ³bind IPX to NE1000 net=DEADBEAF ³ ³mount all ³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÙ NOTE: When using the 802.3 frame type, rather than the 802.2 default, the screen shown above displays the frame type number. If you load multiple LAN drivers, your AUTOEXEC.NCF file is different. See "INSTALL" in System Administration. 2. (Optional) From the table below, decide which loadable modules to load with AUTOEXEC.NCF. --------------------------------------------------------------------- To Add these modules --------------------------------------------------------------------- Create disk partitions, create LOAD INSTALL volumes, format a hard disk, etc. Lock the file server console, view LOAD MONITOR network operation information. Load the print server on the file LOAD PSERVER finance_print server and establish print services. Correct volume problems or remove LOAD VREPAIR name space entries from File Allocation and Directory tables. --------------------------------------------------------------------- To delete or modify commands, backspace to erase the command. 3. (Optional) From your system configuration, determine additional loadable modules to include in AUTOEXEC.NCF. Additional module types are shown in the table below. --------------------------------------------------------------------- Module Type Module Name --------------------------------------------------------------------- Equipment UPS.NLM Remote Console REMOTE.NLM RSPX.NLM Remote Boot for token ring TOKENRPL.NLM Remote boot for IBM and Western ETHERRPL.NLM Digital on Ethernet Third-party loadable modules (See third-party documentation) --------------------------------------------------------------------- NOTE: If you use an uninterruptible power supply, see "UPS" in System Administration for troubleshooting tips. Some loadable modules need other loadable modules to function. If the prerequisite module is not loaded first, the operating system will look at your default drive and then at SYS:SYSTEM and automatically load the necessary module. 4. From the table below, decide if you want any of the following console commands to execute with the AUTOEXEC.NCF file. --------------------------------------------------------------------- To Add these console commands --------------------------------------------------------------------- Implement security SECURE CONSOLE measures Display the processor SPEED speed --------------------------------------------------------------------- 5. Decide from the table below, additional commands you would like added to AUTOEXEC.NCF. --------------------------------------------------------------------- To Add these or other commands --------------------------------------------------------------------- Mount Volumes. MOUNT VOL1 (or other volume name) MOUNT ALL Note: Volume SYS: is mounted automatically when its corresponding disk driver is loaded during the STARTUP.NCF file's execution. Bind protocols other BIND IP to... than IPX to the LAN drivers. Set server parameters. SET commands (see "SET" in Utilities Reference.) Pause after each PAUSE command. --------------------------------------------------------------------- 6. (Optional) Allow unencrypted passwords. Use the table below to help you decide whether to use unencrypted passwords on a network using encrypted passwords. --------------------------------------------------------------------- For Use --------------------------------------------------------------------- A new installation with one file Encrypted passwords. server on the network. Upgrading from NetWare 2.x Encrypted passwords temporarily. operating system. A netWare v3.11 file server Encrypted passwords permanently. running on the same network as NetWare v2.11 or earlier. A NetWare v3.11 file server Encrypted passwords. Use SET in running on the same network AUTOEXEC.NCF until utilities on as NetWare v2.11 or v2.15. other file servers are upgraded. Copy NetWare v3.11 utilities to all NetWare v2.12 or v2.15 file servers to allow all servers to use encrypted passwords. (See "Appendix A" of Utilities Reference.) --------------------------------------------------------------------- Type the following command at the console prompt to allow unencrypted passwords: SET ALLOW UNENCRYPTED PASSWORDS=ON For more information on AUTOEXEC.NCF files or on the commands listed above, see System Administration. See also "Boot Files" in Concepts. 7. Press to save the file. 8. Press twice to exit INSTALL. Format the DOS Partition ------------------------ Procedure --------- 1. At the console prompt (:), down the server by typing DOWN 2. Insert the bootable INSTALL diskette in drive A:. 3. Return to the DOS prompt by typing EXIT 4. From the downed server, create a DOS primary partition and make it the active partition by typing FDISK NOTE: The two utilities used to partition and format the DOS partition are found on the bootable INSTALL diskette. These DR DOS files, FDISK.COM and FORMAT.COM, also ship with NetWare v3.11. FDISK is a DOS utility that creates or deletes DOS partitions on your hard disk. It can also select which partition is active. The DOS partition will be placed on the first few cylinders of the hard disk. The server will reboot DOS as part of the FDISK process. 5. Format the new DOS partition. If you are using DR DOS, the format command is as follows: FORMAT C:/s/x The /s parameter makes the partition bootable. The /x parameter tells DR DOS that it is formatting a hard drive. NOTE: If you are using DR DOS to format your hard drive, use FORMAT.COM on the INSTALL diskette or a later version. If you are not using DR DOS, type the format command as follows: FORMAT C:/s 6. Reboot the server to make sure that DOS boots from the hard disk. Copy the New Boot Files to a Boot Directory ------------------------------------------- Procedure --------- 1. Create a boot directory. For example: MD C:\SERVER.311 The boot files are copied to this directory on drive C:. 2. Copy the newly created STARTUP.NCF file from the System_1 diskette to the boot directory by typing COPY A:\STARTUP.NCF C:\Boot_directory 3. Copy the v3.11 server boot files to the boot directory. Copy the following files to the newly-created boot directory on drive C: (or another directory on C: that you specify.) o SERVER.EXE (the NetWare operating system). o NUT.NLM (an interface utility needed for certain NetWare Loadable Modules). o NWSNUT.NLM (an interface utility needed for certain NetWare Loadable Modules). o Disk drivers (*.DSK). o Name space modules (*.NAM). o CLIB.NLM (C NLM Run-time Library). o Diagnostic NLMs (*.NLM). o INSTALL.NLM (the installation utility). o LAN drivers (*.LAN). o Message and help files. The upgrade is complete. 4. From the boot directory, load the server operating system by typing SERVER 5. Complete the steps under "What to Do After the Upgrade" below. What to Do After the Upgrade ---------------------------- Complete the following steps before allowing users to log in. Procedure --------- 1. Change SUPERVISOR password. Log in from a workstation as SUPERVISOR. Change the password using either SETPASS or SYSCON. 2. Change user passwords. If you chose to assign random passwords, print the NEW.PWD file and distribute the password information to each user. Users should change their passwords immediately, using either SETPASS or SYSCON. 3. Check applications to see if they run properly. Some DOS applications don't work when installed on volumes that have more than 32 MB of disk space. Some of these applications can be made to work by doing the following: o Restrict the application's directory on the destination server with DSPACE. o Make the directory path a fake root using the MAP command. 4. Check directory security. Check directory security if you used any of the following items for NetWare v2.1x security: o Maximum Rights Mask o Private attribute 5. Set any new directory and file attributes using FLAG or FILER. 6. Check directories for unnecessary NetWare files. NetWare v2.1x ------------- The following NetWare v2.1x files are not compatible with NetWare v3.11 and should be deleted. VAP files (*.VAP, *.HLD, *.VP?) LARCHIVE.EXE LRESTORE.EXE MACBACK.EXE NARCHIVE.EXE NRESTORE.EXE NET$BIND.SYS NET$BVAL.SYS NET$BIND.OLD NET$BVAL.OLD NET$ERR.SYS NET$OS.EXE NET$DOS.SYS NET$MSG.SYS NET$REC.DAT HIDEFILE.EXE and SHOWFILE.EXE still work but have not been included in NetWare v3.x. These files were copied into SYS:SYSTEM. You can either delete them (FLAG allows users to add and remove System and Hidden attributes from files) or leave them. NetWare v2.0a ------------- The following NetWare v2.0a files are not compatible with NetWare v3.11. They should be deleted. ENDSPOOL.EXE Q.EXE QUEUE.EXE SPOOL.EXE The utilities listed above are replaced by ENDCAP, PCONSOLE, and CAPTURE in NetWare v3.x. See Utilities Reference for more information. 7. Modify the system and user login scripts. Update as necessary any references to the server in the system and user login scripts if you changed the server name. Although user login scripts are upgraded, they are not modified and server names are not changed to match your new environment. Use SYSCON to modify the login scripts. With NetWare 2.x, you could give users drive mappings to directories in which they had not been granted rights. NetWare 3.x will not allow users to have drive mappings to directories in which they have not been assigned rights. If you have set up your login scripts so that users have drive mappings to directories in which they have no rights, these users will receive the following message when they log in: "Attempt to map drive to invalid path in MAP command." Complete one of the following: o Delete the drive mapping from the login script. o Delete the drive mapping from the system login script and insert the drive mapping in the user login scripts only when the user has been granted rights to the directory. o Create a group, grant the group the trustee assignment, assign the appropriate users to the group, and then use an IF. . . THEN command in the system login script before the drive mapping (IF member of "groupname", THEN map p:=volume:directory). 8. Create new boot diskettes for each workstation. All users on the NetWare v3.x file server need to boot with the new shell and IPX files before they log in. 8a. If the server was renamed, change the file server's name in the users' AUTOEXEC.BAT files to the new v3.11 file server name. 8b. If you have other NetWare v2.x file servers on your network, upgrade the workstation files for those users even if you aren't upgrading the file server. The new workstation files shipped with NetWare v3.11 are compatible with NetWare v2.x. All users on the internetwork should use the latest version of the workstation files to ensure that there are not conflicts. 9. Copy the NetWare v3.11 utilities to other file servers on the network. The NetWare v3.x public utilities will run on file servers running NetWare v2.x. Complete one of the following: o If you have file servers running v2.0a, v2.10, or v2.11, do not copy the NetWare 3.x public utilities to them. However, do copy the NetWare v3.x LOGIN.EXE file to the SYS:LOGIN and SYS:PUBLIC directories. o If you have NetWare v2.12 or v2.15 file servers on your network, replace the NetWare public utilities with the NetWare v3.x public utilities to allow the v2.12 and v2.15 file servers to work with encrypted passwords. To copy utilities, complete the following steps: 9a. Log in to the NetWare v2.x file server as SUPERVISOR. 9b. Flag the NetWare v2.x utilities Normal. In the SYS:LOGIN and SYS:PUBLIC directories, type FLAG *.* N 9c. Protect the system login script. In the SYS:PUBLIC directory, type FLAG NET$LOG.DAT SRO 9d. Map a drive to the SYS:PUBLIC directory on the NetWare v3.11 file server by typing MAP drive:=fileserver/SYS:PUBLIC Replace drive with a drive letter not currently being used and fileserver with the name of the NetWare v3.11 file server. 9e. Enter your username and password for the NetWare v3.11 file server. 9f. Copy the NetWare v3.11 PUBLIC files to the NetWare v2.x file server. For example, if drive Q is mapped to SYS:PUBLIC on the NetWare v3.11 server and drive F is mapped the SYS:PUBLIC on the NetWare v2.x file server, change to drive F and type NCOPY Q:*.* 9g. Flag the NetWare v3.11 utilities on the NetWare v2.x file server Shareable and Read Only. Type FLAG *.* SRO 9h. Repeat Steps 9e and 9f for the SYS:LOGIN directory. IMPORTANT: Login scripts on the NetWare v3.11 file server do not execute properly unless you copy the NetWare v3.11 login programs to all NetWare LOGIN directories on your internetwork. 9i. When you have copied the NetWare v3.11 utilities to all NetWare v2.1x file servers and you do not have any NetWare v2.0a file servers, you can change the setting for unencrypted passwords. At the console prompt of the NetWare v3.11 file server, type SET ALLOW UNENCRYPTED PASSWORDS=OFF If you still have NetWare v2.0a file servers on your internetwork, the setting at the NetWare v3.11 file server for unencrypted passwords must be ON. 10. If your v2.x server had mirrored disks, remirror them using INSTALL.NLM. 11. Update as necessary upgraded print queues using PCONSOLE. 12. Use NBACKUP to make a backup copy of all data on the NetWare v3.11 server. See Utilities Reference for NBACKUP instructions. 13. Check user restrictions and accounting charge rates to make sure your system is configured the way you want it. 14. (Optional) If your network includes workstations that use an operating system that supports long filenames, make sure you have loaded the name space module, then use the ADD NAME SPACE command to add name space to the volume. Type ADD NAME SPACE name-support TO VOLUME volume_name For example, if you have a volume named MAC for Macintosh files, type the following at the console prompt: ADD NAME SPACE MACINTOSH TO VOLUME MAC Use this command once for every volume that needs to store files with long names. To ensure name space support each time the file server is brought up, load the appropriate name space module in the STARTUP.NCF file. 15. (Optional) If you want to store Macintosh files and folders on a NetWare v3.11 server, install NetWare for Macintosh (a separate Novell product) on the v3.11 server. This product provides support for Macintosh workstations that connect to the v3.11 server. 16. Allow users to log in to the NetWare v3.11 file server. User can login if o The SYS: volume is mounted o The user exists in the bindery o The LAN driver is loaded and bound to a protocol o Login in enabled To ensure that login is enabled, type ENABLE LOGIN ========================================================================== ************************************************************************ DISCLAIMER Novell, Inc. makes no representations or warranties with respect to any NetWare software, and specifically disclaims any express or implied warranties of merchantability, title, or fitness for a particular purpose. Distribution of any NetWare software is forbidden without the express written consent of Novell, Inc. Further, Novell reserves the right to discontinue distribution of any NetWare software. Novell is not responsible for lost profits or revenue, loss of use of the software, loss of data, costs of re-creating lost data, the cost of any substitute equipment or program, or claims by any party other than you. Novell strongly recommends a backup be made before any software is installed. Technical support for this software may be provided at the discretion of Novell. ************************************************************************