User Guide

Manuals Brands Novell Manuals Other NETWARE 6-DOCUMENTATION

October 25, 2001

Novell Confidential

NetWare 6 Readme

NetWare

README

www.novell.com

6.0

Novell

Summary of content (3761 pages)

PAGE 1

NetWare 6 Readme Novell NetWare 6 ® www.novell.com 6.
PAGE 2

Manual 99a 38 July 17, 2001 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, 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.
PAGE 3

Manual 99a 38 July 17, 2001 Novell Trademarks ConsoleOne is a trademark of Novell, Inc. DirXML is a trademark of Novell, Inc. eDirectory is a trademark of Novell, Inc. GroupWise is a registered trademark of Novell, Inc. in the United States and other countries. Hardware Specific Module and HSM are trademarks of Novell, Inc. Internetwork Packet Exchange and IPX are trademarks of Novell, Inc. IPX/SPX is a trademark of Novell, Inc. Link Support Layer and LSL are trademarks of Novell, Inc.
PAGE 4

Manual NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 5

Manual 99a 37 June 14, 2001 Contents NetWare 6 Readme 7 1 General Information 9 2 Installation and Upgrade 13 Before the Installation or Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 During the Installation or Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 After the Installation or Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 3 ConsoleOne 1.3 21 4 DNS/DHCP 25 5 iManage 1.0 and iMonitor 1.
PAGE 6

Manual 99a June 14, 2001 37 18 Novell Compatibility Mode Driver 63 19 Novell eDirectory 8.6 for NetWare 65 20 Novell GroupWise 67 21 Novell iFolder 69 22 Novell International Cryptographic Infrastructure (NICI) 71 23 Novell Modular Authentication Service (NMAS) 73 24 Novell Native File Access Protocols General Issues . . . . Macintosh / AFP Issues Windows / CIFS Issues UNIX / NFS Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 . . . .
PAGE 7

Manual 99a 38 July 17, 2001 NetWare 6 Readme This document provides information on known issues and limitations for NetWare® 6. The issues are divided into sections based on product features. Use the Table of Contents or the Search feature to locate the information you need. For information about additional issues discovered after the release, see the Novell Support Knowlegebase (http://support.novell.com/search/ kb_index.jsp) and enter TID #10064501.
PAGE 8

Manual 8 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 9

Manual 1 99a July 17, 2001 38 General Information This chapter contains general information about the NetWare® 6 release. For information about additional issues discovered after the release, see the Novell® Support Knowlegebase (http://support.novell.com/search/ kb_index.jsp) and enter TID #10064501. NetWare 6 Contents The NetWare 6 package consists of the following: Operating System CD Client CD Novell ClientTM 4.81 for Windows* NT*/2000 Novell Client 3.31 for Windows 95/98 NMAS Client 2.
PAGE 10

Manual 99a 38 July 17, 2001 MP-Enabled Components The following core NetWare 6 components are MP-enabled: Core operating system ODITM (including LSLTM, LAN, TSMTM, MSMTM, HSMTM) TCP/IP NCP/IP Winsock (including NILE and BSD) CLIB BSD calls Novell Storage ServicesTM file system Novell eDirectoryTM, including LDAP Novell JVM for NetWare Novell Modular Authentication Service (NMASTM) Novell Cluster ServicesTM NetWare Enterprise Web Server NetWare Web Search NetWare FTP Server
PAGE 11

Manual 99a July 17, 2001 38 Novell Portal Services 1.0 Novell Single Sign-on 2.1 If you install Novell Single Sign-on to a NetWare 6 server that is not an SD Key Server and you select No when prompted to make the server an SD Key Server, you may see messages indicating that Novell Single Signon did not successfully install. The messages and entries in the log file (sys:system\sssi.log) falsely indicate that the SD Key Client and Secret Store Service were not installed successfully.
PAGE 12

Manual 99a 38 July 17, 2001 Client DOS Utilities Many DOS utilities have been removed from NetWare 6. The following utilities are still included for your convenience, but they are not supported: CAPTURE CX FILER LOGIN LOGOUT MAP NCOPY NDIR NetWare Administrator NLIST NPRINTER RIGHTS International Issues Euro Character. There are several places throughout Netware 6 where the euro character is displayed as its hex value “[20AC]”.
PAGE 13

Manual 2 99a 38 July 17, 2001 Installation and Upgrade This chapter contains the following subsections: “Before the Installation or Upgrade” on page 13 “During the Installation or Upgrade” on page 16 “After the Installation or Upgrade” on page 18 You should also review the other sections of this Readme for additional installation and upgrade issues. For complete instructions on preparing the network and installing or upgrading to NetWare 6, see the NetWare 6 Overview and Installation Guide.
PAGE 14

Manual 99a 38 July 17, 2001 Upgrading NetWare 5 Servers with NDS 7 and NSS Volumes A NetWare 5 server with NDS® 7 and NSS volumes is inaccessible after completing the Prepare a Server with NDS 7 and NSS step in NetWare Deployment Manager. For this reason, complete this step just before you upgrade to NetWare 6.
PAGE 15

Manual 99a 38 July 17, 2001 Deployment Manager and specifically complete Step 3: Prepare for NDS eDirectory 8.6. This step identifies and updates a server on the network that holds the Master or Read/Write replica of the Root of the tree. NetWare Deployment Manager (NWDEPLOY.EXE) runs on a Windows workstation and is located on the NetWare Operating System CD. For complete instructions on preparing the network, see the NetWare 6 Overview and Installation Guide.
PAGE 16

Manual 99a 38 July 17, 2001 During the Installation or Upgrade Copying and Overwriting Existing Files Because all the components of NetWare 6 have been tested as a whole, you should select Overwrite on all files that report a new date conflict during an upgrade. Installing from a Bootable CD If your server supports a bootable CD-ROM and you want to boot to the NetWare Operating System CD, make sure that the machine boot order specifies that the CD boots before the hard drive.
PAGE 17

Manual 99a 38 July 17, 2001 Installing a NetWare 5.1 Server into a Tree with a NetWare 6 SDI Server When installing a NetWare 5.1 server into a tree with a NetWare 6 Security Domain Infrastructure (SDI) server, the installation fails with a “125” error due to a security upgrade. The following error message is displayed: Error while Contacting Security Domain Infrastructure Key Server: NW6_1.Servers.RCH.TX.
PAGE 18

Manual 99a 38 July 17, 2001 Search, iManage, NetWare Web Access, and Novell NetStorage. If you plan to install any of these products after the upgrade, make sure that you install the Apache Web server first. After the Installation or Upgrade Missing Device Drivers The server installation program copies to a startup directory (C:\NWSERVER) only drivers (such as HAMs, CDMs and PSMs) for devices that were auto-detected during the installation process.
PAGE 19

Manual 99a 38 July 17, 2001 To maintain backup and restore services on NetWare 6 and your network, you must install the patch. The patch will supersede the SMS modules installed by default during the NetWare 6 installation. For more information, see the Readme included with the patch. Agent Installation for GroupWise 6 Replaces LDAP Files Needed by iFolder The Agent Installation program for GroupWise® 6 lets you overwrite LDAP modules that consequently disable iFolder running on NetWare 6.
PAGE 20

Manual 20 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 21

Manual 3 99a July 17, 2001 38 ConsoleOne 1.3 Installing the NICI Client Some of the ConsoleOne snap-ins for NetWare 6 require the NICI Client. To use those snap-ins, you must install NICI on every workstation where you will use ConsoleOne. IMPORTANT: Two versions of NICI are provided for Windows platforms: 1.5.7 and 2.0.2. We recommend that you install both versions. NICI 1.5.7 is implemented as a kernel driver, while NICI 2.0.2 is implemented as a shared DLL. Applications using NICI 1.5.
PAGE 22

Manual 99a 38 July 17, 2001 ConsoleOne Is Not Refreshing Properly With 3D mouse pointer software installed on a machine running ConsoleOne, the screen might appear to not refresh properly. To solve this problem, remove the 3D mouse pointers. For more information on this issue, refer to Solution #10058840 (http:// support.novell.com). ConsoleOne Does Not See the Tree In a pure IP environment, ConsoleOne does not see the eDirectoryTM tree of the server that ConsoleOne is running on.
PAGE 23

Manual 99a 38 July 17, 2001 Option Setting File Cache Level Change from 3 to 0. File Write Through Change from Off to On. True Commit Change from Off to On. 4 Click OK. Support for the Hong Kong Supplementary Character Set This release of ConsoleOne does not support the Hong Kong Supplementary Character Set (HKSCS). We are currently working on a patch to allow HKSCS support in future releases of ConsoleOne. ConsoleOne 1.
PAGE 24

Manual 24 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 25

Manual 4 99a 38 July 17, 2001 DNS/DHCP Known Issues The Novell® iManage browser-based DNS/DHCP management utility does not support the following: IPV6.INT zones Configuring DHCP Option 60 Pooled Mac addresses (Use the Java Management tool to manage this feature.) While importing the DHCP configuration, a default subnet address range is automatically created. The DHCP Server reference is not automatically updated; you can manually update the server reference later.
PAGE 26

Manual 99a 38 July 17, 2001 While importing the DHCP configuration, if the subnet address range contains a reference to an external DHCP server, this reference is automatically replaced by a reference to the default DHCP server that you specify. The Novell DNS and DHCP servers are based on ISC BIND Version 4.9.6 and ISC DHCP Version 2.
PAGE 27

Manual 5 99a 38 July 17, 2001 iManage 1.0 and iMonitor 1.5 for Novell eDirectory 8.6 This chapter contains the following subsections: “iManage 1.0” on page 27 “iMonitor 1.5” on page 31 iManage 1.0 Associating a Role to a Scope If you add a member to a role and then try to associate that role to a scope that does not exist, you will get an error message. Click OK to clear the error message.
PAGE 28

Manual 99a 38 July 17, 2001 Setting Up Encoding for Foreign Languages If you are experiencing problems with correct character display in iManage, you should verify that your browser's language and character set encoding are configured properly.
PAGE 29

Manual 99a 38 July 17, 2001 When creating new rbsRole objects in iManage, the tasks for that role should be assigned from the same rbsCollection container that the role was created in. Out-of-Memory Errors If you receive out-of-memory errors when running iManage (Error: 500 on client browsers and OutOfMemory Java exception on the Server Login Screen), edit the SYS:TOMCAT\33\BIN\TOMCAT33.
PAGE 30

Manual 99a 38 July 17, 2001 Modifying the iManage Installation Path during a NetWare 6 Custom Installation You should not modify the iManage installation path during the NetWare custom installation unless the container you specify in the installation field already exists. If you do specify a container that does not exist, you will receive -601 (No Such Entry) errors on the following files: .../BASE/EDIR.XML .../DNSDHCP/DNSDHCP.XML .../IPRINT/IPRINT.XML .../NLS/NLS.
PAGE 31

Manual 99a 38 July 17, 2001 Performing a Post-installation of iManage When performing a post-installation of iManage, you must restart both Apache and Tomcat after the installation is complete in order for iManage to work properly. Granting Additional eDirectory Rights to Owners of rbsCollection Containers When you make a user an owner of an rbsCollection container, you should grant that user the additional eDirectory rights needed to fully administer that collection.
PAGE 32

Manual 32 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 33

Manual 6 99a 38 July 17, 2001 iPrint/NDPS Installing Printers on Windows NT/2000 To install a printer on Windows NT/2000, you must have Administrator rights or be a Power User. Managing iPrint iPrint can be managed with the Novell® iManage browser-based management utility. Not all operations have been included in iManage. For those operations that you cannot complete in iManage, you can use NetWare Administrator. For information on setting up iManage, see the Novell iManager Administration Guide.
PAGE 34

Manual 99a 38 July 17, 2001 Running iPrint Map Designer To have full functionality of the iPrint Map Designer, IPPSRVR.NLM must be loaded before starting iPrint Map Designer. Changing Printer Security Levels If you change the printer agent security level to high and do not check the Requires Security check box on the IPP Support page of the printer’s Client Support Page in iManage, you will receive the following error: Error message: iPrint Client - "The request requires user authentication.
PAGE 35

Manual 99a 38 July 17, 2001 3 Remount the volume with TTS enabled by entering mount NDPS_Manager_host_volume_name iPrint Client Install Page Has No Link When using a map generated by the iPrint Map Designer, if users click on a printer from a workstation that does not have the iPrint client installed, they might be redirected to an iPrint client install page that does not have the client install link. To resolve this, use a text editor to edit LOGIN\IPPDOCS\TOOLS.
PAGE 36

Manual 36 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 37

Manual 7 99a 38 July 17, 2001 IPX Dependencies If you select TCP/IP as your only protocol during the NetWare® 6 installation, IPX/SPXTM will no longer be available. If you have problems loading IPX/SPX-dependent NLMTM programs, add the following line after the Server Name in the AUTOEXEC.NCF file: serverID XXXXXXXX Replace XXXXXXXX with the internal IPXTM address you want to assign to the server. This address can be numbers and letters A, B, C, D, E, F only (serverID is a hex value).
PAGE 38

Manual 38 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 39

Manual 8 99a 38 July 17, 2001 NetWare Enterprise Web Server No NDS Replica on the Web Server If the Web server does not have an NDS® replica, users cannot access private pages through the Web server. Users are allowed to authenticate, but the page access returns a 404 error. To avoid this problem, make sure the Web server has an NDS replica. Internet Explorer Issues Folder operations in WebDAV have limitations.
PAGE 40

Manual 99a 38 July 17, 2001 3 Click Microsoft Internet Explorer 5 > Change/Remove > Repair Internet Explorer. 4 Restart your system if required. INDEX.HTML Renamed When upgrading to NetWare 6 from an earlier version of NetWare, the file INDEX.HTML in the document root of the Enterprise Web Server (volume:\NOVONYX\SUITESPOT\DOCS) might be renamed to INDEX_ENTERPRISE.HTML. This occurs when the new NetWare 6 default home page is installed as INDEX.HTML.
PAGE 41

Manual 9 99a July 17, 2001 38 NetWare FTP Server Intruder Detection To disable intruder detection, both intruder detection parameters (INTRUDER_HOST_ ATTEMPTS and INTRUDER_USER_ATTEMPTS) must be set to zero (0). To enable intruder detection, both intruder detection parameters (INTRUDER_HOST_ ATTEMPTS and INTRUDER_USER_ATTEMPTS) must be set to a value greater than zero (0).
PAGE 42

Manual 42 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 43

Manual 10 99a 38 July 17, 2001 NetWare Migration Wizard 6 NOTE: Additional Readme information is available at the end of the NetWare Migration Wizard 6 installation. Once Migration Wizard is installed, you can also view the Readme before you launch the wizard by clicking Start > Programs > Novell > NetWare Migration Wizard > NetWare Migration Wizard Readme.
PAGE 44

Manual 44 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 45

Manual 11 99a 38 July 17, 2001 NetWare WebAccess Do Not Run NetWare WebAccess and Novell Portal Services on Same Server NetWare WebAccess and Novell Portal Services cannot be run simultaneously on the same server. NetWare WebAccess is based on Novell Portal Services technology. Therefore, the limitation of not being able to run two instances of Novell Portal Services on the same server also applies when attempting to run NetWare WebAccess and Novell Portal Services on the same server.
PAGE 46

Manual 46 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 47

Manual 12 99a 38 July 17, 2001 NetWare Web Manager Upgrading Products Accessible through NetWare Web Manager If you are upgrading products accessible through NetWare Web Manager, new configuration files will be written out and the old configuration files will be backed up in their current location. A “_BKddd” (where ddd is a number) will be appended to the old configuration file. For example, MAGNUS.CONF will become MAGNUS.CONF_BK000. If another installation is done on top of this one, MAGNUS.
PAGE 48

Manual 48 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 49

Manual 13 99a 38 July 17, 2001 NetWare Web Search Server Web Search and Web Server Interaction The NetWare Web Search installation program automatically detects and registers itself with both the Apache and Enterprise Web servers if they are installed on your server. However, the NetWare Web Search Manager (AdminServlet) will be registered only with the Apache Web server, which is the Web server used by all NetWare Web administration utilities (such as NetWare Web Manager and NetWare Remote Manager).
PAGE 50

Manual 99a 38 July 17, 2001 To fix this problem so that all available indexes display on the search page, either use the templates that ship with the newer Web Search (located in the \NSearch\Templates\Samples directory) or make the following changes to the SEARCHTEMPLATE.HTML file that you are currently using as your search page: 1. Change $$BeginCollectionsLoop to $$BeginServerCollectionsLoop. 2. Change $$EndCollectionsLoop to $$EndServerCollectionsLoop.
PAGE 51

Manual 14 99a 38 July 17, 2001 Novell Advanced Audit Service Default Configuration NAAS is not supported a mixed network environment containing NDS® 6.x, 7.x, and 8.x. NAAS enables auditing only for NetWare servers that are running in pure NDS (Novell eDirectoryTM) 8.x networks. It does not audit NetWare servers running NDS 8.x even if they are part of a mixed network running NDS versions earlier than NDS 8.x. Therefore, you should install and configure NAAS only in networks solely running NDS 8.x.
PAGE 52

Manual 99a 38 July 17, 2001 The default configuration utility can make a user Auditor for only one partition. To make the same user an Auditor for more than one partition, do the following: Manually configure NAAS. Grant the auditor Read and Compare rights to the LDAP Server attribute for the partition containing the User object. Grant the auditor Read and Compare rights to the LDAP:keyMaterialName attribute for the partition containing the User object.
PAGE 53

Manual 99a 38 July 17, 2001 Loading the Shims If all three NAAS Shims are required to be loaded, the load order should be FSSHIM.NLM NSSSHIM.NLM DSSHIM.NLM eDirectory Auditing Auditing is not enabled for the following events in Novell eDirectory: DSE ADD MEMBER DSE DELETE MEMBER If the NetWare server hosts two partitions and the server partition is a child partition of the other, only the server partition is audited.
PAGE 54

Manual 54 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 55

Manual 15 99a 38 July 17, 2001 Novell Certificate Server Novell Certificate Server Dependencies The Certificate Server ConsoleOneTM snap-in has the following dependencies: Client NICI 2.0.2 or later for Windows Novell LDAP SDK Novell ClientTM version 4.8 or later for Windows NT/2000, or Novell Client version 3.
PAGE 56

Manual 99a 38 July 17, 2001 Browser Support You must use the Internet Explorer 5 or later or the Netscape Navigator 4 or later browser to use the certificates generated by Novell Certificate Server for SSL or LDAP connections. Older browsers are not supported.
PAGE 57

Manual 16 99a 38 July 17, 2001 Novell Client for Windows See the Novell® ClientTM Readme (http://www.novell.com/documentation/lg/ noclienu/index.html) for issues related to the Novell Client for Windows 95/ 98 and Novell Client for Windows NT/2000.
PAGE 58

Manual 58 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 59

Manual 17 99a July 17, 2001 38 Novell Cluster Services This chapter contains the following subsections: “Installation/Upgrade Issues” on page 59 “Other Issues” on page 60 Installation/Upgrade Issues Perform Cluster Pre-upgrade from an NT Workstation You must run the Deployment Manager option to prepare your cluster for an upgrade from an NT workstation rather than from a Windows 9x workstation. Also ensure that your cluster-enabled volumes are in the Running state.
PAGE 60

Manual 99a 38 July 17, 2001 NSS volume corruption occurs if all of the following conditions exist on your system: The Prepare a Novell Cluster for Upgrade option in the Deployment Manager was run and completed. At least one of the NetWare 5 servers in the cluster was upgraded to NetWare 6. One of the NetWare 5 servers not yet upgraded was rebooted and an attempt was made on that server to create a traditional partition using NWCONFIG.
PAGE 61

Manual 99a 38 July 17, 2001 Do Not Use the Prepare Volume for Use by Novell Cluster Services Option in NetWare Remote Manager If you are using NetWare Remote Manager to create NSS pools and volumes to use in your cluster, do not check the Prepare Volume for Use by Novell Cluster Services check box. This feature does not work and will not correctly cluster enable your newly created pool or volume.
PAGE 62

Manual 62 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 63

Manual 18 99a 38 July 17, 2001 Novell Compatibility Mode Driver There is no control on the Designated Router Election process. To make any migration agent a Designated Router, use INETCFG to assign it the highest priority IP Address.
PAGE 64

Manual 64 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 65

Manual 19 99a 38 July 17, 2001 Novell eDirectory 8.6 for NetWare Installing into an Existing Tree With this release, you cannot install a NetWare 6 server into a partition that has all of its replicas on a NetWare 4 server if that server will get a replica of the partition. If you are installing into a tree that has NetWare 5 servers, each NetWare 5.0 server must be running NetWare 5.0 Support Pack 6a (http:// support.novell.com/misc/patlst.htm#nw) or later. Each NetWare 5.
PAGE 66

Manual 99a 38 July 17, 2001 Additional Readme Information For information on additional eDirectory issues for this release, see TID #10063534 (http://support.novell.com) in the Novell Support Connection Knowledgebase.
PAGE 67

Manual 20 99a 38 July 17, 2001 Novell GroupWise In order to use GroupWise® 5.5 Enhancement Pack WebAccess on NetWare® 6, you must download and install the WebAccess 5.5 EP SP4 Rev 3 patch or later (FWAEP4C.EXE, FWAEP4D.EXE, etc.) available from Novell Support Connection® Patches and Files (http://support.novell.com/filefinder). The patch is a prerelease version (Field Test File) of GroupWise 5.5 Enhancement Pack Support Pack 4. Your system must be running GW 5.5 SP3a before you can install this patch.
PAGE 68

Manual 68 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 69

Manual 21 99a 38 July 17, 2001 Novell iFolder Selecting the Pre-migration Server Option If you install iFolder via a Custom installation of the Pre-migration server option available in NetWare 6, make sure NetWare Web Manager is also selected to be installed. You will need to reboot your server after the installation in order for iFolder to work properly.
PAGE 70

Manual 99a 38 July 17, 2001 Apply the iFolder Patch 1 Go to the Novell Support Web site (http://support.novell.com) and click Patches and Files. 2 Enter IFLDRCLA.EXE The A is a variable and will change as the iFolder client is updated. 3 Double-click IFLDRCLA.EXE to begin the download process. Creating a User Account Before you can access your iFolder files from the iFolder Web site, you must first download and install the iFolder client and then log in.
PAGE 71

Manual 22 99a 38 July 17, 2001 Novell International Cryptographic Infrastructure (NICI) Some of the ConsoleOneTM snap-ins for NetWare® 6 require the NICI Client. To use those snap-ins, you must install NICI on every workstation where you will use ConsoleOne. IMPORTANT: Two versions of NICI are provided for Windows platforms: 1.5.7 and 2.0.2. We recommend that you install both versions. NICI 1.5.7 is implemented as a kernel driver and NICI 2.0.2 is implemented as a shared DLL.
PAGE 72

Manual 72 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 73

Manual 23 99a 38 July 17, 2001 Novell Modular Authentication Service (NMAS) NICI Client You must have the NICI Client installed on each client that will run ConsoleOneTM and NMAS. See “Novell International Cryptographic Infrastructure (NICI)” on page 71 for more information.
PAGE 74

Manual 99a 38 July 17, 2001 4 Configure the BorderManager services to use the Login Policy Object. Refer to the Border Manager documentation (http://www.novell.com/ documentation/) for details. 5 Run the NMAS installation from the server-side GUI. 6 Reinstall any NMAS Methods and re-create any NMAS login sequences. Simple Password and Force Password Change The Simple Password method is used for various authentication services in NetWare 6.
PAGE 75

Manual 24 99a 38 July 17, 2001 Novell Native File Access Protocols This chapter contains the following subsections: “General Issues” on page 75 “Macintosh / AFP Issues” on page 78 “Windows / CIFS Issues” on page 80 “UNIX / NFS Issues” on page 82 General Issues Update NetWare 5 Servers Running NMAS before Installing Novell Native File Access Protocols Before installing Novell Native File Access Protocols (as part of the NetWare 6 installation or otherwise), all NetWare 5 servers (in the tree)
PAGE 76

Manual 99a 38 July 17, 2001 Uninstalling the Software To remove the software, complete the following steps on each server running Novell Native File Access Protocol software. 1 Run Native File Access for Macintosh* (AFP) Uninstall using NWCONFIG or the GUI Uninstall. Reboot the server or unload the AFPTCP.NLM (AFPSTOP.NCF). 2 Run Native File Access for Windows (CIFS) Uninstall using NWCONFIG or the GUI Uninstall. Reboot the server or unload the CIFS NLMTM programs (CIFSSTOP.NCF).
PAGE 77

Manual 99a 38 July 17, 2001 Possible Login Error If you encounter a login error while connecting to the server from a Macintosh or Windows workstation, run ConsoleOne and verify that the Simple Password, LSMCIFS, and LSMAFP login sequences are installed. If the sequences are not installed, do the following: 1 Run ConsoleOne and locate the Security container. 2 Double-click the Security container. 3 Right-click the Login Policy icon and click Properties > New Sequence.
PAGE 78

Manual 99a 38 July 17, 2001 Macintosh / AFP Issues AppleTalk Not Supported as a Transport Protocol The legacy AppleTalk* protocol stack is not supported as a transport protocol in this version of Novell Native File Access Protocols for Macintosh. AppleTalk migration is targeted for a subsequent release. Older Mac applications that have unique dependencies upon AppleTalk as a transport protocol must be updated to a version that is known to work over TCP/IP.
PAGE 79

Manual 99a 38 July 17, 2001 Mac OS 8.x Will Not Mount Volumes Checked to Mount at Startup Mac OS 8.x will not mount volumes checked to mount at startup. To resolve this, add the server volume's alias to the StartUp Items folder inside the System Folder on the Mac's local startup disk. Drag a NetWare Folder to the Trash and Errors Occur When you drag a NetWare folder to the trash, an error occurs because it is unable to leave the item in the trash and it will delete it immediately.
PAGE 80

Manual 99a 38 July 17, 2001 Volume ID You might get pervasive errors in a clustered AFP environment when the volume ID is set to higher than 32. To eliminate these errors, use ConsoleOne to edit the cluster AFP/TCP volume resource and change the volume ID to 32 or lower. Remember to make the value you choose unique from other volume IDs. Windows / CIFS Issues Problem with Microsoft Patch Microsoft recently released a patch to its Windows NT 4.
PAGE 81

Manual 99a 38 July 17, 2001 Password Changes Trying to change a password from a Windows 9x or NT4 client workstation might fail if the default network username and password in the client's cache is not a valid combination on the CIFS server where the password change was attempted. To avoid this problem, validate the username and password combination in the client's cache on the CIFS server before attempting the password change.
PAGE 82

Manual 99a 38 July 17, 2001 MS Paint "Out of Memory" Error CIFS users might occasionally see an Out of Memory error when using MS Paint on a Windows NT workstation. This error message is incorrect and no processes are out of memory. The error message will disappear if the data file is first saved to local storage and then copied to the remote storage directory. UNIX / NFS Issues Upgrade Issues Before beginning an upgrade from NetWare 5.0 with NetWare NFS Services 2.
PAGE 83

Manual 99a 38 July 17, 2001 When Native File Access for UNIX is installed, the nfsstart entry is added to AUTOEXEC.NCF, so the services are not automatically available after installation. To make Native File Access for UNIX available, run nfsstart after installation or reboot the server. ConsoleOne If you administer NFS exports of multiple servers and switch between them, it is possible that the data you view is for the previous server.
PAGE 84

Manual 99a 38 July 17, 2001 Traditional volumes can be mounted only using NFS version 2. Even though showmount shows the volumes as exported, they are not mountable using NFS version 3. You need to explicitly mount the exported traditional volumes specifying the mount version as 2.
PAGE 85

Manual 25 99a 38 July 17, 2001 Novell NetDrive NetDrive supports HTTPS for WebDAV only on Windows NT 4.0 and Windows 2000 workstations. If your NetDrive client is behind a firewall regulated by a BorderManagerTM server that is configured for FTP proxy and authentication, NetDrive cannot map a network drive via FTP to any servers that reside outside the firewall. To solve this problem, disable the FTP proxy authentication on the BorderManager server.
PAGE 86

Manual 86 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 87

Manual 26 99a 38 July 17, 2001 Novell NetStorage Changing iFolder IP Address after NetStorage Installation If you change the iFolderTM server IP address, DNS name, or port number after NetStorage has been installed, you must either reinstall NetStorage or edit the XSYNCNSP\IFOLDER SERVER registry setting to reflect the change. NetStorage will not function properly without this change.
PAGE 88

Manual 99a 38 July 17, 2001 Internet Explorer Unable to Open Some Web Folders If you use Microsoft Web Folders with NetStorage to create a new folder, you might not be able to open that folder using Internet Explorer. Hosts File Not Usable by NetStorage NetStorage cannot use the SYS:\ETC\HOSTS file to resolve DNS names. If you have applications that can use DNS names (such as iFolder), your DNS names must be registered with a valid DNS server which is identified in the SYS:\ETC\RESOLVE.CFG file.
PAGE 89

Manual 27 99a 38 July 17, 2001 Novell Storage Services Previous NSS Volumes Not Automatically Upgraded Previous NSS volumes are not automatically upgraded during the NetWare 6 installation process. After you install NetWare and reboot the server, you can upgrade previous NSS volumes to the current NSS volume layout. Before you upgrade previous NSS volumes, you must ensure that NDS® is up and running and that the Backlink process is complete.
PAGE 90

Manual 99a 38 July 17, 2001 Modifying a Volume’s NDS Object When Converting Volumes You can convert traditional volumes to NSS volumes after you upgrade to NetWare 6. The following is an example of using the volume conversion utility (VCU) when you want to modify the volume’s NDS object: vcu TRAD NSSPOOL provo_tree\novell\provo ds_poolname ds_volName DS tree: provo_tree DS context:provo.
PAGE 91

Manual 28 99a 38 July 17, 2001 Novell TCP/IP Missing INETCFG Information If any information is missing from INETCFG after a new installation, it is because no information was uploaded to the TCPIP.CFG file. Similarly, if INETCFG information is missing or you get configuration error messages after an upgrade, it is because no new information was uploaded to the TCPIP.CFG file and some entries have become invalid. In either case, delete the SYS:/ETC/TCPIP.CFG file and reconfigure through INETCFG.
PAGE 92

Manual 99a 38 July 17, 2001 Load Balancing Load balancing might not work when all the clients’ IP address are mapped to a single server NIC and all the clients start data transfer simultaneously. Multihoming might not work in some cases where the hosts are supernetted. Viewing Bindings You can discover and load drivers using NWCONFIG and subsequently bind the boards to IP addresses through INETCFG. However, NWCONFIG does not show the bindings.
PAGE 93

Manual 29 99a 38 July 17, 2001 Pervasive.SQL Pervasive.SQL 2000 Database Licenses A permanent two-user license is installed during the NetWare 6 installation process. If you are upgrading an existing NetWare server, an unlimited license that will expire 90 days after installation is also installed. The permanent two-user license is intended for use by the NetWare operating system. If you have additional applications using Pervasive.SQL 2000 or Pervasive.
PAGE 94

Manual 99a 38 July 17, 2001 Known Issues So that Pervasive can update known issue reports periodically between releases, all Known Issues are now published in the Pervasive Knowledge Base (http://support.pervasive.com/eSupport/). Search on "Pervasive.SQL 2000 Service Pack 3 known issues". You can also see a static list of known issues, including links to the associated Knowledge Base articles, at their Fixed Defects and Known Issues Web page (http://www.pervasive.com/support/updates/psql2kfixed.asp).
PAGE 95

Manual 30 99a 38 July 17, 2001 Scripting Products Scripting Products Included The following scripting products are included with NetWare 6. Readme information can be found at the links provided. Novell Script for NetWare (NSN) (http://www.developer.novell.com/ ndk/nscript.htm#readme) Perl for NetWare (http://www.developer.novell.com/ndk/ perl5.htm#readme) NetBasic* 6.0 (http://www.developer.novell.com/ndk/nb6.htm#readme) Universal Component System (UCS) (http://www.developer.novell.
PAGE 96

Manual 99a 38 July 17, 2001 Novell Script Pages Novell® Script Pages (NSP) prevents any NSP page from being uploaded and executed without the execute bit set on the NSP file itself or on the parent directory. To mark an NSP file or directory with the execute bit, do the following: 1 Access NDS® from the NetWare Web Manager General Administration page. 2 Navigate to the NSP file or directory and display the access control rights for that object. 3 Check the Execute check box and save your changes.
PAGE 97

Manual 31 99a 38 July 17, 2001 Storage Management Services (SMS) This chapter contains the following subsections: “Backup and Restore Issues” on page 97 “Client Issues” on page 98 “Other Issues” on page 99 Backup and Restore Issues Update SMS Components A new release of Storage Management Services (SMS) is available at the Novell Support Web site (http://support.novell.com). This release contains important fixes to the SMS components delivered with NetWare 6.
PAGE 98

Manual 99a 38 July 17, 2001 Exclude/Include Options for Workstation Restore When Exclude/Include options are set for a workstation restore, only the selected data sets are restored. The log file and the status window of the session reports incorrect status. All the data sets are reported as restored, whereas only the data sets matching the specified options are actually restored. Hard Links Not Supported by NSS in NetWare 6 Hard links are not supported by NSS in NetWare 6.
PAGE 99

Manual 99a 38 July 17, 2001 If you need to assign a security policy to a group, do the following: Return to the Administrative Tools window and click Local Security Policies > Local Policies > User Rights Assignment. The list of policies and the local and effective settings are displayed. Double-click Act As Part of the Operating System Security Policy to display the Local Security Policy Setting dialog box.
PAGE 100

Manual 100 NetWare 6 Readme NetWare 6 Readme 103-000171-001 October 25, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 101

Manual 32 99a 38 July 17, 2001 Third-Party Adapters, Drivers, and Applications Using Virus Scan Software with NetWare 6 When performing virus scans with Norton or McAfee software, you must exclude the protected NSS volume named _ADMIN. Otherwise, the server will abend. ISA Adapters Are Not Supported on NetWare 6 For performance and scalability reasons, all ISA adapter drivers have been removed from NetWare 6.
PAGE 102

Manual 99a 38 July 17, 2001 Suggested LAN Driver Substitution In some cases there are no substitutes for LAN drivers. For example, Compaq no longer supports the Netflex 3 LAN hardware associated with the CPQNF3.LAN driver. 3Com provides limited support for their 3c90x LAN card line to LAN cards starting with the 3c905b hardware and beyond. Unsupported versions of these drivers are located on the NetWare 6 Operating System CD and can be installed in the NWSERVER\DRIVERS\UNSUPDRV directory.
PAGE 103

QuickStart Rev 99a 44 August 22, 2001 To begin a QuickStart (English): Click in the box under the word Novell. Insert QuickStart and Title elements. 2. Type the product name. 3. Insert the HeadQS element and type the title of your card. 4. Put in your product version: Click Special > Variable > select the variable named Version > Edit Definition > enter the version number > click Done > Done. It will appear as background text replacing Version X.X.
PAGE 104

QuickStart Rev 99a 44 August 22, 2001 UPGRADE SYSTEM REQUIREMENTS The server to be upgraded must be running one of the following: NetWare 5.1 with Support Pack 2 or later NetWare 5 with Support Pack 6 or later NetWare 4.2 with Support Pack 8 or later NetWare 4.
PAGE 105

QuickStart Rev 99a 44 August 22, 2001 IP address and domain names (required for connecting to the Internet): An IP address An IP address of a domain name server The name of your domain Network board and storage device properties, such as the interrupt and port address (required if not included in NetWare) PREPARE THE NETWORK 1 Run NetWare Deployment Manager (NWDEPLOY.EXE), located on the NetWare 6 Operating System CD. 2 Complete all relevant tasks in the Prepare the Network section.
PAGE 106

QuickStart Rev 99a 44 August 22, 2001 5 Set up Domain Name Service (DNS). 6 Set the server time zone. 7 Set up Novell eDirectory. 8 License the NetWare server. SELECT AND INSTALL ADDITIONAL PRODUCTS Additional installation screens will appear depending on the products you select. 1 Set up Novell Certificate Server. 2 Configure LDAP. 3 Install Novell Native File Access Protocols. 4 Set up NetWare WebAccess. 5 Set up Novell iManage. 6 Install Novell iFolderTM. 7 Install Novell NetStorage.
PAGE 107

QuickStart Rev 99a 44 August 22, 2001 WHAT’S NEXT? Although you have installed or upgraded to NetWare 6, you might need to configure products to work in the new environment. Additionally, some products such as Novell Cluster ServicesTM can be set up only after completing the server installation. You can install products using NetWare Deployment Manager or from the GUI server console screen. Copyright © 2001 Novell, Inc. All rights reserved.
PAGE 108

NetWare 6 Overview and Installation Guide Novell NetWare 6 ® www.novell.
PAGE 109

Manual 99a 38 July 17, 2001 Contents Preface 9 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 User Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 1 Welcome to NetWare 6 11 Make End Users More Effective with NetWare 6 . . . . . . . . . . . . . . . . . . . Eliminate Client Software with Novell Native File Access Protocols . . . . . . . . Print from Anywhere with Novell iPrint . . . . . . . . . . .
PAGE 110

Manual 99a July 17, 2001 38 Migrate Network Data to another Server with NetWare Migration Wizard . Use Other Installation Options to Simplify the Move to NetWare 6 . . . . Let’s Get Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1: Decide What Solutions You Want . . . . . . . . . . . . . . . . . Step 2: Install or Upgrade to NetWare 6 . . . . . . . . . . . . . . . . . . 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 111

Manual 99a Installing Networking Protocols . . . . . . . . . . . . . . . . About Internet Protocol (IP). . . . . . . . . . . . . . . . . About IPX . . . . . . . . . . . . . . . . . . . . . . . . . . Using Both IP and IPX . . . . . . . . . . . . . . . . . . . Setting Up Domain Name Service . . . . . . . . . . . . . . . Configuring a NetWare Server as a DNS Server (Optional) Setting the Server Time Zone . . . . . . . . . . . . . . . . . Setting Up Novell eDirectory . . . . . . . . . . . . . . . . . .
PAGE 112

Manual 8 99a 38 NetWare 6 Overview and Installation Guide NetWare 6 Overview and Installation Guide 100-004725-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 113

Manual 99a 38 July 17, 2001 Preface This book is divided into the following sections: Chapter 1, “Welcome to NetWare 6,” on page 11 explains the features and benefits of NetWare 6. It also includes descriptions of products that ship with NetWare 6 and how they add value to your network. Chapter 2, “Setting Up NetWare 6,” on page 27 explains the prerequisites and instructions for installing a NetWare 6 server.
PAGE 114

Manual 99a 38 July 17, 2001 User Comments We want to hear your comments and suggestions about this manual and the other documentation included with NetWare 6. To contact us, send e-mail to webdoc@novell.com or send comments to: Novell, Inc.
PAGE 115

Manual 1 99a July 17, 2001 38 Welcome to NetWare 6 NetWare® 6 provides your business and your network with new solutions, updated products, and rock-solid applications that give you the power to change. NetWare 6 is the Net services software solution that adds tremendous value to your company’s ability to communicate on your network and on the Internet.
PAGE 116

Manual 99a 38 July 17, 2001 got access to servers on your network. No more client configuration. No more client software. No more problems. For more information, see the Novell Native File Access Protocols Installation and Administration Guide. NetWare Server IP CIFS AFP NFS Windows MAC UNIX Print from Anywhere with Novell iPrint Novell iPrint allows mobile employees, business partners, and customers to access printers from a variety of remote locations using existing Internet connections.
PAGE 117

Manual 99a July 17, 2001 38 Office Laptop John Home Novell iFolder Server John Home LDAP Directory Home John Home John Home Kathy Home Your iFolder Files through a Browser Sam Home Use Novell NetStorage to Access Files with an Internet Browser Novell NetStorage provides simple Internet-based access to file storage and serves as a bridge between a company's protected Novell network and the Internet.
PAGE 118

Manual 99a 38 July 17, 2001 Access Internet Services from a Centralized Location with NetWare WebAccess NetWare WebAccess allows administrators to set up a Web page that lets users access multiple network resources from their Web browser. Users do not need a Novell Client or VPN client to access to their resources. They can access these resources on the Web from any computer with a compliant browser. Customized content is provided through gadgets.
PAGE 119

Manual 99a July 17, 2001 38 For more information about NetWare Remote Manager, see the NetWare Remote Manager Administration Guide. Manage eDirectory Objects from an Internet Browser with iManage iManage runs in an Internet browser and is used for administering, managing, and configuring Novell eDirectory objects. iManage lets you assign specific tasks or responsibilities to users and presents users with only the tools (and accompanying rights) necessary to perform those tasks.
PAGE 120

Manual 99a 38 July 17, 2001 Novell ConsoleOne For more information, see the ConsoleOne 1.3 User Guide. Manage IP Addresses with the Novell DNS/DHCP Administration Tool The DNS/DHCP Administration Tool runs in an Internet browser and enables network administrators to easily configure and manage DNS (Domain Name System Service) and DHCP (Dynamic Host Configuration Protocol Service). For more information, see the Novell DNS/DHCP Services Administration Guide.
PAGE 121

Manual 99a July 17, 2001 38 Internet Laptop PC Firewall Net Services Web Sevices iFolder iLogin iPrint Tomcat Servlet Engine eFrame Web Search Enterprise Web Server etc. Portal Services Apache Web Server HTTP Stack NetWare NetWare 6 lets you manage documents with WebDAV, transfer files using FTP, and communicate with HTTP. For more information, see Getting Results with Novell Web Services.
PAGE 122

Manual 99a 38 July 17, 2001 Publish Web Pages with NetWare Enterprise Web Server The NetWare Enterprise Web Server is optimized to run in the NetWare environment. It serves up Web pages to the Internet, an intranet, or an extranet. Use the NetWare Enterprise Web Server to communicate across departments or throughout the world. Let customers, suppliers, vendors, or consultants access specific information.
PAGE 123

Manual 99a July 17, 2001 38 Track Network Usage with Novell Advanced Audit Service Novell Advanced Audit Service (NAAS) is an Novell eDirectory enabled robust, flexible, and scalable auditing framework. It can audit services, both Novell and third-party, and can provide a single, unified view of audit data for the entire Net. It provides a single point of management by storing configurable audit policies in eDirectory.
PAGE 124

Manual 99a July 17, 2001 38 Novell Cluster Services allows you to configure up to 32 NetWare servers into a high-availability cluster, where resources can be dynamically switched or moved to any server in the cluster. Resources can be configured to automatically switch or be moved in the event of a server failure, or they can be moved manually to troubleshoot hardware or balance the workload.
PAGE 125

Manual 99a July 17, 2001 38 Manage Disk Storage Devices with Novell Storage Services Novell Storage Services (NSS) is a file storage and management system that meets the needs of your growing file system requirements. NSS can take free space from multiple storage devices and create unlimited volumes which can store up to 8 trillion files (each up to 8 terabytes in size). You can quickly mount as many as 255 volumes.
PAGE 126

Manual 99a 38 July 17, 2001 Back up Data with Storage Management Services Storage Management ServicesTM (SMSTM) is the data protection system for all your storage requirements. SMS allows backup and restore of targets such as eDirectory, the file system, or an individual workstation's hard disk onto a tape device that can be stored offsite. If you have a hardware failure, corrupted data, or incorrectly deleted or changed data, you can recover a previous version of the data.
PAGE 127

Manual 99a July 17, 2001 38 segments. The Migration Agent is used to migrate systems from IPX to IP in a phased manner without losing connectivity. For more information, see the Server Communications Administration Guide. Reduce Deployment Costs with NetWare 6 NetWare 6 includes several options that help you install a new server, upgrade a legacy NetWare server, or migrate from a Windows NT* server.
PAGE 128

Manual 99a 38 July 17, 2001 Use Other Installation Options to Simplify the Move to NetWare 6 Several other options are also available to help you install or upgrade to NetWare 6. Quickly upgrade with NetWare Accelerated Upgrade—You can run NetWare Accelerated Upgrade from a Windows client workstation so that you don’t need to be physically present at the server console.
PAGE 129

Manual 99a July 17, 2001 38 Installation Option Refer to Add a NetWare 6 server to an existing network Chapter 2, “Setting Up NetWare 6,” on page 27 Upgrade from NetWare 3, NetWare 4, or NetWare 5 Chapter 3, “Upgrade to NetWare 6,” on page 87 Migrate data from another NetWare server or NT Server NetWare Migration Wizard 6 Administration Guide Use advanced installation/ upgrade options Other Installation Options All this information is available on the NetWare 6 Online Documentation CD included
PAGE 130

Manual 26 99a 38 NetWare 6 Overview and Installation Guide NetWare 6 Overview and Installation Guide 100-004725-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 131

Manual 2 99a July 17, 2001 38 Setting Up NetWare 6 This chapter describes how to set up a NetWare® 6 server.
PAGE 132

Manual 99a 38 July 17, 2001 A Super VGA display adapter A DOS partition of at least 200 MB and 200 MB available space 2 GB of available disk space outside the DOS partition for volume SYS: One network board A CD drive A USB, PS/2*, or serial mouse (recommended but not required) Recommended System Requirements For optimal performance, NetWare 6 has the following recommended system requirements: A server-class PC with two-way Pentium III 700 MHz or higher processors NOTE: NetWare 6 can run
PAGE 133

Manual 99a July 17, 2001 38 Supervisor right to the container where the server will be installed Read right to the Security container object for the eDirectory tree DOS and CD drivers (required if the computer does not boot from CD) You can make a bootable floppy diskette using the MKFLOPPY.BAT program located in the INSTALL directory of the NetWare 6 Operating System CD. Client connection utilities (optional, for installing from a network): Novell ClientTM for DOS and Windows* 3.
PAGE 134

Manual 99a 38 July 17, 2001 Preparing the Network Before you introduce a NetWare 6 server into an existing network, you must run NetWare Deployment Manager to update the network. To update the network for NetWare 6, you must do the following: 1 Log in from a Windows 95/98 or Windows NT/2000 workstation to your existing network as a user with the Supervisor right.
PAGE 135

Manual 99a 38 July 17, 2001 5 Run the View and Update eDirectory Version program to update eDirectory as required. HINT: If you are prompted to log in again while running NetWare Deployment Manager, you can enter the IP address of the server by clicking Details. 6 Run the Prepare for eDirectory program to extend the network schema.
PAGE 136

Manual 99a 38 July 17, 2001 7 (Conditional) If you are upgrading a cluster of NetWare servers, run the Prepare a Novell Cluster for Upgrade program. 8 (Conditional) If you are upgrading a NetWare 5 server running NDS® 7 that has NSS volumes, run the Prepare a Server with NDS 7 and NSS program. 9 Follow the instructions in the Update Certificate Authority (CA) Object step to create or update a Security container object and a Certificate Authority (CA) object.
PAGE 137

Manual 99a July 17, 2001 38 Preparing the Computer To prepare your computer for NetWare 6, do the following: Install computer and networking hardware Create and format a DOS partition Access the installation files Installing Computer and Networking Hardware Follow the manufacturer’s instructions to install and connect the network board and network cabling to your computer. Make sure that all storage devices are properly attached to storage adapters.
PAGE 138

Manual 99a 38 July 17, 2001 diskette. DOS 7 and all required DOS utilities are included on the diskette and on the CD. 5 If the computer already has an operating system installed, such as Windows or NetWare, you should completely remove the partitions and the operating system. Use FDISK to remove partitions. 6 Use FDISK to create an active DOS partition by entering FDISK. Create a primary DOS partition and make it the active partition. See “System Requirements” on page 23 for minimum requirements.
PAGE 139

Manual 99a July 17, 2001 38 Installing the Software To begin the installation, complete the following steps. 1 Insert the NetWare 6 Operating System CD, or log in to the network to access the installation files on the network. 2 At the CD drive or network drive prompt, enter INSTALL. Navigating in the Character-Based Screens The initial screens of the installation program display in text-based mode. Auto-detected and default settings appear on each screen.
PAGE 140

Manual 99a 38 July 17, 2001 Selecting the Language and Accepting the License Agreement The installation program is available in several languages. You can install other language options, such as the language for the operating system or for users, later during the installation program. Accepting each License Agreement means that you have read and you accept terms and conditions contained in the License Agreement. Press F10 to accept.
PAGE 141

Manual 99a 38 July 17, 2001 New Server, Upgrade or Pre-Migration Server You can install NetWare on a new computer or you can upgrade an existing computer running NetWare 4 or NetWare 5. New Server—Installs a new server. Creates a new NetWare partition but does not delete system partitions or other partitions such as DOS, UNIX*, or Windows. If you select Express Installation, you can skip to “Naming the Server” on page 46.
PAGE 142

Manual 99a 38 July 17, 2001 Specifying Server Settings You can change the following default server settings for your networking environment. Server ID Number—A unique server identification number (up to eight hexadecimal digits) identifies the server on the network. The server ID number functions like an internal IPX number.
PAGE 143

Manual 99a 38 July 17, 2001 Selecting the Regional Settings Choose the country, code page, and keyboard mapping for your language and computer.
PAGE 144

Manual 99a 38 July 17, 2001 Mouse Type—Choose a mouse type, if available on the computer. The installation program supports USB, PS/2 and serial mouse types, but a mouse is not required. Video Type—The NetWare installation program is optimized to display with video display hardware that is VESA 2 compliant. NOTE: The video type is not auto-detected by the installation program. You must select the settings for the computer.
PAGE 145

Manual 99a July 17, 2001 38 To delete a driver, in the Options box select Modify. Select the driver field and press Enter. Select the driver to delete and press Delete. To modify a driver, in the Options box select Modify. Select the driver field and press Enter. Select the driver to modify and press Enter. Select the property to modify.
PAGE 146

Manual 99a 38 July 17, 2001 Editing the Properties of the Storage Adapter (If Required) The storage adapter must be installed and configured correctly. Properties such as interrupt, port value, and slot must not conflict with any other device in the computer. If you need specific storage adapter properties, contact the storage adapter manufacturer.
PAGE 147

Manual 99a July 17, 2001 38 Selecting a Storage Device Storage devices such as hard disks, CD drives, and tape devices require a software driver to communicate with the storage adapter. The software driver for the storage device is called a custom device module (CDM). Each type of storage device requires a CDM. The installation program auto-detects many types of storage devices, such as IDE drives, SCSI drives, CD drives, and tape drives.
PAGE 148

Manual 99a 38 July 17, 2001 Creating a NetWare Partition and Volume SYS: Partitions correspond with operating systems, such as NetWare, DOS, or UNIX. Partitions divide a large storage region into smaller, more manageable sections. A single storage device can contain up to four partitions. You can divide NetWare partitions into smaller sections called volumes. Each NetWare partition can contain up to eight volumes.
PAGE 149

Manual 99a 38 July 17, 2001 When removing volume SYS: during a new server installation, you must choose one of the following options: Replace Volume SYS: and its NetWare Partition—This removes the existing volume SYS: as well as the entire NetWare partition containing volume SYS:. Any volume that is part of the NetWare partition that contains volume SYS: is also removed—even if the volume spans to other NetWare partitions.
PAGE 150

Manual 99a 38 July 17, 2001 Volume SYS: Size—The size that you specify for the NetWare partition will be used for the size of volume SYS:. To modify the volume SYS: size, in the Options box select Modify. Select the appropriate storage device. Select the NetWare Partition Size field and press Enter. Backspace over the current size. Type the new size and press Enter. The size of volume SYS: will change accordingly. Press F10 to save the settings and continue.
PAGE 151

Manual 99a July 17, 2001 38 Although a mouse is recommended, you can use the keyboard commands in Table 1 to navigate through the installation program. Use the arrow keys on the numeric keypad for cursor movements. HINT: NumLock (number lock) must be on in order for cursor movements to be enabled on the keypad.
PAGE 152

Manual 99a 38 July 17, 2001 Keystroke Action Hold Shift while pressing keypad Accelerate cursor movement Keypad 5 Select or click an object Keypad 0 Lock a selected object (for dragging) Keypad . (period) Unlock a selected object (to drop) Keypad + (plus) Double-click an object Alt+F7 Move to next window Alt+F8 Move to previous window Enabling Cryptography Some technologies require the use of cryptography. To enable cryptography, you must provide a cryptographic file (.
PAGE 153

Manual 99a July 17, 2001 38 Installing the NetWare Server File System The server should now have a NetWare partition and one volume named SYS:. If you have space available for creating additional partitions and volumes, you can create them now. NOTE: If you have allocated all available space to volume SYS:, you will not be prompted for NetWare server file system information. You can skip to “Installing Networking Protocols” on page 53.
PAGE 154

Manual 99a 38 July 17, 2001 Creating Volumes Volumes are created from free space. A large disk can be divided into several volumes during installation. Conversely, a volume can be distributed over multiple disks. WARNING: Creating a volume that spans two or more storage devices is not recommended. If a volume spans disk devices and one of the devices fails, all data on the entire volume could be lost.
PAGE 155

Manual 99a 38 July 17, 2001 To create a volume, select Free Space and click Create. Type the name of the volume and click OK. To allocate only a portion of the selected free space to the volume, type the amount of space to use and click Apply to Volume. Modifying Volumes The size of any existing volume can be increased but not decreased. To decrease the size of an existing volume, the volume must be deleted and recreated.
PAGE 156

Manual 99a 38 July 17, 2001 Mount Volumes Now—You should mount volumes now if you plan to install additional products and services, such as documentation, on volumes other than volume SYS:. You should also mount volumes that you might be moving forward from a previous NetWare server so they can be updated. Mount Volumes after Installation Completes—If you are installing products and services on volume SYS: only, you can wait to mount volumes after the installation program completes.
PAGE 157

Manual 99a 38 July 17, 2001 Installing Networking Protocols NetWare 6 can process IP (Internet Protocol) network packets and traditional IPX (Internetwork Packet ExchangeTM) packets. Both protocols can be assigned to a single network board, which allows the server to communicate using IP and IPX. To install IP, click a network board and then check the IP check box. Enter the required IP information. To install IPX, click a network board and then check the IPX check box.
PAGE 158

Manual 99a 38 July 17, 2001 About Internet Protocol (IP) Internet protocol (IP) lets your network share data with other IP networks, including the Internet. Using IP requires a unique IP address, a subnet, and a router or gateway address. IP Address—Identifies each device on the network. The address consists of 32 bits, which are represented as decimal values separated by periods, such as 123.45.67.89. If your server will connect to the Internet, you must obtain a unique IP address.
PAGE 159

Manual 99a 38 July 17, 2001 About IPX Novell’s traditional protocol, Internetwork Packet Exchange (IPX), lets you continue using IPX-based applications. If IPX, but not IP, is installed on your server, it will actively process IPX packets and ignore packets using other protocols, such as IP. During the installation program, existing IPX frame types will be detected. The installation program will detect one of the following conditions.
PAGE 160

Manual 99a 38 July 17, 2001 HINT: If this server will not be available to the Internet, you can skip this screen and ignore any associated error messages. If you want this server to be available to the Internet, you must enter the following: Host Computer—The simple, readable name on the DNS server that matches this NetWare server’s name (or the name that you have bound to the network board). HINT: Set up the host computer name on the DNS server to use the NetWare server name.
PAGE 161

Manual 99a 38 July 17, 2001 Configuring a NetWare Server as a DNS Server (Optional) In addition to standard services, a NetWare server can be configured to provide DNS services. The DNS Server setup is done after completing the NetWare server installation. Setting the Server Time Zone The server time and time zone are important in order to synchronize network events. Advanced time synchronization settings are available during the Customize section of the installation.
PAGE 162

Manual 99a 38 July 17, 2001 Choosing the Type of eDirectory Installation To set up eDirectory, you must choose one of the following options: Install the server into an existing eDirectory tree Create a new eDirectory tree Before completing this task, you should understand the concepts relating to eDirectory trees, containers, and context. Tree Name—The top level of the available network resources and must be unique from other eDirectory tree names on the network.
PAGE 163

Manual 99a July 17, 2001 38 Install the Server into an Existing eDirectory Tree Installing your server into an existing eDirectory tree incorporates the server into your network. The server can be installed in any Organization (O) or Organizational Unit (OU) container in the eDirectory tree where you have the Supervisor right. You can create containers during the installation program.
PAGE 164

Manual 99a 38 July 17, 2001 Each eDirectory tree must have a name unique from other eDirectory trees on the network. You will also be prompted to create a user (default name Admin) with the Supervisor right, identify an eDirectory context, and assign a password. Summary Now that you have created a new eDirectory tree or installed the server into an existing eDirectory tree, the NetWare Server object and Volume objects will be installed in the container you specified.
PAGE 165

Manual 99a 38 July 17, 2001 If you have created a new eDirectory tree, a user (default name Admin) with Supervisor rights to the eDirectory tree will be created in the same eDirectory container as the NetWare Server object. IMPORTANT: Record the administrator password and other relevant information before proceeding. Licensing the NetWare Server NetWare 6 must have a valid license in order to function as a server.
PAGE 166

Manual 99a 38 July 17, 2001 If prompted, select where in the tree you want to install the license. Install Networking Products After completing the NetWare server portion of the installation, you can select other networking products to install. Other networking products provide enhanced functionality, such as network management and Internet access, to NetWare 6. NOTE: Some products can be installed only by using NetWare Deployment Manager after the server installation is complete.
PAGE 167

Manual 99a 38 July 17, 2001 Although you can choose which products to install, installing the products that are already selected by default will ensure that you receive the features recommended for NetWare. For more information on NetWare products, see Chapter 1, “Welcome to NetWare 6,” on page 11. Depending on the products selected to be installed, you may need to complete the steps in the following sections.
PAGE 168

Manual 99a 38 July 17, 2001 Configuring IP-Based Services (Conditional) Make sure that port assignments and addresses do not conflict. Some port number assignments in NetWare 6 can be reassigned from one service to another. Other port numbers cannot be reassigned. For information on default port assignments, which ports can be reassigned, and which ports cannot be reassigned, see "Port Number Assignments" in Getting Results with Novell Web Services.
PAGE 169

Manual 99a 38 July 17, 2001 Only one Organizational CA object can exist in an eDirectory tree. Once the Organizational CA object is created on a server, it cannot be moved to another server. Deleting and re-creating an Organizational CA object will invalidate any certificates associated with the Organizational CA. Make sure that the server that you intend to permanently host the Organizational CA object and will be a reliable, accessible, and continuing part of your network.
PAGE 170

Manual 99a 38 July 17, 2001 Configuring LDAP TCP and SSL port numbers can be configured for LDAP services. You can also configure ports after the server installation using ConsoleOne. The default setting for the Allow Cleartext Passwords option (unchecked) disallows cleartext passwords, effectively disabling eDirectory user binds on non-SSL connections. Any sent password, however, is received by the server before the bind fails.
PAGE 171

Manual 99a 38 July 17, 2001 Installing Novell Native File Access Protocols Novell Native File Access Pack lets Macintosh, Windows, and UNIX workstations access and store files on NetWare servers without having to install any additional software—such as Novell Client software. The software is installed only on the NetWare server and provides "out of the box" network access. Just plug in the network cable, start the computer, and you have access to servers on your network.
PAGE 172

Manual 99a 38 July 17, 2001 User Benefits of Novell Native File Access Protocols Enabling native protocols on NetWare means that users can access files, map network drives, and create shortcuts to NetWare servers using the native methods available in their specific operating system. Windows users can use their familiar Network Neighborhood. Macintosh users can use Chooser or the Go menu to access network files and even create aliases.
PAGE 173

Manual 99a July 17, 2001 38 Name is the NetWare server name with an added underscore (_) and a W. For example, a NetWare server named SERVER1 defaults to a NNFAP server name of SERVER1_W. NNFAP Server Comment The text in the NNFAP Server Comment field displays when viewing details of the NNFAP server from a Windows workstation. Enabling Unicode When enabled, this command enables Unicode characters (used in doublebyte languages). To support Unicode, an additional file named UNINOMAP.
PAGE 174

Manual 99a 38 July 17, 2001 Workgroup Name: The domain or workgroup that the server will belong to. In this case, Workgroup and Domain are interchangeable. WINS Address: Address of WINS server to be used to locate the primary domain controller (PDC), if the PDC and server running Novell Native File Access Protocols software are on different subnets.
PAGE 175

Manual 99a 38 July 17, 2001 PDC Is On Same Subnet Indicates that the PDC is on the same subnet. Specify PDC Using DNS or WINS Select this option to use DNS or WINS to specify the primary domain controller. PDC Name A PDC server name and static IP address are needed if the PDC is on a different subnet. This option should be used only when there is a valid reason for overriding WINS or DNS.
PAGE 176

Manual 99a 38 July 17, 2001 Selecting IP Addresses to Service Windows Workstations Although we recommend that you enable the CIFS protocol on all IP addresses, you can specify which IP addresses will respond to CIFS protocol requests. Specifying Share Points for Windows Workstations Any volume or directory on the server can be specified as a shared point and made accessible via the Network Neighborhood or My Network Places. If no share points are specified, then all mounted volumes are displayed.
PAGE 177

Manual 99a 38 July 17, 2001 Directory The path to the server volume or directory which becomes the root of the sharepoint. Beginning at the volume name, the full path must be specified and it must end with a backslash (\). For example: VOL1:GRAPHICS\ Share Name The name by which the sharepoint is displayed to Windows computers.
PAGE 178

Manual 99a 38 July 17, 2001 Set up Contexts for Windows Workstations You must specify the NDS contexts of Windows users that require access to the network. These contexts are saved in the context search file. When the Windows user enters a username, the Novell Native File Access Protocol software searches through each context in the list until it finds the correct User object. For example if you had users with full NDS distinguished names such as Bob.sales.acme, Sue.graphics.marketing.acme, Pat.
PAGE 179

Manual 99a 38 July 17, 2001 Next Steps for Novell Native File Access Protocols After completing the installation of the Novell Native File Access Protocols, you must create passwords for users before they can access the files on the server. For more information, see the Novell Native File Access Protocols Installation and Administration Guide.
PAGE 180

Manual 99a 38 July 17, 2001 Choose which gadgets you want to enable and configure now and which gadgets you want to enable and configure later by checking or unchecking the check boxes next to each gadget type. All gadgets are installed automatically when you install NetWare WebAccess. This screen lets you choose whether to enable and configure those gadgets now or later.
PAGE 181

Manual 99a 38 July 17, 2001 For GroupWise®, the URL will be similar to http://IP_address or DNS name/servlet/webacc. Substitute the IP address or DNS name of the Web server running GroupWise WebAccess. For Web-based e-mail, provide the URL you assigned either the IMAP or POP3 server when you set it up. For Microsoft Exchange, provide the URL for accessing your Exchange server. The URL might be an IP address like http://192.168.0.1.
PAGE 182

Manual 99a 38 July 17, 2001 During installation, roles and tasks are installed and associated with the logged-in user (typically the Admin user) by default. These role and task objects are stored in a new eDirectory container (rbsCollection). You can select the location and name of the new container or use the defaults provided. Location Enter the path to the eDirectory container that you want to create the rbsCollection container in, or use the default location.
PAGE 183

Manual 99a 38 July 17, 2001 Install Novell iFolder Novell iFolder is a file storage and management solution to the universal problems associated with storing and retrieving data. With iFolder you have the latest version of your data when you need it and where you need it from any computer that you regularly use. And if you are not at a computer that you regularly use, you can still access and manage your files if you have an Internet connection and a Java-enabled browser.
PAGE 184

Manual 99a 38 July 17, 2001 example, if you wanted users JSmith and Admin to have rights to administer the Server Management Console, you would enter admin;jsmith. Network Domain Enter the IP address or the DNS name of your iFolder server. Install Novell NetStorage Novell NetStorage provides simple Internet-based access to file storage and serves as a bridge between a company's protected Novell network and the Internet.
PAGE 185

Manual 99a 38 July 17, 2001 does not necessarily have to be the IP address or DNS name of the server where NetStorage is to be installed. When a user attempts to log in, NetStorage searches the eDirectory database on the server you specify for the User object. If the User object is found, NetStorage attempts to authenticate the user to eDirectory.
PAGE 186

Manual 99a 38 July 17, 2001 Customizing the Installation You can customize the installation of many products for your networking environment. To customize products and components, at the Summary screen click Customize to access the Customize screen.
PAGE 187

Manual 99a 38 July 17, 2001 Select the product to customize. Click Properties. Modify the product as required. Click OK to return to the Summary screen. Completing the Server Installation The server installation program is now ready to copy files to your computer. Depending on which products you are installing, you might be prompted for additional information. At the Summary screen, click Finish to begin copying the files to the server.
PAGE 188

Manual 99a 38 July 17, 2001 After the files are copied, click Yes to reboot the server. If you chose to load server on reboot, the NetWare 6 server software will automatically load when the computer reboots. If you chose not to load the server on reboot, you can load it manually. To load the server manually, reboot the computer by clicking Yes. When the computer reboots, change to the startup directory containing the NetWare server files (C:\NWSERVER) and enter SERVER.
PAGE 189

Manual 99a 38 July 17, 2001 products using NetWare Deployment Manager or from the GUI server console screen. Install Additional Products Using NetWare Deployment Manager 1 Log in to the network from a Windows workstation running Novell Client software. 2 Run NWDEPLOY.EXE located at the root of the NetWare 6 Operating System CD. 3 Click Post Installation Tasks > Install NetWare 6 Products. 4 Follow the on-screen instructions for adding the product. HINT: Select the PRODUCT.
PAGE 190

Manual 86 99a 38 NetWare 6 Overview and Installation Guide NetWare 6 Overview and Installation Guide 100-004725-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 191

Manual 3 99a July 17, 2001 38 Upgrade to NetWare 6 The NetWare® 6 installation program can be used to upgrade an existing NetWare 4 or NetWare 5 server to NetWare 6.
PAGE 192

Manual 99a 38 July 17, 2001 Meet System and Software Requirements To upgrade to NetWare 6, your system must meet the minimum requirements listed below. System and Software Requirements The server to be upgraded must be running one of the following: NetWare 5.1 with Support Pack 2 or later NetWare 5 with Support Pack 6 or later NetWare 4.2 with Support Pack 8 or later NetWare 4.
PAGE 193

Manual 99a July 17, 2001 38 Client connection utilities (optional, for upgrading from another server): Novell ClientTM for DOS and Windows* 3.1x (optional, for upgrading from a NetWare server running IPXTM). IP Server Connection Utility (optional, for installing from a NetWare server running IP only). For instructions, see PRODUCTS\SERVERINST\IPCONN.TXT on the Novell Client CD.
PAGE 194

Manual 99a 38 July 17, 2001 3 Double-click the Network Preparation folder to view the tasks and read the Overview section to get an understanding of the tasks. 4 Back up any server data and Novell eDirectory data following the instructions in the Back Up Data step. 5 Run the View and Update eDirectory Version program to update eDirectory as required. HINT: If you are prompted to log in again while running NetWare Deployment Manager, you can enter the IP address of the server by clicking Details.
PAGE 195

Manual 99a July 17, 2001 38 6 Run the Prepare for eDirectory program to extend the network schema. 7 (Conditional) If you are upgrading a cluster of NetWare servers, run the Prepare a Novell Cluster for Upgrade program.
PAGE 196

Manual 99a 38 July 17, 2001 8 (Conditional) If you are upgrading a NetWare 5 server running NDS® 7 that has NSS volumes, run the Prepare a Server with NDS 7 and NSS program. 9 Follow the instructions in the Update Certificate Authority (CA) Object step to create or update a Security container object and a Certificate Authority (CA) object.
PAGE 197

Manual 99a 38 July 17, 2001 Preparing the Computer To prepare your existing server for the NetWare 6 operating system, do the following: Back up the NetWare server files Prepare application files Verify a valid DOS partition Access the upgrade program Backing Up the NetWare Server Files Make at least one backup of your NetWare server files, including files on the DOS partition. Do not attempt an upgrade without a backup.
PAGE 198

Manual 99a 38 July 17, 2001 Preparing Servers Running ZENworks for Server 2 (Conditional) If the server is running ZENworks for Servers 2, you must install ZENworks for Servers 2 Support Pack 1 prior to upgrading the server to NetWare 6. ZENworks for Servers 2 Support Pack and related information can be obtained from Novell Technical Support (htttp://support.novell.com). Verify a Valid DOS Partition Your NetWare server uses the DOS partition to start the computer and load NetWare.
PAGE 199

Manual 99a 38 July 17, 2001 5 Make sure that the CONFIG.SYS file contains the FILES=50 and BUFFERS=30 commands. 6 (Conditional) To upgrade from NetWare 6 files located on a network, install the Novell Client for DOS and Windows 3.1x or IP Server Connection Utility software located on the Novell Client CD. What’s Next After accessing the NetWare 6 installation files, follow the instructions for installing a server beginning with “Installing the Software” on page 35.
PAGE 200

Manual 96 99a 38 NetWare 6 Overview and Installation Guide NetWare 6 Overview and Installation Guide 100-004725-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 201

Other Installation Options Novell NetWare 6 ® www.novell.
PAGE 202

doc_tpl.fm Rev 99a 28 October 99 17 Contents Overview 9 Using NetWare Accelerated Upgrade . . . . . . . . . . . Automating the NetWare Installation with a Response File Using Installation Scripts for NetWare Installation . . . . . Documentation Conventions . . . . . . . . . . . . . . . . 1 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 203

doc_tpl.fm [NWI:Install Options] Section . . . . . . . . . . . . . . . . [NWI:Server Settings] Section . . . . . . . . . . . . . . . . [NWI:Locale] Section . . . . . . . . . . . . . . . . . . . . [NWI:Mouse and Video] Section . . . . . . . . . . . . . . . [NWI:Hardware] Section . . . . . . . . . . . . . . . . . . . [NWI:Excluded From Detection] Section. . . . . . . . . . . [NWI:Multi-Processor System] Section . . . . . . . . . . . [NWI:Storage Adapter n] Section . . . . . . . . . . . . . .
PAGE 204

doc_tpl.fm [Novell:SYSDirectory:1.0.0] Section . [Novell:ConfigDirectory:1.0.0] Section [Novell:LANFiles:1.0.0] Section. . . . [Novell:SBDFiles:1.0.0] Section . . . [Novell:portalzip:1.0.0] Section . . . . [Novell:Rconjzip:1.0.0] Section . . . . [Novell:Perl5zip:1.0.0] Section . . . . [Novell:beanszip:1.0.0] Section. . . . [Novell:nscriptzip:1.0.0] Section . . . [Novell:scripteszip:1.0.0] Section . . . [Novell:console1zip:1.0.0] Section . . [Novell:ldapzip:1.0.0] Section. . . . . [Novell:wanmanzip:1.0.
PAGE 205

doc_tpl.
PAGE 206

Manual 99a 38 July 17, 2001 Overview The following advanced options can help you upgrade or install NetWare® servers. Using NetWare Accelerated Upgrade You can run NetWare Accelerated Upgrade from a Windows* client workstation, so that you don’t need to be physically present at the server console. Although NetWare Accelerated Upgrade is quicker than the standard installation process, it does not install additional network products, licensing services, or license certificates.
PAGE 207

Manual 99a 38 July 17, 2001 Using Installation Scripts for NetWare Installation NetWare installation scripts let you Alter or extend the NetWare installation process Install additional products or services on a NetWare server after the operating system has been installed See Chapter 3, “Installation Scripts for NetWare,” on page 101. Documentation Conventions In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.
PAGE 208

Manual 1 99a 38 July 17, 2001 Using NetWare Accelerated Upgrade The NetWare® Accelerated Upgrade utility is an advanced utility that can be used to upgrade a NetWare 4.11, NetWare 4.2, or NetWare 5 server to NetWare 6. NetWare Accelerated Upgrade is intended for use by network administrators who are skilled at troubleshooting and installing NetWare networks. WARNING: Back up all data before using this utility.
PAGE 209

Manual 99a 38 July 17, 2001 NetWare 4 or 5 targeted server Logs in File copy Windows client workstation running NetWare Accelerated Upgrade -ROM files CD Logs in Staging server After the NetWare 6 Operating System CD files are copied to the staging server, you will log in to a Windows workstation and launch the NetWare Accelerated Upgrade utility (ACCUPG.EXE), located at the root of the NetWare 6 Operating System CD.
PAGE 210

Manual 99a 38 July 17, 2001 Upgrading to NetWare 6 To run NetWare Accelerated Upgrade, complete the following tasks: 1. Prepare the Workstation (page 13) 2. Prepare a Staging Server (page 13) 3. Prepare the Network (page 17) 4. Prepare the Target Server (page 15) 5. Run NetWare Accelerated Upgrade (page 18) 6. Complete Post-Upgrade Tasks (page 20) Prepare the Workstation A Windows 95/98, Windows NT*, Windows 2000, or Windows ME workstation with 50 MB of available disk space.
PAGE 211

Manual 99a 38 July 17, 2001 2 (Conditional) If you are upgrading a target server that does not have NICI installed, copy the NetWare 6 NICI file to your target server. Do one of the following: If you copied the NetWare 6 CD files in Step 1 on page 13, create directory named License at the root of the copied NetWare 6 Operating System CD and then copy the #.NFK file from the NetWare 6 License/Cryptography diskette to the newly created License directory.
PAGE 212

Manual 99a 38 July 17, 2001 Prepare the Target Server The target server is the NetWare 4 or NetWare 5 server that you plan to upgrade to NetWare 6. Make sure your target server meets the minimum requirements listed below. WARNING: Do not use NetWare Accelerated Upgrade to upgrade the first server in your tree to NetWare 6. You must already have a server running NetWare 6 in your tree in order to use NetWare Accelerated Upgrade.
PAGE 213

Manual 99a 38 July 17, 2001 Prompt enter Exit, at the Distributor console. Select Subscriber from the list. Prompt enter Exit, at the Subscriber console. Select ZENworks for Servers from the list. Prompt enter Exit, at the ZENworks for Servers console. Select Remote Web Console from the list. Prompt enter Exit, at the Remote Web Console. The following table lists the procedures that NetWare Accelerated Upgrade does not support during a NetWare 4 or NetWare 5 upgrade.
PAGE 214

Manual 99a 38 July 17, 2001 3 (Conditional) If you are upgrading a server in a multiserver tree that is clustered, do the following: 3a Run the NetWare Deployment Manager utility (NWDEPLOY.EXE), located at the root of the NetWare 6 Operating System CD. 3b Click Network Preparation > Prepare a Novell Cluster for Upgrade. 4 Run DSREPAIR > Time Synchronization at the server console of the target server. If you encounter any NDS® synchronization errors, make sure you resolve these before continuing.
PAGE 215

Manual 99a 38 July 17, 2001 Run NetWare Accelerated Upgrade 1 From your workstation, log in to the staging server and double-click the NetWare Accelerated Upgrade executable (ACCUPG.EXE), located at the root of the NetWare 6 Operating System CD. 2 Read the Welcome screen and click the right-arrow. 3 Enter the location where you copied or mounted the NetWare 6 files to the staging server and click the right-arrow.
PAGE 216

Manual 99a 38 July 17, 2001 9 Check any of the following options that you want NetWare Accelerated Upgrade to automatically perform during the upgrade, and then click the right-arrow: Reboot the target server after the upgrade is completed. Even if you checked this option, there might be an instance where you might need to manually reboot the target server once the file copy is complete. Update the existing drivers on the target server to NetWare 6 LAN and disk drivers.
PAGE 217

Manual 99a 38 July 17, 2001 Complete Post-Upgrade Tasks Installing Licensing Certificates Because the NetWare Accelerated Upgrade utility does not install licenses, use iManage via NetWare Web Manager to install license certificates on the new NetWare 6 server. NOTE: If licenses are installed at the [Root] of the NDS tree or you are on an MLA account, you might not need to install additional licenses.
PAGE 218

Manual 99a 38 July 17, 2001 specific drivers manually, you must create and configure a \STARTUP directory that contains the disk drivers and the STARTUP.NCF file. 1 Copy the NetWare 6 Operating System CD files to a volume on a staging server. IMPORTANT: Do not copy the files onto the target server that you are upgrading or onto the client workstation. 2 Make sure that the target server can connect to the staging server. 3 Copy any additional .HAM and .
PAGE 219

Manual 99a 38 July 17, 2001 Setting the Target Server’s Gate Parameter to Its Default Router IP Address For a NetWare 4 Target Server 1 At the server console, enter LOAD INSTALL 2 Select NCF Files Options > Edit AUTOEXEC.NCF File. 3 In the AUTOEXEC.NCF file, add LOAD TCP/IP 4 Add a command that loads the network board and specifies the slot, frame, and name of the network board (the AUTOEXEC.NCF file should list this information).
PAGE 220

Manual 99a 38 July 17, 2001 3 At the BIND IP command line, after the mask address, set the gate parameter to the default router IP address for the target server. For example, if your default router IP address was 137.65.178.1, at the BIND IP command line you would enter the following after the mask address: gate=137.65.178.
PAGE 221

Manual 24 Other Installation Options Other Installation Options 103-000143-001 August 30, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 222

Manual 2 99a 38 July 17, 2001 Automating the NetWare Installation with a Response File Installing the NetWare® operating system software can be easier and more flexible when you use a response file. When used with the graphical server installation, a response file lets you Set and display specific defaults Bypass entire sections of the installation Automate the entire server installation process A response file is a text file containing sections and keys (similar to a Windows .INI file).
PAGE 223

Manual 99a 38 July 17, 2001 This chapter contains the following sections: “Creating a Response File” on page 26 “Using a Response File” on page 27 “Syntax” on page 28 “NetWare Sections and Keys” on page 33 “Performing a Fully Automated Installation” on page 78 “Automating the Installation of Additional Products and Services” on page 79 “CD Boot and the Response File” on page 87 “Customizing the Installation Using Install Scripts” on page 87 “Performing a Factory Install” on page 90 Cr
PAGE 224

Manual 99a 38 July 17, 2001 3 Copy RESPONSE.NI from the SYS:NI\DATA directory to either a diskette or to the new server. 4 Modify the file by adjusting the parameters and removing unwanted sections.
PAGE 225

Manual 99a 38 July 17, 2001 Syntax A response file is a Windows .INI-type file. Data items are identified as keys, and keys have associated values (Key = value). These keys are grouped in sections. For the NetWare installation program, each data input screen has one or more sections associated with it. Section names of the installation generally correspond to the function of the screens. Section and key names are case sensitive. Values associated with keys are not case sensitive.
PAGE 226

Manual 99a 38 July 17, 2001 Section Purpose “[NWI:Excluded From Detection] Section” on page 44 Identifies what drivers will be excluded from the auto-detection. “[NWI:Multi-Processor System] Section” on page 44 Identifies the driver associated with the processor system in the server. “[NWI:Storage Adapter n] Section” on page 45 Identifies the driver and its associated parameters for a specific storage adapter. This Section can be duplicated for as many adapters as are in the server.
PAGE 227

Manual 30 99a 38 July 17, 2001 Section Purpose “[NWI:Protocols] Section” on page 61 Controls whether the protocol screen is displayed. “[NWI:TCPIP] Section” on page 62 Specifies TCP/IP parameters. “[NWI:IPX] Section” on page 63 Specifies IPXTM parameters. “[NWI:IPCMD] Section” on page 64 Specifies Compatibility Mode parameters. “[NWI:SNMP] Section” on page 65 Specifies Simple Network Management Protocol parameters.
PAGE 228

Manual 99a 38 July 17, 2001 Section Purpose “[Novell:DNS_DHCP:1.0.0] Section” on page 85 Specifies full automation of products and services. “[NWI:Install Script] Section” on page 88 Specifies full automation of products and services. “[NWI:Factory] Section” on page 91 Specifies full automation of factory install. “[Novell:StartupDirectory:1.0.0] Section” on page 92 Specifies full automation of factory install. “[Novell:SYSDirectory:1.0.
PAGE 229

Manual 99a 38 July 17, 2001 The Prompt key is listed with each section that corresponds to a data input screen and it Controls whether the screen will be displayed. Lets you use the response file to pass in the keys and values of the section. Lets you bypass the screen. If the value of Prompt is True, the screen will be displayed and the data specified in the response file will be presented as default values. The screen will not be displayed if the value of Prompt is False.
PAGE 230

Manual 99a 38 July 17, 2001 NetWare Sections and Keys The NetWare installation sections and their associated keys are specified below. Section names and Key names are in bold. Included with each key are the default value, possible values, whether the Key is required for the NetWare installation to run silently (for example, to create a new NDS tree without any user input, New Tree=True must appear in the response file). Also included with each Key is a short description of the Key’s purpose.
PAGE 231

Manual 99a 38 July 17, 2001 Small Business = Default False Value True or False Key Required No Example Small Business = True Purpose Controls whether the Small Business licensing model is used. [NWI:Language] Section Prompt = Default True Values True or False Key Required Yes Example Prompt = True Purpose Controls whether the screen is displayed.
PAGE 232

Manual 99a 38 July 17, 2001 Additional Languages = Default (none) Values 1-100 (values are specified in INSTALL\PROFILE.TXT) Key Required No Example Additional Languages = 5,6 Purpose Specifies additional languages that will be installed on the server. [NWI:Install Options] Section Prompt = Default True Values True or False Key Required Yes Example Prompt = True Purpose Controls whether the screen is displayed.
PAGE 233

Manual 99a 38 July 17, 2001 Startup Directory = Default C:\NWSERVER Values (existing DOS path up to 255 characters) Key Required Yes Example Startup Directory = C:\NWSERVER Purpose Identifies the directory where the server’s initialization files will reside on the Boot Partition. Allow User response file = Default True Values True or False Key Required No Example Allow User response file = True Purpose Makes the F3 key available on the opening screen.
PAGE 234

Manual 99a 38 July 17, 2001 [NWI:Server Settings] Section Prompt = Default True Values True or False Key Required Yes Example Prompt = True Purpose Controls whether the screen is displayed. NDS Version = Default 8 Values 7 or 8 Key Required Yes Example NDS Version = 8 Purpose Specifies the version of NDS to install on this server.
PAGE 235

Manual 99a 38 July 17, 2001 CD Driver = Default NetWare Values NetWare or DOS Key Required No Example Source Media Access = NetWare Purpose Determines the driver type (DOS or server) used to access the CD during installation. [NWI:Locale] Section Prompt = Default True Values True or False Key Required Yes Example Prompt = True Purpose Controls whether the screen is displayed.
PAGE 236

Manual 99a 38 July 17, 2001 Code Page = Default 437 Values (values are specified in INSTALL\NLS\language number\LOCALE.TXT) Key Required Yes Example Code Page = 437 Purpose Sets the character set for the server. Keyboard = Default United States Values (values are specified in INSTALL\NLS\\LOCALE.TXT) Key Required Yes Example Keyboard = United States Purpose Sets the keyboard type.
PAGE 237

Manual 99a 38 July 17, 2001 Mouse = Default PS/2 Values PS/2, Serial COM1, Serial COM2, No Mouse (values are specified in INSTALL\NLS\language number\LOCALE.TXT) Key Required Yes Example Mouse = PS/2 Purpose Specifies the mouse type that will be used for the graphical portion of the installation.
PAGE 238

Manual 99a 38 July 17, 2001 Update Storage Driver Directory = Default (none) The Install always looks in C:\NWUPDATE as well. Values (existing DOS path up to 255 characters) Key Required No Example Update Storage Driver Directory = F:\DRV\UPDATE Purpose Specifies the directory path where updated storage (HAM and CDM) drivers will be found; the directory should already exist and be a local DOS path. NOTE: Associated DDI files must accompany the storage drivers in this directory.
PAGE 239

Manual 99a 38 July 17, 2001 Update PSM Driver Directory = Default (none) The Install always looks in C:\NWUPDATE as well Values (existing DOS path up to 255 characters) Key Required No Example Update PSM Driver Directory = F:\DRV\UPDATE Purpose Specifies the directory path where updated processor (PSM) drivers will be found; the directory should already exist and be a local DOS path. NOTE: Associated PDI files must accompany the storage drivers in this directory.
PAGE 240

Manual 99a 38 July 17, 2001 Storage Detection = Default True Values True or False Key Required No Example Storage Detection = True Purpose Controls whether detection of storage adapters and driver matching is performed. If storage adapter and driver information is identified in the response file (see Storage Adapter section), detection can be set to False.
PAGE 241

Manual 99a 38 July 17, 2001 HotPlug Detection = Default True Values True or False Key Required No Example HotPlug Detection = True Purpose Controls whether detection of Hot Plug devices and driver matching is performed. [NWI:Excluded From Detection] Section Driver File = Default (none) Values (name of driver) Key Required No Example Driver File =AHA2940.HAM Purpose Identifies the driver that will be excluded from auto-detection.
PAGE 242

Manual 99a 38 July 17, 2001 [NWI:Storage Adapter n] Section Example [NWI:Storage Adapter 1] Description This section can be included for each storage adapter in the server. Several Keys are described under this section which are optional; if the driver is detectable by NetWare, only the Driver File key is required for the section. The other Keys and Values are varied and are extracted from the driver’s corresponding DDI file.
PAGE 243

Manual 99a 38 July 17, 2001 INT = Default (none) Values 1-F Key Required No, unless the driver is for an ISA adapter. Example INT = F Purpose Specifies the interrupt that the adapter is set to; this parameter is commonly used for ISA bus adapters.
PAGE 244

Manual 99a 38 July 17, 2001 [NWI:Network Adapter n] Section Example [NWI:Network Adapter 1] Description This section can be included for each network adapter in the server. Several Keys are described under this section which are optional; if the driver is detectable by NetWare, only the Driver File Key is required for the section. The other Keys and Values are varied and are extracted from the driver’s corresponding LDI file.
PAGE 245

Manual 99a 38 July 17, 2001 INT = Default (none) Values 1-F Key Required No, unless the driver is for an ISA adapter Example INT = F Purpose Specifies the interrupt that the adapter is set to; this parameter is commonly used for ISA bus adapters.
PAGE 246

Manual 99a 38 July 17, 2001 Frame Type n = Default (none) Values (frame types supported by the driver are found in the driver’s LDI file) Key Required No Example Frame Type 1 = Ethernet_802.2 Purpose Identifies the network frame type to be used when loading the driver. There can be as many descriptions as there are frame types supported by the driver—n uniquely identifies the frame type (for example, 1, 2, etc.).
PAGE 247

Manual 99a 38 July 17, 2001 [NWI:Reserved Adapter n] Section Example [NWI:Reserved Adapter 1] Description This section can be included for each slot in the server. Default (none) Values (can be a 5-digit Hardware Instance Number assigned on servers with buses that support detection—such as PCI) Key Required No, unless the driver is for an ISA adapter Example SLOT = 5 Purpose Specifies the bus slot that should be reserved. If an adapter is found in this slot, an error is generated.
PAGE 248

Manual 99a 38 July 17, 2001 [NWI:NetWare Loadable Module] Section Driver File = Default (none) Values (name of NLM) Key Required No Example Driver File = ROUTE.NLM Purpose Identifies the NLM to load during installation. This is typically used for network support NLM programs.
PAGE 249

Manual 99a 38 July 17, 2001 GUI Prompt = Default True Values True or False Key Required Yes Example GUI Prompt = True Purpose Controls whether the File System screen is displayed during the graphical portion of the install. [NWI:Partition n] Section Example [NWI:Partition 0] Description This section allows partitions to be created on specific devices in the system during installation. The devices are specified by the key entries in the section.
PAGE 250

Manual 99a 38 July 17, 2001 IDE Device Serial Number = Default (none) Values (string of characters) Key Required No Example IDE Device Serial Number = AX8273430930. Purpose Specifies the serial number of the device designated by the manufacturer. (It is usually found on a sticker attached to the device.
PAGE 251

Manual 99a 38 July 17, 2001 SCSI Device Adapter Slot = Default (none) Values 1 to16 Key Required No Example SCSI Device Adapter Slot = 1 Purpose Identifies the physical slot number of the SCSI adapter SCSI Device ID = Default (none) Values 0 to 15 Key Required Yes Example SCSI Device ID = 0 Purpose Specifies the ID of the device on the SCSI chain Partition Type = 54 Default NSS Values NetWare or NSS or Free Key Required No Example Partition Type
PAGE 252

Manual 99a 38 July 17, 2001 Partition Size = or Default (none) Values (up to the size of free space on the device in MB) Key Required No Example Partition Size = 1000 Purpose Identifies the size of the partition. Note that the number is modified to align with a cylinder boundary. "ALL FREE SPACE" specifies that all remaining free space on the device will be used.
PAGE 253

Manual 99a 38 July 17, 2001 [NWI:Volume n] Section Example [NWI:Volume 0] Description This section can be included for each volume defined on the server. Note that SYS must be Volume 0. This section allows volumes to be created on specific partitions in the system during installation. The partitions are specified by the key entries in the section. The zero-based sequence number (n = 0, 1, 2, 3, ...) in the section heading specifies the order in which the volumes are created.
PAGE 254

Manual 99a 38 July 17, 2001 Block Size = Default (calculated on the size of the first segment of the volume) Values 4 or 8 or 16 or 32 or 64 Key Required No Example Block Size = 64 Purpose Identifies the volume’s block size. Note that this key does not apply to NSS volumes. Compression = Default True Values True or False Key Required No Example Compression = True Purpose Specifies whether compression is enabled on the volume.
PAGE 255

Manual 99a 38 July 17, 2001 Data Migration = Default False Values True or False Key Required No Example Data Migration = True Purpose Specifies whether data migration is enabled on the volume. Note that this key does not apply to NSS volumes. Default False Values True or False Key Required No Example Mount = True Purpose Specifies whether the volume should be mounted during installation.
PAGE 256

Manual 99a 38 July 17, 2001 Segment n Size = or Default (none) Values (up to free space on a partition in MB) Key Required Yes Example Segment 1 Size = 1000 Purpose Specifies the size of the volume segment. "ALL FREE SPACE" specifies that all remaining free space on the partition will be used. [NWI:Misc] Section Relogin Password = Default (none) Values (text) Key Required No, unless it is a network installation.
PAGE 257

Manual 99a 38 July 17, 2001 [NWI:File Server] Section NOTE: This is the first section used during the graphical portion of the installation. Prompt = Default True Values True or False Key Required Yes Example Prompt = True Purpose Controls whether the screen is displayed.
PAGE 258

Manual 99a 38 July 17, 2001 [NWI:Protocols] Section Prompt = Default True Values True or False Key Required Yes Example Prompt = True Purpose Controls whether the protocols screen is displayed.
PAGE 259

Manual 99a 38 July 17, 2001 Default IPX Frame Typer= Default (none) Values (Frame types that are supported by a driver are found in the driver’s LDI file Key Required No Example Default IPX Frame Type=Ethernet 802.2 Purpose Identifies the network frame type to be bound to the IPX stack when the "Single Network Adapter" is set to True.
PAGE 260

Manual 99a 38 July 17, 2001 Subnet Mask n = Default (none) Values (valid IP address) Key Required No, unless Logical Name is set. Example Subnet Mask 1 = 255.255.255.0 Purpose Specifies the subnet. Divides the IP address into network address and node address. Gateway n = Default (none) Values (valid IP address) Key Required No Gateway 1 = 127.127.0.254 Purpose Identifies the gateway or router through which this server can communicate outside the subnet.
PAGE 261

Manual 99a 38 July 17, 2001 IPX Address n = Default (address detected by the installation program) Values 00000001-FFFFFFFF Key Required No, unless Logical Name is set Example IPX Address 1 = 01010102 Purpose Specifies the IPX address to be bound. [NWI:IPCMD] Section IPX Compatibility = Default True Values True or False Key Required No Example IPX Compatibility = True Purpose Controls whether SCMD is loaded on this server.
PAGE 262

Manual 99a 38 July 17, 2001 CMD Net Number = Default (none) Values 00000001-FFFFFFFF Key Required No Example CMD Net Number = 01010101 Purpose Specifies the network number. Preferred IP Address = Default (none) Values (valid IP address) Key Required No Example Preferred IP Address = 130.1.130.1 Purpose Specifies the IP address.
PAGE 263

Manual 99a 38 July 17, 2001 Location = Default (none) Values (text) Key Required No Example Location = Building A Purpose Identification information that is sent with SNMP traps to assist in troubleshooting. Contact = Default (none) Values (text) Key Required No Example Contact = John Doe Purpose Identification information that is sent with SNMP traps to assist in troubleshooting.
PAGE 264

Manual 99a 38 July 17, 2001 Trap Targets IPX = Default (none) Values (8-character IPX address:12-character node number) Key Required No Example Trap Targets IPX = C9990111:000001B555555 Purpose Identifies MAC addresses of a computer to which SNMP traps are sent. [NWI:DNS] Section Prompt = Default True Values True or False Key Required Yes Example Prompt = True Purpose Controls whether the DNS screen is displayed.
PAGE 265

Manual 99a 38 July 17, 2001 Nameservers = Default (none) Values (valid IP addresses) Key Required No Example Nameservers = 131.1.131.1, 131.1.131.2 Purpose Identifies the servers to be used for name resolution. [NWI:Host Name] Section Prompt = Default True Values True or False Key Required Yes Example Prompt = True Purpose Controls whether the screen is displayed.
PAGE 266

Manual 99a 38 July 17, 2001 IP Address n = Default (none) Values (valid IP address) Key Required No Example IP Address 1 = 130.1.130.1 Purpose Specifies the IP address associated with a Host Name. Note that Host Name 1 will be set as the Primary address. [NWI:Time Zone] Section Prompt = Default True Values True or False Key Required Yes Example Prompt = True Purpose Controls whether the time zone screen is displayed.
PAGE 267

Manual 99a 38 July 17, 2001 Use Daylight Saving Time = Default True, if Time Zone supports Daylight Saving Time Values True or False Key Required No Example Use Daylight Saving Time = True Purpose Controls whether daylight saving time is set.
PAGE 268

Manual 99a 38 July 17, 2001 Tree Name = Default (none) Values (text) Key Required Yes Example Tree Name = Novell Purpose Specifies the tree name for either a new tree or an existing tree to install the server into. Default False Values True or False Key Required Yes Example New Tree = True Purpose Specifies whether the NDS tree to be installed is a new tree or install into an existing tree. New Tree = NOTE: This key is only used when Prompt = False.
PAGE 269

Manual 99a 38 July 17, 2001 Add Replica = Default (none) Values True or False Key Required No Example Add Replica = True Purpose Controls whether a replica is added to the server. This only applies if the server is not one of the first three servers added to an NDS tree (by default the first three servers receive replicas). Upgrade User Conflict Action = Default (none) Values Delete, Merge, or Rename Key Required No, unless it is an upgrade from NetWare 3.
PAGE 270

Manual 99a 38 July 17, 2001 Admin Context = Default (none) Values (NDS distinguished name) Key Required Yes Example Admin Context = .install.novell Purpose Identifies the NDS context in which the server administrator is to be installed into. Admin Password = Default (none) Values (text) Key Required Yes Example Admin Password = Novell Purpose Specifies the password for the server administrator.
PAGE 271

Manual 99a 38 July 17, 2001 Display Summary = Default True Values True or False Key Required Yes Example Display Summary = True Purpose Controls whether the NDS Summary screen is displayed [NWI:License] Section Prompt = Default True Values True or False Key Required Yes Example Prompt = True Purpose Controls whether the license screen is displayed.
PAGE 272

Manual 99a 38 July 17, 2001 Install Licenses Later = Default False Values True or False Key Required No Example Install Licenses Later = True Purpose Specifies that no licenses will be installed on the server. If this key is set to True, all remaining licensing keys will be ignored.
PAGE 273

Manual 99a 38 July 17, 2001 Search For Existing License = Default True Values True or False Key Required Yes Example Search For Existing License = False Purpose Controls whether the licenses (such as MLA licenses) are searched for in the tree. Used in conjunction with the next key.
PAGE 274

Manual 99a 38 July 17, 2001 Append Line n = Default (none) Values (decimal number) Key Required No Example Append Line 1 = LOAD NFS.NAM Purpose Adds the line to the end of the STARTUP.NCF file. If multiple lines are listed, n should increment sequentially. [NWI:Append To Autoexec.ncf] Section Line n = Default (none) Values (decimal number) Key Required No Example Line 1 = LOAD MONITOR Purpose Adds the line to the end of the AUTOEXEC.NCF file.
PAGE 275

Manual 99a 38 July 17, 2001 Performing a Fully Automated Installation The following parameters must be present to completely automate an installation or upgrade. The syntax and values for the supplementary NetWare installation sections and their associated keys are specified below. For a fully automated installation to work, these sections must appear in the response file in addition to all of the required keys listed in “NetWare Sections and Keys” on page 33. [Novell:NOVELL_ROOT:1.0.
PAGE 276

Manual 99a 38 July 17, 2001 allowSummary = Default True Values True or False Key Required Yes Example allowSummary = False Purpose Controls whether the installation Summary screen is displayed. Default False Values True or False Key Required Yes Example silent = False Purpose Global key that controls whether the installation runs in silent mode with no user interaction. Some sections do not support this key. If this is the case, use a "prompt=false" key instead.
PAGE 277

Manual 99a 38 July 17, 2001 4 Add the following lines under the [Selected Nodes] section heading: Novell:NetWare5:1.0.0=Novell:NetWare5OS:5.0.0,Novell:Products:1.0.0,Novell:NW UpdateGroup:1.0.0 Novell:NetWare5OS:5.0.0=Novell:DiskCarver:1.0.0,Novell:Protocols:1.0.0,Novell :DS_Install:1.0.0, Novell:LicensePrompt:1.0.0,Novell:NW:1.0.0,Novell:NDPS Server Files:1.0.0 Novell:NW:1.0.0=Novell:Startup:1.0.0,Novell:SYS:1.0.0,Novell:DriverFiles:1.0. 0 Novell:Startup:1.0.0=Novell:StartupDirectory:1.0.
PAGE 278

Manual 99a 38 July 17, 2001 Product Selection = Default (none) Values Default or Web Key Required No Example Product Selection = Web Purpose Specifies which bundle of Additional Products and Services to install. Default will install the Web Services bundle. Web will install the Web Services bundle plus WebSphere* Application Server. To specify a custom bundle of Additional Products and Services, do not include this key, and specify each product as described below. Novell:Products:1.0.
PAGE 279

Manual 99a 38 July 17, 2001 Installing Multiple Products on a Server To install multiple products on a server, make sure that the Novell:Products:1.0.0 key has multiple values, separated by commas as shown in the example above. Product Keys and Values In addition to identifying the product in the Novell:Products:1.0.0 key, each product has its own keys and values for the [Selected Nodes] section. These keys and values for each product are listed below.
PAGE 280

Manual 99a 38 July 17, 2001 Novell PKI Services Novell:PKIInstall:1.0.0=Novell:PKIModule:1.0.0,Novell:NICIModule:1.0.0 Novell:PKIModule:1.0.0=Novell:PKIFiles:1.0.0 Novell Internet Access Server Novell:RAS:4.1.0=Novell:RAS Server Files:1.0.0,Novell:SVCDEF_NODE:1.0.0,Novell:SupportedOS:1.0.0,Novell:UpgradeF rom:1.0.0 Novell:RAS Server Files:1.0.0=Novell:RAS System Connect:1.0.0,Novell:RAS System Connect Scripts:1.0.0,Novell:RAS Public:1.0.0 Storage Management Services Novell:SMS:1.0.0=Novell:SMSFiles:1.
PAGE 281

Manual 99a 38 July 17, 2001 adminID = Default (none) Values (NDS distinguished name) Key Required Yes Example adminID=.CN=admin.O=install Purpose Identifies the Admin name and NDS context; this should correspond with the Admin Login Name and Admin Context identified in the NWI:NDS section of the response file. Note the case of the characters in the string.
PAGE 282

Manual 99a 38 July 17, 2001 [Novell:DNS_DHCP:1.0.0] Section Prompt = Default None Values true or false Key Required Yes Example Prompt=false Purpose Controls whether the DNS/DHCP configuration screen is displayed. TreeName = Default (none) Values (text) Key Required Yes Example TreeName=Novell Purpose Specifies the NDS tree name in which DNS/DHCP Services will be installed.
PAGE 283

Manual 99a 38 July 17, 2001 ExtendDNIPSchema = Default (none) Values true or false Key Required Yes Example ExtendDNIPSchema=true Purpose Controls whether the schema is extended for DNS/DHCP Services. Note that this should be set to true. LocatorNDSContext = Default (none) Values (NDS distinguished name) Key Required Yes Example LocatorNDSContext=O=install Purpose Identifies the NDS context that the Locator Object is to be installed into.
PAGE 284

Manual 99a 38 July 17, 2001 RootSrvrNDSContext = Default (none) Values (NDS distinguished name) Key Required Yes Example RootSrvrNDSContext=O=install Purpose Identifies the NDS context that the RootSrvr Zone is to be installed into. In addition to the DNS/DHCP keys identified above, there must also be a line in the [Settings] section with the entry: Novell:DNS_DHCP:1.0.
PAGE 285

Manual 99a 38 July 17, 2001 There are two places in the NetWare installation where you can use install scripts: At the end of the preliminary file copy (just prior to the launching of the graphical portion of the install). An install script executed here can be used for copying files from the DOS partition to the SYS volume. At the end of the NetWare installation. It is called right after you answer AOK@ or ANo@ on the closing screen and before the install cleanup process.
PAGE 286

Manual 99a 38 July 17, 2001 Support Pack Script = Default Support Pack Script = C:\spack\silent.ics Values (existing DOS path up to 255 characters) Key Required No Example If the support pack image is located on the C: drive, use this path: Support Pack Script=c:\nw51sp1\spack.ips e=c:\facterr.log s=c:\nw51sp1 If the support pack image is on a mounted CDROM, use this path: Support Pack Script=NW51:\spack.ips e=c:\err.
PAGE 287

Manual 99a 38 July 17, 2001 Performing a Factory Install A Factory Install can reduce the complexity and time spent on an installation. Much of the hardware configuration and file copy is done in the Factory so that you only need to use the graphical portion of the NetWare installation to complete the on-site configuration. Because the network operating system files are pre-copied to the server, installation time is reduced to a few minutes.
PAGE 288

Manual 99a 38 July 17, 2001 [NWI:Factory] Section Preinstall = Default True Values True or False Key Required Yes Example Preinstall = True Purpose Controls whether the Factory Install option of the NetWare installation is invoked. If Preinstall=True, the remaining keys are checked.
PAGE 289

Manual 99a 38 July 17, 2001 [Novell:StartupDirectory:1.0.0] Section Precopy = Default True Values True or False Key Required No Example Precopy = True Purpose Controls whether the files in the \STARTUP\NLS directory of the install image and destined for the C:\Startup_Directory\NLS directory are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. [Novell:SYSDirectory:1.0.
PAGE 290

Manual 99a 38 July 17, 2001 [Novell:ConfigDirectory:1.0.0] Section Precopy = Default True Values True or False Key Required No Example Precopy = True Purpose Controls whether the files in the \CONFIG directory of the install image, destined for volume SYS, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. [Novell:LANFiles:1.0.
PAGE 291

Manual 99a 38 July 17, 2001 [Novell:SBDFiles:1.0.0] Section Precopy = Default True Values True or False Key Required No Example Precopy = True Purpose Controls whether the files in the \DRIVERS\SBD directory of the install image, destined for the SYS:SYSTEM directory, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. [Novell:portalzip:1.0.
PAGE 292

Manual 99a 38 July 17, 2001 [Novell:Rconjzip:1.0.0] Section Precopy = Default True Values True or False Key Required No Example Precopy = True Purpose Controls whether the files in the zip file, destined for volume SYS, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. [Novell:Perl5zip:1.0.
PAGE 293

Manual 99a 38 July 17, 2001 [Novell:beanszip:1.0.0] Section Precopy = Default True Values True or False Key Required No Example Precopy = True Purpose Controls whether the files in the zip file, destined for volume SYS, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. [Novell:nscriptzip:1.0.
PAGE 294

Manual 99a 38 July 17, 2001 [Novell:scripteszip:1.0.0] Section Precopy = Default True Values True or False Key Required No Example Precopy = True Purpose Controls whether the files in the zip file, destined for volume SYS, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. [Novell:console1zip:1.0.
PAGE 295

Manual 99a 38 July 17, 2001 [Novell:ldapzip:1.0.0] Section Precopy = Default True Values True or False Key Required No Example Precopy = True Purpose Controls whether the files in the zip file, destined for volume SYS, are copied in Phase 2. If Precopy = True, the files are not copied again in the final file copy routine. [Novell:wanmanzip:1.0.
PAGE 296

Manual 99a 38 July 17, 2001 Install Command Line Options The following command line options that can be used when initiating the installation executable. /SERVER_LOG = Default (none) Values (existing DOS path up to 255 characters) Key Required No Example Install /LOG=C:\TMP\ERROR.LOG Purpose Designates where an installation log file will be created.
PAGE 297

Manual 100 Other Installation Options Other Installation Options 103-000143-001 August 30, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 298

Manual 3 99a 38 July 17, 2001 Installation Scripts for NetWare WARNING: This document describes software that is subject to change. Novell® intends to keep it as current as possible, but the user must assume any inherent risk in developing or maintaining code based on the information in this document. Novell may discontinue or decline to support any software feature described within this document at any time. This chapter describes the installation script support for NetWare®.
PAGE 299

Manual 99a 38 July 17, 2001 Launching a Script File 1 At the server console, enter NWCONFIG.NLM. 2 Click Products Options on the Configuration Options screen. 3 Click Other Installation Actions menu > Install a product not listed. 4 Press F3, and then specify the directory path to the script file. The directory path is first checked for an .IPS file. If only one .IPS file exists, it is executed. If more than one exists, only the first one found is executed. If there is no .IPS file, PINSTALL.
PAGE 300

Manual 99a 38 July 17, 2001 Descriptors and Commands This section describes the descriptors and commands found in NETMAIN.ILS and other installation script files. The product installation script files you write contain the same types of descriptors and commands as those in NETMAIN.ILS. A descriptor is a keyword preceded by the @ character. The installation NLM scans the descriptors and uses them to build linked lists and menus in memory.
PAGE 301

Manual 99a 38 July 17, 2001 ANSI escape sequences are recognized by the parser within double or single quotes. For example, '\\', "\n", and '\t' represent a backslash, a new line, and a tab, respectively. A NULL character (ASCII value 0) is not allowed anywhere in the file. Comments Syntax ; Description A comment (semicolon followed by text) exists for documentation purposes only—it does not invoke a script file operation.
PAGE 302

Manual 99a 38 July 17, 2001 @DeletePartition Syntax @DeletePartition Description @DeletePartition deletes the existing partitions that you specify. In contrast, the installation NLM’s automatic partition creation deletes (by default) existing partitions of the first two types listed below. In both cases, all active partitions are left untouched.
PAGE 303

Manual 99a 38 July 17, 2001 @Driver @EndDriver Syntax @Driver Help: “Help description for finding drivers” [Dir: , , , ] [Dir: , , , ] ... @EndDriver Description @Driver specifies help for finding drivers in maintenance-mode installations, or finding disks and directories that contains drivers. specifies the directory to read.
PAGE 304

Manual 99a 38 July 17, 2001 Example @Driver Help: “If installing from a floppy, disk drivers will be on disk NetWare-2 and LAN drivers will be on disk NetWare-3. If installing from CDROM, all drivers will be in the directory :\NW40\SERVER\DRIVERS.” Dir: DDSK, '', 'NETWARE-2', 'NetWare-2' Dir: LAN, '', 'NETWARE-3', 'NetWare-3' @EndDriver Disk NetWare-2 will be scanned for .DSK and .DDI files; disk NetWare-3 will be scanned for .LAN and .LDI files.
PAGE 305

Manual 99a 38 July 17, 2001 Class specifies how the fileset will be used: File Action MANDATORY Always executed. CORE Always copied in a sequential install, but optionally copied in the selective install/maintain mode. OPTIONAL Displayed to the user for selection. They are defaulted to on (selected for copy). OPTIONAL_OFF Displayed for the user to choose, but are defaulted to off.
PAGE 306

Manual 99a 38 July 17, 2001 For a DOS file: Attribute1 Meaning 00000001 Read Only 00000002 Hidden 00000004 System 00000008 Volume Label For a NetWare file: Attribute1 Meaning 00000001 Read Only 00000002 Hidden 00000004 System 00000008 Execute 00000010 Subdirectory 00000020 Archive 00000080 Shareable 00000700 Smode 00001000 Transaction 00004000 Read Audit 00008000 Write Audit 00010000 Immediate Purge 00020000 Rename Inhibit 00040000 Delete Inhibit 00080000 Copy In
PAGE 307

Manual 99a 38 July 17, 2001 The meaning for Attribute2 is 00000001 (do not decompress or process file). The default for Attribute2 is zero, which should be used in all usual circumstances. Flag Meaning 00000001 Do only for a custom install. 00000002 Do in first-phase copy (bit reset = second-phase). 00000004 Do only if NetWare for OS/2*. 00000008 Do only if native (not SFT IIITM or NetWare for OS/2). 00000010 Do only if SFT III. 00000020 Do only for a simplified installation.
PAGE 308

Manual 99a 38 July 17, 2001 @IncludeFile @EndIncludeFile Syntax @IncludeFile File: [DiskDescription: “...[disk description]...”] [DiskVolume: 11 char vol name>] @EndIncludeFile Description @IncludeFile specifies a file () with additional commands to parse and execute. DiskDescription specifies the printed name on the media that shows where the include file is located; DiskVolume is the corresponding media volume name. The command file's directory is searched first.
PAGE 309

Manual 99a 38 July 17, 2001 @MessageFile @EndMessageFile Syntax @MessageFile File: [Version: ] @EndMessageFile Description @MessageFile specifies a file, usually with the extension .MSG, containing message strings. It is typically located in the same directory as the script file or in an NLS subdirectory.
PAGE 310

Manual 99a 38 July 17, 2001 @StartAppObject @EndAppObject Syntax @StartAppObject AppPlatform: AppName: AppPath: [AppDescription: “...Text...”] [AppContact: ] [AppMapping: ] [AppFlags: <>] [AppIcon: ] [AppCaption: “...Text...
PAGE 311

Manual 99a 38 July 17, 2001 Variable Description AppContact The list of usernames to contact for resolving issues with the Application object. AppMapping A list of drive mappings that are made for the application to run correctly. AppIcon The filename and location of the applications icon. AppWorkingDir The startup directory for the application. AppUser A list of users authorized to run the application.
PAGE 312

Manual 99a 38 July 17, 2001 Description Description is the menu description displayed for the @Other configuration option. This label must be first in the set of labels for a particular @Other option. File specifies the *.IPS file to execute, or the NLM to load to install the @Other option. DiskDescription is the prompt name that will be displayed to the user to prompt for another diskette. DiskVolume is the volume name for the disk specified in DiskDescription.
PAGE 313

Manual 99a 38 July 17, 2001 If the other filename extension is .IPS, the file is assumed to be a script and is interpreted. If the other filename extension is .NLM, the file is loaded and executed as an NLM. Example @Other Description: “Install NetWare for Macintosh” DiskDescription: 'NWM System 1' DiskVolume: 'MAC-1' File: PINSTALL.NLM Description: “Install TCP/IP Protocol” DiskDescription: 'TCPIP System 2' DiskVolume: 'TCPIP-2' File: TCPIP.
PAGE 314

Manual 99a 38 July 17, 2001 @StartSchemaMod @EndStartSchemaMod Syntax @StartSchemaMod SchemaFileName: , @EndSchemaMod Description @StartSchemaMod lets NDS schemas be extended through installation scripts. SchemaFileName specifies the filename for the schema file, along with a Description for displaying to the screen during the modification. Example @StartSchemaMod SchemaFileName: “sys:\\system\\schema\\nwadmin.
PAGE 315

Manual 99a 38 July 17, 2001 Standard specifies information to be displayed to the user once the time zone has been selected. This includes the time zone abbreviation and the adjust +/x:xx:xx from GMT (Greenwich Mean Time) or UTC (Universal Coordinated Time). If Daylight exists, it specifies that daylight savings time exists for part of the year. It also specifies the daylight abbreviation, and the adjust +/-x:xx:xx from standard time.
PAGE 316

Manual 99a 38 July 17, 2001 Two time zone descriptions are displayed. When one is selected, the time parameters are filled in according to the above information, and the user can verify or edit them. @TranslateModule @EndTranslateModule Syntax @TranslateModule ,, ,, ... @EndTrandlateModuel Description @TranslateModule is used internally by NETMAIN.ILS.
PAGE 317

Manual 99a 38 July 17, 2001 Commands Command Syntax Command Description Command specifies the name of an optional command handler for commands not included in this file. The command handler name must be eight characters or less and correspond to the name of an NLM that exports external command entry points. Example Command ICMD.NLM ICMD.NLM provides external command support (see “External Command Syntax” on page 126).
PAGE 318

Manual 99a 38 July 17, 2001 Example CopyDriverToServer SYSTEM, '*.LAN', 'NETWARE-3', “NetWare diskette [3]” The *.LAN files are copied to the SYS:SYSTEM directory. CopyDriverToStartup Syntax CopyDriverToStartup , , Description CopyDriverToStartup replaces driver files in the startup or boot directory (where STARTUP.NCF is) with new driver files.
PAGE 319

Manual 99a 38 July 17, 2001 is a directory path relative to SYS: where the files will be copied. names the files to be copied; it might be in the “directory/file” form to copy files from a subdirectory. specifies the name of a diskette volume label and specifies the string used to prompt for the diskettes.
PAGE 320

Manual 99a 38 July 17, 2001 Exec Syntax Exec Description Exec issues the operating system command LOAD , pauses until the child NLM unloads, then continues executing. To load from other subdirectories of the system volume besides \SYSTEM, specify a filename (SYS:// and /). Example Exec MY.NLM MY.NLM will be loaded and executed. Exec will follow the normal NLM search path to find MY.NLM.
PAGE 321

Manual 99a 38 Record Type Data [6] Delete STARTUP line (255 char max) [7] Delete file line (255 char max) July 17, 2001 Example ProductRecord MYPROD, 1, “Description for my product” This creates a product description record for MYPROD with the quoted description. RegisterLanguage Syntax RegisterLanguage , Description RegisterLanguage renames to the respective name .
PAGE 322

Manual 99a 38 July 17, 2001 Example SaveLanguageFile SERVER.MSG If the current language ID is 4, SERVER.MSG in the DOS startup directory (BOOT directory) is copied to the subdirectory 4 in the DOS startup directory. Spawn Syntax Spawn Description Spawn issues the operating system command LOAD , then the installation continues to execute. See “Exec” on page 123. Example Spawn MY.NLM The MY.NLM file is loaded and executed. Spawn follows the normal NLM search path to find MY.NLM.
PAGE 323

Manual 99a 38 July 17, 2001 Using this method ensures that the ICMD.NLM version in SYS:SYSTEM is the actual 4.10 version and that all built-in products that use it will work properly. The new ICMD.NLM might still be fully backward-compatible, but it has not yet been fully tested in that regard. External Command Syntax To use any of the external commands made available by the ICMD.NLM command handler, include the statement command [] ICMD in the script file. Use CopyToServer to copy ICMD.
PAGE 324

Manual 99a 38 July 17, 2001 Description AppendFile appends the contents of the source file onto the destination file. It creates a temporary file that is as large as the destination file, then renames that file to the destination file. Wildcard characters for are not allowed. Example AppendFile input, file1, 'NETWARE-1', “NW [1]”, output, file2, '', '' The user is prompted for diskette NW [1], which is verified by checking for volume label NETWARE-1.
PAGE 325

Manual 99a 38 July 17, 2001 CheckFile Syntax CheckFile , , , Description CheckFile checks for the existence of at a path determined by the value of . If the path is a floppy, and is non-null (not ''), the user will be prompted for disk if it is not already in the drive. If the file is found, the value of variable NWSTATUS will be zero; otherwise it will be non-zero. Example CheckFile NWSRC, file1.
PAGE 326

Manual 99a 38 July 17, 2001 and time services information. The existing AUTOEXEC.NCF on SYS:SYSTEM is overwritten. Console Syntax Console , Description Console enters the text on the system console screen and delays before returning control back to the calling process. Because the system installation process executes in a different thread from the console, it is possible that the next command might finish before this Console command does.
PAGE 327

Manual 99a 38 July 17, 2001 (0|1|2|3) Value Description 0 Source is a file. 1 Source (including ) is a directory; copy directory contents to destination. 2 Source and the destination are files (file-to-file copy). must be 0 if is 2 3 Source (including ) is a directory; copy directory contents to destination only if that directory already exists on the destination.
PAGE 328

Manual 99a 38 July 17, 2001 For a DOS file: Attribute Meaning 00000001 Read Only 00000002 Hidden 00000004 System 00000008 Volume Label For a NetWare file: Attribute Meaning 00000001 Read Only 00000002 Hidden 00000004 System 00000008 Execute 00000010 Subdirectory 00000020 Archive 00000080 Shareable 00000700 Smode 00001000 Transaction 00004000 Read Audit 00008000 Write Audit 00010000 Immediate Purge 00020000 Rename Inhibit 00040000 Delete Inhibit 000800
PAGE 329

Manual 99a 38 July 17, 2001 Reserved path names () are NWSRC, NWDST and NWBOOT, the standard source, destination and boot path for NetWare files. can be a null string. Value Description 0 (or not present) Unconditionally copy this file. 1 Copy if destination file is not present. 2 Copy if destination file is not present; if it is, prompt user (no version check).
PAGE 330

Manual 99a 38 July 17, 2001 CopyFloppyImage Syntax CopyFloppyImage , , , , , , , , , Description CopyFloppyImage copies a diskette image file sector by sector to the specified drive (destination path which must be a diskette drive). Variable Description (0|1) 0 indicates a 3.5-inch high-density drive. 1 indicates a 5.
PAGE 331

Manual 99a 38 July 17, 2001 DiskReset Syntax DiskReset Description DiskReset tells DOS to rescan the directories on the floppy drive. This is necessary because the drive change interrupt is disabled while NetWare has control. Example Assuming myDir corresponds with A:\ DiskReset myDir Drive A:\will be rescanned. Dismounted CD Syntax DisMountCD Description DisMountCD is to be used with PromptForCD (below).
PAGE 332

Manual 99a 38 July 17, 2001 Example GetPath sys, 1, 'SYS:', '' Display_Text_File sys, “license.txt”, ccode The completion code will return a 0 (zero) for a successful return. Anything else is an error. Display Syntax Display <0|1|2>, “......” Description Display displays a message, accompanied by a beep if the first argument is 1. If the argument is 2, the message is displayed as a copy status. Example Display 0, “Product XYZ installation is complete.
PAGE 333

Manual 99a 38 July 17, 2001 Variable Description 1: Daylight savings time exists in this time zone 0: Daylight savings time doesn't exist in this time zone “set parameter” daylight savings time start string. For Example First Sunday of April at 2:00:00 a.m “set parameter” daylight savings time end string. For Example Last Sunday of October at 2:00:00 a.m.
PAGE 334

Manual 99a 38 July 17, 2001 EraseFile Syntax EraseFile , , , , Description EraseFile recursively erases the file or directories indicated in . Wildcards are acceptable. In NetWare, files can be removed no matter what their attributes; in DOS, only normal files can be removed. IMPORTANT: Use this command with care to delete only the intended data.
PAGE 335

Manual 99a 38 July 17, 2001 Example GetPath startup, 1, 'C:\\NWSERVER', '' EditNCF_KEYSTRING '' EditNCF_KEYSTRING 'PK411.NLM' EditNCF startup, 'startup.ncf', 'bak', ccode The contents of C:\NWSERVER\STARTUP.NCF will be searched for a line containing PK411.NLM and will be commented out by the EditNCF command.
PAGE 336

Manual 99a 38 July 17, 2001 EditNCF_KEYSTRINGS Syntax EditNCF_KEYSTRINGS Description EditNCF_KEYSTRINGS defines a list of keystrings to be used by EditNCF when determining which lines to comment out. (A line will be commented out if it contains any of the keystrings). NOTE: The list must be terminated with a null string (empty quotes) for the last entry. This command can be used multiple times. Each time replaces the previously defined list.
PAGE 337

Manual 99a 38 July 17, 2001 The variable version contain the string “v2.11”. ExtractVersionNumbers returns a value of 2 in the variable major, a value of 11 in the variable minor. And a value of 0 in the variable revision.
PAGE 338

Manual 99a 38 July 17, 2001 GetPath Syntax GetPath , , , , [] Description GetPath prompts the user for a path using the prompt. The prompt string will be displayed, with “%s” (like C-language print formatting) being replaced by the string. The keystrokes to modify will be added to your prompt. Trailing backslashes are always removed before the path is displayed. is a variable name that can be used later in a CopyFile command.
PAGE 339

Manual 99a 38 July 17, 2001 Goto Syntax Goto Description Goto causes execution to continue at the first occurrence of label . The scope of a label is always local to a file set. Therefore, a Goto statement cannot transfer execution to a file set different from the current one. Example Goto Done Label Done The statement Goto Done will cause execution to continue at the label Done.
PAGE 340

Manual 99a 38 July 17, 2001 GotoIfNEqual GotoIfGreater GotoIfLess GotoIfGrEqual GotoIfLsEqual Syntax GotoIfNEqual , , GotoIfGreater , , GotoIfLess , , GotoIFGrEqual , , GotoIfLsEqual , , Description These are identical to GotoIfEqual (page 142), except that execution branches only if (respectively): not equal to is greater than is less than
PAGE 341

Manual 99a 38 July 17, 2001 IsSubString Syntax IsSubString , , Description IsSubString returns the zero based of where starts, if is indeed contained within , otherwise is -1. Example IsSubString ‘Little Miss Muffet sat on’, ‘Miss Muffet’, index In this example, would return as 7. Label Syntax Label Description Label serves only as a target of a goto statement with .
PAGE 342

Manual 99a 38 July 17, 2001 Description LangVar sets a variable to the number of a language. It starts with , then it looks for a subdirectory whose name is a number that matches the current server language number. If the subdirectory is found, is set to that number; otherwise, is set to . Example Assuming the current language is 6: LangVar 4, lang, NWSRC, '', '' This command looks in the source install directory for a subdirectory named 6.
PAGE 343

Manual 99a 38 July 17, 2001 NLMExec NLMExecIO Syntax NLMExec , Description NLMExec executes the NLM specified by . If is 1, NLMExec waits for the NLM to complete execution, then continues. NLMExec is the external command version of the Exec (page 123) command. NLMExecIO is identical to NLMExec except it executes the command line on the default DOS server on a NetWare SFT III server. See “SetDOSServer” on page 149 for more information.
PAGE 344

Manual 99a 38 July 17, 2001 PromptForCD Syntax PromptForCD , Description PromptForCD is to be used with DisMountCD (above). PromptForCD will prompt the user to insert the CD labeled into the CD drive and then will attempt to mount the CD volume within the time frame. Example PromptForCD ‘CD 1’, 30 Quit Syntax Quit Description Quit will exit the script processing at this point. No further processing will take place.
PAGE 345

Manual 99a 38 July 17, 2001 This command is the counterpart to the ProductRecord command. See “ProductRecord” on page 123 for more information on record types. Example ReadProductRecord MYPROD, 0, version, ccode The command will search the products database and return the value for for product 'MYPROD'. Read_Var_File Syntax Read_Var_File , , Description Read_Var_File will read the contents of the filename and create variables for script processing.
PAGE 346

Manual 99a 38 July 17, 2001 indicates normal attributes. If the <0|1> argument is 1, the server container object (or everyone) is given rights to the directory. Example If myDir corresponds to VOL1:\ SetDir myDir, DOC, '', '', 10, 1, 0 The directory VOL1:\DOC will be created and all applicable users will have rights to it.
PAGE 347

Manual 99a 38 July 17, 2001 SetLConfigLang Syntax SetLConfigLang Description SetLConfigLang looks for the LCONFIG.SYS file in the server boot directory. The default server language ID number is changed to . Example SetLConfigLang 9 The default server language ID number in the LCONFIG.SYS file is changed to 9 (Japanese). SetVar Syntax SetVar , , [] Description SetVar sets a variable with to the string value.
PAGE 348

Manual 99a 38 July 17, 2001 SGotoIfEqual SGotoIfNEqual SGotoIfGreater SGotoIfLess SGotoIfGrEqual SGotoIfLsEqual The SGotoIf commands have the same options as the GotoIf commands. The SGotoIf commands perform a string comparison instead of an integer comparison. SpaceCheck Syntax SpaceCheck , Description SpaceCheck looks at .
PAGE 349

Manual 99a 38 July 17, 2001 SrchNCF Syntax SrchNCF , , , Description SrchNCF searches an .NCF file for line containing a substring matching (non case-sensitive). If found, the line of text will be returned; otherwise will be empty. NOTE: The same value as not found will be returned if an error is encountered (for example, invalid filename, read error, etc).
PAGE 350

Manual 99a 38 July 17, 2001 Volumes Syntax Volumes Description Volumes creates and mounts volumes on this server, with the volume SYS: placed on the first device larger than (512 bytes per sector). Additional volumes, named “VOL1”, “VOL2”, etc., will be created on other devices, one per device.
PAGE 351

Manual 99a 38 July 17, 2001 part of the variable name and must be included with the variable when referencing it later. If the filename doesn't exist, it will be created. The varname and var value will then be written. If the file does exist, the varname and var value will be appended to the contents of the file. External Command Programming Interface The external command programming interface contains the functions described below. IMPORTANT: These functions require ICMD.NLM 2.18 or later.
PAGE 352

Manual 99a 38 July 17, 2001 ICMDGetVar Use the ICMDGetVar function to get the value of a script variable. Function int ICMDGetVar (char *variableName, char *variableValue) *variableName: Pointer to name of variable *variableValue: Buffer containing value of variable; must be at least 128 bytes Return 0 if successful; non-zero error code if unsuccessful or if variableName does not exist. Description ICMDGetVar is a function exported by ICMD.NLM that another NLM can call.
PAGE 353

Manual 99a 38 July 17, 2001 External Command Variable Substitution A variable, such as the value returned by GetPath (page 141), can be used inside any quoted string within an executed external command. The variable is global. It goes out of scope only when the command processor is replaced by a different one. The variable can be dereferenced explicitly by an expression %{} within another string. Variable Description NWSERVER The name of the server the script is processing on.
PAGE 354

Manual 99a 38 July 17, 2001 All path variables, including the predefined ones, allow subfield specifiers in the form .. PATH String containing the actual path. VOL Disk volume name. PROMPT Disk volume prompt. TYPE Path type. SUBTYPE Path subtype. CONN Connection number (hex). ENGINE Engine number.
PAGE 355

Manual 99a 38 July 17, 2001 Installation NLM Command Line Options Command line options can be preceded by '-', but this is not required. IMPORTANT: These options are not intended for general distribution; they apply only to the NetWare installation NLM. Other Switches are not guaranteed to be supported in all versions. User-Documented Switches for NetWare Installation Switch Description DSREMOVE Allows absolute removal of DS. R Allows license replacement.
PAGE 356

Manual 99a 38 July 17, 2001 Other Switches Switch Description MDEBUG Memory debug. TRANSPORT Transport layer type. (IPX is the default). IPX TCP UDP C= Source path remote context. DS= Specifies that NDS authentication will be used. If command is not present, the connection is made through the bindery. F= Front end flag. Q simplified mode T calculate file set totals V suppressed delayed init (DELAY) X allow more DS options K= Default startup.ncf file spec. L= Mode of installation.
PAGE 357

Manual 99a 38 July 17, 2001 NetWare 4.1 Remote Installation Wrapper You can use NetWare installation to remotely install a product that was not originally intended for remote installation. 1 Create a wrapper script that copies the associated files to the server before executing PINSTALL.NLM. Make sure the system volume is large enough to contain the scratch files, even in local install cases. In the example below, the directory layout is as follows on the diskette: \ (root) PINSTALL.IPS PINSTALL.
PAGE 358

Manual 99a 38 July 17, 2001 NetWare Installation Command Version Availability The following tables list the available NetWare installation and external installation commands. NetWare Install Commands Command NetWare 4.10 NetWare 4.
PAGE 359

Manual 99a 38 July 17, 2001 Command NetWare 4.10 NetWare 4.11 NetWare for Small Business NetWare 5 and NetWare 6 Exec X X X X ProductRecord X X X X RegisterLanguage X X X X SaveLanguageFile X X X X Spawn X X X X 2.18 3.20 3.25 X X X X X X X X X NetWare External Install Commands Command Version of ICMD.NLM 2.
PAGE 360

Manual Command 99a 38 July 17, 2001 Version of ICMD.NLM 2.00 2.18 3.20 3.
PAGE 361

Manual Command SetDir 99a 38 July 17, 2001 Version of ICMD.NLM 2.00 2.18 3.20 3.
PAGE 362

NetWare Migration Wizard 6 Administration Guide Novell NetWare Migration Wizard 6 ® www.novell.
PAGE 363

Manual Rev 99a July 17, 2001 38 Contents Contents 5 NetWare Migration Wizard 6 Administration Guide 7 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 Migrating Data from NetWare 3 9 Meet System and Software Requirements . . . . . . . Preparing the Workstation . . . . . . . . . . . . . Preparing the Source Server . . . . . . . . . . . . Preparing the Servers in the Destination NDS Tree Creating a Template Object . . . . . . . . . . . .
PAGE 364

Manual Rev 99a July 17, 2001 38 Migrate Users and Data to the Destination NDS Tree. . . . . . . . . . . . . . . . . . . . . . . 46 Perform Post-Migration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50 4 Troubleshooting 51 General Connection Problems . . . . . . . . . . . . . Workstation-to-Server Connections . . . . . . . . . . . Server-to-Server Connections . . . . . . . . . . . . . . File Copy . . . . . . . . . . . . . . . . . . . . . . . . SMDR Errors . . . . . . .
PAGE 365

Manual Rev 99a 38 July 17, 2001 NetWare Migration Wizard 6 Administration Guide Novell® NetWare® Migration Wizard 6 lets you copy data from a NetWare or a Windows* NT* server to another NetWare server in your network. Migrating Data from NetWare 3—Migration Wizard copies the NetWare 3 file system and bindery objects to a destination NDS® tree. When the bindery objects are copied to the destination NDS tree, they are automatically converted to NDS objects.
PAGE 366

Manual 8 Rev 99a NetWare Migration Wizard 6 Aministration Guide NetWare Migration Wizard 6 Aministration Guide 103-000161-001 August 29, 2001 Novell Confidential 38 July 17, 2001
PAGE 367

Manual 1 Rev 99a 38 July 17, 2001 Migrating Data from NetWare 3 Novell® NetWare® Migration Wizard 6 copies and consolidates your NetWare 3 bindery and file system from one or more existing NetWare 3 servers to a destination NDS® tree. The following figure shows how the Migration Wizard manages the migration of data from multiple NetWare 3 servers to a destination NDS tree. NetWare 3 Servers Data Destination NDS Tree files volumes objects NetWare Migration Wizard Windows 98 or Windows NT 4.
PAGE 368

Manual Rev 99a 38 July 17, 2001 3. “Verify Your Migration Project” on page 17 4. “Migrate Users and Data to the Destination NDS Tree” on page 17 5. “Perform Post-Migration Tasks” on page 20 Meet System and Software Requirements Log in to your destination NDS tree with a user that is listed in the bindery context of the destination NDS tree. Make sure the user has the Supervisor right to the destination servers that you are migrating file data to and three available user licenses.
PAGE 369

Manual Rev 99a 38 July 17, 2001 Preparing the Source Server The source server is the existing server that contains the data that will be copied to the destination NDS tree. The source server must be running NetWare 3.11 or later. Load the following NLMTM program at the server console of each NetWare 3 source server that you are planning to migrate: For NetWare 3.11, load TSA311.NLM For NetWare 3.12 and 3.2, load TSA312.
PAGE 370

Manual Rev 99a 38 July 17, 2001 If there is a conflict between the properties of a Template object and properties of a NetWare 3 user, the properties of the Template object will, in most cases, take priority.
PAGE 371

Manual Rev 99a 38 July 17, 2001 8 Click Next. 9 Name your migration project, choose a place to save it, and then click Next. By default, Migration Wizard saves your project in C:\Program Files\Novell\NetWare Migration Wizard. 10 Select the source servers that you want to migrate. Only servers that you are already logged in to appear in the Selected Servers text box. To log in to a server, click the Server icon. When you are finished selecting your servers, click Next.
PAGE 372

Manual Rev 99a 38 July 17, 2001 any changes, Migration Wizard will automatically merge the NetWare 3 user with the displayed NDS user. Figure 1 Merging Your NetWare 3 Users with Duplicate NDS Users You have the following options for each NetWare 3 user: Merge the NetWare 3 user with the displayed NDS user Simply leave the NetWare 3 user displayed as it is in the table and continue with the next user.
PAGE 373

Manual Rev 99a 38 July 17, 2001 15e Once you have made a decision for each listed NetWare 3 user, click Finish. The NetWare 3 users that you chose to merge with NDS User objects appear automatically as dropped objects in the destination NDS tree. Continue with the next section, "Model Your Migration Project.
PAGE 374

Manual Figure 2 Rev 99a 38 July 17, 2001 Using the Project Window Dialog Box The three basic steps outlined in this dialog box should be performed for each migration project. Once you are familiar with the tasks that you will be performing, click Close to access the Project Window and begin modeling your migration. Complete the following tasks: 1 Determine which NetWare 3 bindery objects and volume data will be copied to which containers in the destination server’s NDS tree.
PAGE 375

Manual Rev 99a 38 July 17, 2001 Verify Your Migration Project Once you have modeled your migration in the Project Window, you should verify that the proposed locations for these new objects do not conflict with existing names in the destination NDS tree. Remember, dragged-and-dropped items appearing in the NDS tree are merely assigned to be copied to that area in the NDS tree. Objects will not actually be migrated until you begin the migration.
PAGE 376

Manual Rev 99a 38 July 17, 2001 4 If prompted, select what volume you want to migrate your NetWare 3 print queue volume to, and then click Next. 5 If you want to apply a Template object to newly created users, browse the tree, select the Template object from the tree view and then click Next. If you do not want to use a Template object, uncheck the check box and click Next. IMPORTANT: Home directories are not automatically migrated.
PAGE 377

Manual Rev 99a 38 July 17, 2001 10 Click Next to verify that you have enough disk space on the destination volume to accommodate your NetWare 3 file system. Migration Wizard will also scan the contents of all dropped folders and verify that you have sufficient rights to migrate them. 11 If prompted, resolve any naming conflicts between different-type objects, and then click Next. You can choose to rename different-type objects or to not migrate them.
PAGE 378

Manual Rev 99a 38 July 17, 2001 17 (Migration only) View the Error Log and the Success Log. Continue with the next section, "Perform Post-Migration Tasks." Perform Post-Migration Tasks After you’ve migrated the bindery objects and file system to the destination server, complete the following tasks: Modify the print configuration if you want to convert your queue-based printing to NDPS®. For more information, see the Novell Documentation Web site (http:// www.novell.
PAGE 379

Manual 2 Rev 99a 38 July 17, 2001 Migrating Data from NetWare 4, 5, or 6 When you migrate data from a NetWare® 4, NetWare 5, or NetWare 6 source server to a NetWare destination server, Novell® NetWare Migration Wizard 6 copies the file system and NDS® database from the source server to the newly installed NetWare destination server.
PAGE 380

Manual Rev 99a 38 July 17, 2001 To migrate data from NetWare 4, NetWare 5, or NetWare 6, complete the following tasks in the order they are listed. 1. “Meet System and Software Requirements” on page 22 2. “Run Migration Wizard” on page 25 3. “Perform Post-Migration Tasks” on page 32 Meet System and Software Requirements Preparing the Workstation Make sure your workstation has the following: A Windows 98 or Windows NT 4/2000 workstation with 50 MB of available disk space.
PAGE 381

Manual Rev 99a 38 July 17, 2001 (Conditional) If you are migrating data from NetWare 4, make sure that the source server’s volumes are running long name space support on all volumes to be copied. To add long name space support to a NetWare 4.11 or NetWare 4.2 volume, enter the following at the server console: LOAD LONG and then ADD NAME SPACE LONG TO volumename.
PAGE 382

Manual Rev 99a 38 July 17, 2001 During the installation, create volumes on the destination server that are the same size as, or larger than, volumes on the source server. Volume names on the destination server must be the same as the volume names on the source server. Migration Wizard migrates compressed volumes. If you are migrating compressed volumes to uncompressed volumes, Migration Wizard decompresses the volumes during the migration.
PAGE 383

Manual Rev 99a 38 July 17, 2001 Run Migration Wizard 1 Download and install NetWare Migration Wizard 6 from the NetWare section of the Novell Software Downloads Web site (http:// www.novell.com/download). 2 Run Migration Wizard from the location where you installed it. The installation program, by default, installs Migration Wizard at this location: Start Menu > Programs > Novell > Netware Migration Wizard > NetWare Migration Wizard. 3 Read the Welcome screen and click OK.
PAGE 384

Manual Rev 99a 38 July 17, 2001 Copy Volumes 1 In the Project Window, click Copy Volumes. Before Migration Wizard starts copying files, it backs up your directory and file trustees and saves them in files located on the source and the destination server. Once the NDS migration is complete, Migration Wizard restores the trustees from the files it stored on the destination server. You do not need to copy all volumes at once.
PAGE 385

Manual Rev 99a 38 July 17, 2001 directories, Migration Wizard migrates them to the SYS:SYS.MIG directory on the destination server. If there are files in the source server’s SYS: directories that you want to utilize on the destination server, after the NDS migration is completed, copy the files from the SYS:SYS.MIG directory into the appropriate SYS: directory on the destination server. Remember, any applications that have NLM programs in this directory will need to be reinstalled after the migration.
PAGE 386

Manual Rev 99a 38 July 17, 2001 Edit Configuration Files 1 In the Project Window, click Edit Configuration Files. Migration Wizard lets you modify any .NCF or .CFG files on the destination server. These files contain default LOAD statements and parameters. IMPORTANT: If you are editing your AUTOEXEC.NCF, make sure the file is closed before you migrate your NDS database. 2 In the text box, select the configuration file that you want to edit and then click Edit File.
PAGE 387

Manual Rev 99a 38 July 17, 2001 Begin NDS Migration 1 In the Project Window, click Begin NDS Migration. 2 Back up all volumes that you are not planning to migrate and complete the following tasks before continuing: Make sure all volume data migrated successfully. Make sure all critical errors from the file copy are resolved. Make sure the servers in your source NDS tree are in time sync and that NDS is synchronized. For more information, see Step 2 on page 31. 3 Click Next.
PAGE 388

Manual Rev 99a 38 July 17, 2001 IMPORTANT: If you are getting NICI errors when NDS is trying to load or when you are copying the NICI files, you should first check and see if PKI.NLM will load on the destination server. If PKI.NLM won’t load, see “NICI Errors” on page 55. 8 Delete all user connections (except your own) to the source and destination servers, and then click Next. 9 Enter the passwords for the source and destination trees, and then click Next.
PAGE 389

Manual Rev 99a 38 July 17, 2001 14 Reboot your workstation and log in to the former destination server. If you can’t log in, refer to “Workstation-to-Server Connections” on page 52. Continue with the next section, "Finish NDS Migration." Finish NDS Migration 1 In the Project Window, click Finish NDS Migration.
PAGE 390

Manual Rev 99a 38 July 17, 2001 Perform Post-Migration Tasks 1 Run DSREPAIR on the destination server and select Unattended Full Repair. 2 Make sure that user information migrated successfully. 3 Reinstall any applications that have files or NLM programs associated with the following volume SYS: directories: SYSTEM, PUBLIC, MAIL, ETC, and NETBASIC.
PAGE 391

Manual 3 Rev 99a 38 July 17, 2001 Migrating Data from Windows NT Novell® NetWare® Migration Wizard 6 automates key tasks, such as migrating users and their file permissions, assigning passwords, and migrating the NT file system to a designated NDS® tree. This automation eliminates the need to choose from various utilities that would help you perform these tasks individually. Windows NT 3.51/4 Server NetWare Server Data File System and NT Objects NetWare Migration Wizard Windows NT 4.
PAGE 392

Manual Rev 99a 38 July 17, 2001 This information will help you decide which NT servers to migrate first and how many servers you will need to migrate at one time. When you migrate your users and groups, you will want to migrate all files and directories that they have access to at the same time that you migrate their User objects.
PAGE 393

Manual Rev 99a 38 July 17, 2001 Do you have any trusted domains? If so, you must reassign any trusted domain permissions to the appropriate NT user and groups after the migration is complete. Use ConsoleOneTM to reassign all lost trusted domain permissions. Once you have planned your migration, you’re ready to begin your NT migration. Complete the following tasks in the order they are listed. 1. “Meet System and Software Requirements” on page 35 2. “Perform Prerequisite Tasks” on page 36 3.
PAGE 394

Manual Rev 99a 38 July 17, 2001 Platform Hardware Software Windows NT 4 and Windows NT 2000 workstations Minimum hardware requirements of Windows NT 4 and 2000 workstations Novell ClientTM for Windows NT 4 and 2000 version 4.8 or later Minimum hardware requirements of Windows NT 4 Novell Client for Windows NT version 4.
PAGE 395

Manual Rev 99a 38 July 17, 2001 If there is a conflict between the properties of a Template object and an NT policy, the properties of the Template object will, in most cases, take priority. For example, if a minimum password length of seven characters is specified for user Jeff in an NT policy and a minimum password length of nine characters is specified in the Template object, then when Jeff’s object is migrated, the object will be created in NDS with a password length of nine characters.
PAGE 396

Manual Rev 99a 38 July 17, 2001 To create ZENworks User Policy Packages in ConsoleOne, do the following: 1 In NetWare Administrator, right-click an NDS Organizational Unit in the tree view and then click Create > Policy Package. The type of workstation you have in your NT network (Windows NT/ 2000, Windows 95/98, or both) will determine whether you want to create WINNT-2000 user policy packages, WIN 95-98 policy packages, or both. 2 In ConsoleOne, click the user policy package icon in the toolbar.
PAGE 397

Manual Rev 99a 38 July 17, 2001 3 Click Properties and enter the computer name and appropriate domain, and then click OK. 4 Reboot the workstation and launch Migration Wizard again; then continue with the next section, "Run Migration Wizard." Run Migration Wizard 1 Download and install Migration Wizard from Novell Software Downloads (http://www.novell.com/download) > NetWare > NetWare Migration Wizard 6 or from the NetWare 6 Operating System CD. Follow the download and installation instructions.
PAGE 398

Manual Rev 99a 38 July 17, 2001 The destination NDS tree is the NDS tree that you want to migrate your NT data to. If you are not logged in to your NDS tree, the NDS tree name will not appear in the drop-down list. If this is the case, click the Browse button to log in to your NDS tree. Once you are logged in, the NDS tree name automatically appears in the drop-down list.
PAGE 399

Manual Figure 3 Rev 99a 38 July 17, 2001 Merging Your NT Users with Duplicate NDS Users You have the following options for each listed NT user: Merge the NT user with the displayed NDS user. Simply leave that user as it is displayed in the table and continue with the next listed NT user. Merge an NT user with a different NDS user. Click the arrow by the NDS username to view a drop-down list containing all the NDS users that have the same username (including contexts) as the adjacent NT user.
PAGE 400

Manual Rev 99a 38 July 17, 2001 Model Your Migration Project Most of your work will be done in the Project Window, where you can drag and drop NT User and Group objects into NDS containers, and NT folders and volumes into any volume or folder in the destination NDS tree. The Project Window is a place to model different migration scenarios before you begin the actual migration without affecting your NT domain or your destination NDS tree.
PAGE 401

Manual Rev 99a 38 July 17, 2001 performing, click Close to access the Project Window and begin modeling your migration project. Using the Project Window Review the following tips to help you organize your migration project and use the Project Window more effectively. Creating a New NDS Organizational Unit or Folder—To create a new NDS Organizational Unit (OU), right-click the parent NDS Organizational Unit or folder and then click New Organizational Unit or New Folder.
PAGE 402

Manual Rev 99a 38 July 17, 2001 Uppercase and lowercase letters, underscores, and spaces are not acknowledged by NDS. For example, Manager_Profile and MANAGER PROFILE are considered identical names in NDS. Setting the Context—To set the context, right-click an NDS Organizational Unit and then click Set Context. When you set the context, you can designate what part of the NDS tree will appear in the right side of the Project Window. This is useful if you have a large NDS tree with many objects.
PAGE 403

Manual Rev 99a 38 July 17, 2001 Finding Out Where a Dropped NT Object Came From—To find out where a dropped object was located in the NT domain, right-click an NT object and then click Where Did It Come From? When dragging and dropping a large number of objects, this will help you remember where a dropped object was previously located in the NT domain.
PAGE 404

Manual Rev 99a 38 July 17, 2001 Migrate Users and Data to the Destination NDS Tree Although you have selected the volumes and containers where the NT data will be copied, no data has yet been migrated. When migrated, NT User objects are converted to NDS objects and placed in the destination NDS tree. To begin the migration, do the following: 1 From the Migration Wizard toolbar, click Project > Verify and Migrate Project. 2 Read the Welcome screen and then click Next.
PAGE 405

Manual Rev 99a 38 July 17, 2001 4c Review the NT groups that you chose to associate with specific ZENworks User Policy Packages, and then click Next. If you want to change an association, click Back and follow the instructions in Step 4b. HINT: This screen will not appear if you are using ZENworks 3.0. 5 Decide how you want to handle any duplicate filenames between the Microsoft NT domain and the destination NDS tree.
PAGE 406

Manual Rev 99a 38 July 17, 2001 Everyone permissions, be sure to drop the NT Domain Info object high enough in the NDS tree so that all NT users will inherit those permissions. HINT: Every new folder that is created in the NT domain automatically receives the Everyone permissions by default.
PAGE 407

Manual Rev 99a 38 July 17, 2001 12 If prompted, verify that you do not want to migrate the listed NT users and groups, and then click Next. This procedure must be done three times—once for all your NT local groups, NT global groups, and NT users that were not dragged and dropped into the destination NDS tree. If you migrated all of your users and groups, you will not see this dialog box. If you have made a mistake, click Cancel. This will return you to the Project Window.
PAGE 408

Manual Rev 99a 38 July 17, 2001 Perform Post-Migration Tasks After you’ve migrated your NT data to the destination NDS tree, complete the following tasks: Install the latest Novell Client software on any workstations that it was not previously installed on. You can download the client from the Novell Software Download Web site (http://www.novell.com/download). For instructions on installing the Novell Client on multiple workstations at the same time, see the Novell Client Documentation at (http://www.
PAGE 409

Manual 4 Rev 99a 38 July 17, 2001 Troubleshooting Refer to the appropriate section if you are having trouble with any of the following: General Connection Problems (page 51) Workstation-to-Server Connections (page 52) Server-to-Server Connections (page 53) File Copy (page 53) SMDR Errors (page 54) Restoring Trustees (page 54) NUWAGENT.
PAGE 410

Manual Rev 99a 38 July 17, 2001 The NDS user that you are using to do the migration has the Supervisor right to the source server’s NDS object. Use ConsoleOneTM to verify that the NDS object of the NDS user is listed in the source server’s Operators list.
PAGE 411

Manual Rev 99a 38 July 17, 2001 Server-to-Server Connections If you have problems establishing or maintaining connections between your servers, try one or more of these troublshooting suggestions: Do not remove the source or destination server from the NDS tree. The servers must be able to communicate with the other servers in the tree during the migration. Make sure the destination and source servers can communicate with each other. For IPX connections, enter DISPLAY SERVERS at the server console.
PAGE 412

Manual Rev 99a 38 July 17, 2001 SMDR Errors Sometimes the SMDR.NLM program that is running on the destination server can’t make a connection to the source server. To correct this problem, try one or more of the following: Reboot the source server. Unbind the protocol you are not using from the destination server. For example, if you are using IPX for the migration, but IP is bound on the destination server, unbind the IP protocol on the destination server during the migration.
PAGE 413

Manual Rev 99a 38 July 17, 2001 NUWAGENT.NLM NUWAGENT.NLM is the NLM program that the Migration Wizard uses to do much of its work. If you get errors that the NUWAGENT.NLM won’t load, try the following: Manually load NUWAGENT.NLM from the server console. Enter SMDR NEW at the destination server console. This re-creates the SMDR configuration and allows NUWAGENT.NLM to load.
PAGE 414

Manual Rev 99a 38 July 17, 2001 NDS Migration If the migration fails during the NDS Migration step, you need to restore the source and destination servers to their original configuration before you can retry the NDS migration. The instructions for restoring the servers to their original configurations are different depending on when the migration of data failed.
PAGE 415

Manual Rev 99a 38 July 17, 2001 4 To perform the NDS migration again, launch Migration Wizard and open the project you were previously working on. When the project opens and you see the Project Window, click the Begin NDS Migration button and follow the instructions in “Begin NDS Migration” on page 29.
PAGE 416

Manual Rev 99a 38 July 17, 2001 If the message appears saying that NDS has already been removed, bring the destination server down and continue with the next section, "Remove NDS from the Source Server." If NDS was not successfully removed, exit NWCONFIG and enter NWCONFIG -DSREMOVE at the destination server console.Then follow this procedure again, beginning with Step 2. Remove NDS from the Source Server Once NDS has been removed from the destination server, remove NDS from the source server.
PAGE 417

Manual Rev 99a 38 July 17, 2001 Restore NDS to the Source Server By removing NDS from the source server, you removed the server from any replica rings that held a partition of the source server. Now you must complete the following procedure to restore NDS to the source server. 1 Enter one of the following at the server console: If your source server was running NetWare 4, enter LOAD INSTALL. If your source server was running NetWare 5 or later, enter LOAD NWCONFIG.
PAGE 418

Manual Rev 99a 38 July 17, 2001 15 Enter the Admin username and password. 16 Exit DSREPAIR. 17 At the workstation where you performed the migration, open your project. 18 From the Migration Wizard Tools menu, click Restore Trustees to restore the trustee assignments. 19 If the source server held the master replica of any partitions and you want to restore these partitions prior to doing the NDS migration again, use DSREPAIR to re-create them.
PAGE 419

Novell Client for Windows Novell Client for Windows www.novell.
PAGE 420

doc_tpl.fm Rev 99a 22 June 00 28 Contents Novell Client Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 1 Installing Novell Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Preparing to Install the Client Software . . . . . . . . Checking Server Protocols and Requirements . . . Downloading the Latest Client Software . . . . . .
PAGE 421

doc_tpl.fm Rev 99a 22 June 00 Logging In to the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logging Out of the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up Passwords in Windows NT/2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Setting Client Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Properties before Installation . . . . . . . . . . . . .
PAGE 422

doc_tpl.fm Text File Usage . . . . Other . . . . . . . . . # . . . . . . . . . . . . . Command Format . . Example . . . . . . . @. . . . . . . . . . . . . Command Format . . Examples . . . . . . . ATTACH . . . . . . . . . BREAK . . . . . . . . . . Command Format . . CONTEXT . . . . . . . . Command Format . . Example . . . . . . . DISPLAY . . . . . . . . . Command Format . . Example . . . . . . . DRIVE . . . . . . . . . . Command Format . . Example . . . . . . . EXIT . . . . . . . . . . . FDISPLAY . . . . .
PAGE 423

doc_tpl.fm PROFILE . . . . . . Command Format Example . . . . . REMARK . . . . . . Command Format Example . . . . . SCRIPT_SERVER . Command Format SET . . . . . . . . . Command Format Examples . . . . SET_TIME . . . . . . Command Format SHIFT . . . . . . . . Command Format Examples . . . . TERM . . . . . . . . Command Format Example . . . . . TREE . . . . . . . . Command Format Example . . . . . WRITE. . . . . . . . Command Format Examples . . . . B C . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 424

Manual 99a 38 July 17, 2001 Novell Client Documentation This documentation includes information on installing and configuring Novell® ClientTM for Windows* XP version 4.82, Novell Client for Windows NT*/2000 version 4.81, and Novell Client for Windows 95/98 version 3.31 and later software. If you are using a previous version of Novell Client software, you should update it to the latest version (http://www.novell.com/download).
PAGE 425

Manual 12 Novell Client for Windows Novell Client for Windows 103-000159-001 December 7, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 426

Manual 1 99a July 17, 2001 38 Installing Novell Clients This chapter explains how to install Novell® ClientTM for Windows XP, Novell Client for Windows NT/2000, and Novell Client for Windows 95/98 software on one workstation or across the network.
PAGE 427

Manual 99a 38 July 17, 2001 Checking Server Protocols and Requirements You must prepare your servers to work with the Novell Client software. You must know what protocols you use on the server and make sure that the servers are configured to support long filenames. NetWare® 5 or later automatically supports long filenames and does not need to have the name space added to it. However, you must add long filename support to NetWare 3 and NetWare 4 servers.
PAGE 428

Manual 99a July 17, 2001 38 Adding Long Name Space Make sure that long filename support is installed on NetWare 3 or NetWare 4 servers. NetWare 5 or later servers automatically support long filenames. IMPORTANT: Each name space added to a volume requires additional server memory. If you add name space support to a volume on a server without sufficient memory, that volume cannot be mounted.
PAGE 429

Manual 99a 38 July 17, 2001 If you have never installed a client or created a network connection, you might not have access to Network Neighborhood or My Network Places. Therefore, you must install the client software from CD-ROM. See “Installing Novell Client at the Workstation” on page 17.
PAGE 430

Manual 99a July 17, 2001 38 Additional Information “Installing Novell Client at the Workstation” on page 17 “Installing Clients from the Network” on page 19 Installing Novell Client at the Workstation If you plan to install Novell Client software on a small number of workstations, or if the workstations are not yet connected to a network, install from the Novell Client CD or download it from the Novell Web site (http:// www.novell.com/download).
PAGE 431

Manual 99a 38 July 17, 2001 For Windows NT/2000/XP, enter path_to_the_software/ SETUPNW.EXE /508 2 Click a language, a platform, and then the software you want to install. 3 Follow the on-screen instructions. Once Novell Client is installed, check your network protocol configuration. See “Configuring Network Protocols” on page 18. Configuring Network Protocols After you install Novell Client, make sure that it is configured correctly for your network.
PAGE 432

Manual 99a 38 July 17, 2001 Installing Clients from the Network You can install Novell Client software on multiple workstations from the network by copying files to the server and modifying the login script. This installation is sometimes referred to as an Automatic Client Upgrade (ACU). HINT: You can install the Novell Client using the Application Launcher component of ZENworks.
PAGE 433

Manual 99a 38 July 17, 2001 Copying Files 1 Do one of the following: From the Novell Client CD, copy the WINNT or WIN95 directories to the new folder. If you are installing only one platform, you need to copy only the platform directory (WINNT or WIN95) for the platform you will install.
PAGE 434

Manual 99a July 17, 2001 38 If you did not create the status log file prior to running the network installation, you must give users the Create and Write rights to the directory. Modifying the ACU Configuration File The Automatic Client Upgrade utility (ACU.EXE) determines whether the client needs to be updated and allows you to specify several installation options. Option Description Settings [LAUNCHINSTALL] Specifies whether the platformspecific setup utility will be launched once ACU.
PAGE 435

Manual 99a July 17, 2001 38 Option Description Settings [CLIENTLOCAL INSTALL] Specifies whether the installation will be copied to a specified local directory and run locally. LocalInstall=Yes | No (default: No) LocalDirectory=directory where you want the installation copied (default: C:\Novell\ClientLocalInstall) DeleteLocalInstall=Yes | No (default: No) HINT: If you want to delete the files after the installation is complete, set the DeleteLocalInstall parameter to Yes.
PAGE 436

Manual 99a July 17, 2001 38 IMPORTANT: If you are configuring Windows 95/98 workstations, options that were set in the NWSETUP.INI file or on the command line in previous versions of Novell Client (such as Display First Screen or CAB FIX) are now set up in Novell Client Install Manager. To create a configuration file, do the following: 1 Start Novell Client Install Manager (NCIMAN.EXE).
PAGE 437

Manual 99a 38 July 17, 2001 Creating or Modifying the Login Script You need to modify login scripts for users whose workstations will be upgraded. To upgrade workstations for users in a container, modify that container’s login script. To upgrade workstations for users in a profile, modify that profile’s login script. To upgrade specific users’ workstations, modify those users’ login scripts.
PAGE 438

Manual 99a 38 July 17, 2001 Sample Client Installation Login Script (Windows 95/98 and NT/2000 Only) The following sample shows the commands that you add to the login script in order to install the client software from the network. The sample includes text for installing across an internal network. HINT: In this sample, the text that is necessary to the script is represented in uppercase letters. The information that you should customize for your network is in lowercase letters.
PAGE 439

Manual 99a 38 July 17, 2001 Upgrading a Client Workstation to Windows 2000 You can upgrade a Windows 95/98 or Windows NT 4.0 workstation with Novell Client software to Windows 2000 without uninstalling the client software. NOTE: IPX Compatibility and Novell NetWare/IP Adapter will not be upgraded from Windows NT to Windows 2000. Some Windows NT 4.0 printer drivers are incompatible with Windows 2000 and will not install. Contact Microsoft for more information.
PAGE 440

Manual 99a July 17, 2001 38 For more information on Automatic Client Upgrade, see “Installing Clients from the Network” on page 19. For more information on installing Novell Client on individual workstations, see “Installing Novell Client at the Workstation” on page 17. Upgrading a Client Workstation to Windows XP If you are upgrading your Windows operating system on workstations that already have the Novell Client installed, you must first uninstall the Novell Client to ensure a clean upgrade.
PAGE 441

Manual 28 Novell Client for Windows Novell Client for Windows 103-000159-001 December 7, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 442

Manual 2 99a July 17, 2001 38 Setting Up Client Login You can customize the client login environment to suit your network and have greater control over what users can access during login.
PAGE 443

Manual 99a 38 July 17, 2001 Profile sets environments for several users at the same time. Profile login script are executed after the container login script and are associated with Profile objects. A user can be assigned only one profile login script but can choose other profile login scripts. User sets environments (such as printing options or an e-mail username) specific to a single user.
PAGE 444

Manual 99a 38 July 17, 2001 Where Login Scripts Should Be Located Login scripts are properties of objects. Consequently, only certain objects can contain login scripts. This, in turn, largely determines where login scripts can be located. The following figure shows how the different types of login scripts can reside in an NDS tree and how they affect users. In the figure, there are three users: ESAYERS, SWILLIAMS, and MRICHARD.
PAGE 445

Manual 99a 38 July 17, 2001 For example, in the previous figure, although there are two levels of container objects above users ESAYERS and SWILLIAMS, only the script for the container they’re in (OU=SALES_PV) executes when they log in. If the SALES_PV Organizational Unit had no container login script defined, no container login script would execute for ESAYERS and SWILLIAMS, even though a container login script exists at a higher level.
PAGE 446

Manual 99a July 17, 2001 38 To create or modify a login script using ConsoleOne, complete the following steps: 1 Double-click the object whose login script you want to create or modify. 2 Click Login Script. 3 Enter the login script commands and information into the login script text box. For a sample, see “Sample Login Scripts” on page 93. IMPORTANT: Make sure that you edit the sample login script to match the server names, directory paths, and specifications of your own network.
PAGE 447

Manual 99a 38 July 17, 2001 The User object is now a trustee of the Profile object and has the rights necessary to run the profile login script. Repeat these steps for all additional users who need to use this script. Getting around the One Profile Login Script Restriction Users can belong to only one profile login script and so, as a rule, only one profile login script can be executed for any user.
PAGE 448

Manual 99a 38 July 17, 2001 4 Make necessary changes to the sample login script to customize it for your network. IMPORTANT: Make sure that you edit the sample login script to match the server names, directory paths, and specifications of your own network. 5 Click OK to save the new login script. If the login script that you just created was a container or user login script, you’re finished.
PAGE 449

Manual 99a 38 July 17, 2001 Setting Up Login Restrictions Login restrictions are limitations on user accounts that control access to the network.
PAGE 450

Manual 99a July 17, 2001 38 HINT: To create and then distribute location profiles that will be used by multiple workstations, use the Novell Client Configuration policy created in the Workstation Configuration policy package in ConsoleOne. For more information on using ZENworks for Desktops policy packages, see the ZENworks for Desktops documentation. If you have questions while setting up a policy package, click Help.
PAGE 451

Manual 99a 38 July 17, 2001 Removing a Location Profile You might need to remove a location profile once it has been created. If you are removing a location profile created on an individual workstation, complete the procedure below. If you want to remove a location profile created in a Client Configuration policy, you can either delete the Client Configuration policy or change the associations of specific users with this policy.
PAGE 452

Manual 99a July 17, 2001 38 The Workstation Only check box that appears under the Password field during an initial NT/2000 login If you do not want to allow workstation-only logins—for example, if you want to require that the user log in to NetWare in order to use the workstation—you can hide the Workstation Only check box.
PAGE 453

Manual 99a 38 July 17, 2001 Logging In to the Network IMPORTANT: We recommend that users do not use the command line LOGIN utility. There are several ways to initiate a Novell Client Login once users have already logged in to NetWare or to the local workstation: Right-click the red N icon in the System Tray and then click NetWare Login. Right-click Network Neighborhood and then click NetWare Login. Click Start > Programs > Novell (Common) > Novell Login.
PAGE 454

Manual 3 99a 38 July 17, 2001 Setting Client Properties You can optimize Novell® ClientTM for your network by using property pages to configure installation options and protocol support, optimize performance, configure optional client parameters, and set a variety of other parameters. By default, the client is configured for high speed with moderate use of memory and data protection. You can adjust the client to optimize its performance in any of these areas.
PAGE 455

Manual 99a 38 July 17, 2001 3 Modify the installation options as needed. 3a Double-click the configuration option that you want to modify in the Installation options list box. 3b In the property pages, set the parameters and then click OK. The values that you set appear in the right list box.
PAGE 456

Manual 99a 38 July 17, 2001 Using DHCP If a DHCP server is set up on your network, the DHCP server can inform Novell Client of network-specific configuration information. You can easily configure Novell DHCP servers (NetWare 5 and later) to distribute this information to the clients. See the server configuration documentation for your NetWare product.
PAGE 457

Manual 44 Novell Client for Windows Novell Client for Windows 103-000159-001 December 7, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 458

Manual 4 99a July 17, 2001 38 Managing Novell Client Managing Novell® ClientTM requires that you manage users’ network connections, passwords, rights and other security issues, etc. All of these features are available from the Novell Client desktop. Common Networking Tasks Novell Client software is integrated with Windows. Features are integrated into standard Windows interfaces such as My Computer, Network Neighborhood, Control Panel, and the N icon in the system tray.
PAGE 459

Manual 99a 38 July 17, 2001 File rights apply only to the file that they are assigned to. The rights can be inherited from the folder that contains the file. Folder rights apply not only to the folder but also to the files and folders it contains. Checking File or Folder Rights 1 In Windows Explorer or Network Neighborhood, right-click the file that you want to check. 2 Click Properties > NetWare Rights. 3 In the Trustees box, click the user account.
PAGE 460

Manual 99a 38 July 17, 2001 This check box is available only if you’re viewing the NetWare rights for multiple files or folders. Additionally, at least one of the files or folders must have at least one trustee assignment. The trustees and rights shown are the combined trustees and rights for all the files. 5 Check or uncheck the check box. If you check Combine Multiple Trustees, the trustee assignments that are shown will apply to all selected files after you click OK or Apply. 6 Click OK.
PAGE 461

Manual 99a 38 July 17, 2001 AutoAdminLogon Options This section lists the options that you can choose from when setting AutoAdminLogon. To set the options, use the procedure in “Setting the AutoAdminLogon Options” on page 50. Additional information on AutoaAdminLogon may also be available in Technical Information Document # 10052847 on the Novell Technical Support Web site (www.support.novell.com).
PAGE 462

Manual 99a July 17, 2001 38 does not have to type this information. For more information, see “Setting Up Location Profiles” on page 36. NOTE: The NT Credential information in the Location Profile will not be used. The NT user information in the registry will be used instead.
PAGE 463

Manual 99a 38 July 17, 2001 AutoAdminLogon for NetWare under Terminal Server Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ WindowsNT\CurrentVersion\Winlogon Key: HKEY_LOCAL_MACHINE\SOFTWARE\Novell\ Login AutoAdminLogon=1 DefaultLocationProfile=Name of the Location Profile that contains the information about the Novell User to log in to the NetWare network such as Username, Tree, Context, Server, etc.
PAGE 464

Manual 99a 38 July 17, 2001 If the primary connection’s password expires when running NetWare Login from the icon, the user will be given the chance to synchronize all NetWare and NT passwords. Make sure that users do not synchronize the NT password, because NetWare Login does not update the Registry setting for AutoAdminLogon. Uninstalling Novell Client You can uninstall the Novell Client by using the uninstall utility or by selecting Remove in Network Properties.
PAGE 465

Manual 52 Novell Client for Windows Novell Client for Windows 103-000159-001 December 7, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 466

Manual 5 99a 38 July 17, 2001 Printing to a Network Printer Printer setup can be automated so that users’ workstations attach to the network printers they use each time users log in to the network. Users can use the network printers without having to manually connecting to the printer every time they want to print. After connecting to a network printer, users can select the printer from any application that they are using. See the application’s documentation for information on using printers.
PAGE 467

Manual 99a 38 July 17, 2001 Setting Up Network Printing 1 Click Start > Settings > Printers. 2 Double-click Add Printer. 3 Click Network Printer Server > Next. 4 Select a printer you want to use from the Shared Printers box. For NetWare 4 or later (NDS®) networks, double-click Novell Directory Services® and find the context for the printer. Then select a Printer object from the list. For NetWare 3.x and bindery networks, double-click NetWare Servers.
PAGE 468

Manual 99a 38 July 17, 2001 3 Enter the correct information in the dialog box. 4 Click Settings. These settings apply only to printer ports that are captured from Windows. Printer ports that are captured in a login script or from the command line do not use these settings. These settings do not apply to printers that appear in the Windows Printers folder. Changing the printer settings for a specific captured printer port does not change the default printer settings.
PAGE 469

Manual 99a 38 July 17, 2001 Printing DBCS Characters from DOS in Windows NT/ 2000 In Windows NT and Windows 2000, the default command window runs as a 32-bit process. In order to use the existing DOS printer driver for DOSintrinsic commands, you must use a 16-bit command window. This allows DOS-intrinsic commands such as COPY, TYPE, etc., to use the print driver. The following instructions explain how to set up NT to support this.
PAGE 470

Manual 99a 38 July 17, 2001 Disabling NetWare Login Dialog Boxes Brought Up by the Print Provider If users log in to a workstation but do not log in to NetWare and they have NetWare printers installed, they will be prompted to log in to NetWare once by the QMS print provider and once by the NDPS® print provider. These login dialog boxes can be disabled if desired.
PAGE 471

Manual 99a 38 July 17, 2001 NetWare and then manually turn the printer online by opening the Printers folder, right-clicking the printer, and deselecting Print Offline. If you set HKLM\SOFTWARE\Novell\Print\Never Login\UserDialupSettings=1 the print provider sets Never Login to the dial-up connection settings and attempts to print. NOTE: This functionality is available only in Windows 95B or later.
PAGE 472

Manual A 99a 38 July 17, 2001 Login Script Commands and Variables This appendix lists login script commands alphabetically and by the type of tasks the commands perform. It also contains a list of identifier variables used in login scripts. Before implementing any commands or variables, make sure you understand basic login script conventions. See “Login Script Conventions” on page 59 and “Using Identifier Variables” on page 62. NOTE: Commands that work only on DOS or Windows 3.
PAGE 473

Manual 99a 38 July 17, 2001 Convention Explanation Characters per line Maximum 512 characters per line, including any variables after they are replaced by their values; 78 characters per line (common screen width) is recommended for readability. Punctuation and symbols Type all symbols (#, %, ", _) and punctuation exactly as shown in examples and syntax. Commands per line Use one command per line. Start each command on a new line; press Enter to end each command and start a new command.
PAGE 474

Manual 99a 38 July 17, 2001 Convention Explanation NDS Attribute Values Any NDS® attribute value can be read from a login script, including extended names. The syntax for accessing NDS attributes is identical to common script variables with a few exceptions: The NDS attribute must be at the end of the string. If multiple variables are required, they must be in separate strings. You must use the actual NDS attribute value names. You cannot use localized names or nicknames.
PAGE 475

Manual 99a 38 July 17, 2001 Using Identifier Variables Many login script commands allow you to take advantage of identifier variables to make login scripts more efficient and flexible. Use identifier variables to enter a variable (such as LAST_NAME) rather than a specific name (such as Smith) in a login script command. When the login script executes, it substitutes real values for the identifier variables. By using the variable, you can make the same login script command applicable to multiple users.
PAGE 476

Manual 99a 38 July 17, 2001 The following table lists the identifier variables. Category Identifier Variable Function Date DAY Day number (01 through 31) DAY_OF_WEEK Day of week (Monday, Tuesday, etc.) MONTH Month number (01 through 12) MONTH_NAME Month name (January, February, etc.) NDAY_OF_WEEK Weekday number (1 through 7; 1=Sunday) SHORT_YEAR Last two digits of year (99, 00, 01) YEAR All four digits of year (1999, 2000, 2001) AM_PM a.m. or p.m.
PAGE 477

Manual 99a 38 Category Identifier Variable Function User (cont’d.
PAGE 478

Manual 99a 38 July 17, 2001 Category Identifier Variable Function DOS Environment Any DOS environment variable can be used in angle brackets. To use a DOS environment variable in MAP, COMSPEC, and FIRE PHASERS commands, add a percent sign (%) in front of the variable.
PAGE 479

Manual 99a 38 July 17, 2001 name. The remaining variables change, depending on what the user types when executing the login utility. The %n variables must precede all command line options. The “SHIFT” on page 86 login script command allows you to change the order in which these %n variables are substituted. Login Scripts Commands by Task This list identifies which specific login script commands to use, depending on what you need your login scripts to accomplish.
PAGE 480

Manual 99a 38 July 17, 2001 Workstation Environment SET (page 84) SET_TIME (page 86) Text File Usage @ (page 68) # (page 67) DISPLAY (page 71) EXIT (page 72) FDISPLAY (page 72) TERM (page 88) WRITE (page 90) Other LASTLOGINTIME (page 80) REMARK (page 83) # Use the # command to execute a program that is external to the login script. The # command executes an external program and waits until it is finished running before continuing with other login script commands.
PAGE 481

Manual 99a 38 July 17, 2001 Command Format # [path] filename [parameter] Replace path with a drive letter or, if you have specified NOSWAP on the command line or in the login script, you can replace variable with a full directory path beginning with the NetWare volume name. Replace filename with an executable file (files that end in .EXE, .COM, or .BAT, for example). It isn’t necessary to include the extension, but doing so can speed up the execution of the external program.
PAGE 482

Manual 99a 38 July 17, 2001 The executable file cannot be found Insufficient workstation memory is available to load the file Command Format @ [path] filename [parameter] Replace path with a drive letter. Replace filename with an executable file (files that end in .EXE, .COM, or .BAT, for example). Do not include the extension. Replace parameter with any parameters that must accompany the executable file.
PAGE 483

Manual 99a 38 July 17, 2001 BREAK Use BREAK ON to allow the user to terminate execution of the login script. The default is BREAK OFF. If BREAK ON is included in a login script, the user can press Ctrl+C or Ctrl+Break to abort the normal execution of the login script. NOTE: When the BREAK option is ON, type-ahead keyboard input is not saved to the buffer. Command Format BREAK ON|OFF CONTEXT Use CONTEXT to set a user’s current context in the NDS tree.
PAGE 484

Manual 99a 38 July 17, 2001 DISPLAY Use DISPLAY to show the contents of a text file when the user logs in. When you use DISPLAY, all characters in the file, including any printer and word processing codes, appear. This command works best with an ASCII file. To display only the text and suppress codes, use “FDISPLAY” on page 72. NOTE: If the given path does not exist or if the file is not found, no error message appears on the screen when the user logs in.
PAGE 485

Manual 99a 38 July 17, 2001 Instead of specifying a drive letter such as F: or G:, you can use an asterisk followed by a number n to represent the nth network drive (for example, *3). This allows drive letters to reorder themselves automatically if previous drive mappings are deleted or added. Command Format DRIVE [drive |*n] Replace drive with a local or network drive letter, or replace n with a drive number. The use of either is dependent on their already being assigned within the login script.
PAGE 486

Manual 99a 38 July 17, 2001 NOTE: If the given path does not exist or if the file is not found, no error message appears on the screen when the user logs in. Command Format FDISPLAY [path] filename Replace path with either a drive letter or a full directory path beginning with the NetWare volume name. Replace filename with the complete name (including the extension) of the file that you want to display. Examples Suppose you put messages in a file called SYSNEWS.
PAGE 487

Manual 99a 38 July 17, 2001 Examples The following line executes the phaser sound four times upon login: FIRE 4 The following line executes the rifle sound three times upon login: FIRE 3 RIFLE.WAV To use a variable as the number of times to fire, use % before the variable, as follows: FIRE %variable For more information about using variables, see “Using Identifier Variables” on page 62. GOTO Use GOTO to execute a portion of the login script out of the regular sequence.
PAGE 488

Manual 99a 38 July 17, 2001 The GOTO command looks at the value of (a DOS environment variable). If the value of is less than 9, then increments by 1 and GOTO loops back to the AGAIN label. When gains the value of 9, the IF...THEN test becomes false, the GOTO is ignored, and the script continues normally. IF...THEN Use IF...THEN to perform an action only under certain conditions.
PAGE 489

Manual 99a 38 July 17, 2001 IF...THEN statements can be nested (up to 10 levels). However, GOTO should not be used in a nested IF...THEN statement to enter or exit from the body of an IF...THEN statement. If your IF...THEN statement consists of only one line, you do not need to include END even if that line wraps. If your IF...THEN statement must be on more than one line (for example, if you used ELSE or WRITE, which must be on separate lines), you must include END.
PAGE 490

Manual 99a 38 July 17, 2001 The following lines mean “If the hour (on a 24-hour scale) is greater than or equal to 12, then write ‘afternoon’”: IF VALUE HOUR24>="12" THEN WRITE "afternoon" END The following command executes the CAPTURE utility on the fourth day of the week (Wednesday): IF NDAY_OF_WEEK="4" THEN #CAPTURE Q=FAST_Q NB TI=10 NFF END The following example shows nested IF...THEN statements.
PAGE 491

Manual 99a 38 July 17, 2001 INCLUDE Use INCLUDE to execute independent files or another object’s login script as a part of the login script currently being processed. These subscripts can be text files that contain valid login script commands (any of the commands explained in this appendix) or login scripts that belong to a different object you have rights to. Text files that contain login script commands, as well as other objects’ login scripts, can be used as subscripts.
PAGE 492

Manual 99a 38 July 17, 2001 Examples To execute a text file called SCRIPT.NEW (located in volume VOL1) as a subscript, add the following line to your main login script: INCLUDE VOL1:ADMIN\USERS\SCRIPT.NEW Suppose you are creating a container login script for all users under the Organizational Unit object SALES_LA. You recently created a container login script for users under the Organizational Unit object SALES_PV.
PAGE 493

Manual 99a 38 July 17, 2001 LASTLOGINTIME Use LASTLOGINTIME to display the last time the user logged in. If you include this command in the login script, the time of the last login is displayed on the workstation screen. Command Format LASTLOGINTIME MAP Use MAP to map drives and search drives to network directories or to map to NDS objects such as cluster-enabled volumes.
PAGE 494

Manual 99a 38 July 17, 2001 Command Format MAP [[options]|[parameters][drive:=path] Replace drive with any valid network drive letter, local drive letter, or search drive number. Replace path with either a drive letter, a full directory path, a Directory Map object, or an NDS object such as a cluster-enabled volume.
PAGE 495

Manual 99a 38 July 17, 2001 The Windows NT/2000 native environment forces a map root on all drives. To prevent a forced map root in a Windows NT/2000 environment, set the MAP ROOT OFF = 1 environment variable. All drives are then mapped as specified, and only explicit map root drives are rooted. C (CHANGE) changes a search drive mapping to a regular mapping or a regular mapping to a search drive mapping.
PAGE 496

Manual 99a 38 July 17, 2001 Command Format PAUSE PROFILE Use PROFILE in a container script to set or override a user’s assigned or command line-specified profile script. This is useful when defining a group profile.
PAGE 497

Manual 99a 38 July 17, 2001 ; [text] Replace text with the comment you want to include in the login script. Example The following are examples of explanatory text that you might use with the REMARK command and its variants: * This is Richard’s login script ; Mapped network drives follow: REM The next mapping is a fake root. REMARK This login script is for new users. SCRIPT_SERVER NetWare 2 and NetWare 3 users can use SCRIPT_SERVER to set a home server where the bindery login script is read from.
PAGE 498

Manual 99a 38 July 17, 2001 This command does not work in a login script if the DOS workstation’s environment is too small. In this case, you should set the environment size in the CONFIG.SYS file. After you use the SET command to set a value for an environment variable, you can use that variable in other login script commands. To include an environment variable as an identifier variable in a command, enclose the name of the variable in angle brackets (for example, ).
PAGE 499

Manual 99a 38 July 17, 2001 For example, the following line displays My path is G:\REPORTS\DAILY: WRITE "My path is ";path To include an environment variable in a MAP command, precede the variable with a percent sign (%). For example, you could include the following lines in a login script to set and map a drive to the variable NWS: SET NWS="C:\XYZ" MAP S16:=% SET_TIME Use SET_TIME to set the workstation time equal to the time on the NetWare server that the workstation first connects to.
PAGE 500

Manual 99a 38 July 17, 2001 Command Format SHIFT [n] Replace n with the number of places that you want the variable to shift. The default is SHIFT 1. Examples When Mary logs in, she wants to access her word processing program, change the way it is set up, and map a drive to her work directory called ACCNTS. Mary also has a command in her login script to map a drive to her DATABASE directory, but she does not need it today.
PAGE 501

Manual 99a 38 July 17, 2001 %2 now becomes ACCNTS. Upon executing the loop, the login script maps a drive to the ACCNTS directory. Mary could also change the order of her login command without affecting the way her work environment is set up, as follows: LOGIN MARY ACCNTS WP The parameters in this login command are given the following values: %0=FS1 %1=MARY %2=ACCNTS %3=WP In this case, Mary’s login script looks for %2, which is now ACCNTS. The login script maps a drive to the ACCNTS directory.
PAGE 502

Manual 99a 38 July 17, 2001 Command Format TERM nnn Replace nnn with an error level. Any error level between 000 and 999 is valid. Example If you want the login script to exit and return an error code of 718, you can add the following statement to the login script: TERM 718 TREE The TREE command can be used only with clients that support multiple NDS tree attachments. Use TREE to attach to another NDS tree within the network and to access its resources.
PAGE 503

Manual 99a 38 July 17, 2001 IMPORTANT: Use caution when including passwords in a login script. It is more secure to eliminate the password. Then, at the point in the login script where the TREE command is executed, the user is prompted for the password. Example To attach the user with the complete name MRICHARD.ACME (whose password is BUTTERFLY) to an NDS tree named CORP, add the following line to the login script: tree corp/.mrichard.
PAGE 504

Manual 99a 38 July 17, 2001 Text strings can include the following special characters: Character Meaning \r Causes a carriage return \n Starts a new line of text \" Displays a quotation mark on the screen \7 Makes a beep sound In addition to the semicolon, you can use other operators to form compound strings (in other words, to join text and identifier variables into one command).
PAGE 505

Manual 99a 38 July 17, 2001 For example, either of the following lines displays Hello, Smith when user Bob Smith logs in: WRITE "Hello, ";%LAST_NAME WRITE "Hello, %LAST_NAME" To make a beep sound occur while the phrase Good morning appears on the screen, add the following line to the login script: WRITE "Good %GREETING_TIME \7" 92 Novell Client for Windows Novell Client for Windows 103-000159-001 December 7, 2001 Novell Confidential
PAGE 506

Manual B 99a 38 July 17, 2001 Sample Login Scripts You can create login scripts from these sample login scripts using NetWare® Administrator. Using a sample login script can help reduce syntax errors, reducing the time it takes you to create your login scripts. For more information on how to create login scripts, see “Creating Login Scripts from a Sample or Existing Login Script” on page 34.
PAGE 507

Manual 99a 38 July 17, 2001 IF OS = "WINNT" THEN MAP P:=SYS:USERS\%LOGIN_NAME\WINNT MAP INS S16:=SYS:APPS\WINAPPS\WINNT SET TEMP = "P:\USERS\%LOGIN_NAME\WINNT\TEMP" END MAP MAP MAP MAP INS S16:=VOL1:APPL\LOTUS INS S16:=SYS:EMAIL M:=VOL1:SHARED N:=VOL1:MODEMS MAP O=SYS:DOC IF MEMBER OF "MANAGERS" THEN MAP *3:=VOL1:PROJECTS\REPORTS END Sample Profile Login Script If you have groups of users with identical login script needs, you can create a Profile object and then create a login script for it.
PAGE 508

Manual 99a 38 July 17, 2001 Sample User Login Script The following sample login script is an example of a login script created for user Mary. The user login script executes after the container and profile login scripts have executed. In addition, a user login script prevents the default login script from executing for this specific user. Therefore, you should consider whether any commands in the default login script are necessary for setting the user’s environment.
PAGE 509

Manual 96 Novell Client for Windows Novell Client for Windows 103-000159-001 December 7, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 510

Manual C 99a July 17, 2001 38 Troubleshooting Issues This appendix provides troubleshooting information for known issues. HINT: If you do not find a solution to your issue here, check the Readme file that accompanied the software as well as the Novell® Support Connection® information database (http://www.support.novell.com). Windows 95/98 Issues The following issues will help you troubleshoot Novell ClientTM for Windows 95/98. For additional issues, check the Novell Client Readme.
PAGE 511

Manual 99a 38 July 17, 2001 located in TID 2952441. This update addresses an issue in which a file opened once by different threads (one open in each thread) in an application and then closed leaves an instance of the file open, even after exiting the application. This problem could cause the server to run out of memory or hang. IP with IPX Compatibility Dependency When using the IP with IPXTM Compatibility client configuration, make sure that the TCP/IP stack has been configured with a TCP/IP gateway.
PAGE 512

Manual 99a July 17, 2001 38 Installing ZENWorks for Desktops 2 Remote Management and Novell Client Software Version 3.31 on a New Workstation If you have new workstations that require ZENworks for Desktops 2 Remote Management and Novell Client for Windows 95/98 version 3.31, do one of the following. Install Remote Management Using an Application Object 1 Install Novell Client for Windows 95/98 version 3.31 without selecting Remote Management.
PAGE 513

Manual 99a 38 July 17, 2001 Login Restrictions Set for IPX/SPX Prevent User from Logging In Symptom: Login restrictions are set for IPX/SPXTM and the node address. When the administrative workstation is reset, the new client files are automatically updated and the reboot prompt is displayed. After restarting, the workstations that are placed in the restriction list as being able to log in as Admin and which now have the new client cannot log in and no administration of the server can be done.
PAGE 514

Manual 99a 38 July 17, 2001 By default, the client uses DHCP to locate a Discovery Agent. (This assumes that a Discovery Agent is configured on the dial-up host network.) The client uses an NWHOST file, if present, which contains server names and their addresses. This might be a preferred way to run your client. (The file is created in the NOVELL\CLIENT32 directory on the workstation.) The client also supports DNS names.
PAGE 515

Manual 99a 38 July 17, 2001 Printing Do Not Configure a Local NPRINTER with Interupts Do not configure a local NPRINTER with interrupts. Use the default Polled Mode instead. Windows NT/2000/XP Issues The following issues will help you troubleshoot Novell Client for Windows NT/2000 and Novell Client for Windows XP. For additional issues, check the Novell Client Readme.
PAGE 516

Manual 99a 38 July 17, 2001 Update Required on NetWare 4.11 and NetWare 4.2 Servers NetWare 4.11 and NetWare 4.2 servers require an update on the server prior to the installation of this Client. The server update information is located in TID 2952441. This update addresses an issue in which a file opened once by different threads (one open in each thread) in an application and then closed leaves an instance of the file open, even after exiting the application.
PAGE 517

Manual 99a 38 July 17, 2001 Login MFC42.DLL Error Novell Client runs with MFC42.DLL version 4.21.7022 or later. MFC42.DLL version 6.00.8267.0 is installed when you install Novell Client. If an older version is installed over the version installed by Novell Client, the client login fails with an error message similar to the following: The ordinal 6453 could not be located in the dynamic link library MFC42.DLL. The actual message might vary, depending on the version of MFC42.DLL you are using.
PAGE 518

Manual 99a July 17, 2001 38 Login Script CAPTURE Execution in a Login Script If you use a login script that contains an external CAPTURE command using CAPTURE.EXE, the screen might go blank with a blinking cursor in the upper-left corner. The capture eventually executes and the screen returns to normal. This happens if Windows NT or Windows 2000 is set to “full screen” when the CAPTURE command is executed from the login script.
PAGE 519

Manual 99a 38 July 17, 2001 MAP.EXE The MAP.EXE utility might function improperly if the computer’s DOS environment size is too small. If you encounter problems while running MAP.EXE, increase the DOS environment size by adding or editing the SHELL= line in the WINNT\SYSTEM32\CONFIG.NT file. For example: SHELL=%SYSTEMROOT%\SYSTEM32\COMMAND.COM /E:2048 MAP.EXE was not designed as a Windows NT/2000/XP executable and, therefore, does not recognize drives mapped to NT servers as network drives.
PAGE 520

Manual 99a 38 July 17, 2001 You can turn off the default by adding SET MAPROOTOFF="1" as the first line in the login script. This will globally force all NT workstations using the login script to not map root drives. Or, you can perform the following procedure on a local workstation: 1 Right-click My Computer. 2 Click Properties > Environment. 3 Enter MAPROOTOFF as a variable. 4 Set the value of the MAPROOTOFF variable to 1. 5 Click Select.
PAGE 521

Manual 99a 38 July 17, 2001 Printing Issues NDPS and NetWare 5 You might experience difficulties printing through NDPS if your network connection is dropped and later auto-reconnects. You could receive the following error messages: Error writing to : Space to store the file waiting to be printed is not available on the server. A write fault occurred while printing. To resolve this problem, you must download and install NetWare 5 Support Pack 2 or later.
PAGE 522

Manual 99a 38 July 17, 2001 IPX Compatibility Requirements for RAS Client IPX Compatibility Mode requires the services of SLP. For more information, see “SLP Requirements for Server Name Resolution from RAS Clients” on page 108. Before installing the Novell IP Client with IPX Compatibility support, make sure that the RAS Client is configured to perform only IP networking over the RAS connections.
PAGE 523

Manual 99a 38 July 17, 2001 IPX Compatibility Network Number over the LAN adapter but configure a different network number for IPX Compatibility to use over the RAS connection (WAN adapter). You should be aware that nodes utilizing IPX Compatibility on the same network should be configured to use the same network number in order to directly communicate when using Client/Server IPX applications.
PAGE 524

Manual 99a 38 July 17, 2001 Software Compatibility Issues Microsoft SMB Client Support over IPX Novell Client for Windows NT/2000/XP coexists with the Microsoft SMB Client over IPX networks. The Microsoft SMB Client utilizes NetBIOS when communicating over IPX, which increases the utilization of your network.
PAGE 525

Manual 112 Novell Client for Windows Novell Client for Windows 103-000159-001 December 7, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 526

Novell Licensing Services Administration Guide Novell NetWare 6 ® www.novell.
PAGE 527

Manual 99a June 14, 2001 37 Contents Overview 7 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1 Understanding Novell Licensing Services 9 Key NLS Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Examples of NLS Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 How NLS Works . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 528

Manual 6 99a 37 Novell Licensing Services Administration Guide Novell Licensing Services Administration Guide 103-000138-001 August 30, 2001 Novell Confidential June 14, 2001
PAGE 529

Manual 99a 38 July 17, 2001 Overview Novell® Licensing Services (NLS) that ships with NetWare® 6 supports the User Access License (UAL) model. User objects gain access to network services by connecting to the network instead of to servers. These User objects receive a permanent license unit that allows them to access network services at any time and from any workstation attached to the network. For information on NLS concepts and how NLS works, see “Understanding Novell Licensing Services” on page 9.
PAGE 530

Manual 99a 38 July 17, 2001 This documentation does not cover information about policy managers and license certificates for specific products. Refer to product-specific documentation for that information. Documentation Conventions In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. Also, a trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.
PAGE 531

Manual 1 99a 38 July 17, 2001 Understanding Novell Licensing Services Since NLS is integrated with eDirectoryTM, you need to be familiar with the basics of eDirectory, especially eDirectory objects, partitions, and replicas of partitions. “Key NLS Terms” on page 9 “How NLS Works” on page 17 Key NLS Terms Understanding the following terms will help you maintain licensing and license units on your network.
PAGE 532

Manual 99a 38 July 17, 2001 An license service provider provides the actual licensing service. It handles requests from NLS clients and maintains the license certificates, which are stored within eDirectory. When you install NetWare and licensing certificates, NLS Installs the license service provider software on the server Creates an License Service Provider object (NLS_LSP_servername) in the eDirectory tree You can also use NetWare Deployment Manager to accomplish these two tasks.
PAGE 533

Manual 99a 38 July 17, 2001 NLS client—Software that requests licensing services from license service providers. An NLS client runs on client workstations and on NetWare servers. (The client can run on either a workstation or a server or on both the workstation and the server.) This software supports 32-bit Windows* and NetWare Loadable ModuleTM (NLMTM) platforms.
PAGE 534

Manual 99a 38 July 17, 2001 License Certificate object—An object in eDirectory; represents a license certificate. License certificates correspond to the printed license statement that is typically included in the packaging for software products. The icon for a License Certificate object looks like a single sheet of paper representing a license certificate.
PAGE 535

Manual 99a 38 July 17, 2001 Because multiple license certificates can exist in an envelope, envelopes allow you to install several license certificates at the same time. Envelopes can contain an embedded activation key for license certificates. A sample envelope file is 4234171D.NLF. License Container object—An object in eDirectory; contains one or more License Certificate objects. A License Container object is a special container object in eDirectory.
PAGE 536

Manual 99a 38 July 17, 2001 Policy—An electronic representation of a term or condition in your license agreement. Policies are contained in license certificates. For example, a certificate for a company could include the following tags for policies: Each license unit is consumable. Each license unit allows nodal reuse. (A user can use it multiple times from different workstations.) The certificate does not require an license service provider assignment.
PAGE 537

Manual 99a 38 July 17, 2001 Each NLS-enabled product has its own policy manager. The policy manager for NetWare differs from the policy manager for BorderManager. Both of these policy managers differ from the policy manager for a third-party software manufacture’s application. Because each application or service supports a different policy, you might have many policy managers running on a network.
PAGE 538

Manual 99a 38 July 17, 2001 NOTE: NLS is a service. The terms and conditions of your license agreement determine how the product is to be used. A soft stop policy informs users that they are out of compliance but allows them to continue using license units under certain conditions. A no stop policy ignores situations in which no license units are available. NLS keeps track of the overage by logging the noncompliance, but does not inform or warn the user.
PAGE 539

Manual 99a July 17, 2001 38 Example 3: Metering A client workstation requests an application that is not NLS-enabled. ZENworks, integrated with NLS, requests a license unit on behalf of the application. Depending on the response from NLS, Application Launcher in ZENworks chooses whether or not to load the application. Therefore, Application Launcher can be configured to request license units for applications that are not NLS-aware. How NLS Works The following figure illustrates how NLS Works.
PAGE 540

Manual 99a 38 July 17, 2001 In NetWare, for example, the NLS client communicates with the license service provider on that server. 3. The license service provider examines the request and determines whether it can fill the request. It does this by checking the eDirectory context of the requesting client for the specific information or license unit being requested. In NetWare, for example, the license service provider searches the user’s context for a NetWare license unit. 4.
PAGE 541

Manual 99a July 17, 2001 38 A License certificate B C Server D E User Begins searching here In this example, the user accesses the network from context .E.C.A. To search for a license unit, the license service provider begins its search in the user’s context—.E.C.A The license service provider searches up the tree to context A and finds an available license unit. 5. The license service provider returns status to the client library.
PAGE 542

Manual 20 99a 38 Novell Licensing Services Administration Guide Novell Licensing Services Administration Guide 103-000138-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 543

Manual 2 99a 38 July 17, 2001 Installing Novell Licensing Services This chapter discusses “Guidelines for Installing NLS” on page 21 “Installing NLS” on page 22 “Verifying That NLS Is Installed” on page 22 Guidelines for Installing NLS Prepare the network. If you are upgrading a server, the server should have a read/write replica of the partition where the NetWare® 6 server will be installed. Provide fault tolerance. Two servers running NLS in a partition provide fault tolerance.
PAGE 544

Manual 99a 38 July 17, 2001 NOTE: If you are running NetWare for Small Business or NetWare for Growing Business, you should install the corresponding Support Pack before upgrading to NetWare 6. Know where to install NLS. For more information, see Guidelines for Installing License Certificates in the User Access Licensing for NetWare Guide. Installing NLS When you install or upgrade to NetWare 6, NLS is automatically installed.
PAGE 545

Manual 3 99a 38 July 17, 2001 Using Novell Licensing Services You can manage NLS functionality in iManage, the Novell® browser-based management tool, to complete the following tasks: “Managing License Certificates” on page 23 “Deleting a License Certificate” on page 25 “Moving a License Certificate” on page 25 “Modifying or Deleting Server Assignments” on page 26 “Viewing Information about License Certificates and Containers” on page 26 You can still use NetWare Administrator to administer NL
PAGE 546

Manual 99a 38 July 17, 2001 If you purchase and install additional license certificates, they will also be added to the eDirectory tree as objects in the appropriate License Container object. About Envelopes An envelope is an .NLF file containing one or more license certificates. (The envelope might have just one certificate because it also contains other information associated with the product—for example, information for NISenabled installations.
PAGE 547

Manual 99a 38 July 17, 2001 4 Fill in the following fields: Location: Browse to or enter the context where you want the licenses installed. User licenses should be installed at or above the user's context. You might want to install the licenses high in the tree so that they will be available to more users. Server licenses should be installed at or above the server's context. Server Assignment: If you are installing a server base license, the Server Assignment field displays.
PAGE 548

Manual 99a 38 July 17, 2001 Assigning Licenses to a Server Each server needs a server license. You need to install a server license only if you did not install licenses during the installation process or if the server license was deleted. To install a server license certificate, follow the steps in “Installing License Certificates” on page 24. Modifying or Deleting Server Assignments 1 In iManage, click License Management > Manage License Properties.
PAGE 549

Manual 99a 38 July 17, 2001 Using SNMP You can use SNMP to find out about licensing service events on your network. About SNMP and NLS SNMP is a management interface and high-level protocol. General-purpose protocols such as IPXTM, TCP/IP, and UDP can host SNMP. NLS takes events and errors, wraps them in one of these protocols, and sends them to a management utility or console. For example, suppose you instruct SNMP to raise an event whenever a license unit is conveyed to a User object.
PAGE 550

Manual 99a 38 July 17, 2001 Three Configuration Files for SNMP NLS uses three configuration files for SNMP. The configuration files allow the various systems which provide SNMP information to tailor that information to your needs as you manage the network. All three files are installed into SYS:\ETC. SNMP.CFG lets you add descriptive strings that might be included in SNMP packets.
PAGE 551

Manual 99a 38 July 17, 2001 5 Load SNMP.NLM on a server. SNMP.NLM (the SNMP agent) provides the APIs and framework to allow SNMP to work on NetWare. SNMP.NLM traps events, generates SNMP messages about the trapped events, and sends the messages to the management console. 6 At the management console, view the SNMP messages.
PAGE 552

Manual 30 99a 38 Novell Licensing Services Administration Guide Novell Licensing Services Administration Guide 103-000138-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 553

Manual 4 99a 38 July 17, 2001 Troubleshooting Novell Licensing Services This chapter contains tips, information about system messages and error codes, and a list of Technical Information Documents. “Tips” on page 31 “Error Codes and System Messages” on page 33 “TIDs” on page 34 Tips Unable to get a server base license Problem: The server console displays “Unable to get a Server Base license.” Action: Delete and reinstall the license certificate.
PAGE 554

Manual 99a 38 July 17, 2001 Place server license certificates so that NLS servers do not have to traverse slow WAN links to access license units. Place user certificates so that NLS dos Not have to traverse WAN links when users are authenticating to the tree. Place at least one License Service Provider object in a container near the root of the tree. Also, consider loading license service provider software on servers that many or most users log in to in the eDirectory tree.
PAGE 555

Manual 99a 38 July 17, 2001 Error Codes and System Messages Many messages for Novell® Licensing Services are self-documenting; information that you need appears on-screen with the message. Additional information about error codes are provided below. Other error codes are provided in NLSLSP Messages in System Messages. Error Code C0001002 Displays Possible Problem Possible Solutions You removed and reinstalled eDirectoryTM. See TID 2941280. The Server object and [Public] don’t have enough rights.
PAGE 556

Manual 99a 38 July 17, 2001 Error Code C0001005 Diplays Possible Problem Possible Solution The license certificate requires a server assignment but doesn’t have one. Assign a server. See “Modifying or Deleting Server Assignments” on page 26. TIDs The following TIDs might help you resolve some issues relating to NLS on your network. The TIDs are available at www.support.novell.com/servlet/ knowledgebase.
PAGE 557

Novell iFolder Administration Guide Novell iFolder www.novell.com 1.
PAGE 558

Manual 99a July 17, 2001 38 Contents Contents 5 Novell iFolder Administration Guide 7 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 Welcome to Novell iFolder 9 What Is Novell iFolder? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2 Installing Novell iFolder on NetWare 5.1 Server Requirements. . . . . . . . . . . Client Workstation Requirements . . . . Browser Requirements . . . . . . . . . .
PAGE 559

Manual Using the Server Management Console Removing an iFolder Account . . . . Restoring a User’s Folder . . . . . . Changing LDAP Settings . . . . . . Optimizing Your iFolder Server . . . . . 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99a July 17, 2001 38 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Novell iFolder Administration Guide Novell iFolder Administration Guide 103-000132-001 November 21, 2001 Novell Confidential . . . . .
PAGE 560

Manual 99a 38 July 17, 2001 Novell iFolder Administration Guide Novell® iFolderTM 1.0 is a file storage and management solution to the universal problems associated with storing and retrieving data. With iFolder you have the latest version of your data when you need it and where you need it from any computer that you regularly use. And if you are not at a computer that you regularly use, you can still access and manage your files if you have an Internet connection and a Java-enabled browser.
PAGE 561

Manual 8 99a Novell iFolder Administration Guide Novell iFolder Administration Guide 103-000132-001 November 21, 2001 Novell Confidential 38 July 17, 2001
PAGE 562

Manual 1 99a July 17, 2001 38 Welcome to Novell iFolder Novell® iFolderTM gives you automatic, secure, and transparent synchronization of files between your hard drive and the iFolder server, which results in easy access to personal files anywhere, anytime. Being able to access your files from any computer from any location eliminates the editing mistakes and menial updating tasks that frequently occur when your local machine is not accessible from different access points.
PAGE 563

Manual 99a 38 July 17, 2001 What Is Novell iFolder? There are three components to Novell iFolder: iFolder server software iFolder runs on NetWare® 5.1, NetWare 6, Windows NT* 4.0, and Windows 2000 servers. Once you have installed the iFolder server software on your server, your users can install the iFolder client in order to access their iFolder files, and you can access the Server Management Console and the default iFolder Web site to manage your iFolder user accounts.
PAGE 564

Manual 99a 38 July 17, 2001 need to have the application installed on your workstation in order to access that file. Any changes that are made in this directory, from any workstation, are uploaded to the iFolder server. The frequency of the uploading can be determined by either the user or the network administrator. The iFolder icon appears in the system tray of your workstation.
PAGE 565

Manual 99a 38 July 17, 2001 If you are installing Novell iFolder on Windows NT 4.0 or Windows 2000, follow the instructions in Chapter 4, “Installing Novell iFolder on Windows NT 4.0 or Windows 2000,” on page 25. If you are installing Novell iFolder on Novell Cluster Services, follow the instructions in Chapter 5, “Installing Novell iFolder on Novell Cluster Services,” on page 33.
PAGE 566

Manual 2 99a 38 July 17, 2001 Installing Novell iFolder on NetWare 5.1 Before you begin the iFolderTM installation, make sure that you have met the following iFolder server, client, and browser requirements. Server Requirements NetWare® 5.1 server with Support Pack 3 installed. NetWare Support Packs are available at the Consolidated Support Pack Home Page (http://support.novell.com/csp/csplist.html). An LDAP v3 enabled directory, such as NDS® eDirectoryTM 8.5.
PAGE 567

Manual 99a 38 July 17, 2001 Client Workstation Requirements Novell® iFolder is compatible with Windows 95, 98, 2000, NT, and ME workstations. The iFolder client is very small and will take only about 2 MB of free space on your workstation. IMPORTANT: If you are installing the iFolder client on a Windows 95 workstation, you must have the Winsock 2 update from Microsoft installed. This update can be downloaded from the Microsoft Web site (http://www.microsoft.
PAGE 568

Manual 99a 38 July 17, 2001 5 Enter your username and the name of your company, and then click Next. 6 Browse to the drive letter that you mapped in Step 1 and then click Next. HINT: In order to install Novell iFolder on multiple servers from the same workstation, you must delete the directory that represents your last installation. To do this, go to C:\Program Files\Installshield Installation Information.
PAGE 569

Manual 99a 38 July 17, 2001 This will be the path to the SYS:Public directory where you copied the ROOTCERT.DER prior to the installation. For more information, see “Server Requirements” on page 13. 12 Enter the LDAP login DN context. This is the context of the container where your User objects are located. iFolder allows you to enter multiple contexts. After each context, insert a semicolon. Do not put any spaces between the contexts.
PAGE 570

Manual 99a 38 July 17, 2001 16 (Conditional) Create an LDAP proxy user. 16a Launch ConsoleOne. 16b Create a user without a password. 16c Right-click your Tree object and then click Properties > NDS Rights > Add Trustee. 16d Select the User object you just created and then click OK. 16e When the Rights Assigned to Selected Object dialog box appears, click Add Property. 16f Check the Show All Properties check box, select the CN property from the list, and then click OK. 16g Click OK > Apply > Close.
PAGE 571

Manual 99a 38 July 17, 2001 admin to have rights to administer the Server Management Console, you would enter admin;jsmith. 21 If prompted, enter the IP address or the DNS name of your server and then click Next. 22 Click Finish to complete the installation. 23 Do one of the following: If you are using only one IP address, to start Novell iFolder you can reboot your server (this will run the edited AUTOEXEC.
PAGE 572

Manual 3 99a 38 July 17, 2001 Installing Novell iFolder on NetWare 6 Before you begin the iFolderTM installation, make sure that you have met the following iFolder server, client, and browser requirements. Server Requirements 10 MB of free space on the SYS: volume where you plan to install iFolder. Client Workstation Requirements Novell® iFolder is compatible with Windows 95, 98, 2000, NT, and ME workstations.
PAGE 573

Manual 99a 38 July 17, 2001 Installing Novell iFolder on NetWare 6 1 Do a Custom install of NetWare 6. For instructions on installing NetWare 6, see the NetWare 6 Overview and Installation Guide. 2 During the NetWare 6 installation, select iFolder as one of the products that you want to install. 3 (Conditional) If prompted, resolve port conflicts or assign secondary IP addresses. If you are installing iFolder with no other Web products, you will not see this screen.
PAGE 574

Manual 99a 38 July 17, 2001 6 (Optional) Continue with the NetWare 6 installation until you get to the Summary screen at the end of the NetWare 6 installation. The Summary screen lists all the products that you have selected to install with NetWare 6. 7 At the Summary screen, click NetWare 6 > iFolder > Configure > Primary LDAP Settings. 8 Enter the following LDAP information for your primary LDAP server: LDAP Host Enter the IP address of your LDAP server in the LDAP Host field.
PAGE 575

Manual 99a 38 July 17, 2001 9 (Conditional) If you have a secondary LDAP server, click Secondary LDAP Settings. 10 Enter the settings for the secondary LDAP server. Fill in this information only if you have two LDAP directories that contain usernames that need iFolder accounts.
PAGE 576

Manual 99a 38 July 17, 2001 Assign the CN Property to the Public Object IMPORTANT: Any rights assigned to the Public object are automatically inherited by all other objects in the Novell® eDirectoryTM tree. You might not want to assign the CN property to the Public object if these rights will cause a security risk.
PAGE 577

Manual 99a 38 July 17, 2001 Novell iFolder is now installed and running on your NetWare 6 server. To learn more about Novell iFolder, go to Chapter 6, “Using Novell iFolder,” on page 37. LDAP over SSL If your LDAP server is not the same server as your iFolder server, and you want LDAP over SSL, you need to export your LDAP server’s trusted root certificate and then copy it to your iFolder server. This certificate (ROOTCERT.DER) should be located in your LDAP server’s SYS:PUBLIC directory.
PAGE 578

Manual 4 99a 38 July 17, 2001 Installing Novell iFolder on Windows NT 4.0 or Windows 2000 Before you begin the iFolderTM installation, make sure that you have met the following iFolder server, client, and browser requirements. Server Requirements A Windows NT 4.0 server with Service Pack 6A or later installed or a Windows 2000 server with Service Pack 1 installed. Microsoft Service Packs are available at the Microsoft Web site (http:// updates.zdnet.com/products/pr_13616.htm).
PAGE 579

Manual 99a 38 July 17, 2001 You can do this in either of two ways: 1) If you have your own certificate server, such as Novell Certificate Server, then you can get a certificate from your server, or 2) You can go to a certificate vendor, such as Entrust* or VeriSign*, and purchase a certificate from them. For more information on installing and creating SSL certificates for IIS 4, go to the Microsoft Product Support Services Web site (http:// support.microsoft.com/support/kb/articles/Q228/9/91.ASP).
PAGE 580

Manual 99a 38 July 17, 2001 2 Locate the iFolder software that you downloaded and double-click the iFolder IIS server executable (IISiFolderServer.EXE). 3 Read the Welcome screen and click Next. 4 Click Yes to accept the licensing agreement. 5 Enter your username and the name of your company, and then click Next. 6 Browse to the location where you want iFolder to install the setup files and then click Next. 7 Enter the IP address of your LDAP server in the LDAP host field.
PAGE 581

Manual 99a 38 July 17, 2001 If you are assigning the CN property to the Public object, continue with the next step. Any rights assigned to the Public object are automatically inherited by all other objects in the NDS tree. You might not want to assign the CN property to the Public object if these rights will cause a security risk.
PAGE 582

Manual 99a 38 July 17, 2001 15g Double-click the user so that the name appears in the Proxy Username field. 15h Click Apply > OK. 16 Click Next in the iFolder setup. 17 (Conditional) If you are using a secondary LDAP server, enter the LDAP information for that server. Fill in this information only if you have two LDAP directories that contain usernames that need iFolder accounts.
PAGE 583

Manual 99a 38 July 17, 2001 Configuring the iFolder Web Site on Windows NT 4.0 1 Launch the Internet Services Manager by clicking Start > Windows NT 4.0 Option Pack > Microsoft Internet Information Server > Internet Service Manager. 2 Right-click the Default Web Site icon and then click Properties > Home Directory. 3 Set the local path.
PAGE 584

Manual 99a 38 July 17, 2001 6 Click the Documents tab. 7 Check the Enable Default Documents check box. 8 Click the Add button. 9 Enter index.html into the text field and click OK. Novell iFolder in now installed on your Windows 2000 server. For more information about Novell iFolder, go to Chapter 6, “Using Novell iFolder,” on page 37. Installing Novell iFolder on Windows NT 4.
PAGE 585

Manual 32 99a Novell iFolder Administration Guide Novell iFolder Administration Guide 103-000132-001 November 21, 2001 Novell Confidential 38 July 17, 2001
PAGE 586

Manual 5 99a 38 July 17, 2001 Installing Novell iFolder on Novell Cluster Services Before you set up Novell® iFolderTM on Novell Cluster ServicesTM, you should already have a basic understanding of how Novell Cluster Services works. A short overview is provided in the Novell Cluster Services Overview and Installation Guide (http://www.novell.com/documentation/lg/ncs/ index.html). NOTE: Novell Clustering Services runs only on NetWare.
PAGE 587

Manual 99a 38 July 17, 2001 Post-Installation Tasks 1 Do one of the following: For NetWare 5.1 servers, create an NSS volume on your shared storage disk system, commonly referred to as a storage area network or SAN. This is the volume that will contain all your iFolder user data and accounts. The size of this volume will vary according to how many iFolder users you plan to have and the amount of data they will be storing. For more information, see NetWare Cluster Services (http:// www.novell.
PAGE 588

Manual 99a 38 July 17, 2001 For more information, see Novell Cluster Services (http:// www.novell.com/documentation/lg/ncs6p/index.html) > Installation and Setup > Setting Up Cluster Services. 3 Create a folder on the cluster-enabled volume. 4 Choose one iFolder server in the cluster and go to the SYS:Apache\iFolder\Server directory and edit the HTTPD_NW_ADDITIONS.CONF file.
PAGE 589

Manual 99a 38 July 17, 2001 Locate the ServerName parameter. By default, this parameter displays the IP address of the server. Replace this IP address with the IP address or DNS name of the cluster-enabled volume. Locate the SecureListen ipaddress "SSL CertificateIP" parameter. Change the IP address that is listed to the IP address or DNS name of the cluster-enabled volume. 8 Save your changes to the HTTPD.CONF file and then copy it to every iFolder server in the cluster.
PAGE 590

Manual 6 99a July 17, 2001 38 Using Novell iFolder This chapter covers the following three topics: “Managing Novell iFolder Accounts” on page 37 “Using the Server Management Console” on page 38 “Optimizing Your iFolder Server” on page 40 Managing Novell iFolder Accounts Once Novell® iFolderTM is installed and running on your server, your users can download and install the iFolder client.
PAGE 591

Manual 99a 38 July 17, 2001 Management Console by opening a browser and entering https:// ifolderserverip/iFolderServer/Admin. IMPORTANT: The Server Management Console URL is case sensitive. For more information, see the next section, Using the Server Management Console. Using the Conflict Bin The iFolder client has a feature called the Conflict Bin. A user will rarely need to access this option, however, it is useful for you to undestand how this feature works.
PAGE 592

Manual 99a 38 July 17, 2001 Once you are logged in, you can view and modify iFolder accounts as well as set specific policies for your iFolder clients and server. You can perform the following tasks in the Server Management Console: View general server information View and Modify LDAP settings View user account information As an administrator, you can remove a user account, change a user’s disk storage quota on the iFolder server, and set specific policies for individual users.
PAGE 593

Manual 99a 38 July 17, 2001 Restoring a User’s Folder If a user wants to recover data from a deleted or corrupted file, you can restore his folder to a secondary iFolder server and from there he can access his files. 1 At the Server Management Console, click User Accounts. 2 Roll your mouse over the user’s ID and look at the ID that appears in the bottom of your browser. 3 Restore this folder from a backup tape to a secondary iFolder server that the user can attach to and restore the files.
PAGE 594

Novell NetDrive Administration Guide Novell NetWare 6 ® www.novell.
PAGE 595

Manual 99a July 17, 2001 38 Contents Contents 5 Novell NetDrive Administration Guide 7 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 Installing Novell NetDrive Workstation Requirements . . . . . . . . . Workstation and Protocol Compatibility Application Compatibility . . . . . . . . Installing NetDrive . . . . . . . . . . . . . 2 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 596

Manual 6 99a Novell NetDrive Administration Guide Novell NetDrive Administration Guide 103-000170-001 September 4, 2001 Novell Confidential 38 July 17, 2001
PAGE 597

Manual 99a 38 July 17, 2001 Novell NetDrive Administration Guide Novell® NetDrive is an easy-to-use Internet client that lets you access your NetWare® 6 servers over standard Internet protocols, such as WebDAV and FTP. NetDrive does not rely on the Novell ClientTM in order to map network drives. Documentation Conventions In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. Also, a trademark symbol (®, TM, etc.
PAGE 598

Manual 8 99a Novell NetDrive Administration Guide Novell NetDrive Administration Guide 103-000170-001 September 4, 2001 Novell Confidential 38 July 17, 2001
PAGE 599

Manual 1 99a 38 July 17, 2001 Installing Novell NetDrive Novell® NetDrive lets you to map a network drive to any NetWare® 6 server without using Novell ClientTM software. This means that with NetDrive, you can access and modify your files from any workstation using just an Internet connection. Once a network drive is mapped, the drive letter that you assigned during the mapping appears in Windows* Explorer and functions just like those that are mapped through Novell Client.
PAGE 600

Manual 99a 38 July 17, 2001 Workstation Requirements You need only 2 MB of available space on your hard drive to install and run the NetDrive client. Workstation and Protocol Compatibility Review the following table for information on what protocols are supported with your workstation operating system. IMPORTANT: If you are installing the NetDrive client on a Windows 95 workstation, download the Winsock 2 update from Microsoft*. This update can be downloaded from the Microsoft Web site (http://www.
PAGE 601

Manual 99a 38 July 17, 2001 Installing NetDrive 1 Double-click NETDRIVE.EXE located in the NetDrive directory at the the root of the NetWare 6 Client CD. 2 Follow the installation instructions. When you click Finish on the last installation screen, Windows Explorer launches and the following shortcuts appear in an Explorer window: Help on NetDrive, NetDrive, and Uninstall NetDrive. 3 Double-click the NetDrive shortcut icon.
PAGE 602

Manual 12 99a Novell NetDrive Administration Guide Novell NetDrive Administration Guide 103-000170-001 September 4, 2001 Novell Confidential 38 July 17, 2001
PAGE 603

Manual 2 99a July 17, 2001 38 Using Novell NetDrive Once NetDrive is installed, you can perform many basic tasks within the NetWare® Main Window. Adding a Site 1 In the NetWare Main Window, click New Site. 2 Enter the name of your site and the URL for the NetWare 6 server in the appropriate fields of the New Site dialog box. If you omit the FTP or HTTP suffix from the URL, then NetDrive defaults to FTP.
PAGE 604

Manual 99a 38 July 17, 2001 Mapping a Drive Once you have created a site and clicked Finish, the name of your site and the URL of your NetWare 6 server are automatically generated in the NetDrive Main Window; however, you still need to complete the following steps before you can connect to a NetWare 6 server. 1 From the Server Type drop-down list, select the protocol that your NetWare 6 server is using, and then select the drive letter that you want to use for the mapped drive.
PAGE 605

Manual 99a 38 July 17, 2001 Copying Files To copy files, copy or cut and paste files as you normally would in Windows Explorer. To disconnect from the server, right-click the Drive icon in Explorer and click Disconnect. WARNING: Since a connection can be interrupted in the middle of a file transfer, you should always keep a backup copy of files that are transferred or modified on your server.
PAGE 606

Manual 16 99a Novell NetDrive Administration Guide Novell NetDrive Administration Guide 103-000170-001 September 4, 2001 Novell Confidential 38 July 17, 2001
PAGE 607

Manual 3 99a 38 July 17, 2001 Using NetDrive in a Thin-Client Environment NetDrive lets you access your iFolderTM files in a thin-client environment. If you are accessing your virtual desktop through one of the following applications running on your thin-client server, you can use NetDrive to access your iFolder server and files: Terminal Services Client Citrix* MetaFrame Novell® OnDemand ServicesTM To access your iFolder files, do the following: 1 Install NetDrive on your thin-client server.
PAGE 608

Manual 18 99a Novell NetDrive Administration Guide Novell NetDrive Administration Guide 103-000170-001 September 4, 2001 Novell Confidential 38 July 17, 2001
PAGE 609

Manual 4 99a 38 July 17, 2001 Troubleshooting FTP Problems The following are troubleshooting tips that should help when you encounter FTP errors. If you can’t create files using Microsoft Word, your NetWare® 6 FTP server that is running FTP might not support filenames that have the tilde (~). To configure NetDrive to remove or replace tildes when connecting to your FTP Web server, click your FTP site in the NetDrive Main Window and then click Advanced > File Names.
PAGE 610

Manual 99a 38 July 17, 2001 If you can’t copy a file from an FTP mapped drive, check the Drive Monitor Log window for FTP/HTTP status responses. If you can’t find a file on your NetWare 6 FTP server, flush your directory cache. To do this, in the NetDrive Main Window click File > Program Settings > Cache > Flush Directory Listing upon Each Connection. If you can’t rename your files, it might be because your NetWare 6 FTP server doesn’t support this functionality.
PAGE 611

QuickStart Rev 99a 44 August 22, 2001 To begin a QuickStart (English): Click in the box under the word Novell. Insert QuickStart and Title elements. 2. Type the product name. 3. Insert the HeadQS element and type the title of your card. 4. Put in your product version: Click Special > Variable > select the variable named Version > Edit Definition > enter the version number > click Done > Done. It will appear as background text replacing Version X.X.
PAGE 612

QuickStart Rev 99a 44 August 22, 2001 System Requirements If you have met the requirements for NetWare 6 and have NetWare 6 installed, you have met almost all of the system requirements for NetStorage. The following list specifies the system requirements for installing and running Novell NetStorage: At least one NetWare 6 server in the eDirectoryTM tree where NetStorage will be installed A Netscape* Navigator* 4.7 or later or Internet Explorer 5.
PAGE 613

QuickStart Rev 99a 44 August 22, 2001 5 (Optional) Specify IP addresses or DNS names of servers in other eDirectory trees that have at least read/write eDirectory replicas, or specify the same IP address or DNS name you used for the primary eDirectory server but with a different context. You can add two alternate eDirectory server IP addresses or DNS names and context settings.
PAGE 614

QuickStart Rev 99a 44 August 22, 2001 STARTING AND USING NOVELL NETSTORAGE Once you install NetStorage, it will start automatically when you start your NetWare 6 server. If NetStorage is not accessible, restart the NetWare 6 server where NetStorage is installed. Also, the date and time on the server running NetStorage should be reasonably close (within a few hours) of the date and time on the machine being used to access NetStorage.
PAGE 615

QuickStart Rev 99a 44 August 22, 2001 Clicking the Folder View button in the browser window displays folders in another column and lets you expand and contract folders. The Text View only displays the files and folders in the current directory and does not let you expand or contract folders. Local files and folders are not accessible using NetStorage. Also, mapping drives or changing login scripts is not permitted. Copyright © 2001 Novell, Inc. All rights reserved.
PAGE 616

Novell Storage Services Administration Guide Novell NetWare 6 ® www.novell.
PAGE 617

Manual 99a July 17, 2001 38 Contents Introducing Novell Storage Services 7 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 Overview 9 NSS Features and Benefits . . . . . . . . . . . . . . . . . . . . NSS Management . . . . . . . . . . . . . . . . . . . . . . . Combine Logical Volumes in a Single Storage Pool . . . . . . Create Logical Volumes . . . . . . . . . . . . . . . . . . . .
PAGE 618

Manual Setting Up ConsoleOne on a Workstation . . . . . . Configuring Disk Space . . . . . . . . . . . . . . . Renaming a Storage Pool . . . . . . . . . . . . . . Renaming a Logical Volume . . . . . . . . . . . . . Increasing the Size of a Storage Pool . . . . . . . . Deleting NSS Pools or Logical Volumes . . . . . . . Reviewing and Restoring Deleted Logical Volumes . Changing the Purge Delay Setting. . . . . . . . . . Creating a Traditional Volume . . . . . . . . . . . .
PAGE 619

Manual 99a 38 July 17, 2001 Introducing Novell Storage Services As your network structure grows, you need larger storage capacity, more efficient file management, and faster volume mounting speed. For example, you might need large volumes for numerous directories and files, or have numerous files open simultaneously. Novell® Storage ServicesTM (NSS) is a 64-bit file storage and management system that meets your file system needs.
PAGE 620

Manual 8 99a 38 Novell Storage Services Administration Guide Novell Storage Services Administration Guide 103-000141-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 621

Manual 1 99a 38 July 17, 2001 Overview Novell® Storage ServicesTM is a storage and file system that provides an efficient way to use all of the space on your storage devices. NSS is best used with systems that require the ability to store and maintain large volumes and numerous files or large databases. Novell Storage Services is the default storage and file system for NetWare® 6. You use it to create, store, and maintain both traditional and NSS volumes. The NSS volumes are called logical volumes.
PAGE 622

Manual 99a 38 July 17, 2001 and logical volumes, it includes instructions for setting up and maintaining traditional volumes. NSS Features and Benefits This section describes the features and benefits of NSS. NSS Management ConsoleOneTM is the primary utility used to configure and maintain both traditional and NSS logical volumes. See “Using ConsoleOne to Configure Novell Storage Services” on page 25. NOTE: NWCONFIG and NSS Menu are not compatible with some of the NetWare 6 NSS features.
PAGE 623

Manual 99a 38 July 17, 2001 Exceed the Limit of Volumes in a Storage Pool (Overbooking) Individual logical volumes cannot exceed the size of a storage pool. However, you can create numerous volumes in a storage pool. Individual logical volumes must be smaller than the storage pool, but the sum of multiple logical volumes can exceed the pool size. This feature, called overbooking, can be an efficient way to manage your file system.
PAGE 624

Manual 99a 38 July 17, 2001 Retain Previously Saved Files (Snapshot) The File Snapshot feature allows your backup utility to keep a consistent copy of all files. This is done by having the file system keep an original copy of all open files. For example, when your system backs up or crashes at a time when you are modifying a file, the backup could contain both old and new data. Snapshot captures the most recent closed copy of the file.
PAGE 625

Manual 99a 38 July 17, 2001 Prevent Access to Deleted Files (Data Shredding) The Data Shredding feature overwrites purged disk blocks with random patterns of hexidecimal characters. This prevents unauthorized users from using a disk editor to access purged files. You can place up to seven data shred patterns over deleted data. Set Up User Space Restrictions User space restrictions let you limit the space users have on volumes.
PAGE 626

Manual 99a 38 July 17, 2001 Redirect Data from Unreliable Blocks (Hot Fix) As your file system constantly reads and writes data to disk, some disk storage blocks lose their ability to reliably store data. NSS uses Hot Fix to prevent data from being written to unreliable blocks. Hot FixTM redirects the original block of data (still in memory) to the Hot Fix Redirection Area of the partition where the data can be stored correctly.
PAGE 627

Manual 99a 38 July 17, 2001 You can specify no Hot Fix Redirection Area when you create disk partitions. Having no Hot Fix Redirection Area saves partition space. This might be useful on large RAID systems that provide a method of fault tolerance. IMPORTANT: If Hot Fix is not enabled, then the partition will not have the fault tolerance provided by NetWare. Data on corrupted sectors of the disk won’t be redirected to the Hot Fix Redirection Area.
PAGE 628

Manual 99a 38 July 17, 2001 You can only mirror partitions. However, you might want to mirror an entire storage pool. Because you can have only one storage pool on a partition, the only way to mirror that storage pool is to mirror all of the partitions the pool resides on. To mirror partitions, you need to select an option that makes the partitions compatible for mirroring when you create them—you cannot change that mirroring option after you create a partition.
PAGE 629

Manual 99a 38 July 17, 2001 Important Information about NSS RAID Each element in the RAID configuration should come from a different device. NSS will let you obtain RAID elements from the same device, but this will severely impede the performance of your file system. Currently, the NSS RAID supports RAID 0. The stripe size ranges between 4 KB and 256 KB in increments of 2 KB.
PAGE 630

Manual Figure 1 99a 38 July 17, 2001 Novell Storage Services Configuration Free Space Storage Devices CD-ROM Free Space = Storage Deposit Partitioned Free Space Free Space Free Space Storage Pool Storage Pool Free Space Volume size can equal storage pool size Logical Vol1 18 Logical Vol2 Logical Traditional NSS volume volume Vol3 (Read-Only) Novell Storage Services Administration Guide Novell Storage Services Administration Guide 103-000141-001 August 30, 2001 Novell Confidential
PAGE 631

Manual 2 99a 38 July 17, 2001 Setting Up and Configuring Novell Storage Services Novell® Storage ServicesTM installs automatically when you install NetWare® 6. This section provides instructions for setting up and configuring Novell Storage Services (NSS) after the installation. It also contains information about configuring and maintaining traditional partitions and volumes.
PAGE 632

Manual 99a 38 July 17, 2001 Do the following to ensure NDS is running: 1 Use iMonitor to determine that the upgrade process is complete. 1a Open iMonitor in a network browser by entering the IP address of the server followed by /nds. For example: http://155.555.1/nds. 1b Click Agent Process Status > External Reference Status. 1c Make sure the time stamp (under the Time column) shows a time after the time you began the upgrade—specifically when NDS unloaded during the upgrade.
PAGE 633

Manual 99a 38 July 17, 2001 Upgrading NSS Volumes To upgrade NSS volumes, enter one of the following commands at the NetWare 6 server console: NSS /ZLSSVOLUMEUPGRADE=ALL NSS /ZLSSVOLUMEUPGRADE=volumename Transaction Tracking System (TTS) Transaction Tracking protects database applications by backing out transactions that are incomplete due to a system failure. TTS can be available on either all traditional or all NSS logical volumes.
PAGE 634

Manual Task 99a Purpose Command Set number of cache buffers This sets the minimum number of cache buffers allocated for NSS file system access. The default and minimum number of cache buffers is 512. The range is 256 to 1048576. nss/ MinBufferCacheSize= value Look up cache buffers To quickly look up cache buffers, the cache uses a hashing algorithm that maps names to buckets. Sometimes multiple names map to the same bucket.
PAGE 635

Manual 99a 38 July 17, 2001 Task Purpose Command Set the amount of cache NSS takes from the traditional file system This is the percent of cache between NSS and the server. The CacheBalance percentage determines how many cache blocks NSS will take from the traditional file system for its own cache. A high cache balance percentage will impede the performance of the traditional file system. A low cache balance will impede the performance of NSS.
PAGE 636

Manual 99a July 17, 2001 38 Task Purpose Command Show the cache hit ratio at the server console This is the number of cache hits divided by the number of attempts to get a file cache buffer from the cache. Any amount above 90 percent is good. This means the system is spending less time going to the disk to retrieve data. Lower numbers indicate NSS needs more memory. If this occurs, you might want to set the cache balance percentage higher.
PAGE 637

Manual 99a 38 July 17, 2001 Task Purpose Command Determine how often NSS rebalances the amount of cache it uses This timer lets you determine how often (in seconds) NSS will rebalance the amount of cache it uses according to the total amount of memory on the server. If you have difficulty loading NLMs because of low memory, you might want to lower this timer setting. A lower setting forces NSS to rebalance more often.
PAGE 638

Manual 99a 38 July 17, 2001 This opens the ConsoleOne interface where you can access the snap-ins for managing NSS. The NSS configuration features are in the Media snap-in. Setting Up ConsoleOne on a Workstation To use ConsoleOne on a client workstation, you need to load ConsoleOne 1.3 or later. Then you must copy the NSS JAR files from your server to your client machine. 1 Copy these three NSS JAR files to your local LIB directory: public\mgmt\consoleone\1.3\lib\nssadmin.jar public\mgmt\consoleone\1.
PAGE 639

Manual 99a 38 July 17, 2001 Creating a RAID Device NSS lets you create a RAID 0 device by striping data across multiple drives on your system. This RAID configuration occurs at the software level. You can use this RAID feature for both logical and traditional volumes. Important information about NSS RAID Each element in the RAID configuration should come from a different device.
PAGE 640

Manual 99a 38 July 17, 2001 Deleting a RAID Device When you delete a RAID device, the file system deletes all the partitions and volumes from all physical storage devices used in the RAID configuration. 1 From ConsoleOne, open the tree you want. 2 Right-click on the server object and select Properties. 3 Click Media > Raid Devices. 4 Select the Raid device you want to delete. 5 Click Delete. The file system displays a warning message to ensure you want to delete the RAID device. 6 Click Yes or No.
PAGE 641

Manual 99a 38 July 17, 2001 Marking a Device as Sharable for Clustering Some storage devices exist in a storage area network (SAN). These devices can be shared by multiple servers in a cluster. IMPORTANT: The system hardware does not specify disk drives to come up automatically as sharable for clustering or not sharable for clustering. You must manually set different devices according to the configuration of your storage system.
PAGE 642

Manual 99a 38 July 17, 2001 5 Select the type of partition you want to create (NSS, Traditional, Remote Storage Device). 6 Enter the size of the partition in bytes (B), kilobytes (KB), megabytes (MB), or gigibytes (GB). 7 To reserve space for the Hot Fix error correction feature, select Hot Fix and enter the amount of space or percentage you want to reserve. Mirrored partitions must be compatible in data area size.
PAGE 643

Manual 99a 38 July 17, 2001 Delete a Partition 1 From ConsoleOne, open the tree you want. 2 Right-click the server object and select Properties. 3 Click Media > Partitions. 4 Select the partition you want to delete, click Delete. Creating a Storage Pool After creating and setting up your partitions, you can create storage pools within the partitions. When you create a storage pool, NSS lets you determine how much space to use from each storage device on your server.
PAGE 644

Manual 99a 38 July 17, 2001 Creating a Logical Volume After creating storage pools, you can create any number of logical volumes for the storage pools according to the physical space available. When you create a logical volume, you can either assign it a space or allow it to expand to the pool size. The size of a single volume cannot exceed the size of a storage pool. However, the combined sizes of multiple volumes can exceed the size of the storage pool. This is called overbooking.
PAGE 645

Manual 99a 38 July 17, 2001 use. This means your backup system might not recognize this option whether you select it or not. Compression. Activates file compression in the logical volumes. Data Shredding. Activates the Data Shredding security feature. This feature scrambles any data that you delete to prevent anyone from accessing the information with a disk reader. Enter the number of times you want the data shredder to scramble your deleted files. You can select between one and seven times.
PAGE 646

Manual 99a 38 July 17, 2001 Renaming a Storage Pool You can rename existing storage pools. For example, you might want to assign a storage pool name that relates to a department name change. 1 From ConsoleOne, open the tree you want. 2 Right-click on the server object and select Properties. 3 Click Media > NSS Pools. 4 Select a pool to rename. 5 Click Rename. 6 Enter a new name for the pool. 7 Click Finish. Renaming a Logical Volume You can rename logical volumes.
PAGE 647

Manual 99a 38 July 17, 2001 6 Enter the amount of space you want from each storage object in the Used column. 7 Click Finish. Deleting NSS Pools or Logical Volumes You might need to delete a storage pool or a logical volume to create more free space for other storage pools. When you delete a logical volume or a traditional volume from a partition, that partition still owns the space, but you can reassign the space to another storage pool or traditional file system volume.
PAGE 648

Manual 99a 38 July 17, 2001 deleted volumes. You purge or restore volumes in the “Deleted Logical Volumes on Pool” screen. 1 From ConsoleOne, open the tree you want. 2 Right-click on the server object and select Properties. 3 Click Media > Logical Volumes. 4 Click Deleted Volumes. 5 Select one of the following options: Purge. Click Purge to immediately purge all the deleted volumes. Prevent Purge/Allow Purge. Click Prevent Purge to stop the volume purging process.
PAGE 649

Manual 99a 38 July 17, 2001 Creating a Traditional Volume NSS is the default file storage and management system in NetWare 6. However, you might want to continue maintaining traditional partitions and volumes in NSS. The following is a list of guidelines for creating traditional volumes in NetWare 6: NWCONFIG and NSS Menu are not compatible with NetWare 6. Use ConsoleOne to create, mount, modify, and rename traditional volumes.
PAGE 650

Manual 99a 38 July 17, 2001 Suballocation. Enables the file system to divide partially used disk blocks into suballocation blocks of 512 bytes. These blocks can be used by other data files. Mount Volume on Creation. Instructs the operating system to mount the volume when you create it. Otherwise, you can mount it later. 10 Click Finish. Increasing the Size of a Traditional Volume To increase the size of a traditional volume, you need to add another segment to that volume.
PAGE 651

Manual 99a 38 July 17, 2001 Deleting a Traditional Volume You can delete traditional volumes. 1 From ConsoleOne, open the tree you want. 2 Right-click on the server object and select Properties. 3 Click Media > Traditional Volumes. 4 Select the volume you want to delete and click Delete. Dismounting a Traditional Volume To repair a traditional volume, you need to dismount that volume. 1 From ConsoleOne, open the tree you want. 2 Right-click on the server object and select Properties.
PAGE 652

Manual 99a 38 July 17, 2001 The server console displays a mirroring error when the server boots. This mirroring refers to the two copies of FATs and DETs that the operating system keeps (if disks are mirrored, NetWare keeps four copies). If a volume fails to mount as the server is booting, VREPAIR loads automatically and attempts to repair the volume. When VREPAIR autoloads, it uses the default options.
PAGE 653

Manual 99a 38 July 17, 2001 2b To set alternate options at the Options menu, choose Set VRepair Options by typing 2 Enter 3 To begin the repair process, choose Repair A Volume from the Options menu. If more than one volume is dismounted, select the volume to repair from those listed. If only one volume is dismounted, VREPAIR assumes it is the volume that needs repairing and begins the repair.
PAGE 654

Manual 99a 38 July 17, 2001 Setting Up File Snapshot The File Snapshot feature enables your backup utility to keep an original copy of all data files. For example, when your system backs up or crashes at a time when you are modifying a file, the file backup could contain both old and new data. Snapshot captures the most recent closed copy of the file. This way, if you lose data between the backup cycles, you still have a solid copy of the previously saved file.
PAGE 655

Manual 99a 38 July 17, 2001 The following are some additional calls that return information about File Snapshot: GetFileSize GetFileHoles You can also use ConsoleOne to select the File Snapshot feature. See “Creating a Logical Volume” on page 32. Converting Traditional Volumes to Logical Volumes You can convert traditional volumes to logical volumes. This is not an automatic process or an in-place upgrade.
PAGE 656

Manual 99a 38 July 17, 2001 /d: Delete original volume if copy process is successful. If you choose to delete the traditional volume, the new volume will retain the name of the that volume. /r: Remove xxx_new NSS volume and restore xxx traditional volume (use this option if you want to keep the original volume name for the new logical volume name).
PAGE 657

Manual 99a 38 July 17, 2001 Modifying NDS Objects The volume conversion utility lets you modify the NDS objects and physical names for both logical and traditional volumes except the VOL SYS. Use the following commands VCU commands if you want to change the NDS objects with the volume conversion process.
PAGE 658

Manual 99a 38 July 17, 2001 8 Click Modify. 9 Enter or edit the user space amount in the Limit field and click OK. Setting Up Directory Space Restrictions You can limit the amount of space occupied by a directory and the files it contains. 1 Open ConsoleOne. 2 Right-click on the directory you want. 3 Click Properties and then Facts. 4 Select Restrict Size. 5 Enter the amount you want to limit the size to and click Apply. 6 Click Close.
PAGE 659

Manual 99a 38 July 17, 2001 2 Right-click on the server object and select Properties. 3 Click Media > NSS Pools or Logical Volumes. 4 Select the storage pool or volume you want to activate or deactivate. 5 Click Activate or Deactivate. 6 Click Activate when you are ready to restore access to the volume or pool. Salvaging and Purging Deleted Files You can salvage files that were deleted by users, or purge deleted files to improve your file system performance. Deleted files are in a DELETED.
PAGE 660

Manual 99a 38 July 17, 2001 Rebuilding NSS Storage Pools and Volumes To repair storage pools and logical volumes, NSS uses the VERIFY and REBUILD utilities. VERIFY checks the file system integrity for an NSS pool by searching for inconsistent data blocks or other errors. This utility indicates if there are problems with the file system. REBUILD verifies and uses the existing leaves of an object tree to rebuild all the other trees in the system.
PAGE 661

Manual 99a 38 July 17, 2001 NSS Server Console Commands Use the following commands at the server console to view NSS information and perform tasks. Online Help Commands Enter nss /help or nss /? to access Help. NSS Configuration Information Commands nss /modules Lists the providers, loadable storage subsystems, and semantic agents. nss /status Lists the current NSS status. volumes Lists all NetWare and NSS volumes that are mounted, including Admin volume.
PAGE 662

Manual 99a 38 July 17, 2001 tasks such as flushing file metadata to disk in the background. Increasing the number of WorkToDo entries might be useful on a system that is heavily used. NSS always reserves 20 WorkToDo entries. The default is 40. The range is 5 to 100. nss /FileFlushTimer=value Sets the flush time for modified open files in seconds. Increasing this number might reduce the number of writes to disk; however, it increases the amount of data that will be lost if the system crashes.
PAGE 663

Manual 99a 38 July 17, 2001 FlushFilesImmediately Synchronously flush files in the volume when they are closed. NoFlushFilesImmediately Disable synchronously flushing files in the volume. FileCopyOnWrite Create a copy of files in the volume when they are open for write. NoFileCopyOnWrite Do not create a copy of files on the volume when they are open for write. UpgradeObjectsOnVolume Upgrade objects on volumes to the current version.
PAGE 664

Manual 99a 38 July 17, 2001 PoolRebuild Select pools from a menu and rebuild them. PoolVerify=pool Verify the specified pool’s physical integrity. PoolVerify Select pools from a menu and verify their physical integrity. LogicalVolumePurgeDelayAfterLoad The number of seconds to delay purging deleted logical volumes. This allows time to reverse the deletion. LogicalVolumePurgeDelayAfterContinue The number of seconds to delay purging a logical volume after clicking continue.
PAGE 665

Manual 99a 38 July 17, 2001 DOS FAT Commands nss /(No)FATLongNames Enables long filenames on FAT volumes. The default is ON. nss /(No)FATLazyWrites Performs lazy writes of FAT. If set to ON, data that is written will be kept in memory for a specified period of time before it is also written to FAT. This increases performance. The default is ON. nss /FATLazyWriteDelay=value Sets the FAT lazy write delay (in seconds).
PAGE 666

Manual 99a 38 July 17, 2001 The CD9660.NSS module makes the contents of the standard ISO9660 CDROM available as a Read-Only logical volume. If the CDROM is in the drive when CD9660 loads, it will mount as a logical volume immediately. The volume name displayed by the NetWare volumes command is the CDROM volume label if one exists. Otherwise, NSS generates a volume name in this form: CDXXXXXX (where X is a number). This volume functions the same as any other NetWare volume, except that it is Read-Only.
PAGE 667

Manual 99a 38 July 17, 2001 NetWare utilities. Any client or server utility that accesses or manages NetWare volumes can do the same with DOS FAT partitions. MAP command. NetWare clients can map to the volume and use it as any other NetWare mapping. Local partition. Allows access to the local partition.
PAGE 668

Manual 56 99a 38 Novell Storage Services Administration Guide Novell Storage Services Administration Guide 103-000141-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 669

Manual 3 99a 38 July 17, 2001 Viewing Storage Objects We recommend that you monitor the status of your storage objects and Novell® Storage ServicesTM configuration to ensure they work properly and have available disk space. Viewing Storage Devices You can use ConsoleOneTM to view your storage devices and see which ones have free space. 1 From ConsoleOne, open the tree you want. 2 Right-click on the server object and select Properties. 3 Click Media > Show Devices.
PAGE 670

Manual 99a 38 July 17, 2001 pool. On a traditional partition, space that is not occupied by a NetWare® volume is free space. 1 From ConsoleOne, open the tree you want. 2 Right-click on the server object and select Properties. 3 Click Media > Free Space. The left panel lists the storage devices that have free space. 4 Select the device you want. For information about the Free Space screen, click Help. Any time the Devices button appears, you can click it to open the Devices screen.
PAGE 671

Manual 99a 38 July 17, 2001 View the Status of Your NSS Storage Pools You can view the status of NSS storage pools. For example, you might want to see what volumes are in a particular storage pool, or how much space is in all your storage pools. 1 From ConsoleOne, open the tree you want. 2 Right-click on the server object and select Properties. 3 Click Media > NSS Pools. The left panel lists the NSS storage pools. 4 Select a storage pool. For information about the NSS Pools screen, click Help.
PAGE 672

Manual 99a 38 July 17, 2001 3 Click Media > Logical Volumes. 4 Click Properties. 5 Click Statistics > NSS Quota Usage. This screen shows the volume’s quota, amount of spaced used, and the remaining space. The screen also shows the amount of space used and the available space on the storage pool. For information about the NSS Quota Usage screen, click Help. View and Modify Logical Volume Attributes You can view and modify the attribute settings for specific volumes.
PAGE 673

Manual 4 99a 38 July 17, 2001 Troubleshooting The following table describes some problems you might experience with Novell® Storage ServicesTM (NSS) and provides suggestions for solving the problems. For additional troubleshooting information, see the Novell Knowledgebase at (www.support.novell.com). Problem Explanation Solution NSS does not recognize a Device NSS recognizes only what the Media Manager recognizes. For this release, NSS recognizes only hard drives and CD ROMs.
PAGE 674

Manual 62 99a 38 July 17, 2001 Problem Explanation Solution Cannot compress a file You must choose the file compression option when you create a logical volume. Apply the file compression option to an existing logical volume: From ConsoleOne, click Media > NSS Logical Volumes > Properties > Attributes > NSS Attributes. Then select compression.
PAGE 675

Traditional File Services Administration Guide Novell NetWare 6 ® www.novell.
PAGE 676

Manual 99a July 17, 2001 38 Contents Preface 7 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1 Overview of Traditional File System Volume . . . . . . . . . . . . . . . . . Understanding Mounting a Volume. Volume Objects in NDS . . . . . . Understanding Volume Segments . Directories . . . . . . . . . . . . . . . Directory Path . . . . . . . . . . . Fake Root. . . . . . . . . . . . . . Directory Map Objects . . . . . . . Optimizing Performance .
PAGE 677

Manual 99a July 17, 2001 38 Mapping Drives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mapping Drives in Windows 95/98, NT/2000 . . . . . . . . . . . . . Mapping Drives in DOS . . . . . . . . . . . . . . . . . . . . . . . . Distributing Applications on the Network . . . . . . . . . . . . . . . . . Security: Rights to Files and Directories. . . . . . . . . . . . . . . . . . Description of Directory and File Rights . . . . . . . . . . . . . . . . Adding a Trustee to a Directory or File . .
PAGE 678

Manual 99a 38 July 17, 2001 Preface NetWare® provides the traditional NetWare file system components and utilities, such as NetWare partitions, NetWare volumes, and file management utilities.
PAGE 679

Manual 99a 38 July 17, 2001 Documentation Conventions In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path. Also, a trademark symbol (®, TM, etc.) denotes a Novell trademark. An asterisk (*) denotes a third-party trademark.
PAGE 680

Manual 1 99a 38 July 17, 2001 Overview of Traditional File System This chapter of the file system documentation explains key aspects of the traditional NetWare® file system and contains the following topics: Volume (page 9) Directories (page 12) Optimizing Performance (page 14) Drive mapping (page 16) How NetWare Protects Network Data (page 17) “Security” on page 18 Information on volumes, directories, files, and other characteristics of the file system is presented to give you background n
PAGE 681

Manual 99a July 17, 2001 38 A NetWare server is divided into one or more volumes. The first network volume is named SYS: and is created during NetWare installation. Using ConsoleOne, you can create a new volume on any hard disk that has a NetWare partition. A NetWare server supports up to 64 volumes. NetWare volumes are subdivided in two ways: Physically. You divide volumes into volume segments; different segments of a volume can be stored on one or more hard disks.
PAGE 682

Manual 99a 38 July 17, 2001 Because of this, volumes with a smaller block size require more server memory to mount and manage. However, if most of your files are small, a large block size wastes disk space. The volume's DET is loaded into memory If a volume fails to mount, it might be because you have run out of RAM. This is because the FAT takes up cache buffers. NOTE: The new file system, Novell Storage Services (NSS), mounts volumes more quickly and can mount any size volume with 1 MB of memory.
PAGE 683

Manual 99a 38 July 17, 2001 However, when you spread segments of a volume over several disks, you should protect the volumes against disk failure by mirroring; otherwise, if a single disk fails, one or more entire volumes shut down. You can add segments to a volume, but removing a segment from a volume destroys the entire volume.
PAGE 684

Manual 99a 38 July 17, 2001 characters in a directory path (counting the drive letter and delimiters), but DOS permits only 127 characters. Also, some applications restrict the number of characters in the directory path. For more information, check the application's documentation. Fake Root A fake root is a subdirectory that functions as a root directory. NOTE: Fake roots work with the NetWare DOS Requester, with NetWare shells, and clients including Windows* 3.x, Windows 95, and Windows NT*.
PAGE 685

Manual 99a 38 July 17, 2001 If you create a Directory Map object to point to an application, users can access the application by mapping a drive to the Directory Map object. If the application's location in the directory structure changes, you can update the object instead of having to change all users' drive mappings.
PAGE 686

Manual 99a 38 July 17, 2001 Salvageable Files Salvageable files are files saved by NetWare, after being deleted by users, that can be salvaged (recovered). Salvageable files are usually stored in the directory they were deleted from. If a user deletes that directory, the salvageable files are saved in a DELETED.SAV directory located in the volume's root directory. The user can view a list of deleted files in a directory and recover files by using ConsoleOneTM.
PAGE 687

Manual 99a 38 July 17, 2001 Drive mapping A drive mapping is a pointer to a location in the file system, represented as a letter assigned to a directory path on a volume. A path includes the volume, directory, and any subdirectories leading to the file. A drive mapping assigns a letter to a path so that the letter can be used instead of the complete path name. Drive mappings can be temporary or permanent: Permanent mappings.
PAGE 688

Manual 99a 38 July 17, 2001 Network Drive Mappings Network drive mappings point to volumes and directories on the network. Normally, drives F: through Z: are used for network mappings. Each user can map drive letters to different directories. To create a network drive mapping, use the MAP command. Network Search Drive Mappings Network search drive mappings point to directories containing files such as applications or files.
PAGE 689

Manual 99a 38 July 17, 2001 Security Security is one of the most important aspects of file system organization. NDS rights and the file system's directory and file attributes allow you to determine who may access what, and whether that access amounts to being able to merely read a file or modify it. To use the capabilities described in the NDS area of this documentation, you might want to organize your approach to designing an appropriately secure system by doing the following: 1.
PAGE 690

Manual 2 99a 38 July 17, 2001 Planning This chapter presents a simple example of a network directory structure to help you plan your file system. Based on the example and the accompanying information, you can begin to design a directory hierarchy suitable to your own needs. NOTE: You use the Novell® Storage ServicesTM (NSS) file system to meet your file system needs. NSS lets you create and maintain NSS logical volumes along with traditional NetWare® volumes.
PAGE 691

Manual 99a 38 July 17, 2001 deleted directory are moved to the DELETED.SAV directory. Deleted files can be salvaged if they have not yet been purged. SYS:ETC contains sample files to help you configure the server. SYS:LOGIN contains the programs necessary for users to log in to the network, such as LOGIN.EXE. An NLS subdirectory contains subdirectories for login message files for each supported language. SYS:MAIL might or might not contain subdirectories or files.
PAGE 692

Manual 99a 38 July 17, 2001 The following figure shows this type of directory structure: Figure 2 Application Volume SYSTEM PUBLIC LOGIN MAIL SYS NetWare server WORDPROC DBAPP SPRDSHT APPSVOL Create a separate directory off volume SYS: for each application. Make trustee assignments for each application. Then go into the system or profile login script and map a search drive to each application. The following figure shows this type of directory structure.
PAGE 693

Manual 99a 38 July 17, 2001 However, users can see and use all applications. Use this directory structure only if you want all users to have access to all applications. The following figure shows this type of directory structure. Figure 5 Application Directory in SYS:PUBLIC APPS PUBLIC NetWare server WORDPROC DBAPP SPRDSHT SYS Installing applications in SYS:PUBLIC is not recommended (unless you create a subdirectory for each application).
PAGE 694

Manual 99a July 17, 2001 38 Home or Username Directories To provide personal workspace for users, create home or username directories. You can create a parent directory in volume SYS: called HOME or USERS. Or, you can create a separate HOME or USERS volume. Then you can create a subdirectory for each user. The name of each subdirectory should be the username. Usernames can be up to 47 characters, but DOS displays only 8 characters in a one-level directory name.
PAGE 695

Manual 24 99a 38 Traditional File Services Administration Guide Traditional File Services Administration Guide 103-000180-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 696

Manual 3 99a 38 July 17, 2001 Setting Up the File System The procedures in this section of the documentation focus on specific tasks pertaining to system administration. Procedures involve various utilities and applications that are provided in the Novell Storage Services Administration Guide. The most productive use of file system documentation is to identify the task you want to complete and find an appropriate procedure.
PAGE 697

Manual 99a 38 July 17, 2001 The following name space NLM programs are available with NetWare: MAC.NAM (Macintosh) LONG.NAM (OS/2, Windows 95/NT/2000) NFS.NAM (NFS). An FTAM name space module is available from third-party providers. Calculating Memory Required for Name Space Support Use the following formula to calculate the name space memory requirement for traditional NetWare non-DOS volumes: 0.032 x volume_size (in MB) / block_size (in MB) Round the size up to the highest number.
PAGE 698

Manual 99a 38 July 17, 2001 3 To verify that the name space loaded, enter the following command: VOLUMES This shows a list of all name spaces. Removing Name Spaces You can remove the name space by deleting the volume and re-creating it, or by using VREPAIR. For instructions on using VREPAIR, see Repairing a Traditional Volume in the Novell Storage Services Administration Guide. Creating a Directory You create directories in ConsoleOneTM.
PAGE 699

Manual 99a 38 July 17, 2001 Mapping Drives Mapping Drives in Windows 95/98, NT/2000 See Common Networking Tasks in the Novell Client for Windows documentation. Mapping Drives in DOS Use the command to map drives and search drives to network directories. For a general description of the MAP command, see MAP in Utilities Reference.
PAGE 700

Manual 99a 38 July 17, 2001 You can create a Directory Map object that points to an application directory. Directory Map objects are useful in login scripts. Instead of mapping a drive to a specific directory path, you map a drive to a Directory Map object that points to a directory. For information about Directory Map objects, see “Directory Map Objects” on page 13. Then, if you change the directory path, you need to change only the Directory Map object’s definition.
PAGE 701

Manual 99a 38 July 17, 2001 Description of Directory and File Rights Trustee rights determine the access users have to directories and files. These rights can be given to NDS object such as User objects, Group objects, Organizational Role objects, or container objects. The following table contains a list and description of rights. Table 1 Trustee Rights Right Allows you to Access Control Add and remove trustees and change rights to directories and files. Create Create subdirectories and files.
PAGE 702

Manual 99a 38 July 17, 2001 Setting Directory or File Attributes To set up attributes and change owners for a directory or file, see the following: “Description of Directory and File Attributes” on page 31 “Changing Attributes of a Directory or File” on page 33 “Changing Attributes of a Directory or File” on page 33 For information on how to use Windows 95 to set directory or file attributes, see Common Networking Tasks in Novell Client for Windows 95 (http:// www.novell.com/documentation/).
PAGE 703

Manual 99a 38 July 17, 2001 Attribute code Description Applies to Dm Do not Migrate prevents directories and files from being migrated from the server's hard disk to another storage medium. Directories and files Ds Do not Suballocate prevents data from being suballocated. Files only H The Hidden attribute hides directories and files so they cannot be listed using the DIR command.
PAGE 704

Manual 99a 38 July 17, 2001 Attribute code Description Applies to X The Execute Only attribute prevents the file from being copied, modified, or backed up. It does allow renaming. The only way to remove this attribute is to delete the file. Use the attribute for program files such as .EXE or .COM. Make a copy of a file before you flag it as Execute Only, so you can replace the file if it becomes corrupted.
PAGE 705

Manual 34 99a 38 Traditional File Services Administration Guide Traditional File Services Administration Guide 103-000180-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 706

Manual 4 99a 38 July 17, 2001 Optimizing File System Performance This chapter on file system optimization focuses exclusively on tasks for the network administrator. Procedures in this section pertain primarily to disk space utilization, and affect performance only as space utilization affects network performance.
PAGE 707

Manual 99a 38 July 17, 2001 To avoid the overhead of uncompressing files that do not compress well, the system calculates the compressed size of a file before actually compressing it. If no disk space will be saved by compression, or if the size difference does not meet the value specified by the SET parameter named Minimum Percentage Compression Gain, the file is not compressed. For a general description of the SET command, see SET in Utilities Reference.
PAGE 708

Manual 99a 38 July 17, 2001 To change SET parameters, execute the SET command at the server console prompt. The following list identifies SET command parameters that affect file compression. The settings apply to all files and directories in compressionenabled volumes on the server. For the function and range of values associated with each SET parameter, see SET in Utilities Reference.
PAGE 709

Manual 99a 38 July 17, 2001 You can purge files automatically using SET. For a general description of the SET command, see SET in Utilities Reference. Saving Disk Space with Block Suballocation Use block suballocation to enhance use of disk space. Block suballocation divides any partially used disk block into suballocation blocks of 512 bytes. These suballocation blocks can be used by files to share what would otherwise be unavailable space.
PAGE 710

Manual 5 99a 38 July 17, 2001 Managing The procedures in the Managing section of the file system documentation pertain to network administrators and users. Procedures for viewing directory and file information, copying, moving, and other routine functions are of interest to users as well as system administrators. Procedures pertaining to volume management and the protection of network data necessarily belong to network administration.
PAGE 711

Manual 99a 38 July 17, 2001 Deleting a Traditional Volume Repairing a Traditional Volume Volume Conversion Viewing Directory and File Information You can see extended information about a directory or file using ConsoleOne. For instructions on viewing directory and File information, see Viewing or Modifying Information about a File or Folder in the ConsoleOne 1.3 User Guide.
PAGE 712

Manual 99a 38 July 17, 2001 instructions on copying directories and files, see Viewing or Modifying Information about a File or Folder in the ConsoleOne 1.3 User Guide. Salvaging and Purging Files Files deleted from the NetWare server remain on the disk until the deleted files are purged. Deleted files can be salvaged any time before they are purged. Purging frees the space used to store the deleted files on the server's hard disk.
PAGE 713

Manual 99a 38 July 17, 2001 If you create a Directory Map object to point to an application, users can access the application by mapping a drive to the Directory Map object. Directory Map objects can be especially useful in login scripts by indicating directories that contain applications or other frequently used files. For instructions on creating Directory Map Objects, see Creating a Directory Map Object in the ConsoleOne 1.3 User Guide.
PAGE 714

Manual 6 99a 38 July 17, 2001 Troubleshooting This chapter presents various troubleshooting procedures for resolving problems with traditional volume including the following: Resolving File I/O Errors (page 43) Resolving Volume I/O Errors (page 44) Resolving Problems When the Server Hangs after Mounting Last Volume (page 44) Resolving Problems When No Volumes Mount (page 45) Resolving Problems When Only Some Volumes Mount (page 45) Resolving Disk Error Problems When a Volume Is Mounting (pa
PAGE 715

Manual 99a 38 July 17, 2001 Check how much space remains on volume SYS:. If it is low, increase the size by adding free space. To increase the amount of free space, do one or more of the following: Delete extraneous files (if you can log in from a workstation). Enter SET IMMEDIATE PURGE OF DELETED FILES = ON at the console prompt and then retry the action. If you have an additional disk, increase the size of the volume by creating an additional segment of the volume on the disk.
PAGE 716

Manual 99a July 17, 2001 38 Make sure that all server and workstation network boards are seated properly and that cabling and connections are attached securely. Make sure that the terminators on cables have the right ohm rating and are installed correctly. The IBM* PC Cluster sends a broadcast message during initialization and then stops processing if the network is not cabled or terminated properly. Check the network boards in all workstations for correct node address settings.
PAGE 717

Manual 99a 38 July 17, 2001 The server does not have enough RAM The disk driver for external drives are not be loaded To resolve problems when only some volumes mount, do the following: Add more RAM. Verify which drivers are loaded. Resolving Disk Error Problems When a Volume Is Mounting To diagnose problems when disk errors occur while a traditional volume is mounting, identify whether the following conditions exist: The server does not have enough memory to mount the volume.
PAGE 718

Manual 99a 38 July 17, 2001 Each additional name space support that you add to a volume increases the size of the file allocation tables and directory entry tables. Adding name space support can cause the tables to grow so large that the server does not have enough RAM to mount the volume. To resolve memory errors when a volume mounts, perform the following actions or ensure that the following conditions exist: Check the status of the available cache buffers.
PAGE 719

Manual 99a 38 July 17, 2001 A power failure has occurred and the server has not been shut down with the DOWN command. A hard disk has failed. A disk channel error has occurred. A volume does not dismount when you enter the DISMOUNT command. Directory information in cache is not completely written to disk. To resolve problems when mismatches exist in the duplicate copies of the FAT and DET, do the following: Run VREPAIR.
PAGE 720

Manual 99a 38 July 17, 2001 WARNING: This is a destructive step that destroys all of the extended file information. Back up all non-DOS files. Load VREPAIR and select Set VRepair Options. Then select the Remove Name Space Support from the Volume and Write All Directory and FAT Entries to Disk options. Then exit to the main menu. Run VREPAIR > Repair a Volume on the volume that would not mount.
PAGE 721

Manual 50 99a 38 Traditional File Services Administration Guide Traditional File Services Administration Guide 103-000180-001 August 30, 2001 Novell Confidential July 17, 2001
PAGE 722

NetWare Server Disks and Storage Devices Administration Guide Novell NetWare 6 ® www.novell.
PAGE 723

Manual 99a 38 July 17, 2001 Contents Server Disks and Storage Devices Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . Partitioning Disks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Logical Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device and Partition Numbering . . . . . . . . . . . . . . . . . . . . . . . . . Object Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Device Names . . . . . . . . .
PAGE 724

Novell Cluster Services Overview and Installation Novell Cluster Services www.novell.com 1.
PAGE 725

Manual Rev 99a 9 June 00 28 Contents Introduction to Novell Cluster Services 7 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 Overview Product Features . . . . Product Benefits . . . . Cluster Configuration. . Cluster Components 2 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 726

Manual Rev 99a Migrating Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Identifying Cluster and Resource States . . . . . . . . . . . . . . . . . . . Additional Cluster Operating Instructions . . . . . . . . . . . . . . . . . . . Installing NetWare on a Server That Will Be Added to an Existing Cluster Readding a Node to a Cluster That Was Prevously in the Cluster . . . . Cluster-enabled Volume Connection Required for Some Utilities . . . . . Some Applications Do Not Fail Over . . . .
PAGE 727

Manual 99a 38 July 17, 2001 Introduction to Novell Cluster Services Novell® Cluster ServicesTM is a server clustering system that ensures high availability and manageability of critical network resources including data (volumes), applications, server licenses, and services. It is a multinode, eDirectoryTM enabled clustering product for NetWare® 6 that supports failover, failback, and migration (load balancing) of individually managed cluster resources.
PAGE 728

Manual 8 99a 38 Novell Cluster Services Overview and Installation Novell Cluster Services Overview and Installation 103-000154-001 August 29, 2001 Novell Confidential July 17, 2001
PAGE 729

Manual 1 99a 38 July 17, 2001 Overview Novell® Cluster ServicesTM is a server clustering system that ensures high availability and manageability of critical network resources including data (volumes), applications, server licenses, and services. It is a multinode clustering product for NetWare® that is enabled for eDirectoryTM and supports failover, failback, and migration (load balancing) of individually managed cluster resources. Licenses for two cluster nodes is included with NetWare 6.
PAGE 730

Manual 99a 38 July 17, 2001 Product Benefits Novell Cluster Services allows you to configure up to 32 NetWare servers into a high-availability cluster, where resources can be dynamically switched or moved to any server in the cluster. Resources can be configured to automatically switch or be moved in the event of a server failure, or can be moved manually to troubleshoot hardware or balance the workload. Novell Cluster Services provides high availability from commodity components.
PAGE 731

Manual Figure 1 99a July 17, 2001 38 Three-Server Cluster Web Server 1 Web Server 2 Web Server 3 Web Site A Web Site C Web Site E Web Site B Web Site D Web Site F Fiber Channel Switch Shared Disk System During normal cluster operation, each server is in constant communication with the other servers in the cluster and performs periodic polling of all registered resources to detect failure.
PAGE 732

Manual 99a 38 July 17, 2001 Web Site A moves to Web Server 2 and Web Site B moves to Web Server 3. IP addresses and applicable licenses also move to Web Server 2 and Web Server 3. When you configured the cluster, you decided where the Web sites hosted on each Web server would go should a failure occur. In the previous example, you configured Web Site A to move to Web Server 2 and Web Site B to move to Web Server 3. This way, the workload once handled by Web Server 1 is evenly distributed.
PAGE 733

Manual 99a 38 July 17, 2001 Cluster Configuration Typical cluster configurations normally include a shared disk subsystem connected to all servers in the cluster. The shared disk subsystem can be connected via high-speed fiber channel cards, cables, and switches, or be configured to use shared SCSI. If a server fails, another designated server in the cluster automatically mounts the shared disk volumes previously mounted on the failed server.
PAGE 734

Manual Figure 4 99a 38 July 17, 2001 Typical Shared SCSI Cluster Configuration Network Hub Network Interface Card Server 1 SCSI Adapter Network Interface Card Sys Server 2 SCSI Adapter Sys Shared Disk System Cluster Components The following components make up a Novell Cluster Services cluster: From 2 to 32 NetWare servers configured to use IP, each containing at least one local disk device (used for a local SYS: volume).
PAGE 735

Manual 2 99a July 17, 2001 38 Installation and Setup Hardware Requirements The following list specifies hardware requirements for installing Novell® Cluster ServicesTM. These requirements represent the minimum hardware configuration. Additional hardware might be necessary depending on how you intend to use Novell Cluster Services.
PAGE 736

Manual 99a 38 July 17, 2001 Shared Disk System Requirements A shared disk system (Storage Area Network or SAN) is required for each cluster if you want data to be highly available. If a shared disk subsystem is used, ensure the following: At least 15 MB of free disk space on the shared disk system for creating a special cluster partition The Novell Cluster Services installation automatically allocates one cylinder on one drive of the shared disk system for the special cluster partition.
PAGE 737

Manual 99a July 17, 2001 38 When working with shared storage, do not attach a noncluster server to the same shared storage device as a cluster unless you have isolated the storage so that the noncluster server has access only to its own volumes. Failure to do so will result in data corruption or volume loss.
PAGE 738

Manual 99a 38 July 17, 2001 Prepare Cluster Servers for an Upgrade If you are upgrading Novell Cluster Services from a previous version and your cluster has shared storage, you must prepare your cluster servers before upgrading them to NetWare 6 and before upgrading Novell Cluster Services. This preparation is necessary to ensure existing shared-volume trustee assignments can be used after the upgrade. To prepare cluster servers for an upgrade, from a NetWare client run NWDEPLOY.
PAGE 739

Manual 99a July 17, 2001 38 Run the Installation Program To install Novell Cluster Services, insert the NetWare 6 Operating System CD in a NetWare client workstation and allow the NetWare Deployment Manager to automatically launch. You can also run NWDEPLOY.EXE from the root of the CD to launch the NetWare Deployment Manager.
PAGE 740

Manual 4 99a 38 July 17, 2001 Enter the name of the server you want to add to the cluster, or browse and select one from the list, and then click Add to Cluster. Repeat this step for every server you want to add to the cluster. Then click Next. You can also remove servers you just added to the cluster by selecting them from the NetWare Servers in Cluster list and clicking Remove. When you add a server to a cluster, Novell Cluster Services automatically detects the server’s IP address.
PAGE 741

Manual 99a July 17, 2001 38 If you choose to not start Novell Cluster Services software on each server that you upgrade or add to your cluster, you will need to manually start it after the installation or you will need to reboot cluster servers to automatically start it. You can manually start Novell Cluster Services by running LDNCS at the server console on each cluster server.
PAGE 742

Manual 99a 38 July 17, 2001 Setting Up Novell Cluster Services If you created a new cluster, you now need to create and configure cluster resources. You might also need to create shared disk partitions if they do not already exist and, if necessary, configure all shared disk system pools and volumes to work with Novell Cluster Services. You might also need to cluster enable the shared disk system pools and volumes.
PAGE 743

Manual 99a July 17, 2001 38 If Cluster Services was previously installed and shared disk partitions were already created, the Partitions List field will include this information. 4 5 On the Media tab, click Partitions >New, and then select the device where you want to create the partition (the same device you selected in the previous step). Specify the size of the partition and click OK to create it. Continue with “Create NSS Pools” on page 24.
PAGE 744

Manual 99a 38 July 17, 2001 Create NSS Pools The new Storage Pools feature in NSS gives you more flexibility in planning and configuring your storage to work with Novell Cluster Services. More than one cluster-enabled volume can now be part of a single cluster resource, and volumes can dynamically grow as needed to take advantage of free disk space. Only one NSS pool can be created on a partition. Storage pools must be created prior to creating and cluster-enabling volumes.
PAGE 745

Manual 99a July 17, 2001 38 Create Cluster Volumes If you plan on using a shared disk system in your cluster and need to create new NetWare pools or volumes after installing Novell Cluster Services, the server used to create the volumes should already have NSS installed and running. NSS is the default file system for NetWare 6. Using ConsoleOne 1 2 In ConsoleOne, on the property page of the Server object, click the Media tab and select NSS Logical Volumes.
PAGE 746

Manual 99a 38 July 17, 2001 by default. In the AUTOEXEC.NCF file of the server where the volume is to be mounted, add separate MOUNT commands followed by the volume name for each of the noncluster volumes you want to mount. Using NetWare Remote Manager The same procedure for creating shared disk partitions using NetWare Remote Manager is used to create cluster volumes. To create a cluster volume on shared storage using NetWare Remote Manager go to Step 1 on page 23.
PAGE 747

Manual 99a July 17, 2001 38 Using ConsoleOne 1 2 3 4 Browse and select the Cluster object. Click File > New > Cluster > Cluster Volume. Browse and select a volume on the shared disk system to cluster enable. Enter an IP address for the volume. This is only required for the first volume to be cluster enabled in the pool. This IP address will be assigned to the pool where the volume resides.
PAGE 748

Manual 99a 38 July 17, 2001 All other fields on this screen should be automatically updated. You can change or edit the information in the fields as desired. See Step 5 on page 27 and Step 6 on page 27 for more information. This is only required for the first volume to be cluster enabled in the pool. This IP address will be assigned to the pool where the volume resides. Checking the Auto-Online check box will cause the resource to automatically start once it is created.
PAGE 749

Manual 99a July 17, 2001 38 To finish creating a cluster resource template, you need to configure load and unload scripts, set failover and failback modes and, if necessary, change the node assignments for the resource template. Using NetWare Remote Manager 1 2 3 4 5 On the left column under the Clustering section, click Cluster Config. At the bottom of the screen above Create New Objects, click New Cluster Resource. Enter a name for the new cluster resource template.
PAGE 750

Manual 99a 38 July 17, 2001 Using NetWare Remote Manager 1 2 3 4 On the left column under the Clustering section, click Cluster Config. At the bottom of the screen under Create New Objects, click New Cluster Resource. Enter a name for the new cluster resource. If a template exists for the resource you are creating, select it from the list and then click Apply. If a template does not exist, check the Define Additional Properties check box and then click Apply.
PAGE 751

Manual 99a July 17, 2001 38 Using ConsoleOne 1 2 Select the Load Script tab on the resource property page. Edit or add the necessary commands to the script to load the resource on the server. Some commands may require command line input. You can add << to a command to indicate command line input. For example, a script command might read LOAD SLPDA <
PAGE 752

Manual 99a 38 July 17, 2001 Configure Unload Scripts Depending on your cluster application or resource, you can add an unload script to specify how the application or resource should terminate. An unload script is not required by all resources or applications, but it can ensure that during a failback or manual migration, a resource unloads before it loads on another node. Consult your application vendor or documentation to determine if you should add commands to unload the resource.
PAGE 753

Manual 99a July 17, 2001 38 Set Start, Failover, and Failback Modes You can configure the start, failover, and failback of cluster resources to happen manually or automatically. With the resource Start Mode set to AUTO, the resource automatically starts on a server when the cluster is first brought up. If the resource Start Mode is set to MANUAL, you can manually start the resource on a server when you want, instead of having it automatically start when servers in the cluster are brought up.
PAGE 754

Manual 4 99a 38 July 17, 2001 Check the Master Only check box to ensure the resource runs only on the master node in the cluster. If the master node in the cluster fails, the resource will fail over to whichever node becomes the master. 5 Click Apply to save changes. Using NetWare Remote Manager 1 2 3 4 On the left column under the Clustering section, click Cluster Config. From the list of Resources, select the desired resource. On the Resource Information screen, click Policies.
PAGE 755

Manual 3 4 99a July 17, 2001 38 Click the Up- and Down-arrow buttons to change the failover order of the servers assigned to the resource or volume. Click Apply to save node assignment changes. Using NetWare Remote Manager 1 2 3 4 5 On the left column under the Clustering section, click Cluster Config. From the list of Resources, select the desired resource. On the Resource Information screen, click Nodes. Select or type in the nodes that you want assigned to this resource.
PAGE 756

Manual 99a 38 July 17, 2001 Membership The Quorum Membership is the number of nodes that must be running in the cluster before resources will start to load. When you first bring up servers in your cluster, Novell Cluster Services reads the number specified in the Membership field and waits until that number of servers is up and running in the cluster before it starts loading resources.
PAGE 757

Manual 99a July 17, 2001 38 Using NetWare Remote Manager 1 2 3 On the left column under the Clustering section, click Cluster Config. Select the Cluster object name. Click Protocol. Heartbeat Heartbeat specifies the amount of time between transmits for all nodes in the cluster except the master. For example, if you set this value to 1, nonmaster nodes in the cluster send a signal that they are alive to the master node every second.
PAGE 758

Manual 99a 38 July 17, 2001 Cluster IP Address and Port Properties The Cluster IP address is assigned when you install Novell Cluster Services. The Cluster IP address normally does need to be changed, but can be if needed. The default cluster port number is 7023, and is automatically assigned when the cluster is created. The cluster port number does not need to be changed unless a conflict is created by another resource using the same port number.
PAGE 759

Manual 4 99a July 17, 2001 38 To change the priority for a resource, select the resource in the list and then click the Increase or Decrease button to move the resource up or down in the list. This lets you change the load order of the resource relative to other cluster resources on the same node. You can also select a resource and then click the Selected button to reset the resource back to its default load order. 5 Click the Apply button to save changes made to resource priorities.
PAGE 760

Manual 3 4 5 6 99a 38 July 17, 2001 On the Cluster Object property page, select the Notification tab. Check or uncheck the Enable Cluster Notification Events check box to enable or disable e-mail notification. If you enable e-mail notification, add the desired e-mail address in the field provided and click the button next to the field to add the address to the list. Repeat this process for each address you want on the notification list.
PAGE 761

Manual 99a July 17, 2001 38 parser that lets you customize the message information for your specific needs. 5 Click the Apply button to save your changes. Cluster Node Properties You can view or edit the cluster node number or IP address of the selected node or view the context for the NetWare Server object. Using ConsoleOne 1 2 3 Select the Cluster object and right-click the desired cluster node on the right side of the ConsoleOne display screen. Click Properties.
PAGE 762

Manual 99a 38 July 17, 2001 Migrating Resources You can migrate resources to different servers in your cluster without waiting for a failure to occur. You might want to migrate resources to lessen the load on a specific server, to free up a server so it can be brought down for scheduled maintenance, or to increase the performance of the resource or application by putting it on a faster machine.
PAGE 763

Manual 99a July 17, 2001 38 Identifying Cluster and Resource States Both the Cluster State view in ConsoleOne and the Cluster Management link in NetWare Remote Manager give you important information about the status of servers and resources in your cluster. Cluster servers and resources display in different colors, depending on their operating state. When servers and resources are green, they are in a normal operating condition.
PAGE 764

Manual 44 99a 38 July 17, 2001 Resource State Description Possible Actions Alert Either the Start, Failover, or Failback mode for the resource has been set to Manual. The resource is waiting to start, fail over, or fail back on the specified server. Click the Alert status indicator and depending on the resource state, you will be prompted to Start, Failover, or Failback the resource. Comatose The resource is not running properly and requires administrator intervention.
PAGE 765

Manual 99a July 17, 2001 38 Resource State Description Possible Actions Running The resource is in a normal running state. Click the Running status indicator and choose to either migrate the resource to a different server in your cluster, or unload (offline) the resource. Unassigned There isn’t an assigned node up that the resource can be loaded on. Click the Unassigned status indicator and if desired, Offline the resource.
PAGE 766

Manual 99a 38 July 17, 2001 Readding a Node to a Cluster That Was Prevously in the Cluster 1 If necessary, install NetWare, including the latest service pack on the server using the same node name and IP address. 2 If the Cluster object for the server is still present, use ConsoleOne to delete the object. You can do this by going to the Cluster container, selecting the node in the right frame, and pressing Delete. 3 Run the Novell Cluster Services installation.
PAGE 767

Manual 99a July 17, 2001 38 Cluster Console Command Description ALERT {resource}{YES/NO} The resource start, failover, or failback mode is set to manual and the resource is waiting to start on a node, or fail over or fail back to another node. Specify the resource name in the command and use the YES or NO switch to specify whether or not you want the resource to fail over, fail back, or start.
PAGE 768

Manual 48 99a 38 July 17, 2001 Cluster Console Command Description OFFLINE {resource} Unloads the specified resource from the node where it is currently running. ONLINE {resource}{node name} Starts the specified resource on the most preferred node that is currently active. You can start the resource on a different node by specifying that node in the command. POOLS Lists the NSS pools on the shared disk system that are accessible by Novell Cluster Services.
PAGE 769

Manual 6 99a 38 July 17, 2001 NetWare Server Disks and Storage Devices Administration Guide NetWare Server Disks and Storage Devices Administration Guide 103-000179-001 August 30, 2001 Novell Confidential
PAGE 770

Manual 99a 38 July 17, 2001 Server Disks and Storage Devices With NetWare®, you can create up to four NetWare (or other) partitions on one hard disk. The primary storage and file system for NetWare is Novell® Storage ServicesTM (NSS). For information about the NSS file system, see Introducing Novell Storage Services in the Novell Storage Services Administration Guide. After you create partitions on your storage devices, you can create volumes where you place your data files.
PAGE 771

Manual 8 99a 38 July 17, 2001 NetWare Server Disks and Storage Devices Administration Guide NetWare Server Disks and Storage Devices Administration Guide 103-000179-001 August 30, 2001 Novell Confidential
PAGE 772

Manual 1 99a 38 July 17, 2001 Overview of Server Disks and Storage Devices Server hard disks and remote storage devices (such as tape drives and CDROM drives) are all managed by the NetWare® operating system. Hard disks are divided into partitions, including one DOS partition and at least one NetWare partition per server. A hard disk can also contain other partitions, such as a UNIX* partition.
PAGE 773

Manual 99a 38 July 17, 2001 Partitioning Disks You can divide a NetWare server hard disk into units called disk partitions. You can also leave free (unassigned) space on a disk. NOTE: A NetWare disk partition is not related to an NDS® partition. One of the server's hard disks must contain a DOS partition. This is the primary boot partition where server.exe is stored. You need only one boot partition per server. You also need to keep a SYS: volume.
PAGE 774

Manual Figure 2 99a 38 July 17, 2001 DOS Partition on First Disk, NetWare and Non-NetWare Partitions on Second Disk Disk 1 Disk 2 SYS: Volume (1 disk segment) Data1: Volume (1 disk segment) DOS Partition (Entire Disk) NetWare Partition Data2: Volume (1 disk segment) Hot Fix Redirection Area UNIX Figure 3 Non-NetWare Partition Disk with One NetWare Partition and Free Space Assigned to NSS Disk Free Space NSS File System NetWare Partition DOS Partition Logical Partitions Server hard disks can
PAGE 775

Manual 99a 38 July 17, 2001 If you do not use Hot Fix and mirroring, the entire physical partition is the logical partition. Figure 4 Logical and Physical Partitions on a Server Disk Disk NetWare Logical Partition Hot Fix Redirection Area NetWare Physical Partition DOS Partition The logical partition contains four redundant copies of the volume definition table (VDT). Each table contains a list of all volume segments in that partition.
PAGE 776

Manual 99a 38 July 17, 2001 Object Numbers Object numbers are hexadecimal numbers assigned to devices, adapters, media, partitions, and divisions of a partition (such as the Hot Fix redirection area). If you mirror partitions, each logical partition in the mirrored set has the same object number as the other partitions in the set. Object numbers are not sequential or persistent. New numbers can be assigned when the server is restarted.
PAGE 777

Manual 99a 38 July 17, 2001 Partition examples The following are example partition entries with the device information: Unpartitioned - D:0x1-1 Unpartitioned indicates that the device is unpartitioned. D:0x is the device number. -1 is the chunk number. (A unique number that this is the first unpartitioned segment on device 1.) NSS-P:0x15-1 NSS-P:0x15-1 indicates that this is an unassigned NSS partition. P:0x15 is the partition ID.
PAGE 778

Manual 99a 38 July 17, 2001 To see a list of storage devices and their names, execute the LIST STORAGE ADAPTERS command at the server console prompt. The screen lists each device adapter, followed by a list of devices driven by that adapter. In the following example, the first line identifies an IDE disk adapter.
PAGE 779

Manual 99a 38 July 17, 2001 Drivers for Host Adapters and Storage Devices All storage devices require drivers. The NetWare Peripheral Architecture (NWPA) divides device drivers into two kinds: a custom device module (CDM) that drives the device itself and a host adapter module (HAM) that drives the adapter has been attached to. The following are two types of drivers: Custom Device Module (CDM) CDMs drive storage devices, including autochangers, that are attached to the host adapter bus.
PAGE 780

Manual 99a 38 July 17, 2001 In the following illustration, several smaller disks are mirrored to partitions on one larger disk. Disk 4 Disk 3 Mirrored to partition 3 Disk 2 Mirrored to partition 2 NetWare Partition 2 Disk 1 Mirrored to partition 1 NetWare Partition 1 Disk 0 Mirrored to partition 0 NetWare Partition 3 NetWare Partition 0 To mirror partitions you must enable Hot Fix. For information about Hot Fix, see “Redirecting Bad Blocks” on page 18.
PAGE 781

Manual 99a 38 July 17, 2001 ranges in order to make the data area identical to the other partitions in the group.) Mirrored partitions must have the same sharable status. Partitions you add to a mirror group cannot be part of any other mirror group. They must be standalone Mirror objects. The partitions you add must include the Mirror and Hot Fix options. You select these options when you create the partition; you cannot add the options later.
PAGE 782

Manual 99a July 17, 2001 38 Read redirection occurs following a disk error during a read request. If the disk is mirrored, the system retrieves the data from the mirrored disk and redirects the data on the primary disk. If the disk isn't mirrored, the data is lost, and the block is marked as bad. Read-after-write-verify redirection occurs after data is written to disk. The data on disk is then read and compared to that in memory.
PAGE 783

Manual 99a 38 July 17, 2001 However, if Hot Fix is not enabled, the partition will not have the fault tolerance. Data on corrupted sectors of the disk will not be redirected to the Hot Fix Redirection Area. For instructions on how to specify no Hot Fix redirection area, see Creating a Partition in the Novell Storage Services Administration Guide.
PAGE 784

Manual 2 99a 38 July 17, 2001 Optimizing the File System Performance NetWare® provides several methods for improving the performance of your file system. For a list of general guidelines for conserving disk space and improving disk performance, see “Optimizing Storage Disk Capacity” on page 21. To improve disk reads and writes, see “Improving Disk Reads” on page 24 and “Improving Disk Writes” on page 26.
PAGE 785

Manual 99a 38 July 17, 2001 is created. If block suballocation has been disabled, enable it in ConsoleOneTM when you create a partition. For information about enabling block suballocation, see Creating a Partition in the Novell Storage Services Administration Guide. Once block suballocation is enabled, you cannot disable the feature without recreating the volume. If you use block suballocation, set your file block size to 64 KB.
PAGE 786

Manual 99a 38 July 17, 2001 prevent large volumes from mounting. As soon as possible, upgrade the system to a newer board that can access higher memory. For instructions on using the SETcommand, see SET in Utilities Reference. For instructions on using MONITOR, see MONITOR in Utilities Reference. Use a driver that supports scatter gather functionality. Provide at least one device large enough to hold a core dump of the server's memory. A core dump cannot span devices.
PAGE 787

Manual 99a 38 July 17, 2001 CD-ROM drives can create large index files. Don't use or mount the CD-ROM unless you have enough space. Limit the size of auditing files. (Auditing works only on traditional NetWare partitions.) Improving Disk Reads On a server that is read-intensive, the following procedures can improve the speed of disk reads. “Changing Concurrent Disk and Directory Writes for Faster Reads” on page 24.
PAGE 788

Manual 99a 38 July 17, 2001 5 Increase the value of Directory Cache Buffer Non Referenced Delay. This parameter specifies how long a directory entry must be cached before it can be overwritten. Increasing this value causes the system to allocate more directory cache buffers and thus speeds up directory access. If the parameter is currently set to the default value of 5.5 seconds, try setting the value to 60 seconds. 6 Press Esc until you return to Available Options.
PAGE 789

Manual 99a 38 July 17, 2001 Improving Disk Writes For a write-intensive server, the following procedures can improve the speed of disk writes. “Increasing the Number of Concurrent Writes” on page 26. “Changing Disk and Directory Caching for Faster Writes” on page 27. “Turning Off Read-After-Write Verification” on page 28.
PAGE 790

Manual 99a 38 July 17, 2001 Changing Disk and Directory Caching for Faster Writes Use this procedure if network users frequently make many small write requests and the server is slow to respond to the requests. 1 From the MONITOR Available Options, select Server Parameters > File Caching. For instructions on using MONITOR, see MONITOR in Utilities Reference. NOTE: You can also set file caching parameters with the SET command in MONITOR. 2 Increase the value of Dirty Disk Cache Delay Time.
PAGE 791

Manual 99a 38 July 17, 2001 NOTE: Increasing the number of concurrent directory cache writes decreases the speed of directory cache reads. Balance the speed of writes and reads to meet the needs or your users. If the parameter is currently at the default value of 10, try increasing the value to 25. The changed value is now persistent. 6 Press Esc until you return to Available Options. Turning Off Read-After-Write Verification Read-After-Write Verify is almost always provided by the hard disk.
PAGE 792

Manual 3 99a 38 July 17, 2001 File System Management It is important to monitor disk space regularly and keep a log to track disk usage over time. For instructions on checking disk space, see Viewing Storage Objects in the Novell Storage Services Administration Guide. Adding a hard disk to the server requires both installing and partitioning the disk, as well as loading disk drivers.
PAGE 793

Manual 99a 38 July 17, 2001 View a List of Adapters and Devices To see a list of server hardware devices, type the following at the server console prompt: LIST DEVICES To see a list of storage adapters and the devices they drive, at the server console prompt enter: LIST STORAGE ADAPTERS The screen lists each adapter, followed by a list of devices driven by that adapter.
PAGE 794

Manual 99a 38 July 17, 2001 3 Scroll to Disk Space and note the available disk space for the volume and record it in a log. 4 Press Tab to return to the list of Mounted Volumes. Check additional volumes as necessary. 5 Press Esc until you return to Available Options. 6 Repeat this procedure weekly for each volume. Checking for Disk Errors MONITOR indicates how many data blocks have been redirected by Hot FixTM because of bad sectors on the disk.
PAGE 795

Manual 99a 38 July 17, 2001 System Hot Fix Blocks: The number of blocks in the Hot Fix redirection area set aside for Hot Fix and Mirroring tables. These blocks are used to manage both Hot Fix and mirroring. The number of available Hot Fix blocks equals the total number of Hot Fix blocks, minus the used and system Hot Fix blocks. 4 Note the number of used Hot Fix blocks and compare it to the total number of blocks and the number of available blocks.
PAGE 796

Manual 99a 38 July 17, 2001 Procedure Use the following procedure to install an additional hard disk in a functioning NetWare server. 1 Follow the instructions that came with your hard disk to install the disk and associated hardware, such as a disk adapter and cable. If necessary, configure the computer to recognize the new disk Refer to the documentation that came with the computer for more information about configuration methods and requirements. 2 Start the server.
PAGE 797

Manual 99a 38 July 17, 2001 4 Select a volume that is on the disk you are replacing, click Dismount. Repeat this step for all volumes on the disk. 5 Click Media > Partitions. 6 Select a partition that is on the disk you are replacing, click Mirror. 7 Select a partition, click Remove. This removes the partition from the mirror group. Repeat steps 6 and 7 for each partition that is on the disk you are replacing. 8 Remove the hard disk and install the replacement.
PAGE 798

Manual 99a 38 July 17, 2001 IMPORTANT: Some drivers do not have a description file (a configuration file that's appended to the driver). These drivers have to be loaded manually at the system console. To load these drivers, follow the screen prompts or press F1 for help. For general information about .cdm and .ham modules, see “Drivers for Host Adapters and Storage Devices” on page 16.
PAGE 799

Manual 99a 38 July 17, 2001 If you have partitions from previous versions of NetWare that you are no longer using, you can delete them and create a new NetWare partition. (See “Deleting NetWare Partitions” on page 36 for more information.) WARNING: When creating a disk partition, never specify a partition size larger than the actual size of the disk. If you specify a larger size, NetWare will eventually try to use the excess disk space.
PAGE 800

Manual 99a 38 July 17, 2001 child to the object above it. In ascending order, parent objects appear immediately above the highlighted object. 2 Select the appropriate hard disk from the list. The Drive Status window appears. The Operating Status field indicates whether the device is activated or deactivated. 3 Press Enter to access the Operating Status options. 4 To change the operating status of the disk, highlight either Activate or Deactivate and press Enter.
PAGE 801

Manual 99a 38 July 17, 2001 1 From ConsoleOne, open the tree you want. 2 Right-click on the server object and select Properties. 3 Click Media > Partitions. 4 Select a Partition that contains the data you want to recover, click Mirror > Resync. This initiates the resynchronization process for the mirror group that contains the partition you selected. Managing Removable Media Devices Mounting a Removable Media Device Use this procedure to mount a removable media device, such as a CD-ROM drive.
PAGE 802

Manual 99a 38 July 17, 2001 4 Select Mount Drive. 5 Press Esc until you return to Available Options. Dismounting a Removable Media Device Use this procedure to dismount a removable media device, such as a CD-ROM device. 1 From the MONITOR Available Options, select Storage Devices. For instructions on using MONITOR, see MONITOR in Utilities Reference. A list of Registered Storage Objects appears. The device information associated with a highlighted storage device appears in the upper window.
PAGE 803

Manual 99a 38 July 17, 2001 A list of Registered Storage Objects appears. The device information associated with a highlighted storage device appears in the upper window. Check the Device Type field to verify the type of storage device. NOTE: Storage devices are listed in hierarchical order to reflect each object's dependencies. In descending order, each object is indented to indicate that it is a child to the object above it.
PAGE 804

Storage Management Services Administration Guide Novell NetWare 6 ® www.novell.
PAGE 805

Manual 99a July 17, 2001 38 Contents Preface 7 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 Overview 9 Backup Services . . . . . . . . . . . . . . . SMS Components . . . . . . . . . . . . Supported Storage Devices and Drivers . Storage Management Engine (SME) . . . Storage Management Data Requester . . Memory Requirements . . . . . . . . . . Backup Files . . . . . . . . . . . . . . . Backup Types . . . . . . . . . . . . . .
PAGE 806

Manual 99a Loading SBCON . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . Unloading SBCON . . . . . . . . . . . . . . . . . . . Loading NWBACK32 . . . . . . . . . . . . . . . . . . Exiting NWBACK32 . . . . . . . . . . . . . . . . . . . Backing Up Data . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . Backing Up from the Server . . . . . . . . . . . . . Backing Up from a Workstation . . . . . . . . . . .
PAGE 807

Manual 99a 38 July 17, 2001 Preface Novell® Storage Management ServicesTM (SMSTM) is a collection of software programs that provides backup and restore services. These services are performed by a collection of components that are independent of operating systems and hardware. You can backup SMS Targets such as Novell eDirectoryTM, binderies, the file system, cluster-enabled pools or an individual workstation's hard disk onto a media that can be stored off-site.
PAGE 808

Manual 8 99a 38 Storage Management Services Administration Guide Storage Management Services Administration Guide 103-000134-001 August 29, 2001 Novell Confidential July 17, 2001
PAGE 809

Manual 1 99a 38 July 17, 2001 Overview Backup services is an essential piece of the Novell® Storage Management ServicesTM (SMSTM) software, a collection of services that provides backup, restore, and data migration. These services are performed by various components and are independent of operating systems and hardware.
PAGE 810

Manual 99a 38 July 17, 2001 The following topics are discussed in this section: “SMS Components” on page 10 “Backup Types” on page 16 “Customizing Your Backup” on page 16 “Keeping a Backup Logbook” on page 21 “Preparing to Back Up” on page 22 “Backups and eDirectory” on page 23 “Backups and the File System” on page 27 “Backups and Clusters” on page 29 “Session Files” on page 37 SMS Components Storage Management Engine (SME) for backup and restore operations.
PAGE 811

Manual 99a 38 July 17, 2001 keeps the names of these workstations in an internal list and displays the list, allowing you to select a target for a backup or restore procedure. The SBCON process involves two machines: The host server is typically the NetWare server running the backup program. The SMS components will include the backup engine, the SMDR, the Storage Device Driver, the tape device, and the required Target Service Agents.
PAGE 812

Manual 99a 38 July 17, 2001 Supported Storage Devices and Drivers SBCON supports 0.25-inch, 4mm, and 8mm storage devices. If you are using 4mm tape, use only DDS (Digital Data Storage)-certified, computer-grade tapes. IMPORTANT: To ensure reliable operations, pretest all media storage devices that are not Novell certified with the appropriate NetWare device driver and SBCON backup and restore utility. Use the driver files recommended by your hardware manufacturer.
PAGE 813

Manual 99a 38 July 17, 2001 Storage Management Data Requester The Storage Management Data Requester (SMDR) is the communication module in the SMS architecture. It provides transparent access to SMS services in an intranet as it allows access to local or remote SMS services. The SMDR APIs are used by SBCON and other third-party applications as well. SMDR uses TCP Port Number 413. Features of SMDR The features of the SMDR 6.00 include the following: Protocol Independence: SMDR 6.
PAGE 814

Manual 99a 38 July 17, 2001 represents an instance of a predefined group class in the eDirectory schema. Any number of such groups can exist in eDirectory. The SMDR can become a member of one or more groups by registering its object's (SMS RPC object) context. When SMDR requires name resolution, it searches all members of the SMDR Group at SMDR Group Context. The SMDR Group Context and SMDR Group are specified in the SMDR.CFG file.
PAGE 815

Manual 99a 38 July 17, 2001 If NetWare Common Install is used to install SMS (see “Customizing the NetWare Server as the Backup Server” on page 43 for more information), this problem will not occur. If the SMDR is explicitly loaded for the first time, the screen for configuration information will not be hidden.
PAGE 816

Manual 99a 38 July 17, 2001 Backup Types SBCON has three types of backup sessions: Full backup—Backs up the entire file system of the selected target regardless of whether the data has changed since the last backup, and clears the Modify bit after the backup. Differential backup—Available only for the file system; backs up only data that has been changed since the last full or incremental backup. When you perform a differential backup, the modify bit is not cleared after the backup.
PAGE 817

Manual 99a July 17, 2001 38 Exclude and Include Options Whenever you perform a custom backup or restore, you can use the exclude and include options to select subsets of what you want to back up. Whether you use exclude or include usually depends on the size of the data you want to back up, compared to the size of the data you do not want to back up.
PAGE 818

Manual 99a 38 July 17, 2001 The same principle applies when you specify a directory with the include option. The figure below shows that all directories, subdirectories, and files under the NetUsers directory are included in the backup. All other areas of the file system structure are excluded from the backup. SYS HOME Public Mail System Login NetUsers Project A2ZCO Widget.exe Report January.prj February.prj March.prj Proposal Tessier.
PAGE 819

Manual SYS HOME 99a Public Mail System Login NetUsers Appl July 17, 2001 38 Project A2ZCO Widget.exe Report January.prj February.prj March.prj Proposal Tessier.Inc Nu_Artco Karl Mary Directories Subdirectories Files Thomas Directories Subdirectories Files Scan Data Sets You can specify a different type of data set to be scanned. A data set is a group of data that can be manipulated by SBCON.
PAGE 820

Manual SYS HOME 99a Public Mail System Login NetUsers Appl July 17, 2001 38 Project A2ZCO Widget.exe Report January.prj February.prj March.prj Proposal Tessier.Inc Nu_Artco Training Workbook Viewgraph Script Schedules June July August Karl Mary Thomas Manuals Widget.Co chapt.1 chapt.2 chapt.3 chapt.4 appx.A appx.B glossary index Acme.
PAGE 821

Manual 99a 38 July 17, 2001 Keeping a Backup Logbook Keep a hard copy log of your backups in case your online log and error files become corrupted.
PAGE 822

Manual 99a 38 July 17, 2001 Preparing to Back Up Careful planning can help you minimize the impact of data loss. Before you back up, consider the following: What should be backed up Where to back up Backup type Who should back up When to back up How to prepare for a backup How to track backup Open Files Backup TSA600.NLM supports backup of open files on Novell Storage Services (NSS) volumes if the CopyOnWrite feature is enabled.
PAGE 823

Manual 99a 38 July 17, 2001 Determining an Appropriate Backup Type Each type of backup has a different effect on the backup and restore process. When planning your backup schedule, consider all of the following variables before determining which schedule is right for you. Media usage and backup speed. This helps increase the speed of the restore. Restoring after incremental backups.
PAGE 824

Manual 99a 38 July 17, 2001 Distributed Database The network of servers that comprise an eDirectory tree structure continually exchange updates and other time-sensitive information. The eDirectory database exists as a set of files that are stored in the SYS: volume and are hidden so they are not accidentally tampered with or deleted. The eDirectory database files cannot be backed up, as was the case with bindery files in NetWare 3.12 or earlier versions.
PAGE 825

Manual 99a 38 July 17, 2001 Placeholder (Unknown) Objects Whenever insufficient information is known about an object, such as when one of its mandatory attributes is missing, eDirectory creates as a placeholder an Unknown object. During a restore session of the eDirectory database information, Unknown objects are created when restoring an object that has an access control list (ACL) or any other attribute that refers to other objects that do not currently exist in the eDirectory tree structure.
PAGE 826

Manual 99a 38 July 17, 2001 traffic during the backup process and improves performance when the backup program performs name resolution across the eDirectory tree structure. The version of TSANDS.NLM that ships with NetWare allows selective backup and restoration of an eDirectory tree structure. HINT: Not all third-party backup applications support this selective backup and restoration. Check with the application vendor for details on product features.
PAGE 827

Manual 99a 38 July 17, 2001 eDirectory backup to back up the portions of the tree for which they have rights. The network administrator assigns the Supervisor right to the backup administrators for the section of the eDirectory tree structure that they are responsible to back up. The network administrator then needs to create a TSANDS.CFG file that lists the fully distinguished names of the containers where each of the backup administrators' rights begin. The TSANDS.
PAGE 828

Manual 99a 38 July 17, 2001 Trustee Assignments Trustee assignments are stored as part of the file system as an ID. They are backed up by default when the file system is backed up with the SMS TSA software. If a User object is deleted and then re-created or restored, its object ID changes. This is why the SMS TSA module uses fully distinguished names for objects to back up the trustee rights from the file system.
PAGE 829

Manual 99a 38 July 17, 2001 Backups and Clusters Novell Cluster ServicesTM allows you to configure up to 32 NetWare servers into high-availability cluster, where resources can be dynamically switched or moved to any server in the cluster. Consolidation of applications and operations on a cluster has benefits such as lower costs, scalability, and increased availability. See the Novell Cluster Services documentation (http:// www.novell.com/documentation) for more information.
PAGE 830

Manual 99a 38 July 17, 2001 If a cluster server is chosen as the target, only noncluster volumes will be backed up. You have to back up each pool individually. You might abort an ongoing backup job with the intention of resubmitting the same job later. In such situations, the job will not restart from where it was terminated; it will restart from the beginning. For more information, see “Backing Up Cluster-enabled Pools from the Server” on page 56.
PAGE 831

Manual 99a 38 July 17, 2001 The TSA packages data from the target and presents it to the SME in a generic format. This allows one SME to interact with many types of TSAs. NetWare 6 provides TSA600.
PAGE 832

Manual 99a 38 July 17, 2001 How SMS Restores Data During a restore session, SBCON reads the backup storage media, and the Target Service Agent (TSA) compares the media data set to the existing hard disk data set.
PAGE 833

Manual BEGIN 99a July 17, 2001 38 END Go to backup session on storage media. no Is there another data set to read? yes Read data set. Overwrite data set? Is the data set to be renamed yes only if newer no yes no ignore Rename the dataset Is data set a subset of what you´re restoring? restore Compare date of data set on media to date of data set on disk.
PAGE 834

Manual 99a 38 July 17, 2001 Restore Options For a custom restore session, you can specify exactly which data to restore. Several options work together to allow you maximum flexibility in your restore session.
PAGE 835

Manual 99a 38 July 17, 2001 Restoring eDirectory and the File System The only way to ensure that your eDirectory database can be fully restored is through partition replication, with replicas of the entire database on multiple servers. On a single-server network, you need to rely more heavily on backing up the data because you do not have replicas to restore information.
PAGE 836

Manual 99a 38 July 17, 2001 stored on volume SYS:, losing SYS: is equivalent to removing NetWare and eDirectory from the file server. You must reinstall NetWare and eDirectory before you restore your data. The procedures for this scenario are divided into two cases: Loss of the only server in a single-server network. Loss of a single server in a multiple-server network. Single-Server Network In a single-server network, server failure brings all network operations to a halt.
PAGE 837

Manual 99a 38 July 17, 2001 5. Restore the file system. (See “Restoring Data” on page 62 and “Custom File System Restore” on page 74.) 6. Restore any replicas that were removed from the server. Loss of the Entire eDirectory Tree If all servers on a network are destroyed because of a disaster, you must perform a complete restore of NetWare, eDirectory, and file system data.
PAGE 838

Manual 99a 38 July 17, 2001 Log and Error Files The files of the backup session are stored in a default directory (such as SYS:SYSTEM\TSA\LOG). If you prefer, you can create your own directory for the log and error files as long as it resides on the host server. The files of the restore session are stored in the directory (SYS:SYSTEM\TSA\RESTORE). You cannot modify the location for the files.
PAGE 839

Manual 99a 38 July 17, 2001 Error File The error file is created on the host server the first time a particular set of data is backed up. It contains a list of any errors that occurred during a backup or restore session. This file contains the following: The session date and time and the description you entered. The target from which the data was backed up for a backup session. The target that was backed up and the location on the server where the data was restored to during a restore session.
PAGE 840

Manual 40 99a 38 Storage Management Services Administration Guide Storage Management Services Administration Guide 103-000134-001 August 29, 2001 Novell Confidential July 17, 2001
PAGE 841

Manual 2 99a 38 July 17, 2001 Setting Up In addition to being able to back up data from a server with SBCON, you can use a Windows 95, 98, 2000 or Windows NT workstation to perform your backups using the graphical interface. This chapter discusses the following: How to customize the NetWare server as the backup server. See “Customizing the NetWare Server as the Backup Server” on page 43. How to load the backup software.
PAGE 842

Manual 99a 38 July 17, 2001 SBCON Guidelines Before you set up and begin backups, follow these guidelines to make backups easier and to avoid problems later. Log in. You will have limited success backing up and restoring if you log in without the Supervisor right. For security reasons, many SBCON options are limited to the network administrator. Reserve disk space for temporary files.
PAGE 843

Manual 99a 38 July 17, 2001 Before Loading the Backup Software Before you load the backup software on the server or on a Windows machine, you need to configure a server to execute your backups. Determine the following: The tree to which the server belongs which must be made the current tree The full eDirectoryTM context of the server Before Running the Backup Software Before backing up software, in general you must: Load the controller and storage device drivers on the server.
PAGE 844

Manual 99a 38 July 17, 2001 The SMDR Group object is where all NetWare and workstation SMDRs are registered for name resolution purposes. 6 Accept the default name of the Backup Queue where all backup jobs will be submitted, or enter a new name and context. Loading Controller and Storage Device Drivers on the Server Controller and device drivers control the mechanical operation, such as read, write, forward, back, and stop of various storage devices and media.
PAGE 845

Manual 99a July 17, 2001 38 Loading the Target Service Agents Target Service Agents are loaded on servers and workstations. If you want to back up a server, load the TSA on the server. Ensure that the controllers and device drivers are loaded.
PAGE 846

Manual 99a 38 July 17, 2001 Loading the files when the server starts. Place the commands in the server's STARTUP.NCF, and in the workstation's NET.CFG file, AUTOEXEC.BAT file (for DOS), or Startup folder (for OS/2). Loading SBCON You can load SBCON from the server command line. If you use NWBACK32 on a client, you do not need to load SBCON. 1 At the server console, enter SMSSTART TSA600.NLM, TSAPROXY.NLM, and SMDR.NLM modules are loaded with default configuration values. SBSC.NLM, QMAN.NLM, SMSDI.
PAGE 847

Manual 99a 38 July 17, 2001 Unloading SBCON To ensure maximum memory utilization and throughput, you should unload backup software and other Storage Management ServicesTM (SMSTM) modules when you are finished performing your backup. That way, more memory will become available on your host or target. 1 Exit SBCON from the Main Menu. Press Esc until you reach the SBCON Main Menu; then press Esc again and confirm the prompt.
PAGE 848

Manual 99a 38 July 17, 2001 3 Run NWBACK32.EXE from SYS:PUBLIC. The following screen appears. You are now ready to back up data. Go to “Backing Up Data” on page 49 to continue. Exiting NWBACK32 1 Exit NWBACK32 from the Quick Access window. 2 Unload all the modules loaded on the server by entering the following command at the server console: SMSSTOP Unloads all the previously loaded SMS modules.
PAGE 849

Manual 99a 38 July 17, 2001 Backing Up Data You can use SBCON to create a tape backup of the eDirectory database or of the file system on your servers or workstations. The prerequisites listed here use SBCON as the Storage Management Engine (SME). Prerequisites Understand the process for loading SBCON. See “Loading SBCON” on page 46 Ensure that you know the workstation password if you are backing up a workstation.
PAGE 850

Manual 99a 38 July 17, 2001 Ensure that media is inserted into your storage device. You can back up your data two ways: from a server using SBCON or from a Windows workstation using NWBACK32. Backing Up from the Server When you back up your data from one server to a target server or workstation, you should use the command line. 1 Load the SBCON modules. See “Loading SBCON” on page 46. 2 Click Main Menu > Job Administration > Backup.
PAGE 851

Manual 99a 38 July 17, 2001 4 Select a target from the Target Services list. The following table describes the targets that can be selected for backup.
PAGE 852

Manual 99a 38 July 17, 2001 This is a descriptive name of the job, which will help you identify the specific backup session; if a restore is necessary, you can easily identify the session you need. There is no special requirement for what to enter as the session description. HINT: You might want to include the full path of the data (for example, SYS:HOME\REPORTS\JULY.02) which you will need to know if a restore session is necessary. 10 Click Device/Media Name and select a device.
PAGE 853

Manual 99a 38 July 17, 2001 14 To return to the Main Menu, press Esc until you back out to the Main Menu. 15 To exit SBCON, press Esc again and answer the confirmation prompt. Customizing Backup You can customize your backup using the Advanced Backup Options form when you use SBCON at the server to launch your backup program. This form allows you to specify exactly what you want to back up data. It could be the server, the eDirectory database, workstation, directory, or file.
PAGE 854

Manual 99a 38 July 17, 2001 3 Select Subsets of What To Backup. The default setting means that everything in the Subsets of What You Want to Backup screen is backed up. Include/Exclude TSA Resources—Includes or excludes resources such as servers or volumes. Include/Exclude Directories—Includes or excludes directories. Include/Exclude Files—Includes or excludes files. Include/Exclude path/files—Includes or excludes pathnames and files. 4 Select Scan Options.
PAGE 855

Manual 99a 38 July 17, 2001 The day, month, or year you enter should not be the actual date when you want the job to run; rather, it is the duration after which the job gets executed.
PAGE 856

Manual 99a 38 July 17, 2001 4 Select where you want your backup data to go. 4a Double-click Where to Backup. 4b Change to the correct eDirectory tree structure and context by clicking the Change to Context button on the toolbar. 4c Double-click Queues. 4d Select a Queue object from the list. 4e Right-click the server to open the drop down box. 4f Click Submit the Job. This step allows you to submit the job to a queue on the chosen server or on the chosen media type. Queue.
PAGE 857

Manual 99a 38 July 17, 2001 5 When prompted, enter the username (and context, if required) for the target. If SBCON rejects the username you entered, you probably need to include the context where the User object is located. For example, instead of entering ADMIN as the username, enter .CN=ADMIN.O=company_name or .ADMIN.company_name.
PAGE 858

Manual 99a 38 July 17, 2001 If the storage media does not have a label, SBCON displays a message saying that the media cannot be identified. Set the label before selecting it for a backup job. 11 Select Advanced Options and set the desired values for all the fields. For more details, see “Customizing Backup” on page 53. NOTE: If you set Enable Auto Recovery to NO in Cluster Options, the remaining options become invalid. 12 Select Append Session.
PAGE 859

Manual 99a 38 July 17, 2001 Backing Up a Workstation To back up the workstation (the target), a Target Service Agent (TSA) must be loaded on the workstation. (See “Loading the Target Service Agents” on page 45.) You can select the directories to back up or back up the entire workstation. Windows 95 and 98 Workstation Make sure that the W95TSA is installed and configured. It is a part of the Novell Client modules (checkbox for Target Service Agent).
PAGE 860

Manual 99a 38 July 17, 2001 Windows 2000 and Windows NT Workstation Make sure that the NT TSA is installed and configured. It is a part of the Novell Client modules (checkbox for Novell Target Service Agent). The Windows NT TSA has two parts: TSA Service (TSAMAIN.EXE) is a service that waits for and acts when there is a request from the backup engine. TSAPrefs (TSAPREFS.EXE) allows an NT administrator to set preferences and monitor the activities of the TSA Service.
PAGE 861

Manual 99a 38 July 17, 2001 Changing Your Target Any time you are performing a series of backup or restore sessions, you might need to change your target. This can be easily done from the SBCON Main Menu either at the command line or from the Windows workstation using NWBACK32. If you do not specify a new target, SBCON automatically selects the target used during the last session and continues without asking you to make a selection.
PAGE 862

Manual 99a 38 July 17, 2001 Restoring Data Use SBCON to restore information from tape backup. These procedures use SBCON as the Storage Management Engine (SME). Know the username and password for the target server or workstation to which you want to restore data. Know the session description that you want to restore. You can get this information from your session log and error files. (See “Session Files” on page 37.
PAGE 863

Manual 99a 38 July 17, 2001 3 Load SBCON. See “Loading SBCON” on page 46. 4 Select Main Menu > Job Administration > Restore. The Restore Options screen appears. 5 Select Target Service and then the NetWare server running your backup and restore Target Services Agent. This is the name of the server or workstation on which you want to restore your data. Before selecting it, you must load the correct TSA. See “Loading the Target Service Agents” on page 45.
PAGE 864

Manual 99a 38 July 17, 2001 Target Service to Restore Dataset to Select Workstation The workstation's host server and then the workstation Server-specific information The server whose server-specific information you want to restore and then the file system to restore 6 When prompted for the target username, enter your username (and context if required) as the network administrator for the target.
PAGE 865

Manual 99a 38 July 17, 2001 volume without compression, the file is corrupted and no error message is displayed. 11 Specify the path to the session log file of the session you want to restore. Use one or more of the following methods: Press Enter to accept the default; then go to Step 12 on page 65. Press Insert to select from a list of directories, press Esc to return to the previous window, and then go to Step 12 on page 65.
PAGE 866

Manual 99a 38 July 17, 2001 The Esc key allows you to exit SBCON one screen at a time until you reach the Main Menu. If you want to exit SBCON, answer the confirmation prompt. NOTE: To unload SBCON and applicable Target Service Agents, see “Unloading SBCON” on page 47. Customizing Restore Using the Advanced Restore Options form at the server, you can perform a custom restore of the database you need. 1 Select Main Menu > Job Administration > Restore. The Restore Options screen appears.
PAGE 867

Manual 99a 38 July 17, 2001 The screen lists major and minor resources. Default indicates that none of that type of subset has been specified. 6 To specify a subset, do the following: 6a Select any item on the screen. 6b Edit the Include or Exclude screens using Insert and Enter. 6c Press Esc to save changes. 6d To view a list of values associated with major TSA resources (for example, server or volumes) select either the include or exclude line. The Selection List Options form appears.
PAGE 868

Manual 99a 38 July 17, 2001 Restoring Data from a Workstation When you restore data, you are copying your backed up data to a server or workstation. 1 Run NWBACK32. See “Loading NWBACK32” on page 47. You can run the NWBACK32 program (NWBACK32.EXE) from SYS:PUBLIC. 2 At the Quick Access window, click Restore. 3 Click What you Want to Restore. 3a Double-click What to Restore. 3b Select the context. 3c Double-click Queues and select the queue. 3d Double-click Servers and select a server.
PAGE 869

Manual 99a 38 July 17, 2001 Restoring eDirectory The procedures in the following sections are performed at the beginning of the restore process.
PAGE 870

Manual 99a 38 July 17, 2001 Make sure disk partitions are at least as large as they were before, and that the volumes are defined as before. 3 Restore eDirectory using “Customizing Restore” on page 66. Restoring Volume SYS: in a Multiple-Server Network To restore SYS: volumes on several servers, do the following. 1 Restore the server-specific eDirectory information file (SERVDATA.
PAGE 871

Manual 99a 38 July 17, 2001 4e Select Remove This Server from the Replica Ring. 4f Enter the supervisor name and password. 4g Select Yes to continue. 5 Exit DSREPAIR. 6 Reinstall NetWare. 6a Begin the installation. 6b When prompted for DS install, select Create a New DS Tree and complete the installation. 6c Load NWConfig and remove DS. 6d Install DS, when prompted for DS install and select Install into an Existing Tree. 6e When prompted to choose a eDirectory tree structure, press F5.
PAGE 872

Manual 99a 38 July 17, 2001 Restoring the Entire eDirectory Tree Structure To restore an entire network from a full backup in a multiple-server environment, do the following: 1 Reinstall NetWare on the first server. By default, this server will hold the master replica of the [Root] partition. When NWCONFIG asks for the names of Organization objects immediately under the [Root] object, use the same names that existed before in the eDirectory tree.
PAGE 873

Manual 99a 38 July 17, 2001 eDirectory Restore Session Types You can choose to restore eDirectory in one of the following ways: “Single Server or an Entire Tree Restore” on page 73 “Custom eDirectory Restore” on page 73 “Custom File System Restore” on page 74 “Server-Specific Information Restore” on page 76 “Single File or Directory Restore” on page 76 Single Server or an Entire Tree Restore 1 Restore the entire eDirectory session from your SMS backup.
PAGE 874

Manual 99a 38 July 17, 2001 If you do not want to overwrite the parent or child that exists on the hard disk, regardless of whether the existing version or the backed-up version has the latest date, select the option (parent or child or both), and enter N. 6 Continue through Step 14 on page 65 to Step 19 on page 65. Custom File System Restore To perform a custom file system restore, do the following. 1 Enter SBCON at the server console prompt.
PAGE 875

Manual 99a 38 July 17, 2001 Follow these important rules about restoring to a new location: When you specify a particular portion of the file system structure as the source location, it does not necessarily mean that this will be the only data restored. You can influence what is restored by using the Include and Exclude options on the Choose Subsets Of What You're Restoring screen (Job Administration > Restore Options > Advanced Restore Options > Subsets of What to Restore).
PAGE 876

Manual 99a 38 July 17, 2001 If you want to overwrite the child that exists on the hard disk only if the date of the backed-up copy on the media is later than the date of the copy on the hard disk, select Overwrite Existing Child and select the option. 8 Continue through Step 15 on page 65 to Step 19 on page 65. Server-Specific Information Restore To view and restore server information, do the following.
PAGE 877

Manual 99a 38 July 17, 2001 3 Press Insert and enter the name space for the name space format you used when entering the file or directory name. The name space allows SBCON to correctly interpret the path information entered earlier in this menu in either the directory field or the location field. IMPORTANT: If files are restored to a new location, the name spaces must be the same or an error message will occur.
PAGE 878

Manual 99a 38 July 17, 2001 Completing the eDirectory Restore If you restored the eDirectory database to volume SYS:, you should complete the restoration for the following to make sure the eDirectory database is working properly: Volume Other than SYS: To finish restoring eDirectory on a volume other than SYS:, do the following. 1 Bring the server up.
PAGE 879

Manual 99a 38 July 17, 2001 Entire Tree To finish restoring eDirectory on the tree, do the following. 1 Restore the file system information to each server following “Restoring Data” on page 62. 2 Re-create partitions and replicas. 3 (Optional) Verify proper restoration of the data, trustee assignments, file ownership, and other related information by spot-checking some of the restored directories and files.
PAGE 880

Manual 99a 38 July 17, 2001 identifies the file server on which the queue directory resides. This information is used to determine the physical location of the resource. The specifics of restoring objects vary depending on what type of object is involved and whether the object's dependencies are physical entities (servers and volumes) or logical entities. In some cases, you can simply restore an object and everything will work fine.
PAGE 881

Manual 3 99a 38 July 17, 2001 Managing After you install and load SBCON, you can manage your jobs, data, devices, reports, and so on either from the server or workstation. Though the screens might look different, you can perform the same tasks in each interface. Be sure to read “Prerequisites for SBCON Tasks” on page 81 before performing any tasks in this section.
PAGE 882

Manual 99a 38 July 17, 2001 Jobs The backup or restore jobs created by you can be administered anytime. You can delete, hold, reschedule, abort, or enable a job. Administering Jobs Jobs can be managed either from the server or from the workstation. From the Server On the SBCON Main Menu at the server, the Current Job List option gives you a job management facility where you can delete a job, hold a job, or enable it if it has been disabled after a job failure.
PAGE 883

Manual 99a 38 July 17, 2001 Dynamic properties contains data that indicates how much data has been backed up along with the filenames. This dialog box appears when a job is running and SBSC is loaded on the server. Enable job allows you to start a job that has been disabled. Delete the job allows you to remove a job. Start/Hold the job allows you to start a job that is in the hold state or place it on hold if it is not in a hold state.
PAGE 884

Manual 99a 38 July 17, 2001 Viewing Job Details This screen gives you all the details of the job you submitted including job name, the time the job was submitted, and the time the job should be executed. You can also schedule the job to run at a predefined time again after its execution. You can view job details from the server or a workstation. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page 81.
PAGE 885

Manual 99a 38 July 17, 2001 Serviced By—This indicates the name of the server where the job is to be executed. From a single server, you can submit jobs to various servers. This field indicates which job is serviced by which server. This field is active only when the job is active; otherwise, it indicates None. Scheduling Options—You can schedule the same job to run at another time. For information, see “Customizing Backup” on page 53.
PAGE 886

Manual 99a 38 July 17, 2001 From a Workstation 1 At the Quick Access window, click Job Administration. 2 Double-click the context. 3 Double-click Queues. 4 Select the job to place on hold. 5 Right-click the job and then click Start/Hold the Job. (Optional) You can also hold the job using the toolbar. Click Job Administration > Start/Hold the Job.
PAGE 887

Manual 99a 38 July 17, 2001 From the Server 1 Select Main Menu > Storage Device Administration. 2 Select a device and press Insert. 3 Select Utilities > Device Status. The Device Status screen is displayed listing the following information: Current Operation—Indicates whether the device is currently reading, writing, formatting the media, or none of these. Device Mode—Indicates whether the device is selected for reading, writing, or both.
PAGE 888

Manual 99a 38 July 17, 2001 You can change a device label from the server or a workstation. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page 81. From the Server 1 Select Main Menu > Storage Device Administration. 2 Select a device name and press Insert. 3 Select Utilities > Change the Device Label. 4 Enter the new name in the field. 5 Press Esc as required to return to the Main Menu.
PAGE 889

Manual 99a 38 July 17, 2001 From the Server 1 Select Main Menu > Storage Device Administration. A list of devices is displayed. If no device is displayed in the list, run LIST DEVICES at the server prompt. 2 Select a device name and press Enter. The List of Media screen appears displaying the following information: Slot—The slot number given by the manufacturer. Media name—The name of the media, which can be changed using the Utilities menu. See “Erasing or Retaining Media” on page 90.
PAGE 890

Manual 99a 38 July 17, 2001 Erasing or Retaining Media This task erases media headers, erases all data on the media, or retentions media in tape devices. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page 81. The following table describes all media options. Option Explanation Change the Media Label This is permanent. Blank media (tape) does not have a label. Before submitting a job to the media, you need to label it.
PAGE 891

Manual 99a 38 July 17, 2001 3 Double-click Queues. 4 Double-click the preferred queue. 5 Double-click Servers. 6 Double-click the preferred server. 7 Double-click Devices. 8 Right-click the media > click Erase Media [or] Retension. (Optional) You can also use the toolbar. Click Device Administration > Media > Erase Media [or] Retension. Checking the Media Status in a Device This task lets you check the status of a particular media type from either the server or a workstation.
PAGE 892

Manual 99a 38 July 17, 2001 Media mode—Whether the media is selected for reading, writing or both, or whether the mount request is pending. Media type—The type of media in the device, such as 4mm DDS (Digital Data Storage) tape, or 8mm tape. Total capacity—The total capacity of the media, if known. Sometimes it is not displayed, depending on the media manager. The type of media manager controls the display of the total capacity of the media.
PAGE 893

Manual 99a 38 July 17, 2001 Log and Error Files SBCON keeps a list of all the log and error files, which show specific information about the backup and restore session. See “Session Files” on page 37 for more information. You can manage these files as follows: View information contained in the log and error files. See “Viewing a Log File” on page 93 and “Viewing an Error File” on page 94 for information. Create these files. See “Creating Log and Error Files” on page 96 for information.
PAGE 894

Manual 99a 38 July 17, 2001 To change the directory, delete the existing directory path and type a new one, and then go to Step 3 on page 94. You can also press Insert during this process to select existing parts of the path from a list. The backup log displays all supported name space types. The DOS name space is the first in the group. A right-angle bracket (>) appears next to the file creator's name space type.
PAGE 895

Manual 99a 38 July 17, 2001 From the Server 1 From the SBCON Main Menu, select Log File Administration > View an Error File. 2 If necessary, set the location of the log and error files for a backup session. (This option is not supported for a restore session.) To set the location, use one or more of the following methods: Press Enter to accept the default location, and then go to Step 3 on page 95.
PAGE 896

Manual 99a 38 July 17, 2001 4 Double-click the preferred queue. 5 Double-click Servers. 6 Right-click the preferred server. 7 Select Error Report. Creating Log and Error Files If you do not know what is on the media, or you have lost or deleted the log and error files, you can re-create them. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page 81. To create a log or error file, see “Creating Session Files” on page 98.
PAGE 897

Manual 99a 38 July 17, 2001 Deleting the Log Files SBCON allows you to overwrite sessions and reuse storage media. When you delete the log file for a session using the following procedure, you automatically delete the corresponding error file as well. To prevent outdated session information from taking up disk space and to help prevent confusion when you select sessions to view or restore, delete the session log files for any session that has been overwritten.
PAGE 898

Manual 99a 38 July 17, 2001 Creating Session Files If you do not know what is on the media, or you have lost or deleted the log and error files, you can re-create them from either the server or a workstation. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page 81. From the Server 1 From the SBCON Main Menu, select Job Administration > Create Session File. The Session Files Options screen appears. 2 Enter a descriptive name.
PAGE 899

Manual 99a 38 July 17, 2001 9 Select the preferred media. 10 Right-click the job and select Submit the Job. 11 Check the appropriate fields in the Submission of Job dialog box. Verifying Backup Data This option allows you to check the data on the media from either the server or a workstation to make sure it has been backed up properly, and to check later that the data is valid and can be restored.
PAGE 900

Manual 99a 38 July 17, 2001 From a Workstation 1 At the Quick Access window, click Verify. 2 Double-click the context if necessary. 3 Double-click Queues. 4 Double-click the preferred queue. 5 Double-click Servers. 6 Double-click the preferred server. 7 Double-click Devices. 8 Double-click the preferred device. 9 Right-click the preferred media. 10 Select Submit the Job. 11 In the Submission of Job dialog box, click the session. 12 Click Finish.
PAGE 901

Manual 4 99a 38 July 17, 2001 Optimizing This chapter discusses the following topics: Whether you should compress your files before backup. See “Compressed Files” on page 101. How to increase speed when backing up your files. See “Host Server Performance” on page 102. How to enhance or optimize server performance. See “Setting Minimum Packet Receive Buffers” on page 103. How to synchronize memory between your media and your server. See “Setting Reserved Buffers Below 16 MB” on page 103.
PAGE 902

Manual 99a 38 July 17, 2001 To help you make a decision about whether to compress or decompress your backed up data, follow these guidelines: Backups are faster if files already compressed are left compressed. Compression is not supported in some environments (such as a NetWare 3.11 server, a DOS workstation, or Novell Storage ServicesTM). If you intend to restore a file that is currently compressed to an environment that does not support compression, back it up in a decompressed state.
PAGE 903

Manual 99a 38 July 17, 2001 Setting Minimum Packet Receive Buffers Packet receive buffers represent the space in the server memory dedicated to handling network traffic. If the buffers are set too low, the server performance may be degraded. To reset the packet receive buffers at the server console prompt, include the following SET command in the STARTUP.NCF file: SET MINIMUM PACKET RECEIVE BUFFERS = X The x represents the number of buffers. Set two buffers for each user on the system.
PAGE 904

Manual 99a 38 104 Storage Management Services Administration Guide Storage Management Services Administration Guide 103-000134-001 August 29, 2001 Novell Confidential July 17, 2001
PAGE 905

Manual 5 99a 38 July 17, 2001 Troubleshooting Common Backup Problems The media owner is unidentified Possible Cause: Action: Media is blank or was written in a non-SIDF format. See “Checking the Media Status in a Device” on page 91. Backup speed is slow Possible Cause: Action: Compressed files are being backed up in a decompressed format. See “Compressed Files” on page 101. Restore speed is slow Possible Cause: File compression and SBCON are running at the same time.
PAGE 906

Manual 99a 38 July 17, 2001 Data is corrupted, but no error message was given Possible Cause: Action: Compressed files were restored to a volume without compression. See Step 10 on page 64. You (the network administrator) can't back up a workstation Possible Cause: The /Password option is set and is denying access to data on the workstation. Action: See “Setting Rights to Back Up Portions of the eDirectory Tree” on page 26.
PAGE 907

Manual 99a July 17, 2001 38 Files were restored but the error file contains a message specifying which name space formats were not restored Possible Cause: Action: The file attributes and name space formats are not configured on the volume you restored to. Check to make sure you selected the correct name space.
PAGE 908

Manual 99a 38 108 Storage Management Services Administration Guide Storage Management Services Administration Guide 103-000134-001 August 29, 2001 Novell Confidential July 17, 2001
PAGE 909

Storage Management Services Administration Guide Novell NetWare 6 ® www.novell.
PAGE 910

Manual 99a July 17, 2001 38 Contents Preface 7 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 Overview 9 Backup Services . . . . . . . . . . . . . . . SMS Components . . . . . . . . . . . . Supported Storage Devices and Drivers . Storage Management Engine (SME) . . . Storage Management Data Requester . . Memory Requirements . . . . . . . . . . Backup Files . . . . . . . . . . . . . . . Backup Types . . . . . . . . . . . . . .
PAGE 911

Manual 99a Loading SBCON . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . Unloading SBCON . . . . . . . . . . . . . . . . . . . Loading NWBACK32 . . . . . . . . . . . . . . . . . . Exiting NWBACK32 . . . . . . . . . . . . . . . . . . . Backing Up Data . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . Backing Up from the Server . . . . . . . . . . . . . Backing Up from a Workstation . . . . . . . . . . .
PAGE 912

Manual 99a 38 July 17, 2001 Preface Novell® Storage Management ServicesTM (SMSTM) is a collection of software programs that provides backup and restore services. These services are performed by a collection of components that are independent of operating systems and hardware. You can backup SMS Targets such as Novell eDirectoryTM, binderies, the file system, cluster-enabled pools or an individual workstation's hard disk onto a media that can be stored off-site.
PAGE 913

Manual 8 99a 38 Storage Management Services Administration Guide Storage Management Services Administration Guide 103-000134-001 August 29, 2001 Novell Confidential July 17, 2001
PAGE 914

Manual 1 99a 38 July 17, 2001 Overview Backup services is an essential piece of the Novell® Storage Management ServicesTM (SMSTM) software, a collection of services that provides backup, restore, and data migration. These services are performed by various components and are independent of operating systems and hardware.
PAGE 915

Manual 99a 38 July 17, 2001 The following topics are discussed in this section: “SMS Components” on page 10 “Backup Types” on page 16 “Customizing Your Backup” on page 16 “Keeping a Backup Logbook” on page 21 “Preparing to Back Up” on page 22 “Backups and eDirectory” on page 23 “Backups and the File System” on page 27 “Backups and Clusters” on page 29 “Session Files” on page 37 SMS Components Storage Management Engine (SME) for backup and restore operations.
PAGE 916

Manual 99a 38 July 17, 2001 keeps the names of these workstations in an internal list and displays the list, allowing you to select a target for a backup or restore procedure. The SBCON process involves two machines: The host server is typically the NetWare server running the backup program. The SMS components will include the backup engine, the SMDR, the Storage Device Driver, the tape device, and the required Target Service Agents.
PAGE 917

Manual 99a 38 July 17, 2001 Supported Storage Devices and Drivers SBCON supports 0.25-inch, 4mm, and 8mm storage devices. If you are using 4mm tape, use only DDS (Digital Data Storage)-certified, computer-grade tapes. IMPORTANT: To ensure reliable operations, pretest all media storage devices that are not Novell certified with the appropriate NetWare device driver and SBCON backup and restore utility. Use the driver files recommended by your hardware manufacturer.
PAGE 918

Manual 99a 38 July 17, 2001 Storage Management Data Requester The Storage Management Data Requester (SMDR) is the communication module in the SMS architecture. It provides transparent access to SMS services in an intranet as it allows access to local or remote SMS services. The SMDR APIs are used by SBCON and other third-party applications as well. SMDR uses TCP Port Number 413. Features of SMDR The features of the SMDR 6.00 include the following: Protocol Independence: SMDR 6.
PAGE 919

Manual 99a 38 July 17, 2001 represents an instance of a predefined group class in the eDirectory schema. Any number of such groups can exist in eDirectory. The SMDR can become a member of one or more groups by registering its object's (SMS RPC object) context. When SMDR requires name resolution, it searches all members of the SMDR Group at SMDR Group Context. The SMDR Group Context and SMDR Group are specified in the SMDR.CFG file.
PAGE 920

Manual 99a 38 July 17, 2001 If NetWare Common Install is used to install SMS (see “Customizing the NetWare Server as the Backup Server” on page 43 for more information), this problem will not occur. If the SMDR is explicitly loaded for the first time, the screen for configuration information will not be hidden.
PAGE 921

Manual 99a 38 July 17, 2001 Backup Types SBCON has three types of backup sessions: Full backup—Backs up the entire file system of the selected target regardless of whether the data has changed since the last backup, and clears the Modify bit after the backup. Differential backup—Available only for the file system; backs up only data that has been changed since the last full or incremental backup. When you perform a differential backup, the modify bit is not cleared after the backup.
PAGE 922

Manual 99a July 17, 2001 38 Exclude and Include Options Whenever you perform a custom backup or restore, you can use the exclude and include options to select subsets of what you want to back up. Whether you use exclude or include usually depends on the size of the data you want to back up, compared to the size of the data you do not want to back up.
PAGE 923

Manual 99a 38 July 17, 2001 The same principle applies when you specify a directory with the include option. The figure below shows that all directories, subdirectories, and files under the NetUsers directory are included in the backup. All other areas of the file system structure are excluded from the backup. SYS HOME Public Mail System Login NetUsers Project A2ZCO Widget.exe Report January.prj February.prj March.prj Proposal Tessier.
PAGE 924

Manual SYS HOME 99a Public Mail System Login NetUsers Appl July 17, 2001 38 Project A2ZCO Widget.exe Report January.prj February.prj March.prj Proposal Tessier.Inc Nu_Artco Karl Mary Directories Subdirectories Files Thomas Directories Subdirectories Files Scan Data Sets You can specify a different type of data set to be scanned. A data set is a group of data that can be manipulated by SBCON.
PAGE 925

Manual SYS HOME 99a Public Mail System Login NetUsers Appl July 17, 2001 38 Project A2ZCO Widget.exe Report January.prj February.prj March.prj Proposal Tessier.Inc Nu_Artco Training Workbook Viewgraph Script Schedules June July August Karl Mary Thomas Manuals Widget.Co chapt.1 chapt.2 chapt.3 chapt.4 appx.A appx.B glossary index Acme.
PAGE 926

Manual 99a 38 July 17, 2001 Keeping a Backup Logbook Keep a hard copy log of your backups in case your online log and error files become corrupted.
PAGE 927

Manual 99a 38 July 17, 2001 Preparing to Back Up Careful planning can help you minimize the impact of data loss. Before you back up, consider the following: What should be backed up Where to back up Backup type Who should back up When to back up How to prepare for a backup How to track backup Open Files Backup TSA600.NLM supports backup of open files on Novell Storage Services (NSS) volumes if the CopyOnWrite feature is enabled.
PAGE 928

Manual 99a 38 July 17, 2001 Determining an Appropriate Backup Type Each type of backup has a different effect on the backup and restore process. When planning your backup schedule, consider all of the following variables before determining which schedule is right for you. Media usage and backup speed. This helps increase the speed of the restore. Restoring after incremental backups.
PAGE 929

Manual 99a 38 July 17, 2001 Distributed Database The network of servers that comprise an eDirectory tree structure continually exchange updates and other time-sensitive information. The eDirectory database exists as a set of files that are stored in the SYS: volume and are hidden so they are not accidentally tampered with or deleted. The eDirectory database files cannot be backed up, as was the case with bindery files in NetWare 3.12 or earlier versions.
PAGE 930

Manual 99a 38 July 17, 2001 Placeholder (Unknown) Objects Whenever insufficient information is known about an object, such as when one of its mandatory attributes is missing, eDirectory creates as a placeholder an Unknown object. During a restore session of the eDirectory database information, Unknown objects are created when restoring an object that has an access control list (ACL) or any other attribute that refers to other objects that do not currently exist in the eDirectory tree structure.
PAGE 931

Manual 99a 38 July 17, 2001 traffic during the backup process and improves performance when the backup program performs name resolution across the eDirectory tree structure. The version of TSANDS.NLM that ships with NetWare allows selective backup and restoration of an eDirectory tree structure. HINT: Not all third-party backup applications support this selective backup and restoration. Check with the application vendor for details on product features.
PAGE 932

Manual 99a 38 July 17, 2001 eDirectory backup to back up the portions of the tree for which they have rights. The network administrator assigns the Supervisor right to the backup administrators for the section of the eDirectory tree structure that they are responsible to back up. The network administrator then needs to create a TSANDS.CFG file that lists the fully distinguished names of the containers where each of the backup administrators' rights begin. The TSANDS.
PAGE 933

Manual 99a 38 July 17, 2001 Trustee Assignments Trustee assignments are stored as part of the file system as an ID. They are backed up by default when the file system is backed up with the SMS TSA software. If a User object is deleted and then re-created or restored, its object ID changes. This is why the SMS TSA module uses fully distinguished names for objects to back up the trustee rights from the file system.
PAGE 934

Manual 99a 38 July 17, 2001 Backups and Clusters Novell Cluster ServicesTM allows you to configure up to 32 NetWare servers into high-availability cluster, where resources can be dynamically switched or moved to any server in the cluster. Consolidation of applications and operations on a cluster has benefits such as lower costs, scalability, and increased availability. See the Novell Cluster Services documentation (http:// www.novell.com/documentation) for more information.
PAGE 935

Manual 99a 38 July 17, 2001 If a cluster server is chosen as the target, only noncluster volumes will be backed up. You have to back up each pool individually. You might abort an ongoing backup job with the intention of resubmitting the same job later. In such situations, the job will not restart from where it was terminated; it will restart from the beginning. For more information, see “Backing Up Cluster-enabled Pools from the Server” on page 56.
PAGE 936

Manual 99a 38 July 17, 2001 The TSA packages data from the target and presents it to the SME in a generic format. This allows one SME to interact with many types of TSAs. NetWare 6 provides TSA600.
PAGE 937

Manual 99a 38 July 17, 2001 How SMS Restores Data During a restore session, SBCON reads the backup storage media, and the Target Service Agent (TSA) compares the media data set to the existing hard disk data set.
PAGE 938

Manual BEGIN 99a July 17, 2001 38 END Go to backup session on storage media. no Is there another data set to read? yes Read data set. Overwrite data set? Is the data set to be renamed yes only if newer no yes no ignore Rename the dataset Is data set a subset of what you´re restoring? restore Compare date of data set on media to date of data set on disk.
PAGE 939

Manual 99a 38 July 17, 2001 Restore Options For a custom restore session, you can specify exactly which data to restore. Several options work together to allow you maximum flexibility in your restore session.
PAGE 940

Manual 99a 38 July 17, 2001 Restoring eDirectory and the File System The only way to ensure that your eDirectory database can be fully restored is through partition replication, with replicas of the entire database on multiple servers. On a single-server network, you need to rely more heavily on backing up the data because you do not have replicas to restore information.
PAGE 941

Manual 99a 38 July 17, 2001 stored on volume SYS:, losing SYS: is equivalent to removing NetWare and eDirectory from the file server. You must reinstall NetWare and eDirectory before you restore your data. The procedures for this scenario are divided into two cases: Loss of the only server in a single-server network. Loss of a single server in a multiple-server network. Single-Server Network In a single-server network, server failure brings all network operations to a halt.
PAGE 942

Manual 99a 38 July 17, 2001 5. Restore the file system. (See “Restoring Data” on page 62 and “Custom File System Restore” on page 74.) 6. Restore any replicas that were removed from the server. Loss of the Entire eDirectory Tree If all servers on a network are destroyed because of a disaster, you must perform a complete restore of NetWare, eDirectory, and file system data.
PAGE 943

Manual 99a 38 July 17, 2001 Log and Error Files The files of the backup session are stored in a default directory (such as SYS:SYSTEM\TSA\LOG). If you prefer, you can create your own directory for the log and error files as long as it resides on the host server. The files of the restore session are stored in the directory (SYS:SYSTEM\TSA\RESTORE). You cannot modify the location for the files.
PAGE 944

Manual 99a 38 July 17, 2001 Error File The error file is created on the host server the first time a particular set of data is backed up. It contains a list of any errors that occurred during a backup or restore session. This file contains the following: The session date and time and the description you entered. The target from which the data was backed up for a backup session. The target that was backed up and the location on the server where the data was restored to during a restore session.
PAGE 945

Manual 40 99a 38 Storage Management Services Administration Guide Storage Management Services Administration Guide 103-000134-001 August 29, 2001 Novell Confidential July 17, 2001
PAGE 946

Manual 2 99a 38 July 17, 2001 Setting Up In addition to being able to back up data from a server with SBCON, you can use a Windows 95, 98, 2000 or Windows NT workstation to perform your backups using the graphical interface. This chapter discusses the following: How to customize the NetWare server as the backup server. See “Customizing the NetWare Server as the Backup Server” on page 43. How to load the backup software.
PAGE 947

Manual 99a 38 July 17, 2001 SBCON Guidelines Before you set up and begin backups, follow these guidelines to make backups easier and to avoid problems later. Log in. You will have limited success backing up and restoring if you log in without the Supervisor right. For security reasons, many SBCON options are limited to the network administrator. Reserve disk space for temporary files.
PAGE 948

Manual 99a 38 July 17, 2001 Before Loading the Backup Software Before you load the backup software on the server or on a Windows machine, you need to configure a server to execute your backups. Determine the following: The tree to which the server belongs which must be made the current tree The full eDirectoryTM context of the server Before Running the Backup Software Before backing up software, in general you must: Load the controller and storage device drivers on the server.
PAGE 949

Manual 99a 38 July 17, 2001 The SMDR Group object is where all NetWare and workstation SMDRs are registered for name resolution purposes. 6 Accept the default name of the Backup Queue where all backup jobs will be submitted, or enter a new name and context. Loading Controller and Storage Device Drivers on the Server Controller and device drivers control the mechanical operation, such as read, write, forward, back, and stop of various storage devices and media.
PAGE 950

Manual 99a July 17, 2001 38 Loading the Target Service Agents Target Service Agents are loaded on servers and workstations. If you want to back up a server, load the TSA on the server. Ensure that the controllers and device drivers are loaded.
PAGE 951

Manual 99a 38 July 17, 2001 Loading the files when the server starts. Place the commands in the server's STARTUP.NCF, and in the workstation's NET.CFG file, AUTOEXEC.BAT file (for DOS), or Startup folder (for OS/2). Loading SBCON You can load SBCON from the server command line. If you use NWBACK32 on a client, you do not need to load SBCON. 1 At the server console, enter SMSSTART TSA600.NLM, TSAPROXY.NLM, and SMDR.NLM modules are loaded with default configuration values. SBSC.NLM, QMAN.NLM, SMSDI.
PAGE 952

Manual 99a 38 July 17, 2001 Unloading SBCON To ensure maximum memory utilization and throughput, you should unload backup software and other Storage Management ServicesTM (SMSTM) modules when you are finished performing your backup. That way, more memory will become available on your host or target. 1 Exit SBCON from the Main Menu. Press Esc until you reach the SBCON Main Menu; then press Esc again and confirm the prompt.
PAGE 953

Manual 99a 38 July 17, 2001 3 Run NWBACK32.EXE from SYS:PUBLIC. The following screen appears. You are now ready to back up data. Go to “Backing Up Data” on page 49 to continue. Exiting NWBACK32 1 Exit NWBACK32 from the Quick Access window. 2 Unload all the modules loaded on the server by entering the following command at the server console: SMSSTOP Unloads all the previously loaded SMS modules.
PAGE 954

Manual 99a 38 July 17, 2001 Backing Up Data You can use SBCON to create a tape backup of the eDirectory database or of the file system on your servers or workstations. The prerequisites listed here use SBCON as the Storage Management Engine (SME). Prerequisites Understand the process for loading SBCON. See “Loading SBCON” on page 46 Ensure that you know the workstation password if you are backing up a workstation.
PAGE 955

Manual 99a 38 July 17, 2001 Ensure that media is inserted into your storage device. You can back up your data two ways: from a server using SBCON or from a Windows workstation using NWBACK32. Backing Up from the Server When you back up your data from one server to a target server or workstation, you should use the command line. 1 Load the SBCON modules. See “Loading SBCON” on page 46. 2 Click Main Menu > Job Administration > Backup.
PAGE 956

Manual 99a 38 July 17, 2001 4 Select a target from the Target Services list. The following table describes the targets that can be selected for backup.
PAGE 957

Manual 99a 38 July 17, 2001 This is a descriptive name of the job, which will help you identify the specific backup session; if a restore is necessary, you can easily identify the session you need. There is no special requirement for what to enter as the session description. HINT: You might want to include the full path of the data (for example, SYS:HOME\REPORTS\JULY.02) which you will need to know if a restore session is necessary. 10 Click Device/Media Name and select a device.
PAGE 958

Manual 99a 38 July 17, 2001 14 To return to the Main Menu, press Esc until you back out to the Main Menu. 15 To exit SBCON, press Esc again and answer the confirmation prompt. Customizing Backup You can customize your backup using the Advanced Backup Options form when you use SBCON at the server to launch your backup program. This form allows you to specify exactly what you want to back up data. It could be the server, the eDirectory database, workstation, directory, or file.
PAGE 959

Manual 99a 38 July 17, 2001 3 Select Subsets of What To Backup. The default setting means that everything in the Subsets of What You Want to Backup screen is backed up. Include/Exclude TSA Resources—Includes or excludes resources such as servers or volumes. Include/Exclude Directories—Includes or excludes directories. Include/Exclude Files—Includes or excludes files. Include/Exclude path/files—Includes or excludes pathnames and files. 4 Select Scan Options.
PAGE 960

Manual 99a 38 July 17, 2001 The day, month, or year you enter should not be the actual date when you want the job to run; rather, it is the duration after which the job gets executed.
PAGE 961

Manual 99a 38 July 17, 2001 4 Select where you want your backup data to go. 4a Double-click Where to Backup. 4b Change to the correct eDirectory tree structure and context by clicking the Change to Context button on the toolbar. 4c Double-click Queues. 4d Select a Queue object from the list. 4e Right-click the server to open the drop down box. 4f Click Submit the Job. This step allows you to submit the job to a queue on the chosen server or on the chosen media type. Queue.
PAGE 962

Manual 99a 38 July 17, 2001 5 When prompted, enter the username (and context, if required) for the target. If SBCON rejects the username you entered, you probably need to include the context where the User object is located. For example, instead of entering ADMIN as the username, enter .CN=ADMIN.O=company_name or .ADMIN.company_name.
PAGE 963

Manual 99a 38 July 17, 2001 If the storage media does not have a label, SBCON displays a message saying that the media cannot be identified. Set the label before selecting it for a backup job. 11 Select Advanced Options and set the desired values for all the fields. For more details, see “Customizing Backup” on page 53. NOTE: If you set Enable Auto Recovery to NO in Cluster Options, the remaining options become invalid. 12 Select Append Session.
PAGE 964

Manual 99a 38 July 17, 2001 Backing Up a Workstation To back up the workstation (the target), a Target Service Agent (TSA) must be loaded on the workstation. (See “Loading the Target Service Agents” on page 45.) You can select the directories to back up or back up the entire workstation. Windows 95 and 98 Workstation Make sure that the W95TSA is installed and configured. It is a part of the Novell Client modules (checkbox for Target Service Agent).
PAGE 965

Manual 99a 38 July 17, 2001 Windows 2000 and Windows NT Workstation Make sure that the NT TSA is installed and configured. It is a part of the Novell Client modules (checkbox for Novell Target Service Agent). The Windows NT TSA has two parts: TSA Service (TSAMAIN.EXE) is a service that waits for and acts when there is a request from the backup engine. TSAPrefs (TSAPREFS.EXE) allows an NT administrator to set preferences and monitor the activities of the TSA Service.
PAGE 966

Manual 99a 38 July 17, 2001 Changing Your Target Any time you are performing a series of backup or restore sessions, you might need to change your target. This can be easily done from the SBCON Main Menu either at the command line or from the Windows workstation using NWBACK32. If you do not specify a new target, SBCON automatically selects the target used during the last session and continues without asking you to make a selection.
PAGE 967

Manual 99a 38 July 17, 2001 Restoring Data Use SBCON to restore information from tape backup. These procedures use SBCON as the Storage Management Engine (SME). Know the username and password for the target server or workstation to which you want to restore data. Know the session description that you want to restore. You can get this information from your session log and error files. (See “Session Files” on page 37.
PAGE 968

Manual 99a 38 July 17, 2001 3 Load SBCON. See “Loading SBCON” on page 46. 4 Select Main Menu > Job Administration > Restore. The Restore Options screen appears. 5 Select Target Service and then the NetWare server running your backup and restore Target Services Agent. This is the name of the server or workstation on which you want to restore your data. Before selecting it, you must load the correct TSA. See “Loading the Target Service Agents” on page 45.
PAGE 969

Manual 99a 38 July 17, 2001 Target Service to Restore Dataset to Select Workstation The workstation's host server and then the workstation Server-specific information The server whose server-specific information you want to restore and then the file system to restore 6 When prompted for the target username, enter your username (and context if required) as the network administrator for the target.
PAGE 970

Manual 99a 38 July 17, 2001 volume without compression, the file is corrupted and no error message is displayed. 11 Specify the path to the session log file of the session you want to restore. Use one or more of the following methods: Press Enter to accept the default; then go to Step 12 on page 65. Press Insert to select from a list of directories, press Esc to return to the previous window, and then go to Step 12 on page 65.
PAGE 971

Manual 99a 38 July 17, 2001 The Esc key allows you to exit SBCON one screen at a time until you reach the Main Menu. If you want to exit SBCON, answer the confirmation prompt. NOTE: To unload SBCON and applicable Target Service Agents, see “Unloading SBCON” on page 47. Customizing Restore Using the Advanced Restore Options form at the server, you can perform a custom restore of the database you need. 1 Select Main Menu > Job Administration > Restore. The Restore Options screen appears.
PAGE 972

Manual 99a 38 July 17, 2001 The screen lists major and minor resources. Default indicates that none of that type of subset has been specified. 6 To specify a subset, do the following: 6a Select any item on the screen. 6b Edit the Include or Exclude screens using Insert and Enter. 6c Press Esc to save changes. 6d To view a list of values associated with major TSA resources (for example, server or volumes) select either the include or exclude line. The Selection List Options form appears.
PAGE 973

Manual 99a 38 July 17, 2001 Restoring Data from a Workstation When you restore data, you are copying your backed up data to a server or workstation. 1 Run NWBACK32. See “Loading NWBACK32” on page 47. You can run the NWBACK32 program (NWBACK32.EXE) from SYS:PUBLIC. 2 At the Quick Access window, click Restore. 3 Click What you Want to Restore. 3a Double-click What to Restore. 3b Select the context. 3c Double-click Queues and select the queue. 3d Double-click Servers and select a server.
PAGE 974

Manual 99a 38 July 17, 2001 Restoring eDirectory The procedures in the following sections are performed at the beginning of the restore process.
PAGE 975

Manual 99a 38 July 17, 2001 Make sure disk partitions are at least as large as they were before, and that the volumes are defined as before. 3 Restore eDirectory using “Customizing Restore” on page 66. Restoring Volume SYS: in a Multiple-Server Network To restore SYS: volumes on several servers, do the following. 1 Restore the server-specific eDirectory information file (SERVDATA.
PAGE 976

Manual 99a 38 July 17, 2001 4e Select Remove This Server from the Replica Ring. 4f Enter the supervisor name and password. 4g Select Yes to continue. 5 Exit DSREPAIR. 6 Reinstall NetWare. 6a Begin the installation. 6b When prompted for DS install, select Create a New DS Tree and complete the installation. 6c Load NWConfig and remove DS. 6d Install DS, when prompted for DS install and select Install into an Existing Tree. 6e When prompted to choose a eDirectory tree structure, press F5.
PAGE 977

Manual 99a 38 July 17, 2001 Restoring the Entire eDirectory Tree Structure To restore an entire network from a full backup in a multiple-server environment, do the following: 1 Reinstall NetWare on the first server. By default, this server will hold the master replica of the [Root] partition. When NWCONFIG asks for the names of Organization objects immediately under the [Root] object, use the same names that existed before in the eDirectory tree.
PAGE 978

Manual 99a 38 July 17, 2001 eDirectory Restore Session Types You can choose to restore eDirectory in one of the following ways: “Single Server or an Entire Tree Restore” on page 73 “Custom eDirectory Restore” on page 73 “Custom File System Restore” on page 74 “Server-Specific Information Restore” on page 76 “Single File or Directory Restore” on page 76 Single Server or an Entire Tree Restore 1 Restore the entire eDirectory session from your SMS backup.
PAGE 979

Manual 99a 38 July 17, 2001 If you do not want to overwrite the parent or child that exists on the hard disk, regardless of whether the existing version or the backed-up version has the latest date, select the option (parent or child or both), and enter N. 6 Continue through Step 14 on page 65 to Step 19 on page 65. Custom File System Restore To perform a custom file system restore, do the following. 1 Enter SBCON at the server console prompt.
PAGE 980

Manual 99a 38 July 17, 2001 Follow these important rules about restoring to a new location: When you specify a particular portion of the file system structure as the source location, it does not necessarily mean that this will be the only data restored. You can influence what is restored by using the Include and Exclude options on the Choose Subsets Of What You're Restoring screen (Job Administration > Restore Options > Advanced Restore Options > Subsets of What to Restore).
PAGE 981

Manual 99a 38 July 17, 2001 If you want to overwrite the child that exists on the hard disk only if the date of the backed-up copy on the media is later than the date of the copy on the hard disk, select Overwrite Existing Child and select the option. 8 Continue through Step 15 on page 65 to Step 19 on page 65. Server-Specific Information Restore To view and restore server information, do the following.
PAGE 982

Manual 99a 38 July 17, 2001 3 Press Insert and enter the name space for the name space format you used when entering the file or directory name. The name space allows SBCON to correctly interpret the path information entered earlier in this menu in either the directory field or the location field. IMPORTANT: If files are restored to a new location, the name spaces must be the same or an error message will occur.
PAGE 983

Manual 99a 38 July 17, 2001 Completing the eDirectory Restore If you restored the eDirectory database to volume SYS:, you should complete the restoration for the following to make sure the eDirectory database is working properly: Volume Other than SYS: To finish restoring eDirectory on a volume other than SYS:, do the following. 1 Bring the server up.
PAGE 984

Manual 99a 38 July 17, 2001 Entire Tree To finish restoring eDirectory on the tree, do the following. 1 Restore the file system information to each server following “Restoring Data” on page 62. 2 Re-create partitions and replicas. 3 (Optional) Verify proper restoration of the data, trustee assignments, file ownership, and other related information by spot-checking some of the restored directories and files.
PAGE 985

Manual 99a 38 July 17, 2001 identifies the file server on which the queue directory resides. This information is used to determine the physical location of the resource. The specifics of restoring objects vary depending on what type of object is involved and whether the object's dependencies are physical entities (servers and volumes) or logical entities. In some cases, you can simply restore an object and everything will work fine.
PAGE 986

Manual 3 99a 38 July 17, 2001 Managing After you install and load SBCON, you can manage your jobs, data, devices, reports, and so on either from the server or workstation. Though the screens might look different, you can perform the same tasks in each interface. Be sure to read “Prerequisites for SBCON Tasks” on page 81 before performing any tasks in this section.
PAGE 987

Manual 99a 38 July 17, 2001 Jobs The backup or restore jobs created by you can be administered anytime. You can delete, hold, reschedule, abort, or enable a job. Administering Jobs Jobs can be managed either from the server or from the workstation. From the Server On the SBCON Main Menu at the server, the Current Job List option gives you a job management facility where you can delete a job, hold a job, or enable it if it has been disabled after a job failure.
PAGE 988

Manual 99a 38 July 17, 2001 Dynamic properties contains data that indicates how much data has been backed up along with the filenames. This dialog box appears when a job is running and SBSC is loaded on the server. Enable job allows you to start a job that has been disabled. Delete the job allows you to remove a job. Start/Hold the job allows you to start a job that is in the hold state or place it on hold if it is not in a hold state.
PAGE 989

Manual 99a 38 July 17, 2001 Viewing Job Details This screen gives you all the details of the job you submitted including job name, the time the job was submitted, and the time the job should be executed. You can also schedule the job to run at a predefined time again after its execution. You can view job details from the server or a workstation. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page 81.
PAGE 990

Manual 99a 38 July 17, 2001 Serviced By—This indicates the name of the server where the job is to be executed. From a single server, you can submit jobs to various servers. This field indicates which job is serviced by which server. This field is active only when the job is active; otherwise, it indicates None. Scheduling Options—You can schedule the same job to run at another time. For information, see “Customizing Backup” on page 53.
PAGE 991

Manual 99a 38 July 17, 2001 From a Workstation 1 At the Quick Access window, click Job Administration. 2 Double-click the context. 3 Double-click Queues. 4 Select the job to place on hold. 5 Right-click the job and then click Start/Hold the Job. (Optional) You can also hold the job using the toolbar. Click Job Administration > Start/Hold the Job.
PAGE 992

Manual 99a 38 July 17, 2001 From the Server 1 Select Main Menu > Storage Device Administration. 2 Select a device and press Insert. 3 Select Utilities > Device Status. The Device Status screen is displayed listing the following information: Current Operation—Indicates whether the device is currently reading, writing, formatting the media, or none of these. Device Mode—Indicates whether the device is selected for reading, writing, or both.
PAGE 993

Manual 99a 38 July 17, 2001 You can change a device label from the server or a workstation. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page 81. From the Server 1 Select Main Menu > Storage Device Administration. 2 Select a device name and press Insert. 3 Select Utilities > Change the Device Label. 4 Enter the new name in the field. 5 Press Esc as required to return to the Main Menu.
PAGE 994

Manual 99a 38 July 17, 2001 From the Server 1 Select Main Menu > Storage Device Administration. A list of devices is displayed. If no device is displayed in the list, run LIST DEVICES at the server prompt. 2 Select a device name and press Enter. The List of Media screen appears displaying the following information: Slot—The slot number given by the manufacturer. Media name—The name of the media, which can be changed using the Utilities menu. See “Erasing or Retaining Media” on page 90.
PAGE 995

Manual 99a 38 July 17, 2001 Erasing or Retaining Media This task erases media headers, erases all data on the media, or retentions media in tape devices. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page 81. The following table describes all media options. Option Explanation Change the Media Label This is permanent. Blank media (tape) does not have a label. Before submitting a job to the media, you need to label it.
PAGE 996

Manual 99a 38 July 17, 2001 3 Double-click Queues. 4 Double-click the preferred queue. 5 Double-click Servers. 6 Double-click the preferred server. 7 Double-click Devices. 8 Right-click the media > click Erase Media [or] Retension. (Optional) You can also use the toolbar. Click Device Administration > Media > Erase Media [or] Retension. Checking the Media Status in a Device This task lets you check the status of a particular media type from either the server or a workstation.
PAGE 997

Manual 99a 38 July 17, 2001 Media mode—Whether the media is selected for reading, writing or both, or whether the mount request is pending. Media type—The type of media in the device, such as 4mm DDS (Digital Data Storage) tape, or 8mm tape. Total capacity—The total capacity of the media, if known. Sometimes it is not displayed, depending on the media manager. The type of media manager controls the display of the total capacity of the media.
PAGE 998

Manual 99a 38 July 17, 2001 Log and Error Files SBCON keeps a list of all the log and error files, which show specific information about the backup and restore session. See “Session Files” on page 37 for more information. You can manage these files as follows: View information contained in the log and error files. See “Viewing a Log File” on page 93 and “Viewing an Error File” on page 94 for information. Create these files. See “Creating Log and Error Files” on page 96 for information.
PAGE 999

Manual 99a 38 July 17, 2001 To change the directory, delete the existing directory path and type a new one, and then go to Step 3 on page 94. You can also press Insert during this process to select existing parts of the path from a list. The backup log displays all supported name space types. The DOS name space is the first in the group. A right-angle bracket (>) appears next to the file creator's name space type.
PAGE 1000

Manual 99a 38 July 17, 2001 From the Server 1 From the SBCON Main Menu, select Log File Administration > View an Error File. 2 If necessary, set the location of the log and error files for a backup session. (This option is not supported for a restore session.) To set the location, use one or more of the following methods: Press Enter to accept the default location, and then go to Step 3 on page 95.
PAGE 1001

Manual 99a 38 July 17, 2001 4 Double-click the preferred queue. 5 Double-click Servers. 6 Right-click the preferred server. 7 Select Error Report. Creating Log and Error Files If you do not know what is on the media, or you have lost or deleted the log and error files, you can re-create them. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page 81. To create a log or error file, see “Creating Session Files” on page 98.
PAGE 1002

Manual 99a 38 July 17, 2001 Deleting the Log Files SBCON allows you to overwrite sessions and reuse storage media. When you delete the log file for a session using the following procedure, you automatically delete the corresponding error file as well. To prevent outdated session information from taking up disk space and to help prevent confusion when you select sessions to view or restore, delete the session log files for any session that has been overwritten.
PAGE 1003

Manual 99a 38 July 17, 2001 Creating Session Files If you do not know what is on the media, or you have lost or deleted the log and error files, you can re-create them from either the server or a workstation. Ensure that you have met the prerequisites detailed in “Prerequisites for SBCON Tasks” on page 81. From the Server 1 From the SBCON Main Menu, select Job Administration > Create Session File. The Session Files Options screen appears. 2 Enter a descriptive name.
PAGE 1004

Manual 99a 38 July 17, 2001 9 Select the preferred media. 10 Right-click the job and select Submit the Job. 11 Check the appropriate fields in the Submission of Job dialog box. Verifying Backup Data This option allows you to check the data on the media from either the server or a workstation to make sure it has been backed up properly, and to check later that the data is valid and can be restored.
PAGE 1005

Manual 99a 38 July 17, 2001 From a Workstation 1 At the Quick Access window, click Verify. 2 Double-click the context if necessary. 3 Double-click Queues. 4 Double-click the preferred queue. 5 Double-click Servers. 6 Double-click the preferred server. 7 Double-click Devices. 8 Double-click the preferred device. 9 Right-click the preferred media. 10 Select Submit the Job. 11 In the Submission of Job dialog box, click the session. 12 Click Finish.
PAGE 1006

Manual 4 99a 38 July 17, 2001 Optimizing This chapter discusses the following topics: Whether you should compress your files before backup. See “Compressed Files” on page 101. How to increase speed when backing up your files. See “Host Server Performance” on page 102. How to enhance or optimize server performance. See “Setting Minimum Packet Receive Buffers” on page 103. How to synchronize memory between your media and your server. See “Setting Reserved Buffers Below 16 MB” on page 103.
PAGE 1007

Manual 99a 38 July 17, 2001 To help you make a decision about whether to compress or decompress your backed up data, follow these guidelines: Backups are faster if files already compressed are left compressed. Compression is not supported in some environments (such as a NetWare 3.11 server, a DOS workstation, or Novell Storage ServicesTM). If you intend to restore a file that is currently compressed to an environment that does not support compression, back it up in a decompressed state.
PAGE 1008

Manual 99a 38 July 17, 2001 Setting Minimum Packet Receive Buffers Packet receive buffers represent the space in the server memory dedicated to handling network traffic. If the buffers are set too low, the server performance may be degraded. To reset the packet receive buffers at the server console prompt, include the following SET command in the STARTUP.NCF file: SET MINIMUM PACKET RECEIVE BUFFERS = X The x represents the number of buffers. Set two buffers for each user on the system.
PAGE 1009

Manual 99a 38 104 Storage Management Services Administration Guide Storage Management Services Administration Guide 103-000134-001 August 29, 2001 Novell Confidential July 17, 2001
PAGE 1010

Manual 5 99a 38 July 17, 2001 Troubleshooting Common Backup Problems The media owner is unidentified Possible Cause: Action: Media is blank or was written in a non-SIDF format. See “Checking the Media Status in a Device” on page 91. Backup speed is slow Possible Cause: Action: Compressed files are being backed up in a decompressed format. See “Compressed Files” on page 101. Restore speed is slow Possible Cause: File compression and SBCON are running at the same time.
PAGE 1011

Manual 99a 38 July 17, 2001 Data is corrupted, but no error message was given Possible Cause: Action: Compressed files were restored to a volume without compression. See Step 10 on page 64. You (the network administrator) can't back up a workstation Possible Cause: The /Password option is set and is denying access to data on the workstation. Action: See “Setting Rights to Back Up Portions of the eDirectory Tree” on page 26.
PAGE 1012

Manual 99a July 17, 2001 38 Files were restored but the error file contains a message specifying which name space formats were not restored Possible Cause: Action: The file attributes and name space formats are not configured on the volume you restored to. Check to make sure you selected the correct name space.
PAGE 1013

Manual 99a 38 108 Storage Management Services Administration Guide Storage Management Services Administration Guide 103-000134-001 August 29, 2001 Novell Confidential July 17, 2001
PAGE 1014

iPrint Administration Guide Novell NetWare 6 ® www.novell.
PAGE 1015

Manual 99a July 17, 2001 38 Contents Contents 5 Simplify Printing Using iPrint 7 Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 1 Understanding iPrint 9 The Novell iPrint Solution . . . . . . . . . Scenario 1: Printing across the Internet Scenario 2: Mobile Users . . . . . . . . Scenario 3: Printing Instead of Faxing . 2 . . . . . . . . . . . . 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
PAGE 1016

Manual 5 A July 17, 2001 38 Printer Availability on Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Printer Driver Default Install Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 28 Setting Up a Secure Printing Environment 31 Secure Printing Using SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Configuring the HTML Interface 33 iPrint Client HTML Interface Description . .
PAGE 1017

Manual 99a 38 July 17, 2001 Simplify Printing Using iPrint iPrint is Novell’s® next generation of printing software that lets users to print from anywhere to anywhere. Utilizing the Internet Printing Protocol standarad, iPrint lets users use their Web browser to install printers on their workstations. Once installed, users can print to iPrint printers through their applications just like any other printer. These printers can be located down the hall or across the ocean.
PAGE 1018

Manual 8 iPrint Administration Guide iPrint Administration Guide 103-000136-001 August 31, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 1019

Manual 1 99a July 17, 2001 38 Understanding iPrint iPrint lets mobile employees, business partners, and customers access printers from a variety of remote locations using existing Internet connections. Whether users are located in an office building, telecommuting from home, or attending a sales meeting in another country, iPrint ensures that they can print documents quickly, easily, and reliably. Using a Web browser, users point to a Web page that displays the available printers.
PAGE 1020

Manual 99a 38 July 17, 2001 In addition to the benefits of IPP, Novell’s implementation of iPrint adds the following value: One Net printing for global access Print driver download and installation Location-based printing Browser-enabled print interface Customizable user interface Secure information transfer Using iPrint, mobile users no longer have to hunt down administrators to find out a printer’s name and context and the required print driver.
PAGE 1021

Manual 99a 38 July 17, 2001 Scenario 1: Printing across the Internet John is an employee working at home who wants to send a document to a printer at his office. John does not remember how to dial into the company’s network, but he has access to the Internet. 1. After the administrator has set up iPrint, he will need to enable a port on his firewall to allow access to the company’s intranet from the Internet. For security, the administrator should enable port 443, which uses SSL.
PAGE 1022

Manual 99a 38 July 17, 2001 Scenario 3: Printing Instead of Faxing Dan has just returned to his hotel room in Chicago after visiting with some clients. While checking his email, he is reminded that he needs to submit a color report to his boss in the corporate office in New York. The report is due by 8 a.m.Although he could send the report by fax, he wants a high-quality printout in color and he does not want to incur additional telephone charges. 1.
PAGE 1023

Manual 2 99a 38 July 17, 2001 Setting Up iPrint on Your Server iPrint is based on the Novell® Distributed Print ServicesTM (NDPS®) architecture. In order to use iPrint, you must have NDPS installed and configured. If you do not have an NDPS system set up, refer to the Novell Distributed Print Services Administration Guide for more information.
PAGE 1024

Manual 99a 38 July 17, 2001 iPrint System Requirements Before you set up iPrint, you must have the following: NDPS Broker:Provides network support services. For more information, see Creating NDPS Brokers in the Novell Distributed Print Services Administration Guide. Print Services Manager: Provides a platform for printer agents. When IPP printing is configured for a printer, the print services manager loads the IPP software, IPPSRVR.NLM.
PAGE 1025

Manual 99a 38 July 17, 2001 Enable DNS on the Print Services Manager To configure a DNS name for the print services manager, use the print services manager startup switch. Syntax NDPSM NDPS_Manager_Object_Name /dnsname=NDPS_Manager_DNS_Name Example NDPSM PrintManager1 /dnsname=Printing.MyCompany.Com where PrintManager1 is the print services manager name and Printing.MyCompany.Com is the desired DNS name.
PAGE 1026

Manual 99a 38 July 17, 2001 Configuring iPrint Printers Complete the following steps for printers that are already set up in NDPS. For more information on creating an NDPS printer, see Creating NDPS Printers in the Novell Distributed Print Services Administration Guide. 1 From iManage, click iPrint Management > Manage Printer. 2 Browse to and select the printer you want to enable IPP printing for. 3 Click Client Support > IPP Support. 4 Check the Enable IPP Access check box.
PAGE 1027

Manual 99a 38 July 17, 2001 Enabling iPrint on All Printers To enable iPrint on all printers associated with a print services manager, complete the following: 1 From iManage, click iPrint Management > Enable iPrint Access. 2 Browse to and select the print service manager you want to enable IPP printing for. 3 To enable all printers associated with this print services manager, check the first check box next to Enabled.
PAGE 1028

Manual 18 iPrint Administration Guide iPrint Administration Guide 103-000136-001 August 31, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 1029

Manual 3 99a 38 July 17, 2001 Setting Up iPrint on Client Workstations In order for users to use iPrint, they need to install the Novell® iPrint Client software and a printer. When a user selects a printer to be installed by iPrint, iPrint checks to see if the Novell iPrint Client software is installed and installs it if necessary. Then the printer driver is downloaded, and the printer is installed in the user’s Printer folder.
PAGE 1030

Manual 99a 38 July 17, 2001 Using the Default Printer Lists Generated by iPrint To enable users to use iPrint, you must give them the iPrint URL, which is http://server_IP_ address_or_dns_name:631/IPP. For example, if the DNS name is printing.mycompany.com, then the user would access IPP from the following URL: http://printing.mycompany.com:631/ipp If users need to print through a secure port using SSL, they should use port 443.
PAGE 1031

Manual 99a 38 July 17, 2001 posted on a Web server for users to access. As users view the maps, they find a printer close to their location to install and then click a printer icon. The client software (if not yet installed) and the printer are installed on their workstation. For more information, see “Using the iPrint Map Designer” on page 23. Using ZENworks to Distribute iPrint You can use ZENworks to distribute the Novell iPrint Client and printers to users’ workstations.
PAGE 1032

Manual 99a 38 July 17, 2001 Saving Passwords for Secure Printers When users print to a secure printer, they are prompted for the eDirectory username and password. Users can select to have their workstation remember their password for printing. For Windows NT/2000 users, passwords are saved on a per-user basis. By default the Remember Password feature is enabled. To disable it, use a text editor to edit the SYS:\LOGIN\IPPDOCS\IPRINT.INI file to reflect the settings you want.
PAGE 1033

Manual 4 99a July 17, 2001 38 Customizing iPrint This chapter describes how to customize iPrint for your company by using the iPrint Map Designer and modifying the HTML pages and iPrint Client interface.
PAGE 1034

Manual 99a 38 July 17, 2001 made outside of the iPrint Map Designer are not supported. If you need to add links to a map, you should create a frameset file and then display the map file in one frame and display your links in a different frame. Creating a Map 1 Copy all of your background images (maps) to SYS:LOGIN\IPPDOCS\IMAGES\MAPS on the server. File types that can be used for background images are .JPEG, .GIF, and .BMP.
PAGE 1035

Manual 99a 38 July 17, 2001 8 (Optional) In the Printer Caption field, enter the information to display, using Enter to parse the information onto multiple lines. 9 Repeat Step 4 through Step 8 and to add additional printers to your map. 10 To edit a printer’s information, click the desired printer’s icon and then edit the printer information fields. To deselect a Printer icon while in the map, click anywhere in the design area. 11 Click Save, and save the Map to SYS:LOGIN\IPPDOCS.
PAGE 1036

Manual 99a 38 July 17, 2001 Using the Keyboard with iPrint Map Designer You can use the keyboard to create maps using iPrint Map Designer. The table below lists the tasks to complete and the corresponding keystrokes required. Table 1 Using the Keyboard Task Press Move between fields Tab Insert printer icon Insert key Before you can insert a priner, your focus must be the design area.
PAGE 1037

Manual 99a 38 July 17, 2001 Customizing the HTML Interface You can edit any of the HTML files provided or you can create your own to customize iPrint for your environment. The HTML files are installed in the SYS:LOGIN\IPPDOCS directory. For information on the HTML interface, see Appendix A, “Configuring the HTML Interface,” on page 33.
PAGE 1038

Manual 99a 38 July 17, 2001 Printer Driver Default Install Options You can change the default options for the printer driver when it is installed on the workstation. For example, you might want the printer driver default for paper size to be 8-1/2 x 11. This means every time the printer and corresponding driver is installed on a workstation, the paper size is set at 8-1/ 2 x 11.
PAGE 1039

Manual 99a July 17, 2001 38 Printer Setting Acceptable Parameter Values Color yes=color no or false=monochrome Duplex simplex, horizontal, vertical Collate yes or true=collate no=do not collate 4 Save the file.
PAGE 1040

Manual 30 iPrint Administration Guide iPrint Administration Guide 103-000136-001 August 31, 2001 Novell Confidential 99a 38 July 17, 2001
PAGE 1041

Manual 5 99a 38 July 17, 2001 Setting Up a Secure Printing Environment Setting up a secure printing environment can be done on three different levels. Access Control lets you assign users to a User, Operator or Manager role to control printers, print services managers, and brokers. For more information, see Managing Printing Security in the Novell Distributed Print Services Administration Guide.
PAGE 1042

Manual Table 3 99a 38 July 17, 2001 Effects of Printer Security with Secure Printing Enabled Printer Security Level Secure Printing Disabled (No SSL) Secure Printing Enabled (With SSL) Low Full access eDirectory authentication Medium Check of user’s effective rights eDirectory authentication and check of user's effective rights High Users must use SSL and authenticate to eDirectory eDirectory authentication, check user’s effective rights, and connection verification Users will receive an er
PAGE 1043

Manual A 99a 38 July 17, 2001 Configuring the HTML Interface This appendix discusses the HTML parameters and operations used in the iPrint interface. This information is provided to give developers insight into how to customize their HTML files. Using this information, HTML developers can edit iPrint Web pages to customize them for their companies. The iPrint HTML files are located in the SYS:\LOGIN\IPPDOCS directory.
PAGE 1044

Manual 99a 38 July 17, 2001 Internet Explorer Browser Customization “HTML Script Example” on page 34 “HTML Code Example” on page 35 HTML Script Example The ExecuteRequest() operation simplifies HTML coding when working with Internet Explorer. It lets you pass/get information from the iPrint without having to reload a Web page. A result type called object is implemented and should be used only in conjunction with ExecuteRequest().
PAGE 1045

Manual 99a 38 July 17, 2001 HTML Code Example The following defines the interface between HTML pages and the browser plug-in. The HTML element