#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'UpgradeUpgradeNovell, Inc.DisclaimerNovell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=5 ID="BP1"How to Use This ManualRENDERAS="SECT1"IntroductionUpgrade describes in detail the different ways you can upgrade your present network operating system to NetWare® 4.1.RENDERAS="SECT1"Contents OverviewRENDERAS="SECT2"Chapter 1: Upgrade OptionsThis chapter describes the four ways to upgrade to NetWare 4.1. It also gives recommendations on which upgrade method to use depending on your individual situation.RENDERAS="SECT2"Chapter 2: Upgrade Using the NetWare 4.1 Installation ProgramThis chapter explains how to upgrade from NetWare 3.1x or NetWare 4.0x to NetWare 4.1 using the NetWare 4.1 installation program.RENDERAS="SECT2"Chapter 3: Upgrade Using Across-the-Wire MigrationThis chapter explains how to upgrade existing NetWare 2, NetWare 3, and other network operating systems servers to NetWare 4.1 using the Across-the-Wire Migration method.RENDERAS="SECT2"Chapter 4: Upgrade Using Same-Server MigrationThis chapter gives instructions on how to upgrade servers to NetWare 4.1 using the Same-Server Migration method.PAGENUM=6 ID="BP2"RENDERAS="SECT2"Chapter 5: Upgrade Using In-Place UpgradeThis chapter gives instructions on how to upgrade a NetWare 2 server to NetWare 3 using the In-Place Upgrade method.RENDERAS="SECT2"Appendix A: Calculating RAM RequirementsThis appendix provides a detailed formula for calculating your NetWare 4.1 RAM requirements.RENDERAS="SECT2"Appendix B: NetWare 4 File and Directory AttributesThis chapter describes the new file and directory attributes unique to NetWare 4TM.RENDERAS="SECT2"Appendix C: Special Instructions for LAN ServerThis chapter gives information for upgrading from LAN Server to NetWare 4.1.RENDERAS="SECT1"Documentation ConventionsThis manual uses the following Novell® conventions.RENDERAS="SECT2"Asterisk ( * )An asterisk denotes a trademarked name belonging to a third-party company. Novell trademarks are denoted with specific trademark symbols (®, TM, etc.).An ownership listing of all (Novell and third-party) trademarks cited in a manual can be found either on the disclaimer page in the front or in a "Trademarks" section at the back of printed manuals. A trademarks list is also available in the DynaText* online documentation.PAGENUM=7 ID="BP3"RENDERAS="SECT2"CommandsBoldface characters indicate items that you type, such as commands and options. You can use any combination of uppercase and lowercase letters.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\A INSTALLRENDERAS="SECT2"Delimiter Bar ( | )In syntax examples, a delimiter bar separating two command options indicates that you can choose one of the options.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"-S | -RDo not type the bar.RENDERAS="SECT2"DOS CommandsDOS commands and command option letters are shown in uppercase letters. For example: FTPD.Because DOS is not case-sensitive, you can type DOS commands in uppercase or lowercase letters.RENDERAS="SECT2"DOS Filenames, Directory Names, and PathnamesDOS filenames, directory names, and pathnames are shown in uppercase letters. For example, AUTOEXEC.BAT.Because DOS is not case-sensitive, you can type these names in uppercase or lowercase letters.PAGENUM=8 ID="BP4"RENDERAS="SECT2"EllipsesEllipses in syntax examples indicate that parameters, options, or settings can be repeated.For example, in the commandFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN SERVER1/SUPERVISOR /option...you could replace option with any number of available options.RENDERAS="SECT2"EmphasisItalic type also indicates emphasized text. For example:Remember to load the driver before you install the application.RENDERAS="SECT2"IconsChecklists, which often contain prerequisites, are marked with the "Checklist" icon to the left of this text.Procedures to follow in order to accomplish a specified task are marked with the "Procedure" icon to the left of this text.Additional or "nonessential" but noteworthy information is marked with the "Note" icon to the left of this text.Vital information about system or software requirements, etc., that deserves particular attention is marked with the "Important" icon to the left of this text.Guidelines or tips about fine-tuning, optimizing, etc., which might be applicable to your site or situation but maybe not to all, are emphasized with the "Suggestion" icon to the left of this text.Warnings about potential danger to data, hardware, or person are emphasized with the "Warning" icon to the left of this text.PAGENUM=9 ID="BP5"RENDERAS="SECT2"Key NamesAngle brackets surround the name of a key. For example, MOREINFO="NONE"<Enter> corresponds to the MOREINFO="NONE"Enter key on your keyboard. MOREINFO="NONE"<Ctrl>+<c> means hold down the MOREINFO="NONE"Ctrl key and simultaneously type the letter MOREINFO="NONE"c (in lowercase, in this case).RENDERAS="SECT2"OptionsIn syntax examples, braces indicate that you are required to choose one of the enclosed options. For example, the following notation means that you must include a 0 or a 1 in the command:FORMAT="LINESPECIFIC"MOREINFO="NONE"{0, 1}RENDERAS="SECT2"Square BracketsIn syntax examples, boldface type enclosed in square brackets indicates command options that you can type as needed. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"FTP [ -D ] [ -F ]RENDERAS="SECT2"System ResponseMonospace type shows system-generated responses that appear on your workstation screen. For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"TNVT220>RENDERAS="SECT2"VariablesItalic type indicates variables---descriptive item names, such as command parameters---that you replace with appropriate values.For example, in the command:FORMAT="LINESPECIFIC"MOREINFO="NONE"FTP -F remote_hostyou type the name of a computer on your network in place of remote_host.PAGENUM=10 ID="BP6"RENDERAS="SECT2"UNIX CommandsUNIX® commands are shown in boldface letters. For example, MOREINFO="NONE"vi. Because UNIX is case-sensitive, these commands are usually lowercase. Type UNIX commands exactly as shown.RENDERAS="SECT2"UNIX Filenames, Directory Names, and PathnamesUNIX filenames, directory names, and pathnames are shown in italics. For example, /etc/hosts.Because UNIX is case-sensitive, these names usually are in lowercase letters. Type UNIX filenames exactly as shown.RENDERAS="SECT1"Supplemental DocumentationThe following publications provide supplemental information specifically related to upgrading to NetWare 4:MARK=BULLET"NetWare Migration Utilities Part 1: The In-Place Upgrade NLM." NetWare Application Notes, June 1993."NetWare Migration Utilities Part 2: The Across-the-Wire Migration Utility." NetWare Application Notes, September 1993.RENDERAS="SECT1"Online HelpMARK=BULLETContext-sensitive help. If you are using a NetWare menu utility and want more information about how to complete a task, press MOREINFO="NONE"<F1>.If you are unsure how to use a command, type the command name and add the /? option for help. For example, for help with the RIGHTS command, type "RIGHTS /?".Online MS Windows help. The Microsoft* (MS) Windows help viewer allows you to read NetWare help developed for the MS Windows environment. To access the NetWare help screens within MS Windows, press <MOREINFO="NONE"F1> or the "?" button.PAGENUM=11 ID="BP7"DynaText online documentation. The DynaText viewer allows you to read NetWare documentation from your DOS, MS Windows, Macintosh*, UNIX, or OS/2* workstation.All NetWare 4TM and 3.12 documentation except the Quick Access Guide are available on the NetWare Online Documentation CD-ROM.RENDERAS="SECT1"Additional Help ResourcesMARK=BULLETNovell Authorized Service CenterSM (NASC) locations. NASCSM facilities are local support providers authorized and supported by Novell. They provide both telephone and on-site assistance, and should be your first source for technical support.For the Novell Authorized Service Center nearest you, in the U.S. and Canada call 1-800-338-NASC.Hardware documentation. Many network problems occur because of malfunctioning hardware.If you can isolate a problem to a certain computer component or cable segment, check the manuals that came with the hardware involved.NetWare Management SystemTM (NMS) services. NMSTM services helps you manage the cabling system, computers, software, and other components of the network.For more information about using NMS on your network, contact your Novell Authorized ResellerCLM representative.Other Novell publications. NetWare Applications Notes and Research Reports cover technical aspects of NetWare based system design, implementation, and management.Applications Notes is a collection of technical articles published monthly. Research Reports is published as the research becomes available.To purchase subscriptions and back issues of these publications from within the United States or Canada, call the Novell Research Order Desk at 1-800-UPDATE1. From other locations, call 801-429-5380.Third-party books and periodicals. A number of books on NetWare, including books published by Novell PressTM publishing, are available at most bookstores.PAGENUM=12 ID="BP8"In addition, numerous networking periodicals give advice on configuring, managing, and troubleshooting your network.NetWireTM forum on the CompuServe bulletin board. A fairly inexpensive way to get up-to-date advice and patches is through NetWire on the CompuServe bulletin board.To open a CompuServe account, call one of the following numbers and ask for "Representative 200"MARK=BULLETIn the United States or Canada: 1-800-524-3388In the United Kingdom: 0800-289-378In Germany: 0130-37-32In other European countries: 44-272-255-111In locations other than the United States, Canada, or Europe, use the appropriate country code for the U.S. and call 614-457-0802. Ask for "Representative 200." This phrase identifies you as a Novell customer.Technical Support Database and NetWire forum on the Internet. The Novell FTP sites support access through FTP, Gopher, and World Wide Web (WWW) systems.  Over 9,000 documents exist on the WWW system for providing technical hints and information.To access the Novell Internet sites, log in as ANONYMOUS and use your E-mail address as your password.   Contact one of the following site addresses:MARK=BULLETIn the United States: ftp.novell.comIn Germany: ftp.novell.deIn the United Kingdom: ftp.salford.ac.ukIn Canada: novell.nrc.caSee public areas in these sites for possible listings of other sites addresses. PAGENUM=13 ID="BP9"FaxBack Service. Novell provides a FaxBack Service for obtaining additional product information to help with support needs.To access the Novell FaxBack Service, complete the following steps.MARK=BULLETWithin the continental United StatesTYPE="VERT"1. Dial 1-800-NETWARE (1-800-638-9273).2. Press #1 (the "Presale Product Information and Upgrade Information" option).3. Again press #1 (the "Receive Product Information via Fax" option).Outside the continental United StatesDial 1-801-429-2772. You are connected directly to the FaxBack Service.Follow the directions provided on the phone. You are prompted to enter a document number and then a fax number to send the document to.Network Support Encyclopedia Professional VolumeSM (NSE Pro) package. This encyclopedia gives customers access to regularly updated information on products and services---plus patches, fixes, and more---from Novell and other vendors.The NSE ProSM package is distributed on CD-ROM on a subscription basis. Updates are sent out several times each year. More information is available on NetWire or from your Novell Authorized Reseller.Troubleshooting hardware and software. Specialized hardware and software packages, such as the Novell LANalyzer® software, are available to help you isolate network problems.Customer service. You can contact your Novell Authorized Reseller for technical assistance.Most Novell Authorized Resellers have Certified NetWare EngineerSM representatives on their staffs ready to assist users with their networking problems.PAGENUM=14 ID="BP10"RENDERAS="SECT1"User CommentsWe are continually looking for ways to make our products and our documentation as easy to use as possible.You can help us by sharing your comments and suggestions about how our documentation could be made more useful to you and about inaccuracies or information gaps it might contain.Submit your comments either by filling out the "User Comments" form at the end of this document or by writing to us directly at the following address:TYPE="VERT"Novell, Inc.Technical Publications MS C-23-1122 East 1700 South Provo, UT 84606 USAWe appreciate your comments.LABEL="1"PAGENUM=1 ID="BP11"Upgrade OptionsRENDERAS="SECT1"IntroductionThis chapter describes the available options for upgrading to NetWare® 4.1.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM84267"Four Upgrade MethodsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM84267"2COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM55196"Choosing Which Upgrade Method to UseCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM55196"3RENDERAS="SECT1"OverviewThere are many options available for upgrading your network servers to NetWare 4.1. The options described in this chapter will help you decide which method is best for you.There are four ways to upgrade to NetWare 4.1:MARK=BULLETNetWare 4.1 installation programAcross-the-Wire MigrationSame-Server MigrationIn-Place UpgradeThe upgrade option you choose depends on the version of NetWare (or another network operating system) you are running and the hardware you have available.PAGENUM=2 ID="BP12"RENDERAS="SECT1"ID="FM84267"Four Upgrade MethodsThere are four ways to upgrade to NetWare 4.1.RENDERAS="SECT2"NetWare 4.1 Installation ProgramThe upgrade option in the NetWare 4.1 installation program (INSTALL.NLM) is a convenient way to upgrade a NetWare 3.1x or NetWare 4.0x server to NetWare 4.1.The NetWare 4.1 installation program is run on the NetWare 3.1x or NetWare 4.0x server that you want to upgrade to NetWare 4.1.RENDERAS="SECT2"Across-the-Wire MigrationAcross-the-Wire Migration uses the Migration utility to convert an existing NetWare 2.1x, NetWare 2.2, or NetWare 3.1x bindery server to a new NetWare 4.1 server.The Migration utility converts the bindery information on the NetWare 2 or NetWare 3TM server to NetWare Directory ServicesTM on a NetWare 4.1 server via a DOS client workstation.RENDERAS="SECT2"Same-Server MigrationSame-Server Migration uses the Migration utility to convert an existing NetWare 2, NetWare 3, or another network operating system server to NetWare 4.1.After you back up the NetWare 2, NetWare 3, or another network operating system server, the Migration utility converts the server's bindery information to NetWare Directory Services and installs NetWare 4.1.RENDERAS="SECT2"In-Place UpgradeThe In-Place Upgrade NetWare Loadable ModuleTM (2XUPGRDE.NLM) reformats a server's NetWare 2.1x or NetWare 2.2 partition, without losing any data, and transforms it into a NetWare 3.1x partition.From there, you use the NetWare 4.1 installation program to upgrade the server from NetWare 3.1x to NetWare 4.1.PAGENUM=3 ID="BP13"RENDERAS="SECT1"ID="FM55196"Choosing Which Upgrade Method to UseThe upgrade method you use depends on the version of NetWare you're running and the hardware you have available.RENDERAS="SECT2"Upgrading from NetWare 2 to NetWare 4.1When upgrading from NetWare 2.1x or 2.2 to NetWare 4.1, you can use the following upgrade methods:MARK=BULLETAcross-the-Wire MigrationSame-Server MigrationIn-Place UpgradeRENDERAS="SECT2"Upgrading from NetWare 3 to NetWare 4.1When upgrading from NetWare 3.1x to NetWare 4.1, you can use the following upgrade methods:MARK=BULLETNetWare 4.1 installation programAcross-the-Wire MigrationSame-Server MigrationRENDERAS="SECT2"Upgrading from NetWare 4.0x to NetWare 4.1When upgrading from NetWare 4.01 or 4.02 to NetWare 4.1, you can use the NetWare 4.1 installation program.Special care should be taken when running NetWare 4.01, 4.02, and 4.1 in the same Directory tree. For more information, see IDREF="FM47491"Chapter 2, "Upgrade Using the NetWare 4.1 Installation Program."PAGENUM=4 ID="BP14"RENDERAS="SECT2"Upgrading from Another Network Operating System to NetWare 4.1The following network operating systems can be upgraded to NetWare 4.1:MARK=BULLETIBM* PCLP 1.3 Extended ServicesIBM LAN Server* 1.0IBM LAN Server 1.1IBM LAN Server 1.2IBM LAN Server 1.3Microsoft* LAN Manager* 2.0When upgrading from any of these network operating systems, you can use the following upgrade methods:MARK=BULLETAcross-the-Wire MigrationSame-Server MigrationRENDERAS="SECT1"Where to Go from HereEach upgrade method described has its own chapter in this book. Once you've decided which upgrade method to use, go the specific chapter and proceed with the upgrade.LABEL="2"PAGENUM=5 ID="BP15"ID="FM47491"Upgrade Using the NetWare 4.1 Installation ProgramRENDERAS="SECT1"IntroductionThis chapter covers the procedures for upgrading an existing NetWare 3TM or NetWare 4TM server to NetWare® 4.1 using the NetWare 4.1 installation program.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM40785"Upgrading NetWare Directory ServicesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM40785"7COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM74815"Running the NetWare 4.1 Installation ProgramCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM74815"8COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM86177"What to Do After the UpgradeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM86177"14RENDERAS="SECT1"OverviewYou can use the NetWare 4.1 installation program upgrade option to ugrade fromMARK=BULLETNetWare 3 (specifically, NetWare 3.11 and NetWare 3.12) to NetWare 4.1.NetWare 4 (specifically, NetWare 4.01 and NetWare 4.02) to NetWare 4.1.PAGENUM=6 ID="BP16"RENDERAS="SECT2"How It WorksMARK=BULLETCopies new NetWare 4.1 files onto the NetWare 3.1x or 4.0x boot directory.This includes SYSTEM and PUBLIC files, SERVER.EXE, disk and LAN drivers, name space support modules, and other IDXID="w9536"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"
loadable modules.On NetWare 3.1x servers, the NetWare 4.1 installation program installs NetWare Directory ServicesTM and upgrades the bindery to a NetWare 4.1 IDXID="w9537"BOOK="_idx" COLLECTION="nw41" TIDREF="i445"
Directory Services database. All IDXID="w9538"BOOK="_idx" COLLECTION="nw41" TIDREF="i445"
bindery objects are placed in the same context as the server that is being upgraded. The following information is upgraded:MARK=BULLETID numbers (IDXID="w9539"BOOK="_idx" COLLECTION="nw41" TIDREF="i4690"
user and group IDs)Print servers and print queuesTrustee rightsSecurity equivalencesMAIL directoriesRestrictions (account, expiration, password, disk space, connection, time, station)On NetWare 4.0x servers with NetWare Directory Services already installed, a screen will appear during the upgrade process stating that Directory Services has already been installed.Resolves any naming conflicts that may occur (if upgrading your server into an existing Directory).Scans the server configuration files (IDXID="w9540"BOOK="_idx" COLLECTION="nw41" TIDREF="i4264"
STARTUP.NCF and AUTOEXEC.NCF) to make sure information gets updated (especially Ethernet driver frame types).(Optional) Upgrades IDXID="w9541"BOOK="_idx" COLLECTION="nw41" TIDREF="i4690"
Print Services.PAGENUM=7 ID="BP17"RENDERAS="SECT2"Bindery ServicesThe following restrictions apply to IDXID="w9542"BOOK="_idx" COLLECTION="nw41" TIDREF="i447"
Bindery objects in NetWare 4.1 Directory Services.MARK=BULLETYou must use bindery-based utilities to modify any information about Bindery objects in NetWare 4.1.You must use a IDXID="w9543"BOOK="_idx" COLLECTION="nw41" TIDREF="i442"
bindery-based utility (under bindery services) to IDXID="w9544"BOOK="_idx" COLLECTION="nw41" TIDREF="i447"
manage IDXID="w9545"BOOK="_idx" COLLECTION="nw41" TIDREF="i2318"
Bindery objects. If you are using bindery services on your NetWare 4.1 network, you must copy the IDXID="w9546"BOOK="_idx" COLLECTION="nw41" TIDREF="i2831"
pre-4.1 utilities to the PUBLIC and LOGIN directories so pre-4.1 clients can function on the network.For more information about objects and their properties, see Chapter 1, "BOOK="superenu" COLLECTION="nw41"Managing NetWare Directory Services Objects," of Supervising the Network and "BOOK="cncptenu" COLLECTION="nw41"Rights" in Concepts.RENDERAS="SECT1"ID="FM40785"Upgrading NetWare Directory ServicesNetWare Directory Services in NetWare 4.1 is backwards compatible with NetWare 4.01 and 4.02. However, the NetWare Directory Services schema has changed in NetWare 4.1. Care should be taken when running combinations of NetWare 4.01, 4.02, and 4.1 in the same Directory tree.  Follow the instructions in this section if you plan on having any combination of NetWare 4.01, 4.02, and 4.1 servers running in the same Directory tree.The NetWare 4.1 NetWare Directory Services schema must be distributed to all NetWare 4.01 and 4.02 servers in your Directory tree for Directory Services to run reliably. This can be done in one of two ways.MARK=BULLETIn your Directory tree, install NetWare 4.1 on a new server or upgrade an existing NetWare 4.01 or 4.02 server to NetWare 4.1.If all servers are running properly, the new schema will be automatically distributed to all current NetWare 4.01 and 4.02 servers in your Directory tree.Run the DSREPAIR utility.If you are not installing or upgrading a new NetWare 4.1 server, or if any NetWare 4.01 and 4.02 servers were not running properly when you installed the new NetWare 4.1 server, the DSREPAIR utility will put the new schema on the designated NetWare 4.01 and 4.02 servers.PAGENUM=8 ID="BP18"For instructions on running DSREPAIR, see "BOOK="superenu" COLLECTION="nw41"Repairing the NetWare Directory Services Database" in Chapter 5 of Supervising the Network.RENDERAS="SECT1"ID="FM74815"Running the NetWare 4.1 Installation ProgramRENDERAS="SECT2"IDXID="w9547"BOOK="_idx" COLLECTION="nw41" TIDREF="i1016"
Necessary 
ResourcesMARK=CHECKBOXMinimum 8 MB of IDXID="w9548"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"
RAM on the server.Minimum of 75 MB free space on volume SYS:.NetWare 4.1 server.CD-ROM device installed on the server being upgraded.NetWare 4.1 CD-ROM or working copies of the NetWare 4.1 diskettes. For an installation from a network directory, a IDXID="w9549"BOOK="_idx" COLLECTION="nw41" TIDREF="i1218"
drive mapped to the working areas where copies of the diskette files are located.RENDERAS="SECT2"PrerequisitesMARK=CHECKBOX(Optional) Use the NetWare 3.1x SALVAGE utility to restore deleted files.To salvage already-deleted files, restore them before upgrading.As you mount existing volumes under NetWare 4.1, purged files are eliminated and appear on the FILER utility screen as eliminated files.Make sure you have a fully functional backup of your NetWare 3.x or NetWare 4.0x system. Do not attempt an upgrade without a backup.Notify users to log out of the NetWare 3.x or NetWare 4.0x server.Broadcast a message from the console (using the BROADCAST command) that users must log out before the server upgrade. Users (this includes print servers) must stay logged out until the upgrade is complete.PAGENUM=9 ID="BP19"Set up and configure a CD-ROM device on the server being upgraded.If you are using IDXID="w9550"BOOK="_idx" COLLECTION="nw41" TIDREF="i2755"
third-party IDXID="w9551"BOOK="_idx" COLLECTION="nw41" TIDREF="i4474"
NLMs, disk drivers (*.DSK), or LAN drivers (*.LAN), check with your Novell Authorized ResellerTM representative for compatibility issues before upgrading your network.Or, call 1-800-414-LABS to receive a FAXBACK catalog listing drivers and modules that are compatible with NetWare 4.1. Call 1-801-429-5544 for operator assistance.Most third-party disk and LAN drivers written for NetWare 3.11 and 3.12 work with NetWare 4.1.If you are upgrading a NetWare 3.1x server into an existing 
Directory tree, find out the following information from the network supervisor:MARK=BULLETTree nameWhich 
context to place this 
server intoAdministrator's name (user ADMIN or another user with Supervisor object rights to this 
context)Administrator's password (for authentication to the Directory)Load NetWare 3.1x INSTALL and edit the AUTOEXEC.NCF file to specify the frame type for Ethernet LAN drivers. NetWare accepts either Ethernet 802.2 or 802.3 frame types. The default is 802.2.This is so other servers and routers broadcasting the 802.2 frame type can see this server.It is possible to load both frame types. Servers, routers, and clients using the 802.2 frame type will be able to communicate with each other, but will not be able to communicate with servers, routers and clients using the 802.3 frame type.If you are upgrading several servers into the same NetWare Directory Services IDXID="w9552"BOOK="_idx" COLLECTION="nw41" TIDREF="i4047"
context, do this before upgrading:MARK=BULLETConsolidate names of users who exist under different names on different servers. For example, user Mark Peters might be MARK on server ONE and MPETERS on server TWO. If you upgraded both servers into the same context, two User objects would be created for the same user, Mark Peters.PAGENUM=10 ID="BP20"Change names of users with the same names on different servers that will be upgraded into the same context. For example, there might be a user MARK on server ONE and a different user MARK on server TWO. Even though they are two different 
users, you may accidentally IDXID="w9553"BOOK="_idx" COLLECTION="nw41" TIDREF="i447"
merge them into one IDXID="w9554"BOOK="_idx" COLLECTION="nw41" TIDREF="i1064"
Directory IDXID="w9555"BOOK="_idx" COLLECTION="nw41" TIDREF="i2403"
object called MARK. (You can rename IDXID="w9556"BOOK="_idx" COLLECTION="nw41" TIDREF="i773"
conflicting IDXID="w9557"BOOK="_idx" COLLECTION="nw41" TIDREF="i447"
bindery IDXID="w9558"BOOK="_idx" COLLECTION="nw41" TIDREF="i2403"
object names during the upgrade process.) For example, a IDXID="w9559"BOOK="_idx" COLLECTION="nw41" TIDREF="i447"
merge of IDXID="w9560"BOOK="_idx" COLLECTION="nw41" TIDREF="i2403"
user MARK on server ONE and MARK on server TWO will give server ONE's MARK access to both servers' files.We recommend you review all your login scripts to check whether they must be updated to take advantage of NetWare 4.1 functionality. See IDREF="FM86177""What to Do After the Upgrade" on page 14 for further instructions for modifying login scripts.Prepare for 
Macintosh* file support:MARK=BULLETThis product provides native-mode support for Macintosh workstations that connect to the NetWare 4.1 server.You will also need to add 
name 
space support to any volume that contains files with long names. For instructions, see "BOOK="instlenu" COLLECTION="nw41"Manage NetWare Volumes" in Chapter 3 of Installation.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"IDXID="w9561"BOOK="_idx" COLLECTION="nw41" TIDREF="i2755"
On the server you are upgrading, load the installation program for the version of NetWare you are running.At the system console (:), type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"IDXID="w9562"BOOK="_idx" COLLECTION="nw41" TIDREF="i1289"
Edit the 
IDXID="w9563"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"
AUTOEXEC.NCF
IDXID="w9564"BOOK="_idx" COLLECTION="nw41" TIDREF="i2496"IDXID="w9565"BOOK="_idx" COLLECTION="nw41" TIDREF="i1289"
file with respect to 
IDXID="w9566"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
frame 
IDXID="w9567"BOOK="_idx" COLLECTION="nw41" TIDREF="i4618"
types.If an IDXID="w9568"BOOK="_idx" COLLECTION="nw41" TIDREF="i1350"
Ethernet driver is loaded with no IDXID="w9569"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
frame IDXID="w9570"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
type specified, the driver uses the IDXID="w9571"BOOK="_idx" COLLECTION="nw41" TIDREF="i7"
802.2 IDXID="w9572"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
default. Previous versions of NetWare defaulted to IDXID="w9573"BOOK="_idx" COLLECTION="nw41" TIDREF="i9"
802.3.  Make sure all LAN drivers have a IDXID="w9574"BOOK="_idx" COLLECTION="nw41" TIDREF="i1568"
frame type specified.PERFORMANCE="REQUIRED"Bring down the server.At the system console (:), type
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>
PAGENUM=11 ID="BP21"PERFORMANCE="REQUIRED"Exit to DOS by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"EXIT MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"IDXID="w9575"BOOK="_idx" COLLECTION="nw41" TIDREF="i845"
Copy all 
IDXID="w9576"BOOK="_idx" COLLECTION="nw41" TIDREF="i493"
old 
IDXID="w9577"BOOK="_idx" COLLECTION="nw41" TIDREF="i845"
boot 
IDXID="w9578"BOOK="_idx" COLLECTION="nw41" TIDREF="i4048"
files to another diskette or directory.Take this precautionary measure to ensure that you have a backup of your old 

boot files.Files include:
TYPE="VERT"*.BAT (batch files)*.DSK (disk drivers)*.LAN (LAN drivers)*.NAM (name spaces)AUTOEXEC.NCFIDXID="w9579"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
INSTALL.NLMSERVER.EXEIDXID="w9580"BOOK="_idx" COLLECTION="nw41" TIDREF="i4264"
STARTUP.NCFVREPAIRPERFORMANCE="REQUIRED"(Conditional) If installing from diskette, insert the NetWare 4.1 
IDXID="w9581"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"CLASS=DISKInstall diskette into drive A:, change to drive A:, and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w9582"BOOK="_idx" COLLECTION="nw41" TIDREF="i4679"
INSTALL MOREINFO="NONE"<Enter>The "Select an Installation Option" menu appears.PERFORMANCE="REQUIRED"(Conditional) If installing from CD-ROM, change to the drive letter corresponding to your CD-ROM device and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w9583"BOOK="_idx" COLLECTION="nw41" TIDREF="i4679"
INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the language you want installed. Press 
MOREINFO="NONE"<Enter> to select the default NetWare 4.1 English version.The "Select the Type of Installation Desired" menu appears.PERFORMANCE="REQUIRED"Choose "NetWare Server Installation." Press 
MOREINFO="NONE"<Enter>.The "Choose the Product You Want to Install" menu appears.PERFORMANCE="REQUIRED"Choose "NetWare 4.1" to upgrade a server that currently has either NetWare 3.1
x or NetWare 4.0
x to NetWare 4.1.
PAGENUM=12 ID="BP22"PERFORMANCE="REQUIRED"Choose "Upgrade NetWare 3.1
x or 4.0
x to 4.1."The "Copy Files to the DOS Partition" screen appears. You must specify the 
IDXID="w9584"BOOK="_idx" COLLECTION="nw41" TIDREF="i1012"
destination directory (where you want SERVER.EXE, etc. to be copied).PERFORMANCE="REQUIRED"Copy the 
IDXID="w9585"BOOK="_idx" COLLECTION="nw41" TIDREF="i493"
new NetWare 4.1 
IDXID="w9586"BOOK="_idx" COLLECTION="nw41" TIDREF="i4048"
server 
IDXID="w9587"BOOK="_idx" COLLECTION="nw41" TIDREF="i2831"
boot files to the boot directory.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Enter the destination path for the files to be copiedIt is recommended that you create a new directory rather than specify the directory where you current NetWare 3.1x or 4.0x SERVER.EXE file resides. You will be prompted to create this as a new server boot directory. Press MOREINFO="NONE"<Enter> after the directory has been created.For example:FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\SERVER.41The files are copied from the CLASS=DISKInstall diskette or the NetWare 4.1 CD-ROM to the destination directory on drive C:.The following files are copied to the boot directory, on drive C: (or another directory on drive C: that you specify.)MARK=BULLETStandard disk drivers (*.DSK)IDXID="w9588"BOOK="_idx" COLLECTION="nw41" TIDREF="i2755"
INSTALL.NLM (the installation utility)Replacement LAN drivers (*.LAN) (for as many pre-4.1 drivers as possible)Message and help filesNWSNUT.NLM (an interface utility needed for certain NetWare Loadable ModulesTM)LAN drivers (*.LAN)SERVER.EXE (the NetWare operating system)PERFORMANCE="REQUIRED"If the directory that you specified does not exist, the following message appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Do you want to create the directory "directory name." Y/NPAGENUM=13 ID="BP23"If you are using a third-party driver not shipped in the red box, you may need to exit the INSTALL and copy the disk driver (*.DSK) to the new boot directory.PERFORMANCE="REQUIRED"If you choose "Yes," press 
MOREINFO="NONE"<Enter> to create the new directory. The following message appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Enter the path to your existing SERVER.EXE file.PERFORMANCE="REQUIRED"Type the path to your existing SERVER.EXE file.PERFORMANCE="REQUIRED"After you set the destination path, follow the instructions on the screen.Once the appropriate files have been copied, a screen displays drivers that were found in the existing startup directory, but were not updated by the installation procedure.Press 
MOREINFO="NONE"<Enter> to continue. The "Select a Local Configuration for the Server" screen appears.PERFORMANCE="REQUIRED"Once the files have been copied, the following screen appears:LABEL="2-1" FLOAT="0"Language configuration screenFILEREF="n41up64a.tif"PERFORMANCE="REQUIRED"(Conditional) Specify the 
IDXID="w9589"BOOK="_idx" COLLECTION="nw41" TIDREF="i859"
country code, 
IDXID="w9590"BOOK="_idx" COLLECTION="nw41" TIDREF="i669"
code page, and 
IDXID="w9591"BOOK="_idx" COLLECTION="nw41" TIDREF="i2015"
keyboard mapping.For information on any of the settings in this screen, press MOREINFO="NONE"<F1> or refer to your DOS manual.Use the Up- and Down-arrow keys to maneuver through the screen.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to view options and select an applicable country code.The "Code Page" filed is highlighted.PAGENUM=14 ID="BP24"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> and select an applicable code page.The "Keyboard Mapping" field is highlighted.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> and select an applicable keyboard type.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to save and continue.PERFORMANCE="REQUIRED"Continue with "
BOOK="instlenu" COLLECTION="nw41"Load the Disk and CD-ROM Drivers" in Chapter 2 of 
Installation to complete the upgrade to NetWare 4.1.PERFORMANCE="REQUIRED"You can copy 

system and public files from a remote workstation using 
IDXID="w9592"BOOK="_idx" COLLECTION="nw41" TIDREF="i3674"
RCONSOLE.For instructions, see Appendix E, "
BOOK="instlenu" COLLECTION="nw41"Install Using RCONSOLE," of 
Installation.RENDERAS="SECT1"ID="FM86177"What to Do After the IDXID="w9593"BOOK="_idx" COLLECTION="nw41" TIDREF="i2746"
UpgradeComplete the following before allowing users to log in.MARK=BULLETSet the ADMIN password.Change user IDXID="w9594"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
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 NetWare Administrator.Check IDXID="w9595"BOOK="_idx" COLLECTION="nw41" TIDREF="i265"
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:MARK=BULLETRestrict the application's directory on the destination server with DSPACE.Make the directory path a fake root using the MAP command.PAGENUM=15 ID="BP25"Check IDXID="w9596"BOOK="_idx" COLLECTION="nw41" TIDREF="i1074"
directory security.Set new 
directory and 
file attributes using FLAG or FILER.Check directories for unnecessary NetWare files.Modify the system and IDXID="w9597"BOOK="_idx" COLLECTION="nw41" TIDREF="i2217"
user IDXID="w9598"BOOK="_idx" COLLECTION="nw41" TIDREF="i2216"
login scripts.If you changed the server name, update references to the server in the system and user login scripts.Although user login scripts are upgraded, they are not modified and server names are not changed to match your new environment. Use the NetWare Administrator utility to modify the login scripts.If you have set up your login scripts so that users have drive mappings to directories in which they have no rights, these users receive the following message when they log in:FORMAT="LINESPECIFIC"MOREINFO="NONE"Attempt to map drive to invalid path in MAP command.Complete one of the following:MARK=BULLETDelete the drive mapping from the login script.Delete the drive mapping from the system login script and insert the drive mapping in the user's login script only when the user has been granted rights to the directory.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 drive:=volume:directory).If you have workstations that boot from diskettes, create new IDXID="w9599"BOOK="_idx" COLLECTION="nw41" TIDREF="i490"
boot diskettes for each workstation.MARK=BULLETIf the server was renamed, change the server's name in the users' AUTOEXEC.BAT files to the new NetWare 4.1 server name.If you have other NetWare 2.x servers on your network, upgrade the workstation files for those users even if you aren't upgrading the server.The new workstation files shipped with NetWare 4.1 are compatible with NetWare 2.x. All users on the internetwork should use the latest version of the workstation files to ensure that there are not conflicts.PAGENUM=16 ID="BP26"(Conditional) Copy the NetWare 4.1IDXID="w9600"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
 utilities to other servers on the network.The NetWare 3.x public utilities will run on servers running NetWare 2.x. Complete one of the following:MARK=BULLETIf you have servers running NetWare 2.0a, 2.10, or 2.11, do not copy the NetWare 3.x public utilities to them. However, copy the NetWare 3.x LOGIN.EXE file to the SYS:LOGIN and SYS:PUBLIC directories.If you have NetWare 2.12 or 2.15 servers on your network, replace the NetWare public utilities with the NetWare 3.x public utilities to allow the NetWare 2.12 and 2.15 servers to work with encrypted passwords.To copy utilities, complete the following steps:Log in to the NetWare 2.x server as SUPERVISOR.Flag the NetWare 2.x utilities Normal. In the SYS:LOGIN and SYS:PUBLIC directories, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG *.* N MOREINFO="NONE"<Enter>Protect the system login script. In the SYS:PUBLIC directory, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG NET$LOG.DAT SRO MOREINFO="NONE"<Enter>Map a drive to the SYS:PUBLIC directory on the NetWare 4.1 server by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP drive:=fileserver/SYS:PUBLIC MOREINFO="NONE"<Enter>Replace drive with a drive letter not being used and replace fileserver with the name of the NetWare 4.1 server.Enter your username and password for the NetWare 4.1 server.Copy the NetWare 4.1 PUBLIC files to the NetWare 2.x server.For example, if drive Q: is mapped to SYS:PUBLIC on the NetWare 4.1 server and drive F: is mapped to SYS:PUBLIC on the NetWare 2.x server, change to drive F: and typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NCOPY Q:*.* MOREINFO="NONE"<Enter>Flag the NetWare 4.1 utilities on the NetWare 2.x server Shareable and Read Only. TypePAGENUM=17 ID="BP27"FORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG *.* SRO MOREINFO="NONE"<Enter>Repeat the above steps for the SYS:LOGIN directory.Login scripts on the NetWare 4.1 server do not execute properly unless you copy the NetWare 4.1 login programs to all NetWare LOGIN directories on your internetwork.Update as necessary upgraded print queues using PCONSOLE.Use SBACKUP to make a backup copy of all data on the NetWare 4.1 server.For SBACKUP instructions, see Chapter 9, "BOOK="superenu" COLLECTION="nw41"Backing Up and Restoring Data," of Supervising the Network.Check user restrictions and accounting charge rates to make sure your system is configured the way you want it.(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 IDXID="w9601"BOOK="_idx" COLLECTION="nw41" TIDREF="i88"
ADD NAME SPACE command to add name space to the volume. TypeFORMAT="LINESPECIFIC"MOREINFO="NONE"ADD NAME SPACE name-support TO VOLUME volume_name MOREINFO="NONE"<Enter>For example, if you have a volume named MAC for Macintosh files, type the following at the console prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"ADD NAME SPACE MACINTOSH TO VOLUME MAC MOREINFO="NONE"<Enter>Use the command once for every volume that needs to store files with long names.To ensure name space support each time the server is brought up, load the appropriate name space module in the STARTUP.NCF file.(Optional) To store IDXID="w9602"BOOK="_idx" COLLECTION="nw41" TIDREF="i2270"
Macintosh files and folders on a NetWare 4.1 server, install NetWare for Macintosh on the NetWare 4.1 server.This product provides support for Macintosh workstations that connect to the NetWare 4.1 server.Assign 
Directory object and property rights to 
Directory objects that were upgraded from bindery objects.PAGENUM=18 ID="BP28"See Chapter 1, "BOOK="superenu" COLLECTION="nw41"Managing NetWare Directory Services Objects," of Supervising the Network for details.Certain login script IDXID="w9603"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"
commands have to be modified or deleted after the IDXID="w9604"BOOK="_idx" COLLECTION="nw41" TIDREF="i2496"
upgrade:MARK=BULLETMEMBER_OF_groupIDXID="w9605"BOOK="_idx" COLLECTION="nw41" TIDREF="i1622"
Groups have been replaced by 
Group IDXID="w9606"BOOK="_idx" COLLECTION="nw41" TIDREF="i1064"
objects and IDXID="w9607"BOOK="_idx" COLLECTION="nw41" TIDREF="i1622"
Profile IDXID="w9608"BOOK="_idx" COLLECTION="nw41" TIDREF="i3385"
objects. This variable becomes a IDXID="w9609"BOOK="_idx" COLLECTION="nw41" TIDREF="i3568"
Group object in NetWare 4.1. For more information, see Chapter 3, "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts," of Supervising the Network.IDXID="w9610"BOOK="_idx" COLLECTION="nw41" TIDREF="i2332"
MAP commandWhen you map a drive to a directory that's located on a NetWare 4.1 Directory Services volume, you may want to modify the volume name to correspond to the new Directory name.However, when you map a drive to a server that is running a previous version of NetWare, the MAP command functions as it did originally and must include the servername.IDXID="w9611"BOOK="_idx" COLLECTION="nw41" TIDREF="i328"
ATTACH commandUsers can still attach to pre-4.1 servers, but the ATTACH command is not valid for NetWare 4.1 servers.The majority of login commands work the same under NetWare 4.1 as they did under previous NetWare versions. In MAP commands, if the server is not specified (MAP F:=SYS:directory), the Message Server attribute of the User will be used.To set up the maximum amount of disk space a user can use, use the NETADMIN or NetWare Administrator utility in NetWare 4.1 after you have finished the upgrade to NetWare 4.1.For more information on NETADMIN or NetWare Administrator, see Chapter 1, "BOOK="superenu" COLLECTION="nw41"Managing NetWare Directory Services Objects," of Supervising the Network.Allow users to log in to the NetWare 4.1 server.Users can log in ifMARK=BULLETVolume SYS: is mountedThe user exists in the binderyPAGENUM=19 ID="BP29"The LAN driver is loaded and bound to a protocolLogins are enabledTo ensure that logins are enabled, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"ENABLE LOGIN MOREINFO="NONE"<Enter>LABEL="3"PAGENUM=21 ID="BP30"Upgrade Using Across-the-Wire MigrationRENDERAS="SECT1"IntroductionThis chapter explains how to upgrade existing NetWare® 2, NetWare 3TM, and other network operating system servers to servers running NetWare 4.1 using the Across-the-Wire Migration method.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM14872"Preparing for MigrationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM14872"27COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM61681"Running the Migration UtilityCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM85551"28COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM96203"Running MIGPRINTCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM96203"40COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM56702"What to Do After MigrationCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM56702"41RENDERAS="SECT1"OverviewAcross-the-Wire Migration uses the Migration utility to convert an existing NetWare 2.1x, NetWare 2.2, or NetWare 3.1x bindery server to a new NetWare 4.1 server. The Migration utility converts the bindery information on the NetWare 2 or NetWare 3 server to NetWare Directory Services on a NetWare 4.1 server via a DOS client workstation.You can use Across-the-Wire Migration when upgrading fromMARK=BULLETNetWare 2 (specifically, NetWare 2.1x and NetWare 2.2) to NetWare 4.1.NetWare 3 (specifically, NetWare 3.11 and NetWare 3.12) to NetWare 4.1.Another network operating system (specifically, IBM* PCLP 1.3 Extended Services; IBM LAN Server* 1.0, 1.1, 1.2, 1.3; and Microsoft* LAN Manager* 2.0) to NetWare 4.1.PAGENUM=22 ID="BP31"RENDERAS="SECT2"How It WorksIn an 
Across-the-Wire 
Migration, data 
files are migrated across the network from the source server to the NetWare 4.1 server.Selected bindery IDXID="w9612"BOOK="_idx" COLLECTION="nw41" TIDREF="i445"
information is migrated to the IDXID="w9613"BOOK="_idx" COLLECTION="nw41" TIDREF="i445"
working directory on the client workstation and translated to the NetWare 4.1 format, and then migrated to the 
NetWare 41 server through 
bindery services. IDXID="w9614"BOOK="_idx" COLLECTION="nw41" TIDREF="i442"
Bindery services occurs when NetWare Directory ServicesTM (
NDS) emulates a flat structure for the objects within an NDSTM Directory tree.The NetWare Migration utility lets you select specific information from the bindery and data files so that you can upgrade a server and create a customized NetWare 4.1 server. The Migration utility leaves the source server intact and only copies information to the NetWare 4.1 server.Across-the-Wire Migration allows you to preserve your user environment (users and their trustee assignments) as well as the IDXID="w9615"BOOK="_idx" COLLECTION="nw41" TIDREF="i66"
default IDXID="w9616"BOOK="_idx" COLLECTION="nw41" TIDREF="i66"
account IDXID="w9617"BOOK="_idx" COLLECTION="nw41" TIDREF="i3833"
restrictions, accounting methods, and IDXID="w9618"BOOK="_idx" COLLECTION="nw41" TIDREF="i3443"
print queues and print servers.LABEL="3-1" FLOAT="0"ID="FM66613"Across-the-Wire MigrationFILEREF="n41up04a.tif"PAGENUM=23 ID="BP32"RENDERAS="SECT3"Three Computers NeededThree computers are needed to upgrade using Across-the-Wire Migration:MARK=BULLETA NetWare server running NetWare 2, NetWare 3, or another network operating system. This is called the source server.A NetWare server running NetWare 4.1. This is called the NetWare 4.1 server.A DOS workstation with NetWare ClientTM for DOS and MS Windows software loaded. This is called the client workstation. The Migration utility will run on this client workstation.RENDERAS="SECT3"Bindery Services Connection NecessaryA IDXID="w9619"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"bindery is the database in NetWare 2.x and 3.x that contains definitions for entities such as users, groups, NetWare servers, and print servers. For more information, see "BOOK="cncptenu" COLLECTION="nw41"Bindery" and "BOOK="cncptenu" COLLECTION="nw41"Bindery services" in Concepts.When you use the Migration utility, it is important to have only bindery connections, because the utility depends on bindery services to work properly. To ensure only bindery connections, log in to the NetWare 4.1 server using the bindery services (/b) option. For example, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN SRV1/SUPERVISOR /BOr use the Migration utility to log in to the NetWare 4.1 server.RENDERAS="SECT3"NetWare Directory ServicesIn NetWare 4.1, NetWare Directory Services replaces the bindery, which served as the system database for previous releases of NetWare.While the bindery supports the operation of a single NetWare server, NetWare 
Directory Services supports an entire network of servers. NetWare Directory Services is a single, logical database: all users, applications, and servers go to one database for information.For more information on NetWare Directory Services, see BOOK="getstenu" COLLECTION="nw41"Introduction to NetWare Directory Services.PAGENUM=24RENDERAS="SECT3"Migrating DirectoriesMARK=BULLETIf a IDXID="w9620"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
directory is being migrated that has the same IDXID="w9621"BOOK="_idx" COLLECTION="nw41" TIDREF="i1269"
name and path as a IDXID="w9622"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
directory that already exists on the NetWare 4.1 server, the files from both directories are merged under the destination directory name.The directory structure and files are migrated and become a part of the IDXID="w9623"BOOK="_idx" COLLECTION="nw41" TIDREF="i1474"
NetWare 4.1 IDXID="w9624"BOOK="_idx" COLLECTION="nw41" TIDREF="i1474"
file system. If necessary, modify the organization on the NetWare 4.1 server after all the source servers are migrated.RENDERAS="SECT3"Migrating FilesMARK=BULLETNetWare 2.x or 3.x system files are not migrated.Any file (newer or older) on a source server that has the same name as one that exists on the NetWare 4.1 server is not copied to the NetWare 4.1 server.An error message appears on the screen during the migration, and is also written to the migration report, to let you know that a file by that name already exists on the NetWare 4.1 server.We recommend you overwrite the incoming file if it is older. You can also keep the file either by renaming it and copying it to the NetWare 4.1 server, or by manually copying it over the old file after migration is completed.The system login script is not migrated, but user login scripts are.You should examine each IDXID="w9625"BOOK="_idx" COLLECTION="nw41" TIDREF="i2217"
user IDXID="w9626"BOOK="_idx" COLLECTION="nw41" TIDREF="i2217"
login 
script after the migration and make corrections if the server name or directory path names have changed.You can use the IDXID="w9627"BOOK="_idx" COLLECTION="nw41" TIDREF="i4631"
UIMPORT utility to migrate IDXID="w9628"BOOK="_idx" COLLECTION="nw41" TIDREF="i4690"
login scripts from bindery-based NetWare to NetWare Directory Services. UIMPORT allows you to import data from an existing database to the NDS database.The Migration utility creates the following two files in SYS:SYSTEM on the NetWare 4.1 server:TYPE="VERT"UIMPORT.CTLUIMPORT.DATFor instructions on using UIMPORT, see Chapter 5, "BOOK="superenu" COLLECTION="nw41"Managing the NetWare Directory Tree," in Supervising the Network.PAGENUM=25RENDERAS="SECT3"Migrating UsersMARK=BULLETUsers on the source server are created as new user objects on the NetWare 4.1 server.User login names, print job configurations, and login scripts are copied.User IDXID="w9629"BOOK="_idx" COLLECTION="nw41" TIDREF="i66"
account 
restrictions (such as account balance restrictions, expiration restrictions, password restrictions, and time restrictions) are copied.Users with the same username are merged; that is, their 
user information (login names, print job configurations, and login scripts) are added together (except for user account restrictions, which are left untouched).IDREF="FM25616"Table 3-1 shows the types and descriptions of 
information you can 
migrate using the Migration utility.LABEL="3-1" PGWIDE=1 TOCENTRY="1"ID="FM25616" Information that Can Be Migrated Using the Migration UtilityCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="14*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Data TypeCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"LimitationsVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"All IDXID="w9630"BOOK="_idx" COLLECTION="nw41" TIDREF="i158"
InformationCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates all the 
information listed in this table.COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Data 
FilesCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates all IDXID="w9631"BOOK="_idx" COLLECTION="nw41" TIDREF="i914"
data 
files and the DOS and NetWare attributes for 
files and directories.COLNAME=3 ROTATE="0" MOREROWS="0"Will not overwrite a file or directory with the same name.COLNAME=1 ROTATE="0" MOREROWS="0"Trustee AssignmentsCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates rights that are assigned to users and groups for directories and files. (Automatic conversion to NetWare 4.1 rights.)COLNAME=3 ROTATE="0" MOREROWS="0"With this selection, you must also choose Users, Groups, and Data Files if the users and data files in question do not already exist on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"UsersCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates user account names, user print job configurations (PRINTCON.DAT), and user login scripts.COLNAME=3 ROTATE="0" MOREROWS="0"Will not overwrite existing items on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"User
 RestrictionsCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates user account restrictions.COLNAME=3 ROTATE="0" MOREROWS="0"Does not include user volume restrictions. If this type is chosen, users must also be migrated. Will not overwrite existing restrictions on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9632"BOOK="_idx" COLLECTION="nw41" TIDREF="i1622"
GroupsCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates the IDXID="w9633"BOOK="_idx" COLLECTION="nw41" TIDREF="i1622"
group members and group trustee rights for directories and files.COLNAME=3 ROTATE="0" MOREROWS="0"If a group from the source server already exists on the NetWare 4.1 server, the source and destination groups will be merged.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9634"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"
Default Account RestrictionsCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates default 
account restrictions.COLNAME=3 ROTATE="0" MOREROWS="0"Overwrites any existing information on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9635"BOOK="_idx" COLLECTION="nw41" TIDREF="i71"
Accounting InformationCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates the accounting charge method chosen to charge for network services charged to individual user accounts.COLNAME=3 ROTATE="0" MOREROWS="0"Overwrites any existing information on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"Print IDXID="w9636"BOOK="_idx" COLLECTION="nw41" TIDREF="i3443"
Queues and Print ServersCOLNAME=2 ROTATE="0" MOREROWS="0"The Migration utility only migrates LAN Server and LAN Manager print queues. Migrates NetWare print queues and print servers and their corresponding setup information.COLNAME=3 ROTATE="0" MOREROWS="0"The source and destination information will be merged.PAGENUM=26 ID="BP35"IDREF="FM51653"Table 3-2 describes how NetWare 2.x or 3.x user designations migrate to NetWare 4.1. The IDXID="w9637"BOOK="_idx" COLLECTION="nw41" TIDREF="i66"
account restrictions are not merged.LABEL="3-2" PGWIDE=0 TOCENTRY="1"ID="FM51653" NetWare User DesignationsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"In NetWare 2.x or 3.xCOLNAME=2 ROTATE="0" MOREROWS="0"In NetWare 4.1VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"User account manager (NetWare 2.1x and 2.2 only)COLNAME=2 ROTATE="0" MOREROWS="0"Has Supervisor rights to objects managed (Object Supervisor property). Cannot create new objects.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9638"BOOK="_idx" COLLECTION="nw41" TIDREF="i4832"
Workgroup manager (NetWare 2.1x and 2.2 only)COLNAME=2 ROTATE="0" MOREROWS="0"Has Supervisor right to the User objects that were created in NetWare 2.x.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9639"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"
Console IDXID="w9640"BOOK="_idx" COLLECTION="nw41" TIDREF="i3098"
operatorCOLNAME=2 ROTATE="0" MOREROWS="0"Becomes an Operator property of the NetWare Server object.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9641"BOOK="_idx" COLLECTION="nw41" TIDREF="i4000"
Security equivalenceCOLNAME=2 ROTATE="0" MOREROWS="0"Becomes a value of the Security Equivalence IDXID="w9642"BOOK="_idx" COLLECTION="nw41" TIDREF="i3576"
property of the User object.PAGENUM=27 ID="BP36"RENDERAS="SECT3"ID="FM62628"ID="FM30183"NetWare 2 Rights and AttributesIn NetWare 2.x, rights are assigned only at the IDXID="w9643"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
directory level. In NetWare 4, rights are assigned at the 
file and 
directory levels.When you use Across-the-Wire Migration, all NetWare 2.x rights and 
attributes are translated into the NetWare 4 format. The Maximum Rights Mask is replaced with an Inherited Rights Filter (IRF), which allows rights to flow down the file system 
directory structure.RENDERAS="SECT3"Migrating PasswordsPasswords are not migrated. The Migration utility allows you to eitherMARK=BULLETIDXID="w9644"BOOK="_idx" COLLECTION="nw41" TIDREF="i3249"
Assign IDXID="w9645"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
passwords that are IDXID="w9646"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
generated 
randomly for all migrated users.Allow users to log in to the new system without a password.Randomly generated passwords are stored in a IDXID="w9647"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
file called IDXID="w9648"BOOK="_idx" COLLECTION="nw41" TIDREF="i2915"
NEW.PWD in SYS:SYSTEM on the NetWare 4.1 server, and can be accessed only by the User object ADMIN.RENDERAS="SECT1"ID="FM14872"Preparing for MigrationDuring the migration process, you will set up your migration on a configuration form. This configuration form focuses on the following three areas:MARK=BULLETPreparing the NetWare 4.1 serverPreparing the source serverPreparing the client workstationRENDERAS="SECT2"ID="FM82228"Preparing the NetWare 4.1 ServerRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXMinumum server setup includes a 15MB DOS partition, a 50MB NetWare partition, and 8 MB of RAM.PAGENUM=28 ID="BP37"Create the volumes that you want to migrate data to.The Migration utility does not create volumes.You may want to create a directory to migrate the NetWare 2.x or 3.x volume SYS: to so that you can remove unnecessary NetWare 2.x or 3.x files more easily. Create a directory on volume SYS: that corresponds to the volume on the NetWare 2.x or 3.x server.Since two servers on the same network cannot share the same name, the NetWare 4.1 server must have a unique name.Make sure that all users, except ADMIN, are logged out of the NetWare 4.1 server and that all files are closed.(Optional) Prepare 
Macintosh* file support.To store 
Macintosh files and folders on the new 
NetWare 4.1 server, add 
name space 
support to any volume that needs to store files with long names. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"ADD NAME SPACE" in Utilities Reference.Install NetWare for Macintosh (a separate Novell® product) to provide native-mode support for Macintosh workstations that connect to the NetWare 4.1 server.Plan for disk space on the NetWare 4.1 server.If you merge two or more NetWare 2.x or 3.x servers onto the same NetWare 4.1 server, plan for sufficient free disk space for the NetWare 4.1 IDXID="w9649"BOOK="_idx" COLLECTION="nw41" TIDREF="i4394"
volume SYS:. Volume SYS: requires at least 50 MB of disk space.RENDERAS="SECT2"ID="FM85551"Preparing the Source ServerRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXIDXID="w9650"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
Back up your IDXID="w9651"BOOK="_idx" COLLECTION="nw41" TIDREF="i4215"
source server.Use your regular backup utility to back up your current NetWare 2.x, NetWare 3.x, or other network operating system server at least twice to ensure a good copy.PAGENUM=29 ID="BP38"Make sure that all users, except ADMIN (or SUPERVISOR), are logged out of the source servers and that all files (except bindery files) are closed during migration.IDXID="w9652"BOOK="_idx" COLLECTION="nw41" TIDREF="i988"Delete 
unnecessary files.Decide if you want to migrate .BAK or .LST files, or any other temporary files. You may want to consolidate some files and directories.Value-Added Processes (VAPs) are not compatible with NetWare 4.1, so you may want to delete them before you start the migration.Rename DOS directories and files that have long names.NetWare 2.x supports 14-character directory and file names. NetWare 4.1 supports DOS naming conventions---eight-character name, three-character extention---for DOS directories and files.Only DOS directories and files that conform to DOS naming conventions (8.3) are migrated.Macintosh and OS/2* files can still follow their respective naming conventions.Modify the IDXID="w9653"BOOK="_idx" COLLECTION="nw41" TIDREF="i4313"
subdirectory depth to 25 levels.NetWare 4.1 sets the default IDXID="w9654"BOOK="_idx" COLLECTION="nw41" TIDREF="i2356"
subdirectory depth to 25 levels; therefore, the Migration utility does not copy subdirectories deeper than 25 levles.If the source server has subdirectories deeper than 25, modify the subdirectory structure so that the subdirectories aren't so deep.IDXID="w9655"BOOK="_idx" COLLECTION="nw41" TIDREF="i462"Run 
BINDFIX on the source server.BINDFIX can delete mail subdirectories and trustee rights of all users who no longer exist on the source server.For more information, see "BINDFIX," in NetWare 2.2 Using the Network or NetWare 3.11 Utilities Reference.PAGENUM=30 ID="BP39"RENDERAS="SECT2"ID="FM11485"Preparing the Client WorkstationRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA DOS workstation with at least 640 KB of memory (with 480 KB of free memory) and 5 MB of free disk space on either a hard disk or another network drive that can attach to both the source server and NetWare 4.1 server.Make sure that your network connection is a bindery connection.If you are authenticated to the NetWare 4.1 server, you must log in with a bindery connection or log out and use the Migration utility to log in.Make sure the CONFIG.SYS file includes the following line:FORMAT="LINESPECIFIC"MOREINFO="NONE"files=20If you add the line to the CONFIG.SYS file, save the file and then reboot the workstation.Make sure the NET.CFG file includes the following lines:FORMAT="LINESPECIFIC"MOREINFO="NONE"Protocol IPXODI IPX retry count=60MARK=CHECKBOXLoad your IDXID="w9656"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
LAN drivers on the DOS 
workstation and run the NetWare Client for DOS and MS Windows software.PAGENUM=31 ID="BP40"RENDERAS="SECT1"ID="FM61681"Running the Migration UtilityRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"ID="FM70056"(Conditional) If your client workstation has a CD-ROM device, use the NetWare 4.1 CD-ROM and change to the MIGRATE directory.PERFORMANCE="REQUIRED"(Conditional) If your client workstation does not have a CD-ROM device, create a MIGRATE directory on your client workstation and copy the migration files from the MIGRATE subdirectory on your NetWare 4.1 server to your client workstation or make migration diskettes using the NetWare 4.1 installation utility.PERFORMANCE="REQUIRED"From the client workstation, start the Migration utility by changing to the directory that contains the Migration utility files and typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MIGRATE MOREINFO="NONE"<Enter>The "Select the Type of Migration" menu appears.PERFORMANCE="REQUIRED"From the "Select the Type of Migration" menu, choose "Across-the-Wire Migration."The "Select Source LAN Type" menu appears.PERFORMANCE="REQUIRED"ID="FM26162"Choose a source 
IDXID="w9657"BOOK="_idx" COLLECTION="nw41" TIDREF="i2026"
LAN type (NetWare 2.
x , NetWare 3.
x,, LAN Server/PCLP, or LAN Manager).The "Select the Destination LAN Type" menu appears.PERFORMANCE="REQUIRED"ID="FM52914"Choose a destination LAN type (4.1).When selecting a source and destination, the Migration utility does version checking according to the source type and destination type you selected.The "Migration Utility Configuration" form appears.IDREF="FM87860"Figure 3-2 illustrates the process of filling out the configuration form used with the Migration utility. The corresponding migration steps are noted where applicable.
PAGENUM=32 ID="BP41"LABEL="3-2" FLOAT="0"ID="FM87860"The Migration Utility Configuration FormFILEREF="n41up07a.tif"PERFORMANCE="REQUIRED"ID="FM90458"Under Step 1, "Configure the Migration Utility," on the configuration form, press 
MOREINFO="NONE"<Enter> to change the 
IDXID="w9658"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
working directory (if desired); then press the Down-arrow key to move to the next field.The 

working directory is where the bindery information and the migration reports are 
IDXID="w9659"BOOK="_idx" COLLECTION="nw41" TIDREF="i445"
stored. Data files are not stored here. You need 5 MB of free disk space in this directory.The working directory is usually located on the workstation's hard disk, but you can also put it on a network drive.
PAGENUM=33 ID="BP42"If you are using a network drive instead of a workstation hard disk, you must have Create, Read, and Write and File Scan rights in the working directory.If the working directory doesn't exist on the workstation hard disk or network drive, the Migration utility creates it for you.PERFORMANCE="REQUIRED"Under Step 1 on the configuration form, press 
MOREINFO="NONE"<Enter> to toggle between 
IDXID="w9660"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"
error/warning actions.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9661"BOOK="_idx" COLLECTION="nw41" TIDREF="i1345"
Error/Warning ActionCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Pause after warnings and errorsCOLNAME=2 ROTATE="0" MOREROWS="0"Choose this option if you want the utility to stop after each warning and error and prompt you to continue with the migration.Each time an error is reported and you are prompted, you can choose to discontinue the prompting.COLNAME=1 ROTATE="0" MOREROWS="0"Do not pause after warnings and errorsCOLNAME=2 ROTATE="0" MOREROWS="0"Choose this option if you do not want to be prompted after each warning and error.All errors are listed in the report file regardless of the option you select. PERFORMANCE="REQUIRED"Under Step 2, "Define the Source Server," on the configuration form, press 
MOREINFO="NONE"<Enter> to display a list of 
IDXID="w9662"BOOK="_idx" COLLECTION="nw41" TIDREF="i4215"
source servers.For LAN Server or LAN Manager: If you are migrating from LAN Server or LAN Manager, the screen shows the domain obtained from the DOSLAN.INI file. Edit this field if the domain you are logged into is not the same as the one listed in the DOSLAN.INI file.PERFORMANCE="REQUIRED"Choose the 

source server you want to migrate from.This selection must match the source type you specified in 
IDREF="FM26162"Step 5 of this procedure.If the source server you want to select is not shown, press 
MOREINFO="NONE"<Insert> to see a list of available servers you can log in to.When migrating multiple source servers, only one source server can be migrated at a time.PERFORMANCE="REQUIRED"Under Step 2 on the configuration form, press 
MOREINFO="NONE"<Enter> again to display categories of information you want to migrate.
PAGENUM=34 ID="BP43"For LAN Server or LAN Manager: If you are migrating from LAN Server or LAN Manager, you are limited to the following IDXID="w9663"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"
categories to migrate:Access Control ProfilesAll Information Data Files Groups Print Queues UsersOnly files that conform to DOS naming conventions (8.3) are migrated.PERFORMANCE="REQUIRED"Using
MOREINFO="NONE" <F5>, mark the information you want to migrate.Follow the Quick Help for details on how to select information.Mark as many categories as necessary.If you select "All Information," all categories are migrated. However, printing environments are not migrated at this time. After the Migration utility has finished, use MIGPRINT.EXE (documented in this chapter) to migrate your printing environment.PERFORMANCE="REQUIRED"Under Step 2 on the configuration form, press 
MOREINFO="NONE"<Enter> again to display a list of 
IDXID="w9664"BOOK="_idx" COLLECTION="nw41" TIDREF="i4206"
source 
IDXID="w9665"BOOK="_idx" COLLECTION="nw41" TIDREF="i4795"
volumes on the source server you want to migrate data from.For LAN Server or LAN Manager: If you are migrating from LAN Server or LAN Manager, source drives are listed.PERFORMANCE="REQUIRED"Mark the volumes using 
MOREINFO="NONE"<F5>, and then press 
MOREINFO="NONE"<Enter>.Mark source volumes to migrate only if you are migrating data files or trustee assignments on those volumes.You must select a source volume (or a source drive in LAN Server or LAN Manager) to migrate if you select any of the following categories to migrate:
TYPE="VERT"All InformationData FilesTrustee Assignments (or Access Control permissions in LAN Server or LAN Manager)PAGENUM=35 ID="BP44"If you are migrating one or more of the following categories, you do not need to select a source volume:
TYPE="VERT"Accounting InformationDefault Account RestrictionsGroupsPrint QueuesUser RestrictionsUsersPERFORMANCE="REQUIRED"Under Step 3, "Define the Destination Server," on the configuration form, press 
MOREINFO="NONE"<Enter> to display a list of servers on the network.PERFORMANCE="REQUIRED"Choose the NetWare 4.1 server that you want to migrate the source server to.This selection must match the destination type you specified in 
IDREF="FM52914"Step 6.If the 
IDXID="w9666"BOOK="_idx" COLLECTION="nw41" TIDREF="i1016"
NetWare 4.1 server you want to select is not shown, press 
MOREINFO="NONE"<Insert> to see a list of available servers that you can log in to.PERFORMANCE="REQUIRED"Under Step 3 on the configuration form, press 
MOREINFO="NONE"<Enter> to select a volume (or source drive in LAN Server or LAN Manager).PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to specify the destination volume and directory on the NetWare 4.1 server.Destination volumes that match the source volumes are displayed as the default.Press 
MOREINFO="NONE"<Insert> to see a list of available volumes and directories on the NetWare 4.1 server.For LAN Server or LAN Manager: If you are migrating from LAN Server or LAN Manager, the list contains servers and drives.If you specify a directory that does not exist on the NetWare 4.1 server, you are asked whether the system should create it. Volumes must already be created on the NetWare 4.1 server before you can migrate data to them.The volume organization, as well as the directory structure, is migrated. You can modify the organization on the NetWare 4.1 server after all the source servers have been migrated.PAGENUM=36 ID="BP45"PERFORMANCE="REQUIRED"ID="FM48563"Press 
MOREINFO="NONE"<Enter> when you complete the destination path of the source volume.PERFORMANCE="REQUIRED"If you have multiple source volumes, continue to specify destination paths.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> when you finish filling out the "Volumes' Destination" field.PERFORMANCE="REQUIRED"(Optional) 
ID="FM20091"Under Step 3 on the configuration form, press 
MOREINFO="NONE"<Enter> and choose a 
IDXID="w9667"BOOK="_idx" COLLECTION="nw41" TIDREF="i3249"
password option.For LAN Manager: If you are migrating from LAN Manager, password lengths are global. For example, if a user has a "password not required" flag set on the LAN Manager side, the user will have no password on the NetWare 4.1 server.  If a 
password is required and the length of the password is zero (0), the Migration utility assigns the destination default password length.See the following table for a description of the options.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Password OptionCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Assign 
Random Passwords (default)COLNAME=2 ROTATE="0" MOREROWS="0"A password for each username that has a password on the source is generated randomly and stored in a file (NEW.PWD) in SYS:SYSTEM on the NetWare 4.1 server.Note:New passwords are given only to users and print servers that had a password on the source server.Only users with rights to SYS:SYSTEM have access to this file. Users cannot log in until they are given their passwords from this list.COLNAME=1 ROTATE="0" MOREROWS="0"Assign no passwordsCOLNAME=2 ROTATE="0" MOREROWS="0"After you finish the migration, all users can log in using their previous username. They are not prompted for a password.Users have the option to create their passwords if no random passwords were issued upon migration.Note: If the user account restrictions require users to have a password, they are prompted to type a new password, which the system verifies.PAGENUM=37 ID="BP46"PERFORMANCE="REQUIRED"Review the fields on the configuration form and make any necessary changes.PERFORMANCE="REQUIRED"To proceed with the migration, press 
MOREINFO="NONE"<F10> to display the "Select a Migration Action" menu.PERFORMANCE="REQUIRED"Choose a "Migration Action" and then press 
MOREINFO="NONE"<Enter>.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="16*"COLNAME=2 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"ChooseVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Migrate all the information you selected from the source server to the NetWare 4.1 server. If you choose this option, the migration starts automatically.All information about the migration is scrolled to the screen and entered into a report file, which you can review later.(The bindery information you selected is copied to the working directory and translated into the NetWare 4.1 format; it is then copied to the NetWare 4.1 server. The data files are migrated directly to the destination 4.1 server.)COLNAME=2 ROTATE="0" MOREROWS="0""Start the Migration"COLNAME=1 ROTATE="0" MOREROWS="0"Make changes to your migration configuration.COLNAME=2 ROTATE="0" MOREROWS="0""Return to Configuration"COLNAME=1 ROTATE="0" MOREROWS="0"Display reports (after the migration is complete).COLNAME=2 ROTATE="0" MOREROWS="0""View Migration Reports"COLNAME=1 ROTATE="0" MOREROWS="0"Exit the utility and return to the DOS prompt.COLNAME=2 ROTATE="0" MOREROWS="0""Exit (Return to DOS)"PAGENUM=38 ID="BP47"When the migration is complete, the Migration utility displays the following message:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Migration from the source server to the destination server is complete. Press <Enter> to continue.PERFORMANCE="REQUIRED"(Conditional) If errors occur during the migration and you chose to be prompted after errors and warnings, you are prompted:
FORMAT="LINESPECIFIC"MOREINFO="NONE"A migration error has occurred and is displayed in the migration log above. Do you want to continue with the migration? (Y=Yes/N=No/I=Ignore Error):Use the following table to help you answer the prompt.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you chooseCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"YesCOLNAME=2 ROTATE="0" MOREROWS="0"The migration continues. The error is written to the report file, and you are prompted again the next time an error occurs.COLNAME=1 ROTATE="0" MOREROWS="0"NoCOLNAME=2 ROTATE="0" MOREROWS="0"The migration stops. The error is written to the report file. You receive this message:MOREINFO="NONE"Migration from the source server to the NetWare 4.1 server is finished. Press MOREINFO="NONE"<Enter>MOREINFO="NONE" to continue.Press MOREINFO="NONE"<Enter> to return to the "Select a Migration Action" menu. From there, press MOREINFO="NONE"<Esc> to edit the fields or choose "Exit" to leave the utility and return to the DOS prompt.COLNAME=1 ROTATE="0" MOREROWS="0"IgnoreCOLNAME=2 ROTATE="0" MOREROWS="0"The migration continues. The error is written to the report file. You are no longer prompted when an error occurs, but all errors are written to the report file.For explanations of all error messages, see 
BOOK="sysmsenu" COLLECTION="nw41"System Messages. PAGENUM=39 ID="BP48"PERFORMANCE="REQUIRED"(Optional)
 To 

view the migration report, select "View Migration Reports" from the "Select a Migration Action" menu and continue with 
IDREF="FM25907"Step 27a.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM25907"Select the 
IDXID="w9668"BOOK="_idx" COLLECTION="nw41" TIDREF="i3796"
report for the migration you completed and press 
MOREINFO="NONE"<Enter>.The IDXID="w9669"BOOK="_idx" COLLECTION="nw41" TIDREF="i3796"
reports reside in the working directory that you specified earlier (in IDREF="FM90458"Step 7).Use the report to help you complete and customize definitions, attributes, and access privileges on the NetWare 4.1 server. If you find errors on your NetWare 4.1 server after the migration, locate them in the migration report file and determine what actions to take on the NetWare 4.1 server to correct the errors.The report file is an ASCII text file that consists of the following:MARK=BULLETSummary information of the bindery IDXID="w9670"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
import phase (migrating bindery data from the source server to the working directory)Summary information of the bindery export phase (migrating bindery data from the working directory to the NetWare 4.1 server)A listing of each item in each category that was read from the source serverA listing of each item in each category that was written to or created on the NetWare 4.1 serverThe number of errors that occurred during the migrationPERFORMANCE="REQUIRED"To exit the report, press 
MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"To return to the "Select a Migration Action" menu, press 
MOREINFO="NONE"<Esc> again.PERFORMANCE="REQUIRED"To exit the Migration utility, choose "Exit (Return to DOS)."PERFORMANCE="REQUIRED"To complete the migration to NetWare 4, continue with the next section, 
IDREF="FM96203""Running MIGPRINT."PAGENUM=40 ID="BP49"RENDERAS="SECT1"ID="FM96203"Running MIGPRINTThe MIGPRINT utility allows you to migrate printers, print queues, print job configurations, and print servers from your NetWare 2 or NetWare 3 source server into your NetWare 4.1 Directory tree.RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXComplete the Across-the-Wire Migration.Make sure you have the Supervisor right on the NetWare 4.1 server.RENDERAS="SECT3"ProceduresPERFORMANCE="REQUIRED"From the client workstation, establish a NetWare Directory Services connection to the NetWare 4.1 server.PERFORMANCE="REQUIRED"From the client workstation, establish a connection to the source server.PERFORMANCE="REQUIRED"(Conditional) If your client workstation has a CD-ROM device, use the NetWare 4.1 CD-ROM and change to the MIGRATE directory.PERFORMANCE="REQUIRED"(Conditional) If your client workstation does not have a CD-ROM device, create a MIGRATE directory (if you haven't already done so) on your client workstation and copy the MIGPRINT.EXE file from the MIGRATE subdirectory on your NetWare 4.1 server to your client workstation.PERFORMANCE="REQUIRED"Initialize a search drive by mapping a search drive to SYS:SYSTEM/NLS.PERFORMANCE="REQUIRED"From the client workstation, start the MIGPRINT utility by changing to the directory that contains the migration utility files and typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MIGPRINT /S=source_server /D=destination_server [/VOL=queue_volume /O=output_file] MOREINFO="NONE"<Enter>Replace 
source server with the name of the the bindery server that you're migrating the print information from.
PAGENUM=41 ID="BP50"Replace 
destination server with the name of the NetWare 4.1 server you're migrating to.(Optional) If you don't want to migrate to the default volume SYS:, replace 
queue volume with the name of another queue volume.(Optional) If you don't want to migrate to the default file, replace 
output file with the name of another file.PERFORMANCE="REQUIRED"Follow the instructions on the MIGPRINT screen.RENDERAS="SECT1"ID="FM56702"What to Do After MigrationAfter the migration is complete, check the NetWare 4.1 server and do the following if they apply:MARK=BULLETUpdate references to the server in the user IDXID="w9671"BOOK="_idx" COLLECTION="nw41" TIDREF="i2217"
login scripts.Although user login scripts are migrated, they are not modified, and server names and directory paths are not changed to match your new environment.You can use the IDXID="w9672"BOOK="_idx" COLLECTION="nw41" TIDREF="i4631"
UIMPORT utility to migrate IDXID="w9673"BOOK="_idx" COLLECTION="nw41" TIDREF="i4690"
login scripts from bindery-based NetWare to NetWare 4.1 Directory Services (NDS). UIMPORT allows you to import data from an existing database to the NDS database.The Migration utility creates the following two files in SYS:SYSTEM on the NetWare 4.1 server:TYPE="VERT"UIMPORT.CTLUIMPORT.DATFor instructions on using UIMPORT, see Chapter 5, "
BOOK="superenu" COLLECTION="nw41"Managing the NetWare Directory Tree," in 
Supervising the Network.
MARK=BULLETCheck IDXID="w9674"BOOK="_idx" COLLECTION="nw41" TIDREF="i265"
third-party IDXID="w9675"BOOK="_idx" COLLECTION="nw41" TIDREF="i4474"
applications.In order for third-party applications to run properly under NetWare 4.1, you may need to reinstall them and/or enter new paths in their setup files.You may need to reinstall third-party applications if:The application has an .EXE file that did not migrate.The application is path-specific and you have changed the path structure during migration.PAGENUM=42 ID="BP51"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:
MARK=BULLETRestrict the application's directory on the NetWare 4.1 server with Object Manager (which replaces DSPACE).MARK=BULLETMake the directory a fake root using MAP.Examine the files in merged directories and reorganize them if necessary.Any directories that were merged may contain unrelated files.Update migrated print queues and print servers.NetWare 4.1 Print Services are different than printing in previous NetWare versions. For more information, see 

BOOK="printenu" COLLECTION="nw41"Print Services.
MARK=BULLETCheck user restrictions and IDXID="w9676"BOOK="_idx" COLLECTION="nw41" TIDREF="i71"
accounting charge rates to make sure your system is configured the way you want it.Set any new 
directory and 
file attributes.If you chose to assign random passwords, you may want to print the IDXID="w9677"BOOK="_idx" COLLECTION="nw41" TIDREF="i2915"
NEW.PWD IDXID="w9678"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
file and distribute the password information to your users. The users should change their passwords immediately.The report, an ASCII text file, shows passwords sorted by date. If users were migrated from more than one server, the current password is the last one listed on the report.If you have menus set up, you may need to run a menu conversion program so your menus function properly under NetWare 4.1.LABEL="4"PAGENUM=43 ID="BP52"Upgrade Using Same-Server MigrationRENDERAS="SECT1"IntroductionThis chapter describes the preparation and procedures necessary to complete a Same-Server Migration.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM96944"Preparing for Migration COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM96944"50COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM71893"Running the Migration Utility COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM71893"53COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM29915"What to Do After Migration COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM29915"63RENDERAS="SECT1"OverviewSame-Server Migration uses the MIGRATE utility to convert an existing NetWare® 2, NetWare 3TM, or another network operating system server to NetWare 4.1. After backing up the NetWare 2, NetWare 3, or another network operating system server, the MIGRATE utility converts the server's bindery information to NetWare Directory ServicesTM and installs NetWare 4.1.You can use Same-Server Migration when upgrading fromMARK=BULLETNetWare 2 (specifically, NetWare 2.1x and NetWare 2.2) to NetWare 4.1.NetWare 3 (specifically, NetWare 3.11 and NetWare 3.12) to NetWare 4.1.Another network operating system (specifically, IBM PCLP 1.3 Extended Services; IBM LAN Server 1.0, 1.1, 1.2, 1.3; and Microsoft LAN Manager 2.0) to NetWare 4.1.PAGENUM=44 ID="BP53"RENDERAS="SECT2"How It WorksSame-Server Migration is used to update a server that will be installed on the same hardware as the old 
server, allowing you to change your NetWare 2, NetWare 3, or another network operating system into a NetWare 4.1 server.Same-Server Migration allows you to use only one server. However, there is some risk to the data involved during the conversion process to NetWare 4.1. Also, you may not be able to migrate the file attributes (because Same-Server Migration does not migrate data files).When you use 
Same-Server Migration, you must IDXID="w9679"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
back up your IDXID="w9680"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
data files, and then IDXID="w9681"BOOK="_idx" COLLECTION="nw41" TIDREF="i3829"
restore them to the NetWare 4.1 server after you install NetWare 4.1.IDREF="FM90063"Figure 4-1 illustrates Same-Server Migration.PAGENUM=45 ID="BP54"LABEL="4-1" FLOAT="0"ID="FM90063"Same-Server MigrationFILEREF="n41up05a.tif"RENDERAS="SECT3"Two Computers NeededTwo computers are needed to upgrade using Same-Server Migration:MARK=BULLETA NetWare server running NetWare 2, NetWare 3, or another network operating system. This is called the server.A DOS workstation with NetWare ClientTM for DOS and MS Windows software loaded. This is called the client workstation. The MIGRATE utility will run on this client workstation.PAGENUM=46 ID="BP55"RENDERAS="SECT3"Bindery Services Connection NecessaryA IDXID="w9682"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"bindery is the database in NetWare 2.x and 3.x that contains definitions for entities such as users, groups, NetWare servers, and print servers. For more information, see "BOOK="cncptenu" COLLECTION="nw41"Bindery" and "BOOK="cncptenu" COLLECTION="nw41"Bindery services" in Concepts. When you use the Migration utility, it is important to have only bindery connections, because the utility depends on bindery services to work properly. To ensure only bindery connections, log in to the NetWare 4.1 server using the bindery services (/b) option. For example, you would typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOGIN SRV1/SUPERVISOR /BOr use the Migration utility to log in to the NetWare 4.1 server.RENDERAS="SECT3"NetWare Directory ServicesIn NetWare 4.1, NetWare Directory Services replaces the bindery, which served as the system database for previous releases of NetWare.While the bindery supports the operation of a single NetWare server, NetWare 
Directory Services supports an entire network of servers. NetWare Directory Services is a single, logical database; all users, applications, and servers go to one database for information.For more information on NetWare Directory Services, see BOOK="getstenu" COLLECTION="nw41"Introduction to NetWare Directory Services. RENDERAS="SECT3"Migrating 
DirectoriesMARK=BULLETIf a IDXID="w9683"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
directory is being migrated that has the same IDXID="w9684"BOOK="_idx" COLLECTION="nw41" TIDREF="i1269"
name and path as a IDXID="w9685"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
directory that already exists on the NetWare 4.1 server, the files from both directories are merged under the destination directory name. The directory structure and files are migrated and become a part of the IDXID="w9686"BOOK="_idx" COLLECTION="nw41" TIDREF="i1474"
NetWare 4.1 IDXID="w9687"BOOK="_idx" COLLECTION="nw41" TIDREF="i1474"
file system. If necessary, modify the organization on the NetWare 4.1 server after all the servers are migrated.PAGENUM=47 ID="BP56"RENDERAS="SECT3"Migrating 
FilesMARK=BULLETNetWare 2.x or 3.x system files are not migrated.Any file (newer or older) on a server that has the same name as one that exists on the NetWare 4.1 server is not copied to the NetWare 4.1 server.An error message appears on the screen during the migration, and is also written to the migration report, to let you know that a file by that name already exists on the NetWare 4.1 server.We recommend you overwrite the incoming file if it is older. You can also keep the file by either renaming it and copying it to the NetWare 4.1 server or by manually copying it over the old file after migration is completed.The system login script is not migrated, but user login scripts are.You should examine each IDXID="w9688"BOOK="_idx" COLLECTION="nw41" TIDREF="i2217"
user IDXID="w9689"BOOK="_idx" COLLECTION="nw41" TIDREF="i2217"
login 
script after the migration and make corrections if the server name or directory path names have changed.You can use the IDXID="w9690"BOOK="_idx" COLLECTION="nw41" TIDREF="i4631"
UIMPORT utility to migrate IDXID="w9691"BOOK="_idx" COLLECTION="nw41" TIDREF="i4690"
login scripts from bindery-based NetWare to NetWare Directory Services. UIMPORT allows you to import data from an existing database to the NDS database. The Migration utility creates the following two files in SYS:SYSTEM on the NetWare 4.1 server:TYPE="VERT"UIMPORT.CTLUIMPORT.DATFor instructions on using UIMPORT, see "BOOK="superenu" COLLECTION="nw41"Importing User Information into the Directory Services Database" in Supervising the Network.RENDERAS="SECT3"Migrating UsersMARK=BULLETUsers on the server are created as new user objects on the NetWare 4.1 server.User login names, print job configurations, and login scripts are copied.User IDXID="w9692"BOOK="_idx" COLLECTION="nw41" TIDREF="i66"
account 
restrictions (such as account balance restrictions, expiration restrictions, password restrictions, and time restrictions) are copied.Users with the same username are merged; that is, their 
user information (login names, print job configurations, and login scripts) are added together (except for user account restrictions, which are left untouched). PAGENUM=48 ID="BP57"IDREF="FM99426"Table 4-1 shows the types and descriptions of 
information you can 
migrate using the Migration utility. LABEL="4-1" PGWIDE=1 TOCENTRY="1"ID="FM99426" Information that Can Be Migrated Using the Migration UtilityCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="14*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Data TypeCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"LimitationsVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"All IDXID="w9693"BOOK="_idx" COLLECTION="nw41" TIDREF="i158"
InformationCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates all the 
information listed in this table.COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Data FilesCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates all IDXID="w9694"BOOK="_idx" COLLECTION="nw41" TIDREF="i914"
data 
files and the DOS and NetWare attributes for 
files and directories.COLNAME=3 ROTATE="0" MOREROWS="0"Will not overwrite a file or directory with the same name.COLNAME=1 ROTATE="0" MOREROWS="0"Trustee AssignmentsCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates rights that are assigned to users and groups for directories and files. (Automatic conversion to NetWare 4.1 rights.)COLNAME=3 ROTATE="0" MOREROWS="0"With this selection, you must also choose Users, Groups, and Data files if the users and data files in question do not already exist on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"UsersCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates user account names, user print job configurations (PRINTCON.DAT), and user login scripts.COLNAME=3 ROTATE="0" MOREROWS="0"Will not overwrite existing items on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"User
 RestrictionsCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates user account restrictions.COLNAME=3 ROTATE="0" MOREROWS="0"Does not include user volume restrictions. If this type is chosen, users must also be migrated. Will not overwrite existing restrictions on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9695"BOOK="_idx" COLLECTION="nw41" TIDREF="i1622"
GroupsCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates the IDXID="w9696"BOOK="_idx" COLLECTION="nw41" TIDREF="i1622"
group members and group trustee rights for directories and files.COLNAME=3 ROTATE="0" MOREROWS="0"If a group from the source server already exists on the NetWare 4.1 server, the source and destination groups will be merged.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9697"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"
Default Account RestrictionsCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates default 
account restrictions.COLNAME=3 ROTATE="0" MOREROWS="0"Overwrites any existing information on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9698"BOOK="_idx" COLLECTION="nw41" TIDREF="i71"
Accounting InformationCOLNAME=2 ROTATE="0" MOREROWS="0"Migrates the accounting charge method chosen to charge for network services charged to individual user accounts.COLNAME=3 ROTATE="0" MOREROWS="0"Overwrites any existing information on the NetWare 4.1 server.COLNAME=1 ROTATE="0" MOREROWS="0"Print IDXID="w9699"BOOK="_idx" COLLECTION="nw41" TIDREF="i3443"
Queues and Print ServersCOLNAME=2 ROTATE="0" MOREROWS="0"The Migration utility only migrates LAN Server and LAN Manager print queues. Migrates NetWare print queues and print servers and their corresponding setup information.COLNAME=3 ROTATE="0" MOREROWS="0"The source and destination information will be merged.PAGENUM=49 ID="BP58"IDREF="FM34742"Table 4-2 describes how NetWare 2.x or 3.x user designations migrate to NetWare 4.1. The IDXID="w9700"BOOK="_idx" COLLECTION="nw41" TIDREF="i66"
account restrictions are not merged.LABEL="4-2" PGWIDE=0 TOCENTRY="1"ID="FM34742" NetWare User DesignationsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"In NetWare 2.x or 3.xCOLNAME=2 ROTATE="0" MOREROWS="0"In NetWare 4.1VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"User account manager (NetWare 2.1x and 2.2 only)COLNAME=2 ROTATE="0" MOREROWS="0"Has Supervisor rights to objects managed (Object Supervisor property). Cannot create new objects.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9701"BOOK="_idx" COLLECTION="nw41" TIDREF="i4832"
Workgroup manager (NetWare 2.1x and 2.2 only)COLNAME=2 ROTATE="0" MOREROWS="0"Has Supervisor right to the User objects that were created in NetWare 2.x.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9702"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"
Console IDXID="w9703"BOOK="_idx" COLLECTION="nw41" TIDREF="i3098"
operatorCOLNAME=2 ROTATE="0" MOREROWS="0"Becomes an Operator property of the NetWare Server object.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9704"BOOK="_idx" COLLECTION="nw41" TIDREF="i4000"
Security equivalenceCOLNAME=2 ROTATE="0" MOREROWS="0"Becomes a value of the Security Equivalence IDXID="w9705"BOOK="_idx" COLLECTION="nw41" TIDREF="i3576"
property of the User object.RENDERAS="SECT3"NetWare 2 Rights and 
AttributesIn NetWare 2.x, rights are assigned only at the IDXID="w9706"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
directory level. In NetWare 4, rights are assigned at the 
file and 
directory levels. When you use Same-Server Migration, all NetWare 2.x rights and 
attributes are translated into the NetWare 4 format. The Maximum Rights Mask is replaced with an Inherited Rights Filter (IRF), which allows rights to flow down the file system 
directory structure.RENDERAS="SECT3"Migrating PasswordsPasswords are not migrated. The Migration utility allows you to eitherMARK=BULLETIDXID="w9707"BOOK="_idx" COLLECTION="nw41" TIDREF="i3249"
Assign IDXID="w9708"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
passwords that are IDXID="w9709"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
generated 
randomly for all migrated users.Allow users to log in to the new system without a password. Randomly generated passwords are stored in a IDXID="w9710"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
file called IDXID="w9711"BOOK="_idx" COLLECTION="nw41" TIDREF="i2915"
NEW.PWD in SYS:SYSTEM on the NetWare 4.1 server, and can be accessed only by the User object ADMIN.PAGENUM=50 ID="BP59"RENDERAS="SECT1"ID="FM96944"Preparing for MigrationDuring the migration process, you will set up your migration on a configuration form. This configuration form focuses on the following two areas:MARK=BULLETPreparing the serverPreparing the client workstationRENDERAS="SECT2"ID="FM92674"Preparing the ServerRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA server with a 386 or higher processor. Minimum recommendations for server setup include15MB DOS Partition 50MB NetWare Partition 8MB RAMIDXID="w9712"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"IDXID="w9713"BOOK="_idx" COLLECTION="nw41" TIDREF="i4215"Back up your 
server.Use your regular backup utility to back up your current NetWare 2.x or 3.x server or IDXID="w9714"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"
LAN Server at least twice to ensure a good copy.If you are doing a IDXID="w9715"BOOK="_idx" COLLECTION="nw41" TIDREF="i404"
Same-Server Migration, note that the NetWare installation procedure destroys all data on your hard disk. Back up the server. You do not need to restore trustees or bindery information using your backup. The migration utility converts the trustees and bindery information to NetWare 4.1 format, IDXID="w9716"BOOK="_idx" COLLECTION="nw41" TIDREF="i442"
accessible through bindery emulation.Make sure that all users, except ADMIN (or SUPERVISOR), are logged out of the server and that all files (except bindery files) are closed during migration.Be sure that your network connection is a bindery connection. If you are authenticated to the NetWare 4.1 server, you must log in with a bindery connection or log out and use the Migration utility to login.IDXID="w9717"BOOK="_idx" COLLECTION="nw41" TIDREF="i988"Remove 
unnecessary files.Decide if you want to migrate .BAK or .LST files, or any other temporary files. You may want to consolidate some files and directories.PAGENUM=51 ID="BP60"Value-Added Processes (
VAPs) that are in a directory that you migrate are copied to the NetWare 4.1 server; however, IDXID="w9718"BOOK="_idx" COLLECTION="nw41" TIDREF="i4743"
VAPs are not compatible with NetWare 4.1, so you may want to delete them before you start the migration.The following NetWare 2.1x files are not compatible with NetWare 4.1. If these files are only in SYS:PUBLIC or SYS:SYSTEM, the migration utility blocks them from being transferred. If copies of these files are in other directories, they are transferred.These files, located in SYS:SYSTEM, must be deleted:LARCHIVE.EXE LRESTORE.EXE MACBACK.EXE NARCHIVE.EXE NRESTORE.EXEPrepare 
Macintosh file support.To store 
Macintosh files and folders on the new 
NetWare 4.1 server, add 
name space 
support to any volume that needs to store files with long names. For more information, see "BOOK="utlrfenu" COLLECTION="nw41"ADD NAME SPACE" in Utilities Reference.Install NetWare for Macintosh to provide native-mode support for Macintosh workstations that connect to the NetWare 4.1 server.Rename DOS files and directories that have long names.NetWare 2.2 and earlier lets you give directories and files 14-character names. NetWare 4.1 allows only IDXID="w9719"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
DOS naming conventions for DOS directories. DOS limits directory names to 8 characters with a 3-character extension. (Macintosh and OS/2 files can still follow their respective naming conventions.)Only directories and files that conform to DOS naming conventions (8.3) are migrated.User IDXID="w9720"BOOK="_idx" COLLECTION="nw41" TIDREF="i2217"
login scripts are migrated from IDXID="w9721"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
SYS:MAIL to the user's new mail directory on the NetWare 4.1 server.Other files left in the mail directories are not copied to the destination mail directory.Obtain IDXID="w9722"BOOK="_idx" COLLECTION="nw41" TIDREF="i2758"
NLMs to replace any IDXID="w9723"BOOK="_idx" COLLECTION="nw41" TIDREF="i265"
third-party VAPs that are currently running on the 2.x server.PAGENUM=52 ID="BP61"VAPs do not run on a NetWare 4.1 system. To find out about 
NLMs that are available to replace your IDXID="w9724"BOOK="_idx" COLLECTION="nw41" TIDREF="i4474"
third-party IDXID="w9725"BOOK="_idx" COLLECTION="nw41" TIDREF="i4745"
VAPs, contact your vendor or call the Novell product information department at 1-800-NETWARE.IDXID="w9726"BOOK="_idx" COLLECTION="nw41" TIDREF="i462"Run 
BINDFIX on the NetWare server.BINDFIX can delete mail subdirectories and trustee rights of all users who no longer exist on the server.For more information, see "BINDFIX," in NetWare 2.2 Using the Network or NetWare 3.11 Utilities Reference.(Conditional) When running interoperably between NetWare and LAN Server or LAN Manager, use NETX.COM.RENDERAS="SECT2"ID="FM52141"Preparing the Client WorkstationRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXA DOS workstation with at least 640 KB of memory (with 480 KB of free memory) and 5 MB of free disk space on either a hard disk or another network drive that can attach to both the source server and NetWare 4.1 server.Make sure that your network connection is a bindery connection.If you are authenticated to the NetWare 4.1 server, you must log in with a bindery connection or log out and use the Migration utility to log in.Make sure the CONFIG.SYS file includes the following line:FORMAT="LINESPECIFIC"MOREINFO="NONE"files=20If you add the line to the CONFIG.SYS file, save the file and then reboot the workstation.Make sure the NET.CFG file includes the following lines:FORMAT="LINESPECIFIC"MOREINFO="NONE"Protocol IPXODI IPX retry count=60
PAGENUM=53 ID="BP62"MARK=CHECKBOXLoad your IDXID="w9727"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
LAN drivers on the DOS 
workstation and run the NetWare Client for DOS and MS Windows software.RENDERAS="SECT1"ID="FM73047"ID="FM71893"Running the Migration UtilityThe server must meet the minimum requirements specified under IDREF="FM92674""Preparing the Server" on page 50.Same-Server Migration does involve some risk to your data files as a result of the conversion process to NetWare 4.1.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"ID="FM95691"(Conditional) If your client workstation has a a CD-ROM, use the NetWare 4.1 CD and go to the MIGRATE subdirection under the NW410 directory.PERFORMANCE="REQUIRED"(Conditional) If your client workstation does not have a CD-ROM, create a MIGRATE directory on your client workstation and copy the migration files from the MIGRATE subdirectory on your 4.1 server to your client workstation or make migration diskettes using the NetWare 4.1 installation utility.PERFORMANCE="REQUIRED"From the client workstation, start the migration utility by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MIGRATE MOREINFO="NONE"<Enter>The "Select the Type of Migration" menu appears.PERFORMANCE="REQUIRED"From the "Select the Type of Migration" menu, choose "Same-Server Migration."Same-Server Migration allows you to stop the utility after you migrate the bindery information to the working directory so that you can install NetWare 4.1.PERFORMANCE="REQUIRED"ID="FM79633"From the "Select the Source LAN Type" menu, choose a source 
IDXID="w9728"BOOK="_idx" COLLECTION="nw41" TIDREF="i2026"
LAN type (NetWare 2.
x or 3.
x or LAN Server, PCLP or LAN Manager).PERFORMANCE="REQUIRED"ID="FM81222"From the "Select the Destination LAN Type" menu, choose a destination LAN type (4.1).
PAGENUM=54 ID="BP63"Once you have selected a source and destination, the migration utility verifies that you selected compatible versions for the migration.LABEL="4-2" FLOAT="0"ID="FM19307"The Same-Server Migration Configuration FormFILEREF="n41up07a.tif"PERFORMANCE="REQUIRED"Under Step 1, "Configure the migration utility," on the configuration form, press the Down arrow key to accept the 

default 
IDXID="w9729"BOOK="_idx" COLLECTION="nw41" TIDREF="i4835"
working directory or press 
MOREINFO="NONE"<Enter> to specify another 
IDXID="w9730"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
working directory. The working directory is where the bindery information and the migration reports are stored.
PAGENUM=55 ID="BP64"Usually, the working directory is located on the hard disk drive of the workstation, but you can also put it on a network drive. You need 5 MB free disk space in this directory.If you are using a network drive instead of a hard drive, you must have Create, Read, Write, and File Scan rights in this directory.If this directory doesn't exist, the migration utility creates it for you on your hard disk.Follow the Quick Help to specify a different working directory.PERFORMANCE="REQUIRED"Under Step 1 on the configuration form, press 
MOREINFO="NONE"<Enter> to select an 
IDXID="w9731"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"
error/warning action. COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9732"BOOK="_idx" COLLECTION="nw41" TIDREF="i1345"
Error/Warning ActionCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Pause after warnings and errorsCOLNAME=2 ROTATE="0" MOREROWS="0"Choose this option if you want the utility to stop after each warning and error and prompt you to continue with the migration.Each time an error is reported and you are prompted, you can choose to discontinue the prompting.COLNAME=1 ROTATE="0" MOREROWS="0"Do not pause after warnings and errorsCOLNAME=2 ROTATE="0" MOREROWS="0"Choose this option if you do not want to be prompted after each warning and error.All errors are listed in the report file regardless of the option you select.PERFORMANCE="REQUIRED"Under Step 2, "Define the source server," on the configuration form, press 
MOREINFO="NONE"<Enter> to display a list of 
IDXID="w9733"BOOK="_idx" COLLECTION="nw41" TIDREF="i4215"
source servers.PERFORMANCE="REQUIRED"Choose the 

server that you want to migrate.This selection must match the type you specified in 
IDREF="FM79633"Step 5 of this procedure.If the server you want to select is not shown, press 
MOREINFO="NONE"<Ins> to see a list of available servers that you can log in to.PERFORMANCE="REQUIRED"Under Step 2 on the configuration form, press 
MOREINFO="NONE"<Enter> to display categories of information you want to migrate.PERFORMANCE="REQUIRED"Using <F5>, mark the information you want to migrate.
PAGENUM=56 ID="BP65"Follow the Quick Help for details on how to select information.Mark as many of the categories as necessary.If you select "All Information," all categories are migrated.PERFORMANCE="REQUIRED"Under Step 2 on the configuration form, press 
MOREINFO="NONE"<Enter> again to display a list of 
IDXID="w9734"BOOK="_idx" COLLECTION="nw41" TIDREF="i4206"
source 
IDXID="w9735"BOOK="_idx" COLLECTION="nw41" TIDREF="i4795"
volumes on the server that you want to migrate data from.PERFORMANCE="REQUIRED"Mark the volumes using <
MOREINFO="NONE"F5>, and then press 
MOREINFO="NONE"<Enter>.Mark source volumes to migrate only if you are migrating information contained on those volumes. If you are migrating one or more of the following categories, you do not need to select a source volume:
TYPE="VERT"Accounting InformationDefault Account RestrictionsGroupsPrint Queues and Print ServersUser RestrictionsUsersYou must select a source volume (or a source drive in LAN Server or LAN Manager) to migrate if you select any of the following categories to migrate:
TYPE="VERT"All InformationTrustee AssignmentsPERFORMANCE="REQUIRED"Review the 
IDXID="w9736"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"
fields on the 
IDXID="w9737"BOOK="_idx" COLLECTION="nw41" TIDREF="i1289"
configuration 
IDXID="w9738"BOOK="_idx" COLLECTION="nw41" TIDREF="i1446"
form and make any necessary 
IDXID="w9739"BOOK="_idx" COLLECTION="nw41" TIDREF="i2496"
changes. You cannot complete the information for the NetWare 4.1 server, since it does not yet exist. After you migrate the source information to your working directory and install NetWare 4.1 on your server, you return to the migration utility and complete the NetWare 4.1 server information.PERFORMANCE="REQUIRED"To proceed with the migration, press 
MOREINFO="NONE"<F10> to display the "Select a Migration Action" menu.
PAGENUM=57 ID="BP66"PERFORMANCE="REQUIRED"ID="FM63049"Select "Migrate to the Working Directory," and then press 
MOREINFO="NONE"<Enter>.All information about the migration is scrolled to the screen and entered into a report file, which you can review later.PERFORMANCE="REQUIRED"(Conditional) If errors occur during the migration and you chose to be prompted after errors and warnings, you receive the following error message and must answer the question.
FORMAT="LINESPECIFIC"MOREINFO="NONE"A migration error has occurred and is displayed in the migration log above. Do you want to continue with the migration? (Y=Yes/N=No/I=Ignore Error):Use the following table to help you answer the question.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you chooseCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"YesCOLNAME=2 ROTATE="0" MOREROWS="0"The migration continues. The error is written to the report file, and you are prompted again the next time an error occurs.COLNAME=1 ROTATE="0" MOREROWS="0"NoCOLNAME=2 ROTATE="0" MOREROWS="0"The migration stops. The error is written to the report file. You receive this message:MOREINFO="NONE"Migration from the server to the working directory is complete. Press <Enter> to continue.Press MOREINFO="NONE"<Enter> to return to the "Select a Migration Action" menu. From there, press MOREINFO="NONE"<Esc> to edit the fields or choose "Exit" to leave the utility and return to the DOS prompt.COLNAME=1 ROTATE="0" MOREROWS="0"IgnoreCOLNAME=2 ROTATE="0" MOREROWS="0"The migration continues. The error is written to the report file. You are no longer prompted when an error occurs, but all errors are written to the report file.See 
BOOK="sysmsenu" COLLECTION="nw41"System Messages for explanations of all error messages.When the migration to the working directory is complete, the following message appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Migration from the working directory is complete. Press <Enter> to continue.PAGENUM=58 ID="BP67"PERFORMANCE="REQUIRED"(Optional
) To 

view the migration 
IDXID="w9740"BOOK="_idx" COLLECTION="nw41" TIDREF="i3796"
report, select "View Migration Reports" from the "Select a Migration Action" menu and continue with Step 19a.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM57180"Select the report for the migration you completed and press 
MOREINFO="NONE"<Enter>.The reports reside in the working directory that you specified earlier.Use the report to help you complete and customize definitions, attributes, and access privileges on the NetWare 4.1 server. If you find errors on your NetWare 4.1 server after the migration, locate them in the migration report file and determine what actions to take on the NetWare 4.1 server to correct the errors.The report file is an ASCII text file that consists of the following:MARK=BULLETSummary information of the bindery IDXID="w9741"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
import phase (migrating bindery data from the server to the working directory)Listing of each item in each category that was read from the serverThe number of errors that occurred during the migrationPERFORMANCE="REQUIRED"To exit the report, press 
MOREINFO="NONE"<Esc> once. PERFORMANCE="REQUIRED"To return to the "Select a Migration Action" menu, press 
MOREINFO="NONE"<Esc> again.PERFORMANCE="REQUIRED"To 
IDXID="w9742"BOOK="_idx" COLLECTION="nw41" TIDREF="i1383"
exit the utility, choose "Exit (return to DOS)." PERFORMANCE="REQUIRED"ID="FM62131"Install NetWare 4.1 on your NetWare 2.
x or 3.
x server or on your LAN Server, PCLP, or LAN Manager server.PERFORMANCE="REQUIRED"ID="FM91389"Restore the 
IDXID="w9743"BOOK="_idx" COLLECTION="nw41" TIDREF="i914"data files from your backup 
IDXID="w9744"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
device to the NetWare 4.1 server.Make a note of where you restore the data files so that you can direct the bindery information to the correct location.Do not restore any trustees or bindery information; restore data files only.PERFORMANCE="REQUIRED"Restart the migration utility by moving to the directory where the migration utility files are on the workstation and typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"MIGRATE MOREINFO="NONE"<Enter>
PAGENUM=59 ID="BP68"The "Select the Type of Migration" menu appears.PERFORMANCE="REQUIRED"Make sure that the working directory is the same one you used when you migrated from the server to the working directory.PERFORMANCE="REQUIRED"From the "Select the Type of Migration" menu, choose "Same-Server Migration."PERFORMANCE="REQUIRED"From the "Select the Source LAN Type" menu, choose a source 
IDXID="w9745"BOOK="_idx" COLLECTION="nw41" TIDREF="i2026"
LAN type (NetWare 2.
x or 3.
x or LAN Server, PCLP or LAN Manager).This should be the same source LAN type you selected in 
IDREF="FM79633"Step 5.PERFORMANCE="REQUIRED"From the "Select the Destination LAN Type" menu, choose a destination LAN type (NetWare 4.1).This should be the same destination LAN type you selected in 
IDREF="FM81222"Step 6.PERFORMANCE="REQUIRED"(Optional) Change the "
IDXID="w9746"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"
Error/
IDXID="w9747"BOOK="_idx" COLLECTION="nw41" TIDREF="i1345"
Warning" prompt if you want.PERFORMANCE="REQUIRED"Move the cursor to Step 3 on the configuration form and complete the destination information to move the bindery information in the working directory to the new NetWare 4.1 server.Do not change the server information on the configuration form.PERFORMANCE="REQUIRED"Under Step 3 on the configuration form, press 
MOREINFO="NONE"<Enter> to display a list of destination NetWare 4.1 servers.PERFORMANCE="REQUIRED"Choose the NetWare 4.1 server that you want to migrate the server information to.Choose the NetWare 4.1 server you just installed.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to display a list of selected source volumes and their default destination volumes.Destination volumes that match the source volumes are displayed as the default.PERFORMANCE="REQUIRED"Select a volume and press 
MOREINFO="NONE"<Enter> to specify the destination volume and directory on the NetWare 4.1 server.
PAGENUM=60 ID="BP69"Press 
MOREINFO="NONE"<Ins> to see a list of available volumes and directories on the NetWare 4.1 server. If you specify a directory that does not exist on the NetWare 4.1 server, you are prompted to create it. Volumes must already be created before you can migrate them.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> when you have completed the destination path of the source volume.PERFORMANCE="REQUIRED"Continue to specify destination paths if you have multiple source volumes.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> when you are finished filling out the "Volumes' destination" field.PERFORMANCE="REQUIRED"(Optional) 
ID="FM44846"Under Step 3 on the configuration form, press 
MOREINFO="NONE"<Enter> and choose a password option.If a password is required and the length of the password is zero (0), the migration utility assigns the destination default password length.See the following table for a description of the options.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Password OptionCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Assign random 
passwords  (Default)COLNAME=2 ROTATE="0" MOREROWS="0"A IDXID="w9748"BOOK="_idx" COLLECTION="nw41" TIDREF="i3249"
password for each username that has a password on the source is generated randomly and stored in a file (NEW.PWD) in SYS:SYSTEM on the NetWare 4.1 server.Note:New passwords are given only to users and print servers that had a password on the server.Only users with rights to SYS:SYSTEM have access to this file. Users cannot log in until they are given their passwords from this list.COLNAME=1 ROTATE="0" MOREROWS="0"Assign no passwordsCOLNAME=2 ROTATE="0" MOREROWS="0"After you finish the migration, all users can log in using their previous username. They are not prompted for a password.Users have the option to create their passwords if no password was chosen upon migration.Note: If the user account restrictions require users to have a password, they are prompted to type a new password, which the system verifies.PAGENUM=61 ID="BP70"PERFORMANCE="REQUIRED"Review the fields on the configuration form and make any necessary changes.Do not change the information in the server area.PERFORMANCE="REQUIRED"To proceed with the migration, press 
MOREINFO="NONE"<F10> to display the "Select a Migration Action" menu.PERFORMANCE="REQUIRED"Select "Migrate from Working Directory."All information about the migration scrolls to the screen and goes into a report file, which you can review later.When the migration from the working directory is complete, the migration utility notifies you.PERFORMANCE="REQUIRED"(Conditional) If errors occur during the migration, and you chose to be prompted after errors and warnings, you receive the following error message and must answer the question.
FORMAT="LINESPECIFIC"MOREINFO="NONE"A migration error has occurred and is displayed in the migration log above. Do you want to continue with the migration? (Y=Yes/N=No/I=Ignore Error):COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you chooseCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"YesCOLNAME=2 ROTATE="0" MOREROWS="0"The migration continues. The error is written to the report file, and you are prompted again the next time an error occurs.COLNAME=1 ROTATE="0" MOREROWS="0"NoCOLNAME=2 ROTATE="0" MOREROWS="0"The migration stops. The error is written to the report file. You receive this message:MOREINFO="NONE"Migration from the working directory to the NetWare 4.1 server is complete. Press <Enter> to continue.Press MOREINFO="NONE"<Enter> to return to the "Select Migration Action" menu. From there, press MOREINFO="NONE"<Esc> to edit the fields or choose "Exit" to leave the utility and return to the DOS prompt.COLNAME=1 ROTATE="0" MOREROWS="0"IgnoreCOLNAME=2 ROTATE="0" MOREROWS="0"The migration continues. The error is written to the report file. You are no longer prompted when an error occurs, but all errors are written to the report file.PAGENUM=62 ID="BP71"See 
BOOK="sysmsenu" COLLECTION="nw41"System Messages for explanations of all error messages.When the migration is complete, the following message appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Migration from the working directory to the destination server is complete. Press <Enter> to continue.PERFORMANCE="REQUIRED"(Optional) To view the migration 
IDXID="w9749"BOOK="_idx" COLLECTION="nw41" TIDREF="i3796"
report, choose "View Migration Reports" and continue with 
IDREF="FM84179"Step 42a.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM84179"Select the report for the migration you completed and press 
MOREINFO="NONE"<Enter>.The reports reside in the working directory that you specified earlier.Use the report to help you complete and customize definitions, attributes, and access privileges on the NetWare 4.1 server. If you find errors on your NetWare 4.1 server after the migration, review the migration report to see if you can find where they occurred.The report file is an ASCII text file that consists of the following:MARK=BULLETSummary information of the bindery IDXID="w9750"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
import phase (migrating bindery data from the server to the working directory).Summary information of the bindery export phase (migrating bindery data from the working directory to the NetWare 4.1 server).PAGENUM=63 ID="BP72"Listing of each item in each category that was read from the server.Listing of each item in each category that was written to or created on the NetWare 4.1 server.The number of errors that occurred during the migration.PERFORMANCE="REQUIRED"To exit the report, press 
MOREINFO="NONE"<Esc> once.PERFORMANCE="REQUIRED"To return to the "Select a Migration Action" menu, press 
MOREINFO="NONE"<Esc> again.PERFORMANCE="REQUIRED"To 
IDXID="w9751"BOOK="_idx" COLLECTION="nw41" TIDREF="i1383"
exit the migration utility, select "Exit (return to DOS)."RENDERAS="SECT1"ID="FM29915"What to Do After MigrationAfter the migration is complete, check the NetWare 4.1 server and do the following if they apply:MARK=BULLETUpdate references to the server in the user IDXID="w9752"BOOK="_idx" COLLECTION="nw41" TIDREF="i2217"
login scripts if you changed the server name.Although user login scripts are migrated, they are not modified, and server names and directory paths are not changed to match your new environment.You can use the IDXID="w9753"BOOK="_idx" COLLECTION="nw41" TIDREF="i4631"
UIMPORT utility to migrate IDXID="w9754"BOOK="_idx" COLLECTION="nw41" TIDREF="i4690"
login scripts from bindery-based NetWare to NetWare 4.1 Directory Services (NDS). UIMPORT allows you to import data from an existing database to the NDS database. The migration utility creates the following two files in SYS:SYSTEM on the NetWare 4.1 server:MARK=BULLETUIMPORT.CTLUIMPORT.DATSee "BOOK="superenu" COLLECTION="nw41"Importing User Information into the Directory Services Database" in Supervising the Network for instructions on using UIMPORT.Run IDXID="w9755"BOOK="_idx" COLLECTION="nw41" TIDREF="i4474"
third-party applications. You may have to reinstall them for them to work properly under NetWare 4.1. You may also need to enter new paths in the setup files for any third-party applications. Some applications may not work properly with the migration utility. The following conditions require you to reinstall the application:PAGENUM=64 ID="BP73"MARK=BULLETThe application has a .EXE file that did not migrate.The application is path specific and you have changed the path structure during migration.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:Restrict the application's directory on the NetWare 4.1 server with Object Manager (which replaces DSPACE).Make the directory a fake root with MAP.Update as necessary migrated print queues and print servers. NetWare 4.1 Print Services are different than printing in previous NetWare versions. See "BOOK="printenu" COLLECTION="nw41"PUPGRADE.NLM" in Print Services for further instruction.Check user restrictions and accounting charge rates to make sure your system is configured the way you want it. Set any new 
directory and 
file attributes.If you chose to assign random passwords, you may want to print the NEW.PWD file and distribute the password information to your users. The users should change their passwords immediately.The report, an ASCII text file, shows passwords sorted by date. If users were migrated from more than one server, the current password is the last one listed on the report.Delete any old Value-Added Process (VAP) files. VAPs that are in a directory that you migrate are copied to the NetWare 4.1 server, but IDXID="w9756"BOOK="_idx" COLLECTION="nw41" TIDREF="i4745"
VAPs are not compatible with NetWare 4.1.If you have menus set up, you may have to run a menu conversion program so your menus function properly under NetWare 4.1.LABEL="5"PAGENUM=65 ID="BP74"Upgrade Using In-Place UpgradeRENDERAS="SECT1"IntroductionThis chapter covers the procedures for upgrading an existing NetWare® server using the In-Place Upgrade NLMTM.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="22*"COLNAME=2 COLWIDTH="3*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"TopicCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM81630"Preparing for In-Place Upgrade  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM81630"69COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM53793"Running the In-Place Upgrade Utility  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM53793"82COLNAME=1 ROTATE="0" MOREROWS="0"IDREF="FM83559"What to Do After In-Place Upgrade  COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83559"101RENDERAS="SECT1"OverviewAn In-Place Upgrade allows you to upgrade an existing NetWare 2 server and file system to NetWare 3TM using SERVER.EXE with 2XUPGRDE.NLM.Your NetWare 2.1x server must be running on hardware that meets NetWare 4TM requirements. For more information, IDREF="FM94533"see "Preparing the Server" on page 69.Then, use the NetWare 4.1 installation programto upgrade the NetWare 3 server to NetWare 4.1.RENDERAS="SECT2"How It WorksIDXID="w9757"BOOK="_idx" COLLECTION="nw41" TIDREF="i3160"
Upgrading a NetWare 2 server to NetWare 3 includes two parts:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The file system is upgraded.The new operating system is installed.PAGENUM=66 ID="BP75"Upgrading a NetWare 2 file system includes four phases:NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"The file system is analyzed/inventoried.The disks are analyzed.The disks are modified.A NetWare 3 bindery is created from the NetWare 2 bindery.This 
upgrade 
utility can use either the NetWare 3.11 or 3.12 operating system to convert the NetWare 2 file system into a NetWare 3.1x file system. NetWare 3.12 is the operating system used in the following examples.LABEL="5-1" FLOAT="0"ID="FM32472"Phases in the UpgradeFILEREF="n41up40a.tif"Following is a discussion of what happens during each IDXID="w9758"BOOK="_idx" COLLECTION="nw41" TIDREF="i172"
phase of the upgrade. When you run the upgrade, status messages refer to each of the actions discussed here.RENDERAS="SECT3"Phase 1: System AnalysisThe NetWare 2 file IDXID="w9759"BOOK="_idx" COLLECTION="nw41" TIDREF="i172"
system is analyzed.MARK=BULLETEach disk is inventoried.The system displays what volumes are on each disk.This phase approximates the memory and disk space requirements needed to successfully complete the upgrade.This phase ensures that MAC.NAM is loaded.PAGENUM=67 ID="BP76"RENDERAS="SECT3"Phase 2: Disk AnalysisIDXID="w9760"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"Each NetWare 2 IDXID="w9761"BOOK="_idx" COLLECTION="nw41" TIDREF="i172"
disk is analyzed.MARK=BULLETThe locations of the Hot FixTM Redirection Area, the system and volume areas, the Directory Entry Tables (DETs) and the IDXID="w9762"BOOK="_idx" COLLECTION="nw41" TIDREF="i1448"
File Allocation Tables (
FATs) are determined. A layout of the IDXID="w9763"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"
disk for NetWare 3.12 is created from this information.A list of IDXID="w9764"BOOK="_idx" COLLECTION="nw41" TIDREF="i474"
disk blocks that have to be IDXID="w9765"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"
moved is created.For example, if a block on volume VOL1: is on the disk in a location that is now assigned to volume VOL0:, then the block has to be moved to a location that was assigned to volume VOL1: when the disk layout for NetWare 3.12 was created.The IDXID="w9766"BOOK="_idx" COLLECTION="nw41" TIDREF="i1052"
DETs and IDXID="w9767"BOOK="_idx" COLLECTION="nw41" TIDREF="i1448"
FATs for each volume are translated.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).This phase ensures the system has enough memory and free disk space to complete the upgrade.If the NetWare 2 disks don't 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.)RENDERAS="SECT3"Phase 3: Disk ModificationEach NetWare 2 disk is IDXID="w9768"BOOK="_idx" COLLECTION="nw41" TIDREF="i2492"
modified.MARK=BULLETBlocks are moved to their new locations on the disk. The NetWare 2 system is not functional after this phase begins.The NetWare 3.12 system tables are written to the system area, the partition table is written onto Track 0, and the DETs and FATs for each of the NetWare 3.12 volumes are duplicated.PAGENUM=68 ID="BP77"RENDERAS="SECT3"Phase 4: BinderyID="FM13539"The NetWare 2 IDXID="w9769"BOOK="_idx" COLLECTION="nw41" TIDREF="i4690"
bindery is upgraded to NetWare 3.12.MARK=BULLETMost of the NetWare 2 IDXID="w9770"BOOK="_idx" COLLECTION="nw41" TIDREF="i445"
bindery information is upgraded to NetWare 3.12. Other information that is upgraded includes account restrictions and print queues.NetWare 2 passwords are not retained in the NetWare 3.12 bindery. If you chose to assign new passwords to users, they are created and put into a file called NEW.PWD, located in the SYS: SYSTEM directory.VAPs do not get upgraded. They are unique to NetWare 2 and do not exist in NetWare 3.Third-party VAP functionality is lost during this upgrade. Delete VAP files after the upgrade. Some VAPs can be upgraded to NLMs. Contact your VAP reseller for upgrade information.Core printing services are also not upgraded. After you have finished upgrading to NetWare 3.12, delete print services and re-create them.Volume and disk restrictions for users are not upgraded because of differences between NetWare 2 and NetWare 3 file systems.In NetWare 2 the restrictions were server-wide, whereas in NetWare 3 the restrictions are limited to volumes.PAGENUM=69 ID="BP78"RENDERAS="SECT1"ID="FM81630"Preparing for In-Place UpgradeThere are certain preparations that need to be made to your NetWare 2 server before upgrading to NetWare 3.RENDERAS="SECT2"ID="FM94533"Preparing the ServerRENDERAS="SECT3"PrerequisitesMARK=CHECKBOXID="FM76772"
A NetWare server running NetWare versions 2.10, 2.11, 2.12, 2.15 (revisions a, b, and c), or 2.2.A computer with an 80386 or higher microprocessor. NetWare 3 does not run on an IDXID="w9771"BOOK="_idx" COLLECTION="nw41" TIDREF="i5"
80286 microprocessor.A IDXID="w9772"BOOK="_idx" COLLECTION="nw41" TIDREF="i4215"
backup IDXID="w9773"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
device, such as a tape drive or a DOS device.Enough disk space to accommodate the NetWare 4.1 IDXID="w9774"BOOK="_idx" COLLECTION="nw41" TIDREF="i1641"
file IDXID="w9775"BOOK="_idx" COLLECTION="nw41" TIDREF="i1474"
system. Each volume should have at least 10% free disk space to accommodate the enlarged directory and file allocation tables.To store the NetWare 4.1 operating system files, we recommend you reserve 50 MB on volume SYS:.We recommend that you create at least a 15MB DOS partition on the disk containing volume SYS:.Make sure no disk has more than eight volumes on it.The NetWare 4.1 CD-ROM, which contains the 2XUPGRDE.NLM file.Sufficient server memory to run the utility and upgrade to NetWare 4.1. NetWare 4.1 installation requires a minimum of 12 MB of IDXID="w9776"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"
RAM.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.For more information, see IDREF="FM15438"Appendix A, "Calculating RAM Requirements."PAGENUM=70 ID="BP79"Sufficient time to upgrade your server. This depends on the following conditions:MARK=BULLETThe number of hard disks, not including mirrored disksThe amount of disk space in useIf you have several hard disks and a lot of disk space in use, the 
upgrade could take several hours.(Optional) NetWare for 
Macintosh (if you want to support Macintosh files on your network).If you are running NetWare 2 using an 80286 microprocessor, upgrade your computer to an 80386 or higher microprocessor.IDXID="w9777"BOOK="_idx" COLLECTION="nw41" TIDREF="i392"
Back up your NetWare 2 system twice to ensure that you have a good backup.A backup is essential if you must restore your NetWare 2 system.Restore any deleted (but not purged) files you may need in the future.Make sure all users are logged out and all files (except bindery files) are closed during the upgrade.Make sure all print servers are logged out.You may need updated disk and LAN drivers to run NetWare 4.1. If you have third-party drivers, check with the manufacturer before you upgrade to see if you have compatible versions.For more information on driversMARK=BULLETContact your Novell Authorized ResellerTM representative or consultant, or call 1-800-NETWARE for the list of currently supported drivers.Download from NetWireTM a list of currently supported drivers. (For more information about NetWire, see "BOOK="cncptenu" COLLECTION="nw41"NetWire" in Concepts or contact your Novell Authorized Reseller representative.)Call Novell LabsTM at 1-800-429-5544 for a list of drivers that have been certified as "Yes, Tested and Approved" with NetWare 4.1.PAGENUM=71 ID="BP80"If you are using the IDE.DSK disk driver, you cannot add a DOS partition to an upgraded NetWare 3 disk.  Claiming a DOS partition with IDXID="w9778"BOOK="_idx" COLLECTION="nw41" TIDREF="i1438"
FDISK on an upgrade 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 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 parameters from the NetWare 2 partition on the IDE disk drive.RENDERAS="SECT2"ID="FM83009"Choosing In-Place Upgrade Options
IDXID="w9779"BOOK="_idx" COLLECTION="nw41" TIDREF="i3931"Before you start the 
upgrade, decide whether you willMARK=BULLETRun the upgrade interactively or as a batch processCreate space for a DOS partitionAssign randomly generated or IDXID="w9780"BOOK="_idx" COLLECTION="nw41" TIDREF="i302"
fixed IDXID="w9781"BOOK="_idx" COLLECTION="nw41" TIDREF="i3249"
passwords to usersRun the /BINDERY optionThe following sections discuss each of your IDXID="w9782"BOOK="_idx" COLLECTION="nw41" TIDREF="i2433"
options to help you make your decisions, and then give you the instructions for completing each possible task.RENDERAS="SECT3"Run the Upgrade InteractivelyIDXID="w9783"BOOK="_idx" COLLECTION="nw41" TIDREF="i1846"When you run the upgrade interactively, you are prompted 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.All status messages and error messages are displayed.PAGENUM=72 ID="BP81"If you are a first-time installer, use the interactive method so you can follow each phase of the upgrade.For example, to run the upgrade interactively, at the console prompt, you would typeMOREINFO="NONE"LOAD A:IDXID="w9784"BOOK="_idx" COLLECTION="nw41" TIDREF="i2"
2XUPGRDE MOREINFO="NONE"<Enter>RENDERAS="SECT3"Run the Upgrade as a Batch ProcessIDXID="w9785"BOOK="_idx" COLLECTION="nw41" TIDREF="i420"When you run the upgrade utility 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 in IDREF="FM35934"Table 5-1 to indicate if you want the utility to create space for a DOS partition and to create and assign new passwords to users. If no options are specified, the defaults are used. You are not prompted for these options later.If you are an experienced installer and have run several upgrades, use the batch process method, especially if you are upgrading several servers.For example, to run the upgrade as a batch process, at the console prompt, you would typeLOAD A:2XUPGRDE /parameterMOREINFO="NONE" <Enter>Replace parameter with any in the following table.LABEL="5-1" PGWIDE=0 TOCENTRY="1"ID="FM35934" In-Place Upgrade Optional ParametersCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="6*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ID="FM32100"ParameterCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"B or  BATCHCOLNAME=2 ROTATE="0" MOREROWS="0"Runs the upgrade in batch mode.COLNAME=1 ROTATE="0" MOREROWS="0"B2 or  BATCHCOLNAME=2 ROTATE="0" MOREROWS="0"Runs the upgrade in batch mode, not pausing for non- critical errors.COLNAME=1 ROTATE="0" MOREROWS="0"BINDERYCOLNAME=2 ROTATE="0" MOREROWS="0"Skips to Phase 4 to upgrade the NetWare 2 bindery only.COLNAME=1 ROTATE="0" MOREROWS="0"F or  FASTCOLNAME=2 ROTATE="0" MOREROWS="0"Skips the lengthy memory and free disk space check.COLNAME=1 ROTATE="0" MOREROWS="0"H, ?, or  HELPCOLNAME=2 ROTATE="0" MOREROWS="0"Shows a list of parameters.COLNAME=1 ROTATE="0" MOREROWS="0"NORESTARTCOLNAME=2 ROTATE="0" MOREROWS="0"Restart data is not saved to disk.COLNAME=1 ROTATE="0" MOREROWS="0"PASSWORD=COLNAME=2 ROTATE="0" MOREROWS="0"Assigns a fixed password to all users.COLNAME=1 ROTATE="0" MOREROWS="0"P0COLNAME=2 ROTATE="0" MOREROWS="0"Does not create a DOS partition.COLNAME=1 ROTATE="0" MOREROWS="0"PxCOLNAME=2 ROTATE="0" MOREROWS="0"Creates a DOS partition on the disk containing volume SYS: (x=partition size in megabytes)Size range: 0 to 32 MB  Default: 15 MBCOLNAME=1 ROTATE="0" MOREROWS="0"R+COLNAME=2 ROTATE="0" MOREROWS="0"Assigns randomly generated passwords.COLNAME=1 ROTATE="0" MOREROWS="0"R-COLNAME=2 ROTATE="0" MOREROWS="0"Does not assign random passwords (default).PAGENUM=73 ID="BP82"You can enter the IDXID="w9786"BOOK="_idx" COLLECTION="nw41" TIDREF="i3213"
parameters in any order. IDXID="w9787"BOOK="_idx" COLLECTION="nw41" TIDREF="i3213"
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 randomly generated passwords, type:FORMAT="LINESPECIFIC"MOREINFO="NONE"MOREINFO="NONE"LOAD A:2XUPGRDE /B /P5 /R+ MOREINFO="NONE"<Enter>Continue with IDREF="FM53793""Running the In-Place Upgrade Utility" on page 82.RENDERAS="SECT3"Run the /BINDERY optionThe /BINDERY option allows you to restart the upgrade, skipping directly to the Bindery phase.The NLM looks for the NetWare 2 bindery files (NET$BIND.SYS and NET$BVAL.SYS) in the SYS:SYSTEM directory and merges them into the NetWare 3 bindery (NET$OBJ.SYS, NET$PROP.SYS, and NET$VAL.SYS).PAGENUM=74 ID="BP83"If your NetWare 2 bindery files are corrupt, simply rename the NET$BIND.OLD and NET$BVAL.OLD files (created when you ran the BINDFIX utility) with the .SYS extension, and then restart the upgrade with the /BINDERY option.If volume SYS: didn't mount, the NetWare 2 bindery did not get upgraded. One situation which may cause the volume not to mount occurs when you have insufficient server memory in the Cache Buffers memory pool.This is caused by the Permanent and Alloc memory pools not releasing memory back to the Cache Buffers. It is remedied by rebooting the server or adding more memory.With the initial release of the In-Place Upgrade NLM, the solution was to re-create the bindery from scratch or to restore the system from backups, fix the problem, and then restart the upgrade. This new option allows you to restart the upgrade, skipping directly to the Bindery phase.When using the /BINDERY option, 
trustee assignments for all users, except SUPERVISOR and GUEST, are lost. Use the NetWare 3 GRANT utility or the NetWare 4.1 RIGHTS utility to restore trustee rights.RENDERAS="SECT2"Prepare to Bring Down the NetWare 2 ServerKeep a record of your hardware configuration information to be used at a later stage of the upgrade, as well as for future reference.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the NetWare 2 server system console prompt (:), typeFORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w9788"BOOK="_idx" COLLECTION="nw41" TIDREF="i736"
CONFIG MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"ID="FM67793"Copy the following 
ID="FMINFOR"information from the server screen:
MARK=BULLETServer nameIDXID="w9789"BOOK="_idx" COLLECTION="nw41" TIDREF="i2026"
LAN configuration information (including the network address)IDXID="w9790"BOOK="_idx" COLLECTION="nw41" TIDREF="i614"
Disk IDXID="w9791"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"
channel IDXID="w9792"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"
configuration IDXID="w9793"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"
informationPERFORMANCE="REQUIRED"From a workstation, run 
IDXID="w9794"BOOK="_idx" COLLECTION="nw41" TIDREF="i462"
BINDFIX.You must have rights to the SYS:SYSTEM directory to run BINDFIX. PAGENUM=75 ID="BP84"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.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, see "BINDFIX" in 
NetWare 2.2 Using the Network or 
NetWare 3.12 Utilities Reference.PERFORMANCE="REQUIRED"IDXID="w9795"BOOK="_idx" COLLECTION="nw41" TIDREF="i1211"
Bring down the 2.1
x 
IDXID="w9796"BOOK="_idx" COLLECTION="nw41" TIDREF="i1215"
server.At the system console (:), type
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>ID="FM81041"Do not bring IDXID="w9797"BOOK="_idx" COLLECTION="nw41" TIDREF="i2824"
down the server simply by turning off its power. This creates errors when upgrading to a NetWare 3 file system.  After the server responds that it is down, wait two to three minutes to be sure that all transactions to the system files are complete before turning the machine off.  Once you've received the "Server servername has been shut down" message, type "Exit" to return to DOS.PERFORMANCE="REQUIRED"Run VREPAIR.From the downed server, run the NetWare 2 VREPAIR utility on each volume.See the NetWare 2 VREPAIR documentation for further instructions.RENDERAS="SECT2"Creating the Upgrade Diskette from CD-ROMBefore performing an In-Place Upgrade, an upgrade diskette must be created from the NetWare 4.1 CD-ROM. To create this diskette, complete the following steps.PERFORMANCE="REQUIRED"Format a high density diskette and make it bootable. For example, from your DOS workstation you would type:FORMAT="LINESPECIFIC"MOREINFO="NONE"FORMAT A: /S MOREINFO="NONE"<Enter>
PAGENUM=76 ID="BP85"PERFORMANCE="REQUIRED"Copy the 
IDXID="w9798"BOOK="_idx" COLLECTION="nw41" TIDREF="i1549"
DOS partitioning and formatting utilities onto the diskette. For example, if your workstation's DOS is located in C:\DOS, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"COPY C:\DOS\FDISK.COM A: MOREINFO="NONE"<Enter>
COPY C:\DOS\FORMAT.COM A: 
MOREINFO="NONE"<Enter>If you are using IDXID="w9799"BOOK="_idx" COLLECTION="nw41" TIDREF="i1217"
DR DOS, make sure the version of IDXID="w9800"BOOK="_idx" COLLECTION="nw41" TIDREF="i1545"
FORMAT.COM you use is dated 12/6/91 or later before you format the DOS partition on the hard disk after an upgrade.PERFORMANCE="REQUIRED"Copy the upgrade files from the CD-ROM onto the bootable upgrade diskette. For example, from your DOS workstation, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"COPY CD-ROM_drive:\UPGRADE\*.* A: MOREINFO="NONE"<Enter>RENDERAS="SECT2"ID="FM53275"Loading NetWare 3.12IDXID="w9801"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"PERFORMANCE="REQUIRED"Insert the bootable 
upgrade diskette into drive A:.PERFORMANCE="REQUIRED"ID="FM72576"Turn the server off and then on again.The computer now boots with the version of DOS on the upgrade diskette.If you are IDXID="w9802"BOOK="_idx" COLLECTION="nw41" TIDREF="i1187"
creating a DOS partition on the hard disk, record the information you enter in the following steps. You use this information again later.PERFORMANCE="REQUIRED"With the upgrade diskette in drive A:, load the NetWare 3.12 operating system by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"A:SERVER MOREINFO="NONE"<Enter>You receive a message similar to the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Loading...
System Console
Novell NetWare v3.12 
Processor speed: 193 
(Type SPEED at the command prompt for an explanation of the speed rating)
File server IDXID="w9803"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
name:PAGENUM=77 ID="BP86"Don't type "SPEED" at this prompt (unless you want to name the server "SPEED").  For an explanation of the IDXID="w9804"BOOK="_idx" COLLECTION="nw41" TIDREF="i4226"
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.PERFORMANCE="REQUIRED"ID="FM15291"IDXID="w9805"BOOK="_idx" COLLECTION="nw41" TIDREF="i2606"
Name the server by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"servername MOREINFO="NONE"<Enter>Use your NetWare 2.1x servername so that you do not have to change any login files, map statements, or batch files.PERFORMANCE="REQUIRED"IDXID="w9806"BOOK="_idx" COLLECTION="nw41" TIDREF="i1856"
Assign an 
IDXID="w9807"BOOK="_idx" COLLECTION="nw41" TIDREF="i301"
IPXTMIDXID="w9808"BOOK="_idx" COLLECTION="nw41" TIDREF="i1936"
internal 
IDXID="w9809"BOOK="_idx" COLLECTION="nw41" TIDREF="i2839"
network 
IDXID="w9810"BOOK="_idx" COLLECTION="nw41" TIDREF="i3022"
number to the server.At the cursor prompt, type the IPX internal network number and press 
MOREINFO="NONE"<Enter>.The NetWare 3.12 console prompt (:) appears. The remaining steps are executed from the console prompt.The IPX internal network number does not exist in a NetWare 2 network. In NetWare 3 and 4, it is a logical network number that identifies the individual server.This number must be different from other IPX external network numbers (for cabling systems) or IPX internal network numbers (for NetWare 3 or 4 servers).The IPX internal network number for each server must be
MARK=BULLETUniqueHexadecimal (base 16, using numerals 0 through 9 and letters A through F)One to eight digits longPERFORMANCE="REQUIRED"ID="FM28295"
Load each 
IDXID="w9811"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
disk driver by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD A:disk_driver MOREINFO="NONE"<Enter>
PAGENUM=78 ID="BP87"Replace the NetWare 2 
disk_driver with one of the NetWare 3.12 drivers shown in the right column of 
IDREF="FM66920"Table 5-2.
IDXID="w9812"BOOK="_idx" COLLECTION="nw41" TIDREF="i1335"LABEL="5-2" PGWIDE=1 TOCENTRY="1"ID="FM66920" NetWare 3.12 Disk DriversCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="8*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Computer architectureCOLNAME=2 ROTATE="0" MOREROWS="0"Disk controller typeCOLNAME=3 ROTATE="0" MOREROWS="0"NetWare 3.12 disk driver (*.DSK)VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Industry Standard Architecture (ISA)COLNAME=2 ROTATE="0" MOREROWS="0"AT, MFM, RLL, ARLLESDIIDECOLNAME=3 ROTATE="0" MOREROWS="0"ISADISKISADISK /bISADISK /b /l (lowercase "L")IDE.DSK (You cannot add a DOS partition to an upgraded NetWare 3 or 4 IDE disk.)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Novell disk coprocessor boardCOLNAME=3 ROTATE="0" MOREROWS="0"DCBCOLNAME=1 ROTATE="0" MOREROWS="0"MicrochannelCOLNAME=2 ROTATE="0" MOREROWS="0"ESDIMFMIBM* SCSICOLNAME=3 ROTATE="0" MOREROWS="0"PS2ESDIPS2MFMPS2OPT  (replaces PS2SCSI)COLNAME=1 ROTATE="0" MOREROWS="0"Extended Industry Standard Architecture (EISA)COLNAME=2 ROTATE="0" MOREROWS="0"AT classCOLNAME=3 ROTATE="0" MOREROWS="0"ISADISKCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"EISA vendor proprietaryCOLNAME=3 ROTATE="0" MOREROWS="0"See vendor.COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"Other devices may be supported. Contact the device manufacturer to find out if it has a NetWare 3.12- supported driver.To decide which disk drivers to load, look at the disk channel configuration information you recorded in 
IDREF="FM67793"Step 2 on page 74. Load the equivalent 3.12 disk driver.
PAGENUM=79 ID="BP88"Third-party disk driver manufacturers include
TYPE="VERT"AdaptecADICAlways TechnologyBus LogicData Technology Corp.DPTFuture DomainQuantumUltraStorIf you have 

third-party 

drivers, you may need to update them to run NetWare 3.12. Check with the manufacturer before you upgrade to check whether your drivers are compatible versions. If they are not compatible, you must update the drivers before you continue with the upgrade.Load the IDXID="w9813"BOOK="_idx" COLLECTION="nw41" TIDREF="i4474"
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.PERFORMANCE="REQUIRED"Answer the disk driver configuration information prompts by typing in the information you recorded in 
IDREF="FM67793"Step 2 on page 74.In NetWare 2, the interrupt number was decimal. In NetWare 3, the interrupt number is hexadecimal.PERFORMANCE="REQUIRED"(Optional) To test 
IDXID="w9814"BOOK="_idx" COLLECTION="nw41" TIDREF="i4474"
third-party 
IDXID="w9815"BOOK="_idx" COLLECTION="nw41" TIDREF="i4474"
LAN drivers for compatibility, load them by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD A:LAN_driver MOREINFO="NONE"<Enter>Replace 
LAN_driver with a 
IDXID="w9816"BOOK="_idx" COLLECTION="nw41" TIDREF="i4474"
third-party NetWare 3.12 
IDXID="w9817"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
LAN driver.
PAGENUM=80 ID="BP89"IDREF="FM76354"Table 5-3 lists all 
IDXID="w9818"BOOK="_idx" COLLECTION="nw41" TIDREF="i1335"
LAN drivers supported by Novell®.
IDXID="w9819"BOOK="_idx" COLLECTION="nw41" TIDREF="i2827"LABEL="5-3" PGWIDE=1 TOCENTRY="1"ID="FM76354" NetWare 3.12 LAN DriversCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="11*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Cabling SystemCOLNAME=2 ROTATE="0" MOREROWS="0"Network BoardCOLNAME=3 ROTATE="0" MOREROWS="0"NetWare 3.12 LAN Driver (*.LAN)VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ARCnet*COLNAME=2 ROTATE="0" MOREROWS="0"RX-NetTM  RX-Net IITM  RX-Net/2TMCOLNAME=3 ROTATE="0" MOREROWS="0"TRXNETCOLNAME=1 ROTATE="0" MOREROWS="0"EthernetCOLNAME=2 ROTATE="0" MOREROWS="0"NE/2TM  NE/2TTMCOLNAME=3 ROTATE="0" MOREROWS="0"NE2COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE/2-32TMCOLNAME=3 ROTATE="0" MOREROWS="0"NE2_32 (replaces NE2-32)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE1000TM---ASSY 950-054401  NE1000---ASSY 810-160-001COLNAME=3 ROTATE="0" MOREROWS="0"NE1000COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE2000TM---ASSY 810-149  NE2000T---ASSY 810-000220  NE2000 PlusCOLNAME=3 ROTATE="0" MOREROWS="0"NE2000COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE2100TM---ASSY 810-000209COLNAME=3 ROTATE="0" MOREROWS="0"NE2100COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE1500T---ASSY 810000214COLNAME=3 ROTATE="0" MOREROWS="0"NE1500TCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE3200TMCOLNAME=3 ROTATE="0" MOREROWS="0"NE3200COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE32HUBTMCOLNAME=3 ROTATE="0" MOREROWS="0"NE32HUBCOLNAME=1 ROTATE="0" MOREROWS="0"Token RingCOLNAME=2 ROTATE="0" MOREROWS="0"NTR2000TMCOLNAME=3 ROTATE="0" MOREROWS="0"NTR2000Do not upgrade if the LAN drivers are not compatible. Call the manufacturer to get an updated version of the driver.If you experience problems with third-party drivers, contact the manufacturer listed in the driver description that appears when you load the driver.For more information on LAN drivers
MARK=BULLETContact your Novell Authorized Resellerrepresentative or consultant, or call 1-800-NETWARE for the list of currently supported drivers.MARK=BULLETDownload from NetWire a list of currently supported drivers. (For more information about NetWire, see "BOOK="cncptenu" COLLECTION="nw41"NetWire" in Concepts or contact your Novell Authorized Reseller representative.PAGENUM=81 ID="BP90"Call Novell Labs at 1-800-429-5544 for a list of drivers that have been certified as "Yes, Tested and Approved" with NetWare 4.1.PERFORMANCE="REQUIRED"(Optional) Answer the LAN driver configuration information prompts by entering the information you recorded in 
IDREF="FM67793"Step 2 on page 74.If the LAN driver loads, it can communicate with the network board and is compatible with NetWare 3.12.If the LAN driver does 
not load, either it is incompatible with NetWare 3.12 or the configuration is wrong. The following message appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"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.PERFORMANCE="REQUIRED"(Optional) 
IDXID="w9820"BOOK="_idx" COLLECTION="nw41" TIDREF="i4664"
Unload the third-party LAN drivers to free more memory for the upgrade by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"UNLOAD LAN_driver MOREINFO="NONE"<Enter>If the LAN driver is left loaded and bound to a protocol, extra memory may be needed as the upgraded volume SYS: is mounted. The bindery will grow to record all servers on the network.PERFORMANCE="REQUIRED"With the upgrade diskette in drive A:, load 

Macintosh name space support by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD A:MAC MOREINFO="NONE"<Enter>Loading the Macintosh name space module ensures that all volumes are mounted properly at the Phase 4 bindery step.PERFORMANCE="REQUIRED"Continue the upgrade by determining which upgrade option you want to use. See 
IDREF="FM83009""Choosing In-Place Upgrade Options" on page 71.
PAGENUM=82 ID="BP91"RENDERAS="SECT1"ID="FM53793"ID="FM55694"Running the In-Place Upgrade UtilityThe optional parameters shown in IDREF="FM35934"Table 5-1 on page 72 can be entered whether the upgrade is run interactively or as a batch process.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"(Conditional) To run the upgrade interactively, make sure the upgrade diskette is in drive A: and typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD A:IDXID="w9821"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
2XUPGRDE MOREINFO="NONE"<Enter>A warning screen appears. You are asked:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Do you have a recent backup of your server? ySkip to 
IDREF="FM26175"Step 3.PERFORMANCE="REQUIRED"(Conditional) To run the upgrade as a batch process, make sure the upgrade diskette is in drive A: and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w9822"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
LOAD A:2XUPGRDE optional parameter(s) MOREINFO="NONE"<Enter>Replace optional parameters with any of the parameters listed in 
IDREF="FM35934"Table 5-1.PERFORMANCE="REQUIRED"ID="FM26175"To proceed with the upgrade, type
 "Y."If the procedure runs correctly (that is, if there are no disk head crashes), you will not need to restore your NetWare 2 file system from the backup.  However, if a failure occurs, you may need to restore your disk to its previous condition.PERFORMANCE="REQUIRED"At the prompt, type the number of megabytes you want for the DOS partition and press 
MOREINFO="NONE"<Enter>.You must create a DOS partition if you do not have one. NetWare 4.1 requires a minimum 15MB DOS partition.The In-Place Upgrade can create the space (between 0 and 32 MB) for a IDXID="w9823"BOOK="_idx" COLLECTION="nw41" TIDREF="i873"
DOS partition on the disk that contains volume SYS:.  Booting the server from a DOS partition is significantly faster than booting from a diskette. Most servers cannot access a DOS partition from an external hard disk.PAGENUM=83 ID="BP92"If there is not enough space on your disk to create a DOS partition, the upgrade stops and displays the following:
FORMAT="LINESPECIFIC"MOREINFO="NONE"This NetWare server has insufficient free hard disk space to complete the upgrade. The In-Place Upgrade process is now being aborted.Reboot the 2.1
x server, and then restart the upgrade. Delete 
IDXID="w9824"BOOK="_idx" COLLECTION="nw41" TIDREF="i988"
unnecessary files to free more space on the disk, and then restart the upgrade.After you create the DOS partition, the "System Analysis" screens appear."System Analyisis" screen 1 details the System Analysis phase where each disk is scanned and inventoried."System Analysis" screen 2 details the second portion of the System Analysis phase: the inventory process. Free memory and disk space are inventoried to ensure that the server has sufficient resources to complete the upgrade.This is done by imitating the Disk Analysis phase for each disk. Servers with only one disk proceed directly to Phase 2 (
IDXID="w9825"BOOK="_idx" COLLECTION="nw41" TIDREF="i172"
Disk Analysis) where they are inventoried.The calculations made during Phase 1 (System Analysis) are discarded in order to conserve server memory."Disk Analysis" screen 1 details the first portion of the 
IDXID="w9826"BOOK="_idx" COLLECTION="nw41" TIDREF="i1110"
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.Servers with only one hard disk proceed directly to the second part of the Disk Analysis phase.The calculations made during the first part of the Disk Analysis phase are discarded to conserver server memory.The Disk Analysis phase analyzes each disk. An image of the new NetWare 3.12 disk is built and stored in memory.This phase is nondestructive and will not damage the existing NetWare 2 file system.
PAGENUM=84 ID="BP93"The "Disk Modification" screen details the Disk Modification phase. In this phase, the NetWare 2 file system is overwritten by the NetWare 3.12 file system.The Disk Modification phase is the only destructive phase of the upgrade. This phase must be completed before NetWare 3.12 can use the disk.PERFORMANCE="REQUIRED"At the "Disk Modification" screen, type "Y" to continue with the upgrade or type "N" to quit.If you have multiple disks, the Disk Analysis and Disk Modification phases repeat themselves.After all the disks have been upgraded, volume SYS: is mounted and the bindery is upgraded . The NetWare 2 bindery is merged into the newly created NetWare 3.12 bindery.The 
IDXID="w9827"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
Bindery phase updates bindery objects, properties, and values such as user accounts and passwords.Randomly generated passwords are assigned if requested (see 
IDREF="FM60498"Step 6).
PAGENUM=85 ID="BP94"LABEL="5-2" FLOAT="0"ID="FM73427"Bindery ScreenFILEREF="n41up33a.tif"PERFORMANCE="REQUIRED"ID="FM60498"(Conditional) In the process of assigning passwords, if you did not use the [R+] or [R-] or [B] or [PASSWORD =] parameters when you started the upgrade, you are prompted to choose a password option.
PAGENUM=86 ID="BP95"Choose one of the following password options:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Password OptionCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Do not assign any passwordsCOLNAME=2 ROTATE="0" MOREROWS="0"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.COLNAME=1 ROTATE="0" MOREROWS="0"Assign a unique randomly generated password to each user.COLNAME=2 ROTATE="0" MOREROWS="0"A IDXID="w9828"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
random password for each user who originally had originally had a password is created by the utility and stored in a file called NEW.PWD.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 listCOLNAME=1 ROTATE="0" MOREROWS="0"Assign the same password to all users.COLNAME=2 ROTATE="0" MOREROWS="0"The same password is assigned to each user who originally had a password. This password is created by the utility and stored in a file called NEW.PWD.The "Status" screen appears, displaying how your disks and volumes were affected by the upgrade. See IDREF="FM99644"Figure 5-4 for an example.PAGENUM=87 ID="BP96"LABEL="5-3" FLOAT="0"Status ScreenFILEREF="n41up34a.tif"The NetWare 2 file system has been upgraded to a NetWare 3 file system.PERFORMANCE="REQUIRED"Press any key to receive further instructions and then return to the console prompt (:). The upgrade confirmation screen appears (see 
IDREF="FM99644"Figure 5-4).
PAGENUM=88 ID="BP97"LABEL="5-4" FLOAT="0"ID="FM99644"Upgrade Confirmation ScreenFILEREF="n41up35a.tif"RENDERAS="SECT2"Mount VolumesRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Mount volume SYS: and other volumes by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"MOUNT ALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Temporarily prevent users from logging in by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"DISABLE LOGIN MOREINFO="NONE"<Enter>This prevents users from logging in as SUPERVISOR.To allow users to log in when the upgrade is completed, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"ENABLE LOGIN MOREINFO="NONE"<Enter>
PAGENUM=89 ID="BP98"RENDERAS="SECT2"Load LAN DriversRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Insert the CLASS=DISKSystem_2 diskette into drive A:.PERFORMANCE="REQUIRED"Load the appropriate LAN drivers by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD A:LAN_driver MOREINFO="NONE"<Enter>For more information on drivers"
MARK=BULLETContact your Novell Authorized Reseller representative or consultant, or call 1-800-NETWARE for the list of currently supported drives.MARK=BULLETDownload from NetWire a list of currently supported drivers. (For more information about NetWire, see "BOOK="cncptenu" COLLECTION="nw41"NetWire" in Concepts or contact your Novell Authorized Reseller representative.)Call Novell Labs at 1-800-429-5544 for a list of drivers that have been certified as "Yes, Tested and Approved" with NetWare 4.1.The default frame type for NetWare 4.1 is 

802.2. To use the 

Ethernet 

802.3 frame type, add "frame=Ethernet 802.3" when loading the LAN driver.For example, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD A:NE2000 frame=Ethernet_802.3 MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Bind LAN drivers to the server's registered protocol.For example, to bind IPX to the NE2000 LAN driver, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IPX TO NE2000 MOREINFO="NONE"<Enter>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, you would type
FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IPX TO NE2000 frame=Ethernet_802.3 MOREINFO="NONE"<Enter>
PAGENUM=90 ID="BP99"RENDERAS="SECT2"Copy SYSTEM and PUBLC FilesRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Load INSTALL.NLM from the CD-ROM by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>Be sure to use the new INSTALL.NLM, located in the SERVER.312 directory. To avoid confusion, delete the old INSTALL.NLM, located in the SYS:SYSTEM directory.PERFORMANCE="REQUIRED"Select "System Options."PERFORMANCE="REQUIRED"Select "Copy System and Public Files" from the "Available System Options" menu.PERFORMANCE="REQUIRED"Insert diskettes as prompted.RENDERAS="SECT2"Create a STARTUP.NCF FileA STARTUP.NCF file contains commands to load the disk drivers and name space support for your server.This file is executed after SERVER.EXE and is stored on the disk you boot from (hard disk or floppy diskette).Once this file loads the disk drivers and name space support, and mounts volume SYS:, it turns control over to the AUTOEXEC.NCF file to complete the boot process.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Insert the writable CLASS=DISKSystem_1 diskette into drive A:.PERFORMANCE="REQUIRED"Select "Create STARTUP.NCF File" from the "Available System Options" menu.
PAGENUM=91 ID="BP100"PERFORMANCE="REQUIRED"Enter the proper drive letter on the "Path For STARTUP.NCF File" screen.Backspace as necessary to make sure the drive is set to:
MARK=BULLETC: to boot from hard disk.MARK=BULLETA: to boot from drive A:. (This file can be copied to drive C: later.)PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter>.A screen similar to the following appears:LABEL="5-5" FLOAT="0"Sample STARTUP.NCF FileFILEREF="n41up97a.tif"The operating system reads the information you previously entered for disk drivers and name space support.PERFORMANCE="REQUIRED"From the following table, determine your system configuration and decide which additional commands you would like added to the 
STARTUP.NCF file.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Add these or other commandsVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Load name spaces for Macintosh, OS/2, UNIX, or FTAMCOLNAME=2 ROTATE="0" MOREROWS="0"LOAD MAC.NAM LOAD OS2.NAM LOAD NFS.NAM LOAD FTAM.NAM(These commands must precede the command to mount the volume that stores the files using the name space.)COLNAME=1 ROTATE="0" MOREROWS="0"Set server parametersCOLNAME=2 ROTATE="0" MOREROWS="0"(You can add the following eight commands to the 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 Buffer 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 "BOOK="utlrfenu" COLLECTION="nw41"SET" in IDXID="w9829"BOOK="_idx" COLLECTION="nw41" TIDREF="i4089"Utilities Reference, or type "SET" at the server console.)COLNAME=1 ROTATE="0" MOREROWS="0"Pause after each commandCOLNAME=2 ROTATE="0" MOREROWS="0"PAUSEPAGENUM=92 ID="BP101"PERFORMANCE="REQUIRED"Type one command per line.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to save the file.RENDERAS="SECT2"Create an AUTOEXEC.NCF FileAn AUTOEXEC.NCF file contains commands to complete the boot process after SERVER.EXE and STARTUP.NCF execute.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.You can use AUTOEXEC.NCF commands to do the following:MARK=BULLETName the server.Assign the server's IPX internal network number.Load LAN drivers for the server and assign the network number.Bind LAN drivers to the server's registered protocol.PAGENUM=93 ID="BP102"Load other modules you want loaded when the server boots.Execute other console commands (such as TRACK ON or VOLUMES) during the boot process.Set other parameters for the server. (See "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.)Mount volumes.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Available System Options" menu, select "Create AUTOEXEC.NCF File."The operating system gathers
 for this file information you have previously entered at the console prompt.A screen similar to the following appears, showing the commands that are automatically placed in the AUTOEXEC.NCF file.LABEL="5-6" FLOAT="0"Sample AUTOEXEC.NCF FileFILEREF="n41up98a.tif"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 "BOOK="utlrfenu" COLLECTION="nw41"INSTALL" in Utilities Reference.PAGENUM=94 ID="BP103"PERFORMANCE="REQUIRED"(Optional) From the following table, decide which loadable modules to load with AUTOEXEC.NCF.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Add these commandsVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Create 
disk partitions, create volumes, format a disk, etc.COLNAME=2 ROTATE="0" MOREROWS="0"LOAD INSTALLCOLNAME=1 ROTATE="0" MOREROWS="0"Lock the server console, view network operation information, etc.COLNAME=2 ROTATE="0" MOREROWS="0"LOAD MONITORCOLNAME=1 ROTATE="0" MOREROWS="0"Load the print server and establish print servicesCOLNAME=2 ROTATE="0" MOREROWS="0"LOAD PSERVERCOLNAME=1 ROTATE="0" MOREROWS="0"Correct volume problems or remove name space entries from the File Allocation Table and Directory Entry TableCOLNAME=2 ROTATE="0" MOREROWS="0"LOAD VREPAIRTo delete or modify commands, backspace to erase the command.PERFORMANCE="REQUIRED"(Optional) From your system configuration, determine additional loadable module commands to include in the AUTOEXEC.NCF file.Additional module types are listed in the table below.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Module TypeCOLNAME=2 ROTATE="0" MOREROWS="0"Module NameVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"UPS equipmentCOLNAME=2 ROTATE="0" MOREROWS="0"UPS.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"Remote consoleCOLNAME=2 ROTATE="0" MOREROWS="0"REMOTE.NLM  RSPX.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"Remote boot for token ringCOLNAME=2 ROTATE="0" MOREROWS="0"TOKENRPL.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"Remote boot for IBM and Western Digital on EthernetCOLNAME=2 ROTATE="0" MOREROWS="0"ETHERRPL.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"Third-party loadable modulesCOLNAME=2 ROTATE="0" MOREROWS="0"(See third-party documentation)If you use an uninterruptible power supply, see "BOOK="utlrfenu" COLLECTION="nw41"UPS" in Utilities Reference for troubleshooting tips.PAGENUM=95 ID="BP104"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.PERFORMANCE="REQUIRED"From the table below, decide if you want any of the following console commands to execute with the 
IDXID="w9830"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"
AUTOEXEC.NCF file.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Add these commandsVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Implement security measuresCOLNAME=2 ROTATE="0" MOREROWS="0"SECURE CONSOLECOLNAME=1 ROTATE="0" MOREROWS="0"Display the processor speedCOLNAME=2 ROTATE="0" MOREROWS="0"SPEEDPERFORMANCE="REQUIRED"Decide from the table below additional commands you want to add to the AUTOEXEC.NCF file.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"Add these or other commandsVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Mount volumesCOLNAME=2 ROTATE="0" MOREROWS="0"MOUNT VOL1 (or other volume name)  MOUNT ALLNote: Volume SYS: is mounted automatically when its corresponding disk driver is loaded during the STARTUP.NCF file's execution.COLNAME=1 ROTATE="0" MOREROWS="0"Bind protocols other than IPX to the LAN driversCOLNAME=2 ROTATE="0" MOREROWS="0"BIND IP to...COLNAME=1 ROTATE="0" MOREROWS="0"Set server parametersCOLNAME=2 ROTATE="0" MOREROWS="0"SET commands (see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference)COLNAME=1 ROTATE="0" MOREROWS="0"Pause after each commandCOLNAME=2 ROTATE="0" MOREROWS="0"PAUSEPAGENUM=96 ID="BP105"PERFORMANCE="REQUIRED"(Optional) Allow unencrypted passwords.Use the table below to help you decide whether to use unencrypted passwords on a network using encrypted passwords.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ForCOLNAME=2 ROTATE="0" MOREROWS="0"UseVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"A new installation with one server on the networkCOLNAME=2 ROTATE="0" MOREROWS="0"Encrypted passwords.COLNAME=1 ROTATE="0" MOREROWS="0"Upgrading from NetWare 2 operating system.COLNAME=2 ROTATE="0" MOREROWS="0"Encrypted passwords temporarily.COLNAME=1 ROTATE="0" MOREROWS="0"A NetWare 3 server running on the same network as NetWare 2.11 or earlier.COLNAME=2 ROTATE="0" MOREROWS="0"Encrypted passwords temporarily.COLNAME=1 ROTATE="0" MOREROWS="0"A NetWare 3 server running on the same network as NetWare 2.11 or 2.15.COLNAME=2 ROTATE="0" MOREROWS="0"Encrypted passwords. Use SET in AUTOEXEC.NCF until utilities on other servers are upgraded.Copy NetWare 3 utilities to all NetWare 2.12 or 2.15 servers to allow all servers to use encrypted passwords.Type the following command at the console prompt to allow unencrypted passwords:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET ALLOW UNENCRYPTED PASSWORDS=ON MOREINFO="NONE"<Enter>For more information on AUTOEXEC.NCF files or on the commands listed above, see Chapter 7, "
BOOK="superenu" COLLECTION="nw41"Maintaining the NetWare Server," in 
Supervising the Network. See also "
BOOK="cncptenu" COLLECTION="nw41"Boot files" in 
Concepts.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to save the file.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> twice to exit INSTALL.
PAGENUM=97 ID="BP106"RENDERAS="SECT2"Format the DOS PartitionIDXID="w9831"BOOK="_idx" COLLECTION="nw41" TIDREF="i1187"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the console prompt (:), bring down the server by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Insert the upgrade diskette into drive A:.PERFORMANCE="REQUIRED"Return to the DOS prompt by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"EXIT MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the downed server, create a DOS primary partition and make it the active partition by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"FDISK MOREINFO="NONE"<Enter>The two utilities (FDISK.COM and FORMAT.COM) used to partition and format the DOS partition are found on the bootable upgrade diskette.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 is placed on the first few cylinders of the hard disk. The server reboots DOS as part of the FDISK process.PERFORMANCE="REQUIRED"Format the new DOS partition.If you are using DR DOS, the format command is as follows:
FORMAT="LINESPECIFIC"MOREINFO="NONE"FORMAT C:/s/x MOREINFO="NONE"<Enter>The /s parameter makes the partition bootable.The /x parameter tells DR DOS that it is formatting a hard disk.If you are using DR DOS to format your hard disk, use FORMAT.COM on the upgrade diskette or a later version.If you are not using DR DOS, type the format command as follows:
FORMAT="LINESPECIFIC"MOREINFO="NONE"FORMAT C:/s MOREINFO="NONE"<Enter>The /s parameter makes the partition bootable.
PAGENUM=98 ID="BP107"PERFORMANCE="REQUIRED"Reboot the server to make sure that DOS boots from the hard disk.RENDERAS="SECT2"Copy the New Boot Files to a Boot DirectoryRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"ID="FM22108"Create a boot directory.For example:
FORMAT="LINESPECIFIC"MOREINFO="NONE"C:\SERVER.410The boot files are copied to this directory on drive C:.PERFORMANCE="REQUIRED"ID="FM70685"Copy the newly created STARTUP.NCF file from the CD-ROM to the boot directory by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"COPY CD-ROM_drive:\STARTUP.NCF C:\boot_directory MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"From the CD-ROM drive, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWNSTLL /IN_PLACE MOREINFO="NONE"<Enter>The "Select an Installation Option" menu appears.PERFORMANCE="REQUIRED"Choose "Upgrade NetWare 3.1
x or 4.
x."PERFORMANCE="REQUIRED"Specify the 
IDXID="w9832"BOOK="_idx" COLLECTION="nw41" TIDREF="i1042"
destination directory (where you want the boot files to be copied).PERFORMANCE="REQUIRED"Copy the NetWare 4.1 server boot files to the boot directory.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F4>.PERFORMANCE="REQUIRED"ID="FM13512"Enter the destination path created in 
IDREF="FM22108"Step 1 for the files to be copied.
PAGENUM=99 ID="BP108"This should be the same directory that the STARTUP.NCF file was copied to in IDREF="FM70685"Step 2.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Change theID="FMDRIVE"source driveCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<F2> and enter a new drive letter or directory, and then press MOREINFO="NONE"<Enter>.COLNAME=1 ROTATE="0" MOREROWS="0"Change the destination directory on drive C:COLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<F4>, enter a directory name, choose "Yes," and then press MOREINFO="NONE"<Enter>.The following files are copied to the newly-created boot directory on drive C: (or another directory on C: that you specify).
MARK=BULLETSERVER.EXE (the NetWare operating system).MARK=BULLETNUT.NLM (an interface utility needed for certain NetWare Loadable ModulesTM).NWSNUT.NLM (an interface utility needed for certain NetWare Loadable Modules).Disk drivers (*.DSK).Name space modules (*.NAM).CLIB.NLM (C runtime library).Diagnostic NLMs (*.NLM).INSTALL.NLM (the installation utility).LAN drivers (*.LAN).Message and help files.PERFORMANCE="REQUIRED"If the directory you specified in 
IDREF="FM13512"Step 6b does not exist, the following message appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"Do you want to create "directory name." Y/NIf you use a third-party driver not shipped in the Red BoxTM (NetWare product package), you may need to exit NWNSTLL and copy the disk driver (*.DSK) to the new boot directory.PERFORMANCE="REQUIRED"If you choose "Yes," press 
MOREINFO="NONE"<Enter> to create the new directory.
PAGENUM=100 ID="BP109"PERFORMANCE="REQUIRED"Copy your STARTUP.NCF file into the new directory if it is different than the directory created in Step 1.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to continue.PERFORMANCE="REQUIRED"Insert the diskettes as prompted.Once the files have been copied, the following screen appears:LABEL="5-7" FLOAT="0"Language Configuration ScreenFILEREF="n41up64a.tif"PERFORMANCE="REQUIRED"Enter your 
IDXID="w9833"BOOK="_idx" COLLECTION="nw41" TIDREF="i859"
Country 
IDXID="w9834"BOOK="_idx" COLLECTION="nw41" TIDREF="i859"
code, code page, and keyboard mapping settings and press 
MOREINFO="NONE"<F10>.For a list of settings for each field, highlight a field and press MOREINFO="NONE"<Enter>, or refer to your DOS manual.  The keyboard mapping command is automatically added to the STARTUP.NCF file.The following screen appears:LABEL="5-8" FLOAT="0"Select a Filename FormatFILEREF="n41up65a.tif"PERFORMANCE="REQUIRED"Select a format for your DOS files and press 
MOREINFO="NONE"<Enter>.Selecting "NetWare Filename Format" leaves previously saved DOS files with nonstandard DOS characters as they were.The upgrade is complete.
PAGENUM=101 ID="BP110"PERFORMANCE="REQUIRED"From the boot directory, load the server operating system by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"SERVER MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Complete the upgrade to NetWare 4.1 by using the NetWare 4.1 installation program. For instructions, see 
IDREF="FM47491"Chapter 2, "Upgrade Using the NetWare 4.1 Installation Program."RENDERAS="SECT1"What to Do After In-Place UpgradeID="FM83559"IDXID="w9835"BOOK="_idx" COLLECTION="nw41" TIDREF="i2746"MARK=BULLETChange the IDXID="w9836"BOOK="_idx" COLLECTION="nw41" TIDREF="i4332"
SUPERVISOR password.Log in from a workstation as SUPERVISOR. Change the password using either SETPASS or SYSCON.Change user IDXID="w9837"BOOK="_idx" COLLECTION="nw41" TIDREF="i3241"
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.Check IDXID="w9838"BOOK="_idx" COLLECTION="nw41" TIDREF="i265"
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:MARK=BULLETRestricting the application's directory on the destination server with DSPACE.Making the directory path a fake root using the MAP command.Check IDXID="w9839"BOOK="_idx" COLLECTION="nw41" TIDREF="i1074"
directory security.Check directory security if you used either of the following items for NetWare 2 security:MARK=BULLETMaximum Rights MaskPrivate attributeSet new 
directory and 
file attributes using FLAG or FILER.Check directories for unnecessary NetWare files.PAGENUM=102 ID="BP111"The following IDXID="w9840"BOOK="_idx" COLLECTION="nw41" TIDREF="i2689"
NetWare 2 files are not compatible with NetWare 4.1 and should be deleted:TYPE="VERT"VAP files (*.VAP, *.HLD, *.VP?)LARCHIVE.EXELRESTORE.EXEMACBACK.EXENARCHIVE.EXENRESTORE.EXENET$BIND.SYSNET$BVAL.SYSNET$BIND.OLDNET$BVAL.OLDNET$ERR.SYSNET$OS.EXENET$DOS.SYSNET$MSG.SYSNET$REC.DAT(HIDEFILE.EXE and SHOWFILE.EXE still work, but have not been included in NetWare 4.1.)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.The following IDXID="w9841"BOOK="_idx" COLLECTION="nw41" TIDREF="i2689"
NetWare 2.0a files are not compatible with NetWare 3, and should be deleted:TYPE="VERT"ENDSPOOL.EXEQ.EXEQUEUE.EXESPOOL.EXEThe utilities listed above are replaced by ENDCAP, PCONSOLE, and CAPTURE in NetWare 3.12. For more information, see 
BOOK="utlrfenu" COLLECTION="nw41"Utilities Reference.Modify the system and IDXID="w9842"BOOK="_idx" COLLECTION="nw41" TIDREF="i2217"
user IDXID="w9843"BOOK="_idx" COLLECTION="nw41" TIDREF="i2216"
login scripts.Update references to the server in the system and user login scripts if you changed the server name.PAGENUM=103 ID="BP112"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, you could give users drive mappings to directories in which they had not been granted rights. NetWare 4.1 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 receive the following message when they log in:FORMAT="LINESPECIFIC"MOREINFO="NONE"Attempt to map drive to invalid path in MAP command.Complete one of the following:MARK=BULLETDelete the drive mapping from the login script.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.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 drive:=volume:directory).Create new IDXID="w9844"BOOK="_idx" COLLECTION="nw41" TIDREF="i490"
boot diskettes for each workstation.MARK=BULLETIf the server was renamed, change the server's name in the users' AUTOEXEC.BAT files to the new NetWare 4.1 server name.If you have other NetWare 2 servers on your network, upgrade the workstation files for those users even if you aren't upgrading the server.The new workstation files shipped with NetWare 4.1 are compatible with NetWare 2. All users on the internetwork should use the latest version of the workstation files to ensure that there are not conflicts.(Conditional) Copy the NetWare 4.1IDXID="w9845"BOOK="_idx" COLLECTION="nw41" TIDREF="i4736"
 utilities to other servers on the network.The NetWare 3 public utilities will run on servers running NetWare 2. Complete one of the following:PAGENUM=104 ID="BP113"MARK=BULLETIf you have servers running NetWare 2.0a, 2.10, or 2.11, do not copy the NetWare 3 public utilities to them. However, copy the NetWare 3.x LOGIN.EXE file to the SYS:LOGIN and SYS:PUBLIC directories.If you have NetWare 2.12 or 2.15 servers on your network, replace the NetWare public utilities with the NetWare 3 public utilities to allow the NetWare 2.12 and 2.15 servers to work with encrypted passwords.To copy utilities, complete the following steps:Log in to the NetWare 2 server as SUPERVISOR.Flag the NetWare 2 utilities Normal. In the SYS:LOGIN and SYS:PUBLIC directories, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG *.* N MOREINFO="NONE"<Enter>Protect the system login script. In the SYS:PUBLIC directory, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG NET$LOG.DAT SRO MOREINFO="NONE"<Enter>Map a drive to the SYS:PUBLIC directory on the NetWare 4.1 server by typingFORMAT="LINESPECIFIC"MOREINFO="NONE"MAP drive:=fileserver/SYS:PUBLIC MOREINFO="NONE"<Enter>Replace drive with a drive letter not being used and replace fileserver with the name of the NetWare 4.1 server.ID="FM85318"Enter your username and password for the NetWare 4.1 server.ID="FM26837"Copy the NetWare 4.1 PUBLIC files to the NetWare 2 server.For example, if drive Q: is mapped to SYS:PUBLIC on the NetWare 4.1 server and drive F: is mapped to SYS:PUBLIC on the NetWare 2 server, change to drive F: and typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NCOPY Q:*.* MOREINFO="NONE"<Enter>Flag the NetWare 4.1 utilities on the NetWare 2 server Shareable and Read Only. TypeFORMAT="LINESPECIFIC"MOREINFO="NONE"FLAG *.* SRO MOREINFO="NONE"<Enter>Repeat the steps for the SYS:LOGIN directory.Login scripts on the NetWare 4.1 server do not execute properly unless you copy the NetWare 4.1 login programs to all NetWare LOGIN directories on your internetwork.PAGENUM=105 ID="BP114"When you have copied the NetWare 4.1 utilities to all NetWare 2 servers and you do not have any NetWare 2.0a servers, you can change the setting for unencrypted passwords. At the console prompt of the NetWare 4.1 server, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"SET ALLOW UNENCRYPTED PASSWORDS=OFF MOREINFO="NONE"<Enter>If you still have NetWare 2.0a servers on your internetwork, the setting at the NetWare 4.1 server for unencrypted passwords must be ON.If your NetWare 2 server had mirrored disks, remirror them using INSTALL.NLM.Update print queues as necessary upgraded using PCONSOLE.Use SBACKUP to make a backup copy of all data on the NetWare 4.1 server.For SBACKUP instructions, see 
"BOOK="utlrfenu" COLLECTION="nw41"SBACKUP" in Utilities Reference.Check user restrictions and accounting charge rates to make sure your system is configured the way you want it.(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 IDXID="w9846"BOOK="_idx" COLLECTION="nw41" TIDREF="i88"
ADD NAME SPACE command to add name space to the volume. TypeFORMAT="LINESPECIFIC"MOREINFO="NONE"ADD NAME SPACE name-support TO VOLUME volume_name MOREINFO="NONE"<Enter>For example, if you have a volume named MAC: for Macintosh files, type the following at the console prompt:FORMAT="LINESPECIFIC"MOREINFO="NONE"ADD NAME SPACE MACINTOSH TO VOLUME MAC MOREINFO="NONE"<Enter>Use the command once for every volume that needs to store files with long names.To ensure name space support each time the server is brought up, load the appropriate name space module in the STARTUP.NCF file.(Optional) To store IDXID="w9847"BOOK="_idx" COLLECTION="nw41" TIDREF="i2270"
Macintosh files and folders on a NetWare 4.1 server, install NetWare for Macintosh (a separate Novell product) on the 4.1 server.PAGENUM=106 ID="BP115"This product provides support for Macintosh workstations that connect to the NetWare 4.1 server.Assign 
Directory object and property rights to 
Directory objects that were upgraded from bindery objects.For details, see Chapter 1, "BOOK="superenu" COLLECTION="nw41"Managing NetWare Directory Services Objects," of Supervising the Network.After verifying that the upgrade to NetWare 4.1 succeeded, delete NetWare 2-specific system files to save disk space.For example, files you may want to delete includeMARK=BULLETNetWare 2 system filesNET$ERR.SYS fileVAPsCertain login script IDXID="w9848"BOOK="_idx" COLLECTION="nw41" TIDREF="i2209"
commands have to be modified or deleted after the IDXID="w9849"BOOK="_idx" COLLECTION="nw41" TIDREF="i2496"
upgrade:MARK=BULLETMEMBER_OF_groupIDXID="w9850"BOOK="_idx" COLLECTION="nw41" TIDREF="i1622"
Groups have been replaced by 
Group IDXID="w9851"BOOK="_idx" COLLECTION="nw41" TIDREF="i1064"
objects and IDXID="w9852"BOOK="_idx" COLLECTION="nw41" TIDREF="i1622"
Profile IDXID="w9853"BOOK="_idx" COLLECTION="nw41" TIDREF="i3385"
objects. This variable becomes a IDXID="w9854"BOOK="_idx" COLLECTION="nw41" TIDREF="i3568"
Group object in NetWare 4.1. For more information, see Chapter 3, "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts," of Supervising the Network.IDXID="w9855"BOOK="_idx" COLLECTION="nw41" TIDREF="i2332"
MAP commandWhen you map a drive to a directory located on a NetWare 4.1 Directory Services volume, you may want to modify the volume name to correspond to the new directory name.However, when you map a drive to a server that is running a previous version of NetWare, the MAP command functions as it did originally and must include the servername.IDXID="w9856"BOOK="_idx" COLLECTION="nw41" TIDREF="i328"
ATTACH commandUsers can still attach to pre-NetWare 4.1 servers, but the ATTACH command is not valid for NetWare 4.1 servers.The majority of login commands work the same in NetWare 4.1 as they did in previous NetWare versions. In MAP commands, if the server is not specified (MAP F:=volume:directory), the Message Server attribute of the User object will be used.PAGENUM=107 ID="BP116"To set up the maximum amount of disk space a user can use, use the NETADMIN or NetWare Administrator utility in 4.1 after you have finished the upgrade to 4.1.For more information on NETADMIN and NetWare Administrator, see Chapter 1, "BOOK="superenu" COLLECTION="nw41"Managing NetWare Directory Services Objects," of Supervising the Network.PERFORMANCE="REQUIRED"Allow users to log in to the NetWare 4.1 server.Users can log in if
MARK=BULLETVolume SYS: is mountedThe user exists in the binderyThe LAN driver is loaded and bound to a protocolLogin is enabledTo ensure that login is enabled, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"ENABLE LOGIN MOREINFO="NONE"<Enter>LABEL="A"PAGENUM=109 ID="BP117"ID="FM15438"Calculating RAM RequirementsThis appendix provides a detailed formula for IDXID="w9857"BOOK="_idx" COLLECTION="nw41" TIDREF="i1555"IDXID="w9858"BOOK="_idx" COLLECTION="nw41" TIDREF="i3664"IDXID="w9859"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"
calculating your NetWare® 4.1 RAM requirements.Calculating RAM requirements involves defining RAM usage for three major components:MARK=BULLETNetWare operating systemVolumesNetWare Loadable ModulesTM (NLMs)The following charts list items that take up RAM and provide a formula for calculating that item's RAM usage. An example of a calculation follows in IDREF="FM65953""Example RAM Calculation" on page 112.For information on any item in the charts, see 
BOOK="cncptenu" COLLECTION="nw41"Concepts.PAGENUM=110 ID="BP118"RENDERAS="SECT1"NetWare Operating System RequirementsIDXID="w9860"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"Some of the following information can only be obtained by installing a server and loading MONITOR.NLM to see server statistics.LABEL="A-1" PGWIDE=1 TOCENTRY="1"ID="FM27125" OS RequirementsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="14*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ItemCOLNAME=2 ROTATE="0" MOREROWS="0"RAM usageCOLNAME=3 ROTATE="0" MOREROWS="0"NotesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Core NetWare operating systemCOLNAME=2 ROTATE="0" MOREROWS="0"7 MBCOLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Cache memoryCOLNAME=2 ROTATE="0" MOREROWS="0"1 MB + (MB of disk space online x 5 KB)COLNAME=3 ROTATE="0" MOREROWS="0"This formula is an estimate based on reasonable performance per user. It assumes that the number of users increases with disk space.COLNAME=1 ROTATE="0" MOREROWS="0"Media ManagerCOLNAME=2 ROTATE="0" MOREROWS="0"150 KB + (0.2 KB x MB of disk space online)COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Connections in useCOLNAME=2 ROTATE="0" MOREROWS="0"2 KB per user connectionCOLNAME=3 ROTATE="0" MOREROWS="0"For an installed server, see MONITOR.NLM.COLNAME=1 ROTATE="0" MOREROWS="0"Packet receive buffersCOLNAME=2 ROTATE="0" MOREROWS="0"2.3 KB per bufferCOLNAME=3 ROTATE="0" MOREROWS="0"For an installed server, see MONITOR.NLM.COLNAME=1 ROTATE="0" MOREROWS="0"Directory cache buffersCOLNAME=2 ROTATE="0" MOREROWS="0"4.3 KB per bufferCOLNAME=3 ROTATE="0" MOREROWS="0"For an installed server, see MONITOR.NLM.COLNAME=1 ROTATE="0" MOREROWS="0"Service processesCOLNAME=2 ROTATE="0" MOREROWS="0"9 KB per service processCOLNAME=3 ROTATE="0" MOREROWS="0"For an installed server, see MONITOR.NLM.COLNAME=1 ROTATE="0" MOREROWS="0"File compression enabled on any volumeCOLNAME=2 ROTATE="0" MOREROWS="0"250 KBCOLNAME=3 ROTATE="0" MOREROWS="0"PAGENUM=111 ID="BP119"RENDERAS="SECT1"Volume-Related RequirementsIDXID="w9861"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"IDXID="w9862"BOOK="_idx" COLLECTION="nw41" TIDREF="i4781"You need to calculate the following items for each volume individually and then add up the results from all volumes.LABEL="A-2" PGWIDE=1 TOCENTRY="1"ID="FM42176" Volume requirementsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="10*"COLNAME=3 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ItemCOLNAME=2 ROTATE="0" MOREROWS="0"RAM usageCOLNAME=3 ROTATE="0" MOREROWS="0"NotesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"File Allocation Tables (FAT)COLNAME=2 ROTATE="0" MOREROWS="0"Volume Blocks x 8.2 bytesCOLNAME=3 ROTATE="0" MOREROWS="0"Calculate Volume Blocks by dividing the size of the volume by its block size.COLNAME=1 ROTATE="0" MOREROWS="0"Block suballocation enabledCOLNAME=2 ROTATE="0" MOREROWS="0"((Blocksize x 2) -1) x 4096 bytes) + (5 x Number of files) bytesCOLNAME=3 ROTATE="0" MOREROWS="0"Calculate the approximate number of files by dividing the volume size by the average file size.COLNAME=1 ROTATE="0" MOREROWS="0"Directory Entry tables (DET)COLNAME=2 ROTATE="0" MOREROWS="0"Number of files x 10 bytesCOLNAME=3 ROTATE="0" MOREROWS="0"Calculate the approximate number of files by dividing the volume size by the average file size.RENDERAS="SECT1"NLM RequirementsIDXID="w9863"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"IDXID="w9864"BOOK="_idx" COLLECTION="nw41" TIDREF="i2755"The following chart lists some NLMs that take up more RAM than most other NLMs and, therefore, should be included in this calculation.LABEL="A-3" PGWIDE=1 TOCENTRY="1"ID="FM89203" NLM requirementsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="7*"COLNAME=3 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ItemCOLNAME=2 ROTATE="0" MOREROWS="0"RAM usageCOLNAME=3 ROTATE="0" MOREROWS="0"NotesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"BTRIEVE.NLMCOLNAME=2 ROTATE="0" MOREROWS="0"700 KBCOLNAME=3 ROTATE="0" MOREROWS="0"Needed for products such as NetWare for Macintosh* and NetWare for NFS*.COLNAME=1 ROTATE="0" MOREROWS="0"CLIB.NLMCOLNAME=2 ROTATE="0" MOREROWS="0"500 KBCOLNAME=3 ROTATE="0" MOREROWS="0"Needed for products such as Print Server, and for many other NLMs.COLNAME=1 ROTATE="0" MOREROWS="0"INSTALL.NLMCOLNAME=2 ROTATE="0" MOREROWS="0"600 KBCOLNAME=3 ROTATE="0" MOREROWS="0"Needed for installation and maintenance.COLNAME=1 ROTATE="0" MOREROWS="0"PSERVER.NLMCOLNAME=2 ROTATE="0" MOREROWS="0"200 KBCOLNAME=3 ROTATE="0" MOREROWS="0"Needed for Print Server.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Calculate each of the items in IDREF="FM27125"Table A-1 on page 110.PAGENUM=112 ID="BP120"PERFORMANCE="REQUIRED"Calculate volume requirements using 
IDREF="FM42176"Table A-2 on page 111.PERFORMANCE="REQUIRED"Calculate NLMTM requirements using 
IDREF="FM89203"Table A-3 on page 111.PERFORMANCE="REQUIRED"Add those results to the OS requirements.See the example below.RENDERAS="SECT1"ID="FM65953"Example RAM CalculationIDXID="w9865"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"Assume you want to install a system withMARK=BULLET500 users2 GB (2,000 MB) of disk spaceFour volumes with file compression and block suballocation enabled:MARK=BULLETVolume SYS: with 100 MBVolume MACVOL: with 500 MBVolume DATA: with 1 GB (file compression enabled)Volume ACCOUNTS: with 400 MBAn average file size of 30 KBBased on these assumptions, a RAM calculation would look like the following.PAGENUM=113 ID="BP121"RENDERAS="SECT2"NetWare Operating System RequirementsFor purposes of an easier calculation, we assumed 1 KB to mean 1,000 bytes (instead of 1,024 bytes), and 1 MB to mean 1,000,000 bytes (instead of 1,048,576 bytes.)NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Assume a core operating system requirement of 7 MB.Add 11 MB for cache memory.1 MB + (2000 x 5 KB) = 11 MBAdd 550 KB for the Media Manager.150 KB + (0.2 KB x 2000) = 550 KBAdd 1 MB for user connections.2 KB x 500 users = 1,000 KB= 1MBAdd 230 KB for packet receive buffers.Assume you need about 100 buffers for a system of this size.2.3 KB x 100 = 230 KBAdd 430 KB for directory cache buffers.Assume you need about 100 buffers for a system of this size.4.3 KB x 100 = 430 KBAdd 180 KB for service processes.Assume about 20 service processes for a system of this size. (Service processes are workstation requests that are tracked by MONITOR.NLM.)Add 250 KB for file compression.Total approximate RAM requirements for the NetWare operating system: 20.7 MBPAGENUM=114 ID="BP122"RENDERAS="SECT2"Volume RequirementsCalculate these requirements individually for each volume on your system.NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Add 2 MB for FAT tables on all four volumes.Volume SYS: (100 MB) needs 0.1 MB.Volume MACVOL: (500 MB) needs 0.5 MB.Volume DATA: (1GB) needs 1 MB.Volume ACCOUNTS: (400 MB) needs 0.4 MB.Total requirements for FAT tables: 2 MBAdd 1 MB for block suballocation on all four volumes.Volume SYS: (100 MB) needs 80 KBVolume MACVOL: (500 MB) needs 341 KBVolume DATA: (1GB) needs 425 KBVolume ACCOUNTS: (400 MB) needs 194 KBTotal requirements for block suballocation: 1 MBAdd 666 KB for directory entries on all four volumes.Volume SYS: (100 MB) needs 33 KBVolume MACVOL: (500 MB) needs 167 KBVolume DATA: (1GB) needs 333 KBVolume ACCOUNTS: (400 MB) needs 133 KBTotal requirements for directory entries: 666 KBTotal approximate RAM requirements for all volumes: 3.67MBRENDERAS="SECT2"NLM RequirementsAssuming that you need CLIB.NLM (500 KB), INSTALL.NLM (600 KB), and PSERVER.NLM (200 KB), add 1.3 MB for NLMs.PAGENUM=115 ID="BP123"RENDERAS="SECT2"Grand TotalOperating system + Volume + NLM requirements = Grand Total20.7 MB + 3.67 MB + 1.3 MB = 25.67 (25.7) MBThe approximate minimum RAM requirement for a NetWare system of this size is 25.7 MB.LABEL="B"PAGENUM=117 ID="BP124"NetWare 4 File and Directory AttributesRENDERAS="SECT1"IntroductionThis appendix describes the file and directory attributes unique to NetWare 4TMNetWare 4 with NetWare Directory ServicesTM has unique file and directory attributes than NetWare 2 and NetWare 3TM. This appendix discusses new attributes available with NetWare 4.For additional information, see "BOOK="cncptenu" COLLECTION="nw41"Rights" and "BOOK="cncptenu" COLLECTION="nw41"Security" in Concepts.PAGENUM=118 ID="BP125"RENDERAS="SECT1"ID="FM65185"IDXID="w9866"BOOK="_idx" COLLECTION="nw41" TIDREF="i3851"
Object RightsObject rights apply to NDS objects, but do not affect the properties of the object.As in the file system, trustees inherit the same rights to an 
object that they had to the 
object's parent in the Directory tree, unless some of those rights are blocked by the Inherited Rights Filter.The following table describes the NetWare 4 object rights.LABEL="B-1" PGWIDE=1 TOCENTRY="1" NetWare 4 Object RightsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="17*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Object rightCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9867"BOOK="_idx" COLLECTION="nw41" TIDREF="i4330"
SupervisorCOLNAME=2 ROTATE="0" MOREROWS="0"Gives a trustee all rights to the object and all its properties. The Inherited Rights Filter, however, can block the Supervisor right under certain conditions.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9868"BOOK="_idx" COLLECTION="nw41" TIDREF="i532"
BrowseCOLNAME=2 ROTATE="0" MOREROWS="0"Allows a trustee to see the object in the Directory tree. When a trustee makes a search which matches the object, the name of the object is returned.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9869"BOOK="_idx" COLLECTION="nw41" TIDREF="i869"
CreateCOLNAME=2 ROTATE="0" MOREROWS="0"Allows a trustee to create a new object below this object in the Directory tree. This right only applies to container objects.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9870"BOOK="_idx" COLLECTION="nw41" TIDREF="i978"
DeleteCOLNAME=2 ROTATE="0" MOREROWS="0"Allows a trustee to delete the object from the Directory tree. However, a trustee cannot delete an object with subordinates before deleting the subordinates.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9871"BOOK="_idx" COLLECTION="nw41" TIDREF="i3776"
RenameCOLNAME=2 ROTATE="0" MOREROWS="0"Allows a trustee to change the name of the object.PAGENUM=119 ID="BP126"RENDERAS="SECT1"ID="FM28112"Property RightsProperty rights apply to the properties of a NetWare Directory Services object. Rights can be assigned to each 
property, or a default set can apply to all IDXID="w9872"BOOK="_idx" COLLECTION="nw41" TIDREF="i447"
properties of an object when other specific 
property 
rights are not set.The following table describes the NetWare 4 property rights.LABEL="B-2" PGWIDE=1 TOCENTRY="1" NetWare 4 Property RightsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Property rightCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9873"BOOK="_idx" COLLECTION="nw41" TIDREF="i4330"
SupervisorCOLNAME=2 ROTATE="0" MOREROWS="0"Gives a trustee all rights to the property. The Inherited Rights Filter, however, can block the Supervisor right.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9874"BOOK="_idx" COLLECTION="nw41" TIDREF="i713"
CompareCOLNAME=2 ROTATE="0" MOREROWS="0"Allows a trustee to compare any value to an existing value of the property. The comparison can return True or False, but not give the value of the property.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9875"BOOK="_idx" COLLECTION="nw41" TIDREF="i3684"
ReadCOLNAME=2 ROTATE="0" MOREROWS="0"Allows a trustee to read the values of the property. This right includes the Compare right.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9876"BOOK="_idx" COLLECTION="nw41" TIDREF="i4852"
WriteCOLNAME=2 ROTATE="0" MOREROWS="0"Allows a trustee to add, change, or remove any values of the property. The Write right includes the Add or IDXID="w9877"BOOK="_idx" COLLECTION="nw41" TIDREF="i982"
Delete Self right.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9878"BOOK="_idx" COLLECTION="nw41" TIDREF="i91"
Add [or Delete] SelfCOLNAME=2 ROTATE="0" MOREROWS="0"Allows a trustee to add or remove itself as a value of the property, but not to change any other values of the property. Only valid for properties that take object names as values.ID="FM75626"PAGENUM=120 ID="BP127"RENDERAS="SECT1"ID="FM28463"Migrating Directory and File RightsIn NetWare 4, rights are granted for a specific directory, file, or object by trustee assignments. A user with a trustee assignment to a file, directory, or object is a trustee of that directory, file, or object.The following table shows the 
directory and 
file 
rights for NetWare versions 2.1x, 2.2, 3.1x, and 4. There is no change in 
directory and file rights from NetWare 3.1x to NetWare 4.LABEL="B-3" PGWIDE=1 TOCENTRY="1" Evolution of Directory and File RightsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="11*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"RightCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"Changes in NetWare 4VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9879"BOOK="_idx" COLLECTION="nw41" TIDREF="i4330"
Supervisory (3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Grants all rights to the directory, its files, and its subdirectories.Note: Do not confuse with IDXID="w9880"BOOK="_idx" COLLECTION="nw41" TIDREF="i4330"
Supervisor object right in NetWare 4, which grants all rights to an object, but can be masked with the Inherited Rights Filter.COLNAME=3 ROTATE="0" MOREROWS="0"Name change to Supervisor.COLNAME=1 ROTATE="0" MOREROWS="0"Create (all versions) [directories and files]COLNAME=2 ROTATE="0" MOREROWS="0"Assigned only if Open was also assigned.COLNAME=3 ROTATE="0" MOREROWS="0"Create now allows users to create subdirectories without the need for the Access Control (was Parental) right.COLNAME=1 ROTATE="0" MOREROWS="0"Delete (2.1x-2.15)  [directories and files]Erase (2.2/3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Deletes directories and files.COLNAME=3 ROTATE="0" MOREROWS="0"Same as 3.11 Erase.COLNAME=1 ROTATE="0" MOREROWS="0"Modify (2.1x-2.15)  [file only]Modify (2.2/3.11)  [directories and files]COLNAME=2 ROTATE="0" MOREROWS="0"Renames files or changes their 
attributes.COLNAME=3 ROTATE="0" MOREROWS="0"Access Control (was Parental) is no longer required to rename directories and files or attributes.Same as 3.11 Modify.COLNAME=1 ROTATE="0" MOREROWS="0"Open (2.1x-2.15)  [directories and files]COLNAME=2 ROTATE="0" MOREROWS="0"Opens directories and files.COLNAME=3 ROTATE="0" MOREROWS="0"Open privileges are included with the Read, Write, and Create rights. (Not assigned because Open is no longer a separate right.)COLNAME=1 ROTATE="0" MOREROWS="0"Parental 2.1x-2.15 [directories and files]Access Control (2.2 and 3.11)COLNAME=2 ROTATE="0" MOREROWS="0"The trustee assignments and Inherited Rights Filters control how other objects can access the object.COLNAME=3 ROTATE="0" MOREROWS="0"All rights assigned to users with Access Control can be revoked at the subdirectory and file level. This right no longer assigns the right to create or rename subdirectories.COLNAME=1 ROTATE="0" MOREROWS="0"Read and Open (2.1x)  [file only]COLNAME=2 ROTATE="0" MOREROWS="0"Reads and scans files.COLNAME=3 ROTATE="0" MOREROWS="0"A separate Open right is no longer required.COLNAME=1 ROTATE="0" MOREROWS="0"Search (2.1x)  [directories and files]COLNAME=2 ROTATE="0" MOREROWS="0"Searches directories and files.COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"File Scan (2.2 and 3.11)  [directories and files]COLNAME=2 ROTATE="0" MOREROWS="0"Scans directories and files.COLNAME=3 ROTATE="0" MOREROWS="0"File Scan includes the right to search to the root of a directory. File Scan is assigned automatically when any of the NetWare rights is assigned.COLNAME=1 ROTATE="0" MOREROWS="0"Write and Open (2.1x)  [file only]Write (2.2 and 3.11)  [directories and files]COLNAME=2 ROTATE="0" MOREROWS="0"Allows the user to write to files.COLNAME=3 ROTATE="0" MOREROWS="0"A separate Open right is no longer required; Write is sufficient.PAGENUM=122 ID="BP128"RENDERAS="SECT1"ID="FM49536"Migrating File AttributesNetWare 4.1 reads the attributes that you set (for example, to compress or back up a file) and sets other attributes to tell you what has been done (for example, that a file has been compressed or migrated).The following table describes 
file attributes for NetWare versions 2.1x/2.2, 3.1x, and 4.For additional information, see "BOOK="cncptenu" COLLECTION="nw41"Attributes" and "BOOK="cncptenu" COLLECTION="nw41"Security" in Concepts.LABEL="B-4" PGWIDE=1 TOCENTRY="1"Evolution of File AttributesCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="9*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"AttributeCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"Changes in NetWare 4VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9881"BOOK="_idx" COLLECTION="nw41" TIDREF="i584"
Can't Compress [Cc] (4)COLNAME=2 ROTATE="0" MOREROWS="0"A status flag set by NetWare. Indicates that the file cannot be compressed because of limited space savings. This attribute is shown on attribute lists, but cannot be set by the user.COLNAME=3 ROTATE="0" MOREROWS="0"NewCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9882"BOOK="_idx" COLLECTION="nw41" TIDREF="i724"
Compressed [Co] (4)COLNAME=2 ROTATE="0" MOREROWS="0"A status flag set by NetWare. Indicates that the file is compressed. This attribute is shown on attribute lists, but cannot be set by the user.COLNAME=3 ROTATE="0" MOREROWS="0"NewCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9883"BOOK="_idx" COLLECTION="nw41" TIDREF="i841"
Copy Inhibit (3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Valid only on Macintosh workstations.COLNAME=3 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9884"BOOK="_idx" COLLECTION="nw41" TIDREF="i976"
Delete IDXID="w9885"BOOK="_idx" COLLECTION="nw41" TIDREF="i976"
Inhibit (3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Restricts deletion of files.COLNAME=3 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9886"BOOK="_idx" COLLECTION="nw41" TIDREF="i1178"
Don't IDXID="w9887"BOOK="_idx" COLLECTION="nw41" TIDREF="i1178"
Compress [Dc] (4)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the file so that it is never compressed.COLNAME=3 ROTATE="0" MOREROWS="0"NewCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9888"BOOK="_idx" COLLECTION="nw41" TIDREF="i1179"
Don't Migrate [Dm] (4)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the file so that it is never migrated to a secondary storage device (like a tape drive or optical disk).COLNAME=3 ROTATE="0" MOREROWS="0"NewCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9889"BOOK="_idx" COLLECTION="nw41" TIDREF="i1378"
Execute Only (2.1x-2.2)COLNAME=2 ROTATE="0" MOREROWS="0"Prevents copying or backing up .EXE or .COM files.COLNAME=3 ROTATE="0" MOREROWS="0"Not availableCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9890"BOOK="_idx" COLLECTION="nw41" TIDREF="i1664"
Hidden (2.1x-2.2 and 3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Hides files from DOS DIR scans and prevents them from being deleted or copied.COLNAME=3 ROTATE="0" MOREROWS="0"No changeCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9891"BOOK="_idx" COLLECTION="nw41" TIDREF="i1764"
Immediate IDXID="w9892"BOOK="_idx" COLLECTION="nw41" TIDREF="i1764"
Compress [Ic] (4)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the file so that it is compressed on disk as soon as the operating system is able to do so, without waiting for a specific event to occur (such as a time delay).COLNAME=3 ROTATE="0" MOREROWS="0"NewCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9893"BOOK="_idx" COLLECTION="nw41" TIDREF="i1787"
Indexed (2.1x-2.2 and 3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Occurs automatically to files that have over 64 disk blocks. Large files don't need to be flagged by the user to be indexed.Cannot be set by the user.COLNAME=3 ROTATE="0" MOREROWS="0"This is now a status flagCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9894"BOOK="_idx" COLLECTION="nw41" TIDREF="i2449"
Migrated [M] (4)COLNAME=2 ROTATE="0" MOREROWS="0"Is a status flag set by NetWare. Indicates that the file is migrated. This attribute is shown on attribute lists, but cannot be set by the user.COLNAME=3 ROTATE="0" MOREROWS="0"NewCOLNAME=1 ROTATE="0" MOREROWS="0"Modified Since Last Backup (2.1x)IDXID="w9895"BOOK="_idx" COLLECTION="nw41" TIDREF="i278"
Archive Needed (2.2/3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Lists files modified since last backup. Assigned automatically.COLNAME=3 ROTATE="0" MOREROWS="0"Same as 3.11 Archive NeededCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9896"BOOK="_idx" COLLECTION="nw41" TIDREF="i3640"
Purge (3.11 and later)COLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w9897"BOOK="_idx" COLLECTION="nw41" TIDREF="i3640"
Purges files marked for deletion.COLNAME=3 ROTATE="0" MOREROWS="0"No changeCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9898"BOOK="_idx" COLLECTION="nw41" TIDREF="i3774"
Rename IDXID="w9899"BOOK="_idx" COLLECTION="nw41" TIDREF="i3774"
Inhibit (3.11 and later)COLNAME=2 ROTATE="0" MOREROWS="0"Prevents users from renaming files.COLNAME=3 ROTATE="0" MOREROWS="0"No changeCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9900"BOOK="_idx" COLLECTION="nw41" TIDREF="i4132"
Shareable (All)COLNAME=2 ROTATE="0" MOREROWS="0"Allows several users to access a file simultaneously.COLNAME=3 ROTATE="0" MOREROWS="0"No changeCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9901"BOOK="_idx" COLLECTION="nw41" TIDREF="i2975"
Non-Shareable (All)COLNAME=2 ROTATE="0" MOREROWS="0"Restricts multiple-user access to files.COLNAME=3 ROTATE="0" MOREROWS="0"In 3.11 and 4 no character is displayed to indicate the file is non-shareableCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9902"BOOK="_idx" COLLECTION="nw41" TIDREF="i3683"
Read Only (All)COLNAME=2 ROTATE="0" MOREROWS="0"Restricts file modification.COLNAME=3 ROTATE="0" MOREROWS="0"No change.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9903"BOOK="_idx" COLLECTION="nw41" TIDREF="i3687"
Read Write (All)COLNAME=2 ROTATE="0" MOREROWS="0"Indicates a file can be modified.COLNAME=3 ROTATE="0" MOREROWS="0"In 3.11 and 4 this attribute is toggled on automatically when the Read Only attribute is not setCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9904"BOOK="_idx" COLLECTION="nw41" TIDREF="i4374"
System (All)COLNAME=2 ROTATE="0" MOREROWS="0"Assigned to IDXID="w9905"BOOK="_idx" COLLECTION="nw41" TIDREF="i4374"
system files. Hides these files from DOS DIR scans and prevents them from being deleted or copied.COLNAME=3 ROTATE="0" MOREROWS="0"No changeCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9906"BOOK="_idx" COLLECTION="nw41" TIDREF="i4549"
Transactional (All)COLNAME=2 ROTATE="0" MOREROWS="0"Activates the Transaction Tracking System (TTS). Prevents data corruption by ensuring all changes are made to files being modified or none are.COLNAME=3 ROTATE="0" MOREROWS="0"No changePAGENUM=125 ID="BP129"RENDERAS="SECT1"ID="FM17346"Migrating Directory AttributesNo directory 
attributes were available in NetWare versions 2.0a, 2.1, 2.11, or 2.12. If you are migrating from any of these versions, set the directory attributes manually after the migration is complete.The following table describes 
directory attributes for NetWare versions 2.1x/ 2.2, 3.11, and 4. For additional information, see "BOOK="cncptenu" COLLECTION="nw41"Attributes" and "BOOK="cncptenu" COLLECTION="nw41"Security" in Concepts.LABEL="B-5" PGWIDE=1 TOCENTRY="1" Evolution of Directory AttributesCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="9*"COLNAME=3 COLWIDTH="8*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"AttributeCOLNAME=2 ROTATE="0" MOREROWS="0"DescriptionCOLNAME=3 ROTATE="0" MOREROWS="0"Changes in NetWare 4VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9907"BOOK="_idx" COLLECTION="nw41" TIDREF="i1664"
Hidden (2.1x-2.2 and 3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Hides directories from DOS DIR scans and prevents them from being deleted or copied.COLNAME=3 ROTATE="0" MOREROWS="0"No changeCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9908"BOOK="_idx" COLLECTION="nw41" TIDREF="i1764"
Immediate Compress [Ic] (4)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the directory so that all files in it are compressed on disk as soon as the operating system is able to do so, without waiting for a specific event to occur (such as a time delay).COLNAME=3 ROTATE="0" MOREROWS="0"NewCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9909"BOOK="_idx" COLLECTION="nw41" TIDREF="i1178"
Don't Compress [Dc] (4)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the directory so that files in it are never compressed.COLNAME=3 ROTATE="0" MOREROWS="0"NewCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9910"BOOK="_idx" COLLECTION="nw41" TIDREF="i1179"
Don't IDXID="w9911"BOOK="_idx" COLLECTION="nw41" TIDREF="i1179"
Migrate [Dm] (4)COLNAME=2 ROTATE="0" MOREROWS="0"Marks the directory so that files in it are never migrated to a secondary storage device (such as a tape drive or optical disk).COLNAME=3 ROTATE="0" MOREROWS="0"NewCOLNAME=1 ROTATE="0" MOREROWS="0"Private (2.1x-2.2)COLNAME=2 ROTATE="0" MOREROWS="0"Allows users to see the directory but not its subdirectories.COLNAME=3 ROTATE="0" MOREROWS="0"Not available.Change the trustee assignments (rights, not attributes) for the users that have access to the directories flagged Private. Grant these users only the Create right to the directory.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9912"BOOK="_idx" COLLECTION="nw41" TIDREF="i4374"
System (ALL)COLNAME=2 ROTATE="0" MOREROWS="0"Assigned to system directories. Hides them from DOS DIR scans and prevents them from being deleted or copied.COLNAME=3 ROTATE="0" MOREROWS="0"No changeCOLNAME=1 ROTATE="0" MOREROWS="0"(IDXID="w9913"BOOK="_idx" COLLECTION="nw41" TIDREF="i2978"
Normal 2.2)COLNAME=2 ROTATE="0" MOREROWS="0"Indicates no attributes have been set.COLNAME=3 ROTATE="0" MOREROWS="0"Not availableCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9914"BOOK="_idx" COLLECTION="nw41" TIDREF="i976"
Delete Inhibit (3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Restricts directory deletion.COLNAME=3 ROTATE="0" MOREROWS="0"No changeCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9915"BOOK="_idx" COLLECTION="nw41" TIDREF="i3640"
Purge (3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Purges directories set for deletion.COLNAME=3 ROTATE="0" MOREROWS="0"No changeCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9916"BOOK="_idx" COLLECTION="nw41" TIDREF="i3774"
Rename Inhibit (3.11)COLNAME=2 ROTATE="0" MOREROWS="0"Restricts renaming of directories.COLNAME=3 ROTATE="0" MOREROWS="0"No changePAGENUM=127 ID="BP130"LABEL="B-6" PGWIDE=0 TOCENTRY="1"ID="FM79990" Bindery Objects that Are Upgraded to Directory ObjectsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare 3.1x bindery objectCOLNAME=2 ROTATE="0" MOREROWS="0"After upgrading to NetWare 4.1VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9917"BOOK="_idx" COLLECTION="nw41" TIDREF="i1619"
Group IDXID="w9918"BOOK="_idx" COLLECTION="nw41" TIDREF="i1366"
EVERYONECOLNAME=2 ROTATE="0" MOREROWS="0"CN=EVERYONE  Object class=IDXID="w9919"BOOK="_idx" COLLECTION="nw41" TIDREF="i4690"
GroupMembers of this 
group have the same rights to objects (and their properties) they had rights to before the upgrade. COLNAME=1 ROTATE="0" MOREROWS="0"Other IDXID="w9920"BOOK="_idx" COLLECTION="nw41" TIDREF="i1622"
groupsCOLNAME=2 ROTATE="0" MOREROWS="0"CN=group_name  Object class=
GroupMembers of these groups have the same rights to objects (and their properties) they had before the upgrade. COLNAME=1 ROTATE="0" MOREROWS="0"User IDXID="w9921"BOOK="_idx" COLLECTION="nw41" TIDREF="i1625"
GUESTCOLNAME=2 ROTATE="0" MOREROWS="0"CN=
GUEST  Object class=UserGUEST has PUBLIC rights as defined in the tree.COLNAME=1 ROTATE="0" MOREROWS="0"User IDXID="w9922"BOOK="_idx" COLLECTION="nw41" TIDREF="i4337"
SUPERVISORCOLNAME=2 ROTATE="0" MOREROWS="0"Effective rights on the Server object are greater than or equal to the Managed right on its ACL property.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9923"BOOK="_idx" COLLECTION="nw41" TIDREF="i4335"
Supervisory equivalentCOLNAME=2 ROTATE="0" MOREROWS="0"Has supervisory rights to the Volume object and the file system.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9924"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"
Console IDXID="w9925"BOOK="_idx" COLLECTION="nw41" TIDREF="i3098"
operatorCOLNAME=2 ROTATE="0" MOREROWS="0"Becomes an Operator property of the Server object.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9926"BOOK="_idx" COLLECTION="nw41" TIDREF="i4832"
Workgroup managerCOLNAME=2 ROTATE="0" MOREROWS="0"Has supervisor right to the User objects created in 3.x, the Bindery Context object, and any new objects created.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9927"BOOK="_idx" COLLECTION="nw41" TIDREF="i65"
User 
Account ManagerCOLNAME=2 ROTATE="0" MOREROWS="0"Has supervisor rights to objects managed in 3.x (Object Supervisor property). Cannot create new objects.COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w9928"BOOK="_idx" COLLECTION="nw41" TIDREF="i4690"
Print queue operatorCOLNAME=2 ROTATE="0" MOREROWS="0"Becomes an Operator property of the Print Queue object. COLNAME=1 ROTATE="0" MOREROWS="0"Print queueCOLNAME=2 ROTATE="0" MOREROWS="0"Becomes a Print Queue object. (Print queues get upgraded to 4.1 queues; Bindery object type=3).COLNAME=1 ROTATE="0" MOREROWS="0"PrinterCOLNAME=2 ROTATE="0" MOREROWS="0"Becomes a Printer object (if you run PUPGRADE.NLM to upgrade print services).COLNAME=1 ROTATE="0" MOREROWS="0"Printer definition/print job configurationCOLNAME=2 ROTATE="0" MOREROWS="0"Become Directory properties in 4.1 (if you run PUPGRADE.NLM to upgrade print services).COLNAME=1 ROTATE="0" MOREROWS="0"Print serverCOLNAME=2 ROTATE="0" MOREROWS="0"Becomes a Print Server object (if you run PUPGRADE.NLM to upgrade print services).PAGENUM=128 ID="BP131"LABEL="B-7" PGWIDE=0 TOCENTRY="1"IDXID="w9929"BOOK="_idx" COLLECTION="nw41" TIDREF="i447"IDXID="w9930"BOOK="_idx" COLLECTION="nw41" TIDREF="i447"ID="FM16922" Bindery Objects that Remain Unchanged in NetWare Directory ServicesCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"3.1x bindery objectCOLNAME=2 ROTATE="0" MOREROWS="0"After upgrading to 4.1VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Bindery queueCOLNAME=2 ROTATE="0" MOREROWS="0"Represents a queue placed in the Directory tree by an upgrade or migration utility, but that NetWare Directory Services cannot identify. This object is for backward compatibility with IDXID="w9931"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
bindery-based utilities.COLNAME=1 ROTATE="0" MOREROWS="0"Other queuesCOLNAME=2 ROTATE="0" MOREROWS="0"Become Bindery IDXID="w9932"BOOK="_idx" COLLECTION="nw41" TIDREF="i438"
Queue objects to maintain the original type of queues.LABEL="C"PAGENUM=129 ID="BP132"Special Instructions for LAN ServerRENDERAS="SECT1"Upgrading from LAN Server to NetWare 4.1If you are upgrading from LAN Server* to NetWare® 4.1, you should be aware of the following items:MARK=BULLETIDXID="w9933"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"
OS/2* extended attributes and IDXID="w9934"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"
long names are not migrated. Files that use extended attributes or long names are not copied. All files must conform to DOS 8.3 naming conventions.Add "/API /NMS:2 /NVS:2" to the DOSLAN.INI file. See your LAN Server documentation for order of parameters.You must either be the IDXID="w9935"BOOK="_idx" COLLECTION="nw41" TIDREF="i1177"
domain Administrator or have administrative IDXID="w9936"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"
privileges in the domain.Use Novell's IDXID="w9937"BOOK="_idx" COLLECTION="nw41" TIDREF="i3062"
ODINSUP or IDXID="w9938"BOOK="_idx" COLLECTION="nw41" TIDREF="i2057"
LANSUP protocol stack. These products allow for loading dual requesters on DOS clients to allow access to IDXID="w9939"BOOK="_idx" COLLECTION="nw41" TIDREF="i2689"
both LAN Server and IDXID="w9940"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"
NetWare server resources.For more information on ODINSUP, see NetWare Application Notes articles entitled "ODINSUP Interoperability Configurations for DOS Workstations" (February 1993) or "NetWare and Windows for Workgroups Integration" (March 1993).When running interoperably between NetWare and LAN Server or LAN Manager*, use NETX.COM.You must be logged in to the IDXID="w9941"BOOK="_idx" COLLECTION="nw41" TIDREF="i1177"
domain you want to migrate from.IDXID="w9942"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"
LAN Server permissions (rights) do not flow down, but are limited to the directory where they are set. After the migration to NetWare 4.1, rights do flow down the IDXID="w9943"BOOK="_idx" COLLECTION="nw41" TIDREF="i3851"
directory structure.LAN Server universal rights are not migrated. These rights are similar to NetWare rights given to group EVERYONE.PAGENUM=130 ID="BP133"IDREF="FM62878"Table C-1 describes LAN Server and LAN Manager components that are not migrated.LABEL="C-1" PGWIDE=0 TOCENTRY="1"IDXID="w9944"BOOK="_idx" COLLECTION="nw41" TIDREF="i2041"ID="FM62878" LAN Server and LAN Manager Components That Are Not MigratedCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="10*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"LAN Server componentCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationCOLNAME=3 ROTATE="0" MOREROWS="0"NetWare equivalentVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ALERTERCOLNAME=2 ROTATE="0" MOREROWS="0"Notifies the administrator of defined events. COLNAME=3 ROTATE="0" MOREROWS="0"None (but NetWare keeps track of many of these events)COLNAME=1 ROTATE="0" MOREROWS="0"ATCOLNAME=2 ROTATE="0" MOREROWS="0"Gives execute command at a set time.COLNAME=3 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"AUTO LOG OFFCOLNAME=2 ROTATE="0" MOREROWS="0"Shuts the system down after extended inactivity.COLNAME=3 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"External resourcesCOLNAME=2 ROTATE="0" MOREROWS="0"These are LAN Server- specific resources that don't apply to NetWare.COLNAME=3 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"MACHINE IDCOLNAME=2 ROTATE="0" MOREROWS="0"Unique workstation name.COLNAME=3 ROTATE="0" MOREROWS="0"Use network board IDCOLNAME=1 ROTATE="0" MOREROWS="0"NETRUNCOLNAME=2 ROTATE="0" MOREROWS="0"Allows you to run programs at the server.COLNAME=3 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"REPLICATORCOLNAME=2 ROTATE="0" MOREROWS="0"Periodically duplicates selected files.COLNAME=3 ROTATE="0" MOREROWS="0"NoneCOLNAME=1 ROTATE="0" MOREROWS="0"RIPLCOLNAME=2 ROTATE="0" MOREROWS="0"Remote Initial Program LoadCOLNAME=3 ROTATE="0" MOREROWS="0"Remote Reset or Remote Boot: the Remote Boot image file must be set up on the NetWare serverCOLNAME=1 ROTATE="0" MOREROWS="0"Station restrictionsCOLNAME=2 ROTATE="0" MOREROWS="0"Defines which machine ID can be used by a username to log in to the LAN Server domain.COLNAME=3 ROTATE="0" MOREROWS="0"Station Restrictions: must be set up using NetWare and network board ID.