There are four recommended tasks to prepare your network for OES NetWare:
Back up your data.
Update eDirectory (if necessary).
Update eDirectory schema (if necessary).
Update the Certificate Authority object in eDirectory.
To install a new server, insert the NetWare 6.5 SP3 CD 1 (Operating System) into your server’s CD-ROM drive and reboot the server.
NetWare 6.5 or 6.0—To upgrade to OES NetWare, choose one of these options:
a. Perform an In-Place upgrade by running INSTALL from the root of the NetWare 6.5 SP3 CD 1 (Operating System).
b. Use the NetWare Server Consolidation Utility to transfer volumes, directories, users, printers, and printer agents from a source server to a previously installed OES NetWare destination server.
NetWare 5.1—To upgrade to OES NetWare, choose one of these options:
a. Perform an In-Place upgrade by running INSTALL from the root of the NetWare 6.5 SP3 CD 1 (Operating System).
b. Use the NetWare Server Consolidation Utility to transfer volumes, directories, users, printers, and printer agents from a source server to a previously installed OES NetWare destination server.
NetWare 4.2—To upgrade to OES NetWare, perform a Down Server upgrade by restarting the server with the NetWare 6.5 SP3 CD 1 (Operating System). Interrupt the installation process and provide the special inst: upgrade installation parameter. Then resume the installation routine.
Any NetWare 5 or NetWare 4—To upgrade to OES NetWare, use the NetWare Server Consolidation Utility to transfer volumes, directories, users, printers, and printer agents from a source server to a previously installed OES NetWare destination server.
Windows NT v4—To upgrade to OES NetWare, use the NetWare Server Consolidation Utility to transfer volumes, directories, users, printers, and printer agents from a source server to a previously installed OES NetWare destination server.
Whether you are building a new network with OES NetWare or installing it into an existing network, there are certain preparations you should make so the installation goes as smoothly as possible.
For those rare few of you creating a new network from the ground up, you have the opportunity to do all the little things that will make that network easier to manage down the road. Carefully consider your choices of cabling, protocols, addressing, naming schemes, access methods, and so forth. As the technical foundation of your network, these are very difficult to change midstream. Consider business factors such as potential company growth, mergers or acquisitions, reorganizations, and all the other business considerations of the 21st century. If you don’t, your network might lack the flexibility necessary to adapt to strategic and structural changes in your organization.
Unfortunately, the results of all this planning will then have to be weighed against the realities of your budget. There will be inevitable compromises, but this type of advanced planning will ensure those compromises don’t come back to haunt you after the network is running.
Consider the following as you prepare your server hardware for the OES NetWare installation:
Processor speed—The server must have an Intel Pentium II or AMD K7 processor or higher. Novell recommends Pentium III 700 MHz or higher for multiprocessor servers.
CD-ROM drive—The server must have an ISO9660-compatible CD-ROM drive. Novell also recommends using a bootable CD-ROM drive compatible with the El Torito specification for booting directly from the CD.
Server memory—An OES NetWare server must have a minimum of 512MB of system memory (RAM).
The OES NetWare installation routine properly detects most storage adapters and devices, but you should be familiar with the brand and type of your server’s storage controllers (SCSI board, IDE controller, and so on), as well as the brand, type, capacity, and so on, of the storage devices (hard disks, CD-ROM/DVD drives, tape drive, and so on) attached to those controllers.
Size of hard disks—There are two considerations when determining the appropriate size of your server hard disk(s): the DOS partition and the NetWare partition. The DOS partition is a portion of the hard disk reserved for DOS system files, server startup files, and any other DOS utilities you want to store on the server. OES NetWare recommends a DOS partition of at least 1GB, but a good rule of thumb is to start with the minimum and then add 1MB for every MB of server RAM installed. That way you will be able to do a core dump to the DOS partition if necessary. Similarly, OES NetWare recommends at least 4GB for the NetWare partition. This same amount is recommended for the SYS: volume, so the space needs of additional volumes should be added to this minimum amount.
Network adapters—Know the type of network adapters installed in the server and have a copy of the latest LAN drivers available. Note the adapter’s settings and the frame type(s) associated with each board. The default frame type for TCP/IP is Ethernet II, and the default frame type for IPX is Ethernet 802.2.
Note
Older drivers from NetWare 5.1 or NetWare 6 may still work just fine with OES NetWare. If you have an older adapter for which OES NetWare doesn’t include drivers, try the older drivers first before spending the money on a new adapter.
Display and input devices—OES NetWare requires an SVGA or better video adapter and monitor along with a standard keyboard and mouse for direct console operation. However, with the powerful web-based administrative tools available with OES NetWare, it is possible to operate a “headless” NetWare server without any direct input or output devices. This also removes one of the primary sources of mischief in the NetWare environment.
Server name—If you haven’t already done so, you should define a naming convention for your network resources and determine an appropriate name for this server within those conventions. The server name can be from 2[en]47 characters long and can include alphanumeric characters, hyphens, and underscores.
Special hardware configuration—If your server supports any special hardware configurations, such as HotPlug PCI or multiple processors, make sure to have current drivers available in case they are needed during the installation.
Remember that installing a new network operating system is a significant undertaking. All hardware configurations should be tested in a lab environment before introducing them to a new version of NetWare in your production network.
Consider the following as you plan the volumes to be created within your server’s NetWare partition:
SYS volume—The SYS volume is the storage location for all NetWare system files and products. As such, it is absolutely critical that your SYS volume not run out of space. You should plan a minimum of 4GB for the SYS volume to have room for the many additional products and services available with OES NetWare.
Additional volumes—You will likely want to create additional volumes beyond SYS for network applications and data. NSS provides disk pools that can span physical drives. Multiple volumes can reside inside each disk pool. After they’re created, these additional volumes can be used in any way you see fit. You can organize data in volumes based on who needs access, on the type of namespace required for the files, or on how you want the data distributed across the network. Remember to keep volume names consistent with your global naming strategy.
File compression—You can choose to implement file compression at any time, but once installed it cannot be removed without re-creating the volume.
Remember that SYS should be reserved exclusively for system files and “nonvolatile” files that won’t be changing a lot or growing significantly over time. Create as many other pools and volumes as you need to support your non-NetWare applications and data, and avoid mixing it into your SYS volume.
Your biggest considerations as you decide which protocols to run on the OES NetWare server are
What is already out there?
How will network usage evolve in the future?
IP has already been selected as the world’s network standard, due to its exclusive use on the Web. However, NetWare’s original IPX is still in limited use, supporting legacy applications and queue-based printing for the most part. You will almost certainly be implementing IP in your network, but it’s still a good idea to understand the advantages and disadvantages of both protocols, along with some other common protocols and protocol configurations prior to implementing your network:
Internet Protocol (IP)—Novell made the move to IP as its default protocol with the release of NetWare 5, and if your network is connected with any external network or the Internet you will be using IP to make that connection. An IP network requires some advanced planning to be sure that all devices can communicate, particularly if you are connecting your network to the outside world (see Table 2.1).
Table 2.1. IP Considerations
|
CONSIDERATION |
DESCRIPTION |
|---|---|
|
Server IP address |
Each device on an IP network must have a unique address. If you are connecting to the Internet, you can reserve a unique address, or block of addresses, through the Internet Network Information Center (InterNIC). |
|
The subnet mask identifies a portion of the network. Subnet masks enable you to divide your network into more manageable segments. |
|
|
Default router address |
This entry determines where packets with an unknown network address will be sent. The default router is often that which connects your network to the Internet. If you want to specify a specific default router, make sure you have that information prior to the OES NetWare installation. |
|
DNS information |
If you want to use domain name services on your network, you need to know your network’s domain name and the addresses of any name servers you want to use. Configuring DNS on OES NetWare is covered in Chapter 4, “OES Management Tools.” |
Internet Packet Exchange (IPX)—IPX is a Novell proprietary protocol that became a de facto standard due to NetWare’s market acceptance. It’s very easy to install and configure, but the Internet has relegated it to a legacy role.
Note
Each server on an IPX network must have a unique internal net number. This number can be randomly generated during installation or you can specify it manually.
Note
You can choose to install both IP and IPX protocol stacks on your OES NetWare server to support both legacy applications and external connectivity. However, this solution adds administrative overhead because both environments have to be managed separately. Furthermore, because IP and IPX services cannot interact, you can run into trouble accessing IPX services from an IP segment and vice versa.
Compatibility Mode—If necessary, Compatibility Mode (CM) can help in a transition from IPX to IP by letting IPX-dependent applications receive the information they need in IPX format, even though the network is running IP. OES NetWare won’t install CM by default. If you need to configure it on your network, see the OES online documentation for details.
There are some basic pieces of eDirectory information you have to supply to complete the OES NetWare installation. eDirectory design concepts are presented in Chapter 6, “Novell eDirectory.” Additional eDirectory reference material is available in Appendix D, “eDirectory Reference Materials”:
Tree name—You need to know the name of the eDirectory tree into which the OES NetWare server will be installed.
Server location within the eDirectory tree—Prior to installing the server, make sure you are familiar with the organization of your eDirectory tree. You need to specify the context within which the server will reside. This consists of the name of the Organization or Organizational Unit to which this server will belong.
Administrator name and password—If you are installing the first server in a new tree, an Admin account will be created and you will specify the Admin password. If you are installing the server into an existing eDirectory tree, you need to provide the name, including context, and password of the existing Admin user.
Server’s time zone—You need to specify the server’s time zone and whether that time zone supports daylight savings time.
Time synchronization—NetWare provides its own proprietary time synchronization service, which is largely self-configuring. The first NetWare server in a network is created as a Single Reference timeserver. Subsequent servers, even if they are installed in a new eDirectory tree, will default to secondary timeservers. If your eDirectory tree spans geographic locations or manages a heterogeneous server environment with Linux, UNIX, or Windows servers, you should implement a time synchronization scheme based on the standard Network Time Protocol (NTP). For more information on time synchronization, see Chapter 5, “OES NetWare Server Management.”
OES NetWare includes Novell eDirectory v8.7.3. To support this version of eDirectory in your existing network, make sure you apply the latest eDirectory Service Packs on your existing servers. You can get the latest eDirectory service packs from Novell at support.novell.com.
OES NetWare relies on Novell Distributed Print Services (NDPS) to provide a robust network printing infrastructure. NDPS has been in use since NetWare 5. iPrint, first released with NetWare 6, leverages NDPS to deliver true “print from anywhere,” simple printer configuration, and robust Internet printing options based on the Internet Printing Protocol (IPP). For more information on iPrint and NDPS, see Chapter 11, “OES NetWare Printing.”
To plan for an NDPS printing environment, consider the following:
Will NDPS be installed—If this server will function as part of the NDPS environment, remember to install NDPS as part of the OES NetWare installation.
Will an NDPS broker be installed—The NDPS broker provides the management framework within which all NetWare print activities occur. The NDPS installation routine will install an NDPS broker on a server only if there is no other broker within three network hops of the server. If necessary, you can override this setting and specify whether to install a broker on this server.
Disable any broker services—The NDPS broker provides three principal services: Service Registry, Event Notification, and Resource Management. Depending on how you choose to configure your NDPS environment, one or more of these services may not be necessary on the server.
Before you install OES NetWare into an existing network, there are a few things you should do to make sure the network is ready for the introduction of OES NetWare. Novell includes Deployment Manager (see Figure 2.1) to help identify and automate these tasks. You can run Deployment Manager from any Windows 2000 or XP workstation by executing NWDEPLOY.EXE from the root of the OES NetWare Operating System CD.
Note
Deployment Manager requires Internet Explorer 5 or 6 to run in a browser window. If you would rather run Deployment Manager as a standalone application, or you do not want to use the ActiveX Control included with the browser-based version, run NWDEPLOYNOBROWSER.EXE instead of NWDEPLOY.EXE.
Deployment Manager is organized into three main categories: Network Preparation, Install/Upgrade Options, and Post-Install Tasks. To prepare your network for OES NetWare, you will focus on the tasks listed under Network Preparation.
You can run Deployment Manager and review its overviews and checklists from any workstation. However, to perform the network checks and updates necessary to prepare your network for the OES NetWare installation, you need to have the latest NetWare client installed. See Chapter 3, “OES NetWare Clients,” for information on installing the NetWare client.
Warning
Before performing any significant work on your network, it is always a good idea to back up your network data. This is noted as the second Network Preparation task in Deployment Manager. Use your preferred data archive utility, such as NetWare’s own Storage Management Services (SMS), to back up eDirectory and server data that might be affected by installation and upgrade processes. For more information on backing up your network data, see Chapter 10, “OES NetWare File Storage and Management.”
Note
Because preparations for OES NetWare will make changes to your servers, install the latest NetWare support packs on the servers that will be associated with the OES NetWare server you are preparing to install. Failure to do so could result in instability in your network environment. Support packs can be found at http://support.novell.com/filefinder/.
Selecting this option enables you to search your network for existing versions of eDirectory to determine whether any existing versions need to be updated prior to installing or upgrading to OES NetWare. To do this, complete the following steps:
1. From Deployment Manager, select Search Tree for eDirectory/NDS versions.
2. Select View and Update NDS.
3. Browse to the eDirectory tree and/or container you want to search for NetWare servers and click Next. Select Include Subordinate Containers to search the entire tree or tree branch you have specified.
4. Deployment Manager will show you the version of eDirectory installed on each server it finds and will indicate whether it needs to be updated. If no server needs to be updated, click Exit to return to the Deployment Manager main menu.
5. Click Next to perform the eDirectory update on those servers that require it.
6. Click Next to restart eDirectory on that server.
7. Click Exit to return to the Deployment Manager main menu. This is an important step because failure to upgrade eDirectory can result in schema corruption and other nastiness.
If you are installing OES NetWare into an existing eDirectory environment, Deployment Manager will review the existing eDirectory schema and prepare it for the new eDirectory installation. For more information on eDirectory schema see Chapter 6.
To review the current schema configuration on your network with Deployment Manager, complete the following steps:
1. From the left pane of Deployment Manager select Prepare for New eDirectory.
2. Select Extend Core Schema in the right pane.
3. Browse to the eDirectory tree you want to review and click Next.
4. Select one of the servers from the list of servers with Read/Write replicas of the Root partition and click Next. The schema will be extended, as necessary, to support new eDirectory features and functionality.
5. Click Exit to return to the Deployment Manager main menu.
With the schema updates in place you can be certain that OES NetWare servers will be able to communicate effectively with the existing eDirectory servers on your network.
Note
If you have NetWare 4 servers in your network with NDS v6 installed, part of the schema extension process includes the generation of Globally Unique Identifiers (GUIDs) that are necessary for trustee assignments to work properly. GUIDs will be created automatically when the updated DS.NLM is started on the NetWare 4 servers, and you can manually trigger this reload of DS.NLM by selecting the Generate GUIDs on NetWare 4 Servers option in Deployment Manager.
Deployment Manager includes several other associated preparatory tasks that may or may not be applicable to your environment, depending on the version(s) of NetWare you may be running. Optional tasks include preparing for server upgrades, Certificate Authority updates, cryptographic key verification, and preparing for Universal Passwords and Native File access.
Each of these preparatory tasks is described with the topic to which it relates, but you should review all the information contained in the Deployment Manager Network Preparation topics and understand which tasks apply to your environment.
After you have gathered all the information you need and made the necessary decisions with regard to installation and configuration, you are ready to perform the OES NetWare installation.
This section explains how to install a new server. If you are upgrading from a previous version of NetWare or from a different network operating system, skip to the section “Upgrading an Existing Server,” later in this chapter. There are three main steps to the OES NetWare installation:
1. (Conditional) Configure a DOS partition.
2. Install startup files and create the SYS volume.
3. Configure the server environment with NetWare Installation Wizard.
The first step is necessary occasionally to prepare the server for the installation process.
The second step takes you through the hardware setup and creates the SYS volume on which the NetWare system files will be stored. This portion of the installation is text-based and runs under DOS on the server. This is the “blue screen” installation for which NetWare has become famous over the years. Throughout this portion of the installation you will be prompted to review the default configuration and to choose Modify or Continue at each screen. Choose Modify to make changes to the default values that the installation routine offers. Choose Continue to accept values and proceed with the installation. In some cases you need to press F10 to save your changes before continuing.
The final step configures the server environment and switches to a graphical tool known as the NetWare Installation Wizard. The Installation Wizard is a Java-based application that enables you to use a mouse during the rest of the installation.
After you have gathered all the information you need and made the necessary decisions with regard to installation and configuration, you are ready to perform the OES NetWare installation.
If your server hardware is capable of booting from a CD-ROM, the OES NetWare bootable CD-ROM will kick you right into the server installation process. If, for some reason, this option does not work, complete the following steps to create a bootable partition:
1. If there is an existing operating system, make sure that any data you want to save has been backed up, along with CONFIG.SYS, AUTOEXEC.BAT, and any device drivers.
2. Boot the server with the OES NetWare License/Cryptography disk. It is a bootable DR-DOS disk and has all the utilities you need to set up the DOS partition.
3. Load FDISK /X. From there you can delete any existing partitions on your server’s hard disk(s). Then create a Primary DOS partition of at least 1GB plus 1MB for each MB of RAM in your server.
4. Reboot the server from the floppy, use FORMAT C: /S/X to format the partition you have created, and transfer DR-DOS system files.
5. Copy CONFIG.SYS, AUTOEXEC.BAT, and any required device drivers you backed up in step 1 to your newly formatted C: drive. This should enable you to boot directly from the C: drive and access the CD-ROM as drive D:.
With the bootable partition in place you are ready to start the actual NetWare installation.
Complete the following steps to install OES NetWare startup files and create the SYS volume:
1. Boot from the NetWare 6.5 SP3 CD 1 (Operating System). Alternatively, boot your server to DOS and execute INSTALL.BAT from the root of the NetWare 6.5 SP3 CD 1 (Operating System).
2. At the Languages screen, select the language in which you want the server installed and press Enter.
3. At the Regional Settings screen, make your selections and click Continue. The Country, Code Page, and Keyboard settings ensure that NetWare correctly processes keyboard input and extended characters.
4. Review the NetWare license agreement and press F10 to accept it.
5. Review the JInfonet license agreement and press F10 to accept it.
6. Select either a Default or Manual installation, then highlight Continue and press Enter. If you choose Default install, you can skip ahead to the “NetWare Installation Wizard” section, which follows. The default install detects drivers and installs the NetWare server with default settings, including the following:
4GB SYS volume (with remaining disk space left as free space)
LAN and disk drivers auto-discovered and loaded
Video mode: SVGA Plug N Play
Keyboard: United States
Mouse: Auto-discovered and loaded
Tip
If you want to automate the installation with a response file, press F3 and specify the path to the appropriate file. The NetWare 6.5 installation automatically creates a response file during any NetWare 6.5 installation and saves it to SYS:NIDATARESPONSE.NI. By making minor modifications to this file, such as changing the server name or IP address, you can use the response file from one server to create another automatically with the same characteristics. For more information on using response files, see the OES online documentation.
The Manual installation walks you through each step of the server installation and enables you to customize and explore your selections more completely. The Manual installation continues with the following steps.
7. At the Prepare boot partition screen, make your selections and click Continue. Here you can delete any preexisting partitions to make more room for the NetWare partition. You can even delete the DOS partition and re-create one of another size.
8. At the Server Settings screen, make your selections as follows and click Continue:
Server ID number—This is a random number for identifying the server on the network. It needs to be changed only if you are filtering addresses or if you have a predefined addressing scheme for your servers.
Load server at reboot—Specify whether you want NetWare to restart automatically when the server is rebooted. This adds two lines to your AUTOEXEC.BAT to load SERVER.EXE from the NWSERVER folder.
Boot OS—Specify whether you want the server’s boot sector to specify DOS or NetWare as the default boot environment.
Allow Unsupported Drivers—If set to Yes, drivers that have not been approved by Novell will be loaded automatically if no other suitable driver is found.
Server SET parameters—If your server devices, such as network or storage adapters, require any special load parameters, they can be entered here and stored in the STARTUP.NCF file, which is located in the NWSERVER directory on your DOS partition.
Video—Specify the graphics mode for your monitor. The default plug-and-play option will typically work.
The installation program now copies startup files and drivers to the C:NWSERVER folder on the DOS partition. When this process is complete, you continue with the server installation.
9. Specify, or note, the Platform Support Module that your server will use and click Continue. NetWare typically auto-detects this driver, but you can modify the selection manually.
10. Specify, or note, the HotPlug Support Module and the Storage Adapter(s) that your server will use and click Continue. NetWare typically auto-detects these drivers, but you can modify the selection manually.
11. Specify, or note, the Storage Devices that your server will use and click Continue. NetWare typically auto-detects these drivers, but you can modify the selection manually.
12. Specify, or note, the Network board that your server will use and click Continue. NetWare typically auto-detects these drivers, but you can modify the selection manually.
13. The NetWare Loadable Modules option enables you to load special NLMs required by some server and network configurations. For example, ROUTE.NLM is necessary for installing a server into a token ring network.
14. Specify the size of the SYS: volume you want created and select Create. Novell recommends a SYS: volume of 4GB.
At the NSS Management Utility main menu, click Continue Installation. This utility can be reached after server installation by loading NSSMU.NLM at the server console. From this utility, you can view, modify, and see the NSS statistics for your current storage configuration.
At this point, the operating system CD is mounted, your newly created SYS: volume is mounted, and the installation program copies all the necessary system files to it. Then the installation program launches the NetWare Installation Wizard, a graphical program that will take you through the rest of the installation.
Continue with the following steps to set up the OES NetWare server environment:
1. At the Product Installation Type screen, select the type of installation you want to perform and click Next. The Installation Wizard routine is identical, regardless of the selection you make here:
Open Enterprise Server 1.0—This option includes NetWare 6.5 Support Pack 3 and adds three additional changes: iManager 2.5 to support integrated management of NetWare and Linux environments; Virtual Office 1.5; and Quickfinder Server, which replaces Web Search Server.
NetWare 6.5 Support Pack 3—If you do not need the integrated management features of OES you can choose to install NetWare 6.5 Support Pack 3 without the updates to iManager, Virtual Office, and Web Search Server.
2. At the Choose a Pattern screen, select Customized NetWare Server and click Next. Patterned Deployments enable you to create special-purpose NetWare installations that include only those components specifically required for the functionality you want. There are several patterns Novell has included with OES NetWare. Select a pattern from the list to see a description of each pattern and the key components installed with that pattern.
3. At the Components screen, select the optional NetWare components you want to install on your server and click Next. Because of the number of optional products with OES NetWare, the specific installation steps for each will not be presented here, but they are provided as each product is introduced later in this book. However, selecting a given component opens a brief description of that component.
Note
The following required components are installed on every NetWare server and so are not included in the optional components list: Novell eDirectory, Java Virtual Machine (JVM), Novell International Cryptographic Infrastructure (NICI), Storage Management Services (SMS), Novell Remote Manager (NRM), and Novell Certificate Server.
4. At the Summary screen, review your component selections and click Copy Files.
At this point you will be required to insert the NetWare 6.5 SP3 CD 2 (Products) to install OES NetWare components and any additional products you have selected.
5. Enter a name for this server and click Next. Click Advanced to view/modify CONFIG.SYS, AUTOEXEC.BAT, Server ID, and Server language support. Typically, you won’t have to make any changes to these settings.
6. At the Protocols screen, make your selections and click Next. Highlight a listed network board and choose the protocols that will be bound to that board. You can choose IP, IPX, or both. If you choose IP, the server will attempt to query the network for information on default router, Subnet mask, and IP address to help you along. If you have multiple network boards installed, repeat this process for each board. Similarly, you can select the IPX frame type and specify appropriate network numbers if you are using the IPX protocol on your network.
a. Protocols enables you to configure your IPX frame types.
b. IPX Compatibility enables you to configure Compatibility Mode (CM) to permit legacy IPX applications to run on your IP network.
c. SNMP enables you to set some basic information that will accompany SNMP traps.
d. SLP enables you to define an SLP Directory Agent (DA) for your network, if one is defined.
7. At the Domain Name Service screen, make your selections and click Next. If you are using DNS on your network, specify a hostname for the server, specify your organization’s domain, and then enter the address(es) of the nearest DNS name servers. You can find more information on DNS/DHCP in Chapter 6.
8. At the Time Zone screen, make your selections and click Next. Select the time zone in which the server will reside. If this time zone uses daylight savings time, make sure the daylight savings time box is checked.
Note
The Advanced button opens a page that enables you to configure the server as a specific type of NetWare time server. Alternatively, you can choose to use NetWare Time Protocol (NTP) for managing time synchronization between servers. For more information on time synchronization and NTP, see Chapter 5.
9. At the eDirectory Installation screen make your selections and click Next. Choose whether this server is being installed into a new eDirectory tree or an existing eDirectory tree.
For a new tree, you specify a tree name, server context, Admin object name, context, and password.
For an existing tree, click the Browse button and select the container into which you want the server installed. You can click Add to create a new container. You will be required to log in as a user with administrative rights to complete this process.
10. At the eDirectory Summary screen, click Next.
11. At the Licenses screen, make your selections and click Next. Insert the NetWare 6.5 License/Cryptography disk or specify the path to your NetWare license files (.NLF). You can also select the Install Without Licenses check box. This option allows you only two user connections to the server. Licenses can be installed after the server installation. More information on NetWare licensing is provided later in this chapter.
12. At the License Certificate Context screen, make your selection and click Next. NetWare 6.5 uses a User licensing scheme that links a license unit directly to a user object so users can log in from any workstation at any location without fear of not having a licensed connection available. License certificates should be installed at or above the users’ context in the eDirectory so they are readily available.
13. At the LDAP Configuration screen, make your selections and click Next. Default LDAP ports are port 389 for unencrypted communications and port 637 for encrypted communications. Uncheck the Require TLS for Simple Bind with Password check box if you want LDAP clients to be able to log in with unencrypted passwords. This option is not recommended if you believe there is any chance of on-the-wire packet snooping.
14. At the Novell Modular Authentication Service (NMAS) screen, make your selections and click Next. You can choose among a variety of password and certificate-based authentication techniques available through NMAS. You can find more information on each of these authentication methods in Chapter 7, “Users and Network Security.”
15. At the Installation Complete window, click Yes to restart your new OES NetWare server. When the computer reboots, the server automatically restarts if you made this selection during the installation. Otherwise, change to the NWSERVER directory in DOS and run SERVER.EXE to start NetWare 6.5.
When the server is running you will see a graphical screen within which NetWare utilities can be displayed. To bring up ConsoleOne, the primary NetWare management utility, select the Novell button at the bottom of the screen and select ConsoleOne. There are also icons at the bottom of the screen for the Server Console, Editor, File Browser, Console Log, and NetWare Remote Manager (NoRM). To toggle out of the graphical environment and access the various text-based server screens, press Alt+Esc.
There are multiple upgrade options with OES NetWare, depending on your current Network Operating System (NOS) and your goals for the upgrade. There are three types of upgrades available with OES NetWare: In-Place Upgrade, Server Consolidation, and Server Migration. Not every upgrade option is available for every NOS. Table 2.2 outlines the upgrade options and NOS versions with which they are compatible.
Table 2.2. NetWare 6.5 Upgrade Options for Different NOS Versions
|
UPGRADE TYPE |
SUPPORTED NOS |
DESCRIPTION |
|---|---|---|
|
In-Place |
NetWare 6.5 NetWare 6.0 NetWare 5.1 NetWare 4.2 |
Traditional upgrade method in which the server is upgraded directly from the server console. NetWare 4.2 is a special case known as a Down Server upgrade. |
|
Server Consolidation |
NetWare 6, 5, and 4 Windows NT 4 |
Uses the NetWare Server Consolidation Utility to transfer volumes, directories, users, printers, and printer agents from a source server to a previously installed OES NetWare destination server. |
|
Server Migration |
NetWare 3 |
The legacy NetWare Migration Wizard can be used to migrate an old NetWare 3 server to a new OES NetWare server. For more information on server migration, see the OES NetWare online documentation. |
The NetWare Server Consolidation Utility migrates NT domain users and local and global groups from a Windows NT v3.51 or v4 server to a destination eDirectory tree. During the migration, the NT users and groups are converted to eDirectory objects and placed in the destination eDirectory tree. Server consolidation also migrates NT shared folders to a NetWare file system while migrating and converting Windows NT permissions to NetWare trustee rights.
The Migration Wizard copies the NetWare 3 file system and bindery objects to a destination Novell eDirectory tree. When the bindery objects are copied to the destination eDirectory tree, they are automatically converted to eDirectory objects. For more information on the NetWare Migration Wizard, see the OES NetWare online documentation.
This is the simplest and most straightforward way to upgrade to OES NetWare. The in-place upgrade is available only for the following versions of NetWare. Install the latest support pack installed on the server prior to performing the in-place upgrade. NetWare support packs are available online at http://support.novell.com/filefinder.
NetWare 6.5 Support Pack 2
NetWare 6.0 Support Pack 5 or later
NetWare 5.1 Support Pack 6 or later
NetWare 4.2 Support Pack 9 or later
The in-place upgrade will update the operating system, eDirectory, and additional NetWare components that have been installed on the server, such as Apache Web Server, Certificate Server, and so on.
You should also review and complete the minimum requirements described in this section prior to performing the upgrade.
The server hardware must meet the minimum requirements for OES NetWare as described in the “Server Hardware Planning” section earlier in this chapter. The server to be upgraded should also be in good general health. To check the health of a server, you can use Deployment Manager:
1. Launch Deployment Manager and select Prepare a Server for Upgrade in the left pane.
2. Select Server Health Utility from the right pane.
3. Browse to the server on which you want to run the health check and click Next.
4. Log in as a user with Administrator rights and click OK. A series of tests will be run on the target server.
5. At the Health Check Selection screen, select those health checks you want to run and click Next. If any discrepancies are found, a message box will pop up with a description of the problem and possible solutions, or sources for more information.
6. At the Health Check Summary, click Next to continue. This screen shows the results of the tests and indicates any areas where your server might be lacking, or is in need of attention (see Figure 2.2). Make sure all errors are resolved before continuing with the upgrade.
The following are a few odds and ends you should think about before the upgrade:
NetWare maintains deleted files in a salvageable state. Make sure there are no deleted files you want to salvage prior to the upgrade. All deleted files will be purged as part of the upgrade.
Make disk copies of LAN drivers, storage drivers, and the AUTOEXEC.NCF from the server’s SYS volume.
If you are running a NetWare cluster, you can also use Deployment Manager to prepare a cluster server for the upgrade to OES NetWare. For more information on NetWare clustering, see Chapter 12, “OES NetWare File Access.”
OES NetWare offers a remote upgrade option for the first time in NetWare. You can run a remote upgrade from either Deployment Manager or iManager 2.0. However, after the upgrade is started the process is the same, regardless of whether it is run remotely.
No matter how you plan on performing the upgrade, remember that your existing NetWare server must have a DOS partition large enough to support OES NetWare. If your DOS partition is smaller than 1GB, you should create a new DOS partition and perform a new server installation as described previously, or consider a server migration, which is discussed later in this chapter.
If you are doing the upgrade from the server console, complete the following steps:
1. Insert the NetWare 6.5 SP3 CD 1 (Operating System) into the server CDROM drive.
2. From the system console (the server command line), mount the NetWare 6.5 SP3 CD 1 (Operating System) as a NetWare volume by typing CDROM at the server console. You can then type VOLUMES to confirm that the CDROM has been mounted.
3. Switch to the GUI console and choose Novell, Install. This is a change from previous versions of NetWare in which the upgrade was performed from the system console.
4. At the Installed Products page, click Add.
5. At the Source Path screen, browse to the root of the NetWare 6.5 SP3 CD 1 (Operating System). The volume name should be NW65OS:. You should see the PRODUCT.NI file in the right pane. Highlight PRODUCT.NI.
6. Click OK to return to the Source Path screen and click OK to continue.
From here, you continue with the standard upgrade process. See the section “Finishing the Upgrade,” later in the chapter.
Deployment Manager now offers the ability to upgrade a server to OES NetWare without ever visiting the console. To upgrade a server through Deployment Manager, complete the following steps:
1. (Conditional) You can use a Windows 95/98 or Windows NT/2000/XP workstation to run Deployment Manager. Make sure the workstation has the latest Novell client installed, and that you are logged in as the Admin user to the eDirectory tree where the server to be upgraded is located. For more information on installing the Novell client, see Chapter 3.
2. On your selected workstation, insert the NetWare 6.5 SP3 CD 1 (Operating System). Launch NWDEPLOY.EXE from the root of the CD to start Deployment Manager.
3. Select Upgrade to NetWare 6.5 in the left pane.
4. Select Upgrade a Server Remotely in the right pane.
From here, you continue with the standard upgrade process. See the section “Finishing the Upgrade,” later in this chapter.
As the common management tool for OES, iManager also provides a mechanism for upgrading existing NetWare servers to OES. For information on installing and configuring iManager, see Chapter 4.
To upgrade a server through iManager, complete the following steps:
1. Launch iManager and select Install and Upgrade in the left pane.
2. Select Upgrade to NetWare 6.5.
3. Select Upgrade a Server Remotely in the right pane.
4. Browse to the root of the NetWare 6.5 SP3 CD 1 (Operating System) and click OK.
From here you continue with the standard upgrade process. See the next section, “Finishing the Upgrade.”
By moving the upgrade routine to the Java-based GUI, Novell has made both remote and console-based upgrades largely identical. There is even less reason to “visit” your server directly because the Java tools now enable you to do most anything remotely from any workstation with a network connection.
To complete the in-place upgrade, use the following steps:
1. Review the NetWare license agreement and click I Accept.
2. Review the JInfonet license agreement and click I Accept.
3. (Conditional—Remote Upgrade) At the Target Server screen specify, or browse to, the name of the server you want to upgrade. You will be asked to confirm authentication to the target server before proceeding.
4. At the Backup Server Files screen, make your selections and click Next:
Backup the server boot directory files—Select the Yes radio button to back up your existing server files. If you choose this option, specify the location of the backup files. Default path is C:NWSERVER.OLD.
Automatically reboot—Select the Yes radio button to have the server automatically reboot upon completing the upgrade.
Allow unsupported drivers—Select the Yes radio button to allow device drivers that have not been approved by Novell to be automatically loaded if no other suitable driver is found.
Specify the upgrade type—Select either a Default or Manual installation. The Default and Manual installation options have been discussed previously in the section “Installing a New OES NetWare Server.”
5. At the Product Installation Type screen, select the type of installation you want to perform and click Next:
Open Enterprise Server 1.0—This option includes NetWare 6.5 Support Pack 3 and adds three additional changes: iManager 2.5 to support integrated management of NetWare and Linux environments; Virtual Office 1.5; and Quickfinder Server, which replaces Web Search Server.
NetWare 6.5 Support Pack 3—If you do not need the integrated management features of OES you can choose to install NetWare 6.5 Support Pack 3 without the updates to iManager, Virtual Office, and Web Search Server.
6. At the Components screen, make your selections and click Next. Check all those components you want to install and/or upgrade during the server upgrade. You should select, at a minimum, iManager 2.5 and Apache/Tomcat.
7. At the Summary screen, review your selections and click Copy Files. The OES NetWare upgrade process will now copy the new server files. You will also be prompted to insert the NetWare 6.5 SP3 CD 2 (Products) so that product files can be copied.
Note
If you are performing a remote upgrade, remember that all the installation files will be moving across the network. The data transfer will slow things down significantly. During remote upgrades, the server will reboot and go through an automated upgrade process. When completed, Deployment Manager will reconnect to the server.
8. When prompted, log in as the Admin user and click OK to complete the eDirectory installation.
9. At the eDirectory Summary screen, review the eDirectory information and click Next.
10. At the Licenses screen, make your selections and click Next. Insert the OES NetWare License/Cryptography disk or specify the path to your NetWare license files (.NLF). You can also select the Install Without Licenses check box. This option allows you only two user connections to the server. Licenses can be installed after the server installation. More information on NetWare licensing is provided later in this chapter.
11. At the License Certificate Context screen, make your selection and click Next. OES NetWare uses a User licensing scheme that links a license unit directly to a user object so users can log in from any workstation at any location without fear of not having a licensed connection available. License certificates should be installed at or above the users’ context in the eDirectory so that they are readily available.
12. At the Novell Modular Authentication Service (NMAS) screen, make your selections and click Next. You can choose among a variety of password and certificate-based authentication techniques available through NMAS. You can find more information on each of these authentication methods in Chapter 7.
Note
At this point, you may be prompted for other product-specific information, depending on those products you have chosen to install as part of the server upgrade.
13. At the Installation Complete window, click Yes to restart your new OES NetWare server. When the computer reboots, the server will automatically restart if you made this selection during the installation. Otherwise, change to the NWSERVER directory in DOS and run SERVER.EXE to start OES NetWare.
The OES NetWare installation is now complete. The new server will start participating in eDirectory activities immediately and you can start configuring the server for the specific purposes you might have in mind.
The Down Server upgrade is a special case option available only for those times when the upgrade options discussed previously don’t work. Situations in which the Down Server upgrade may be appropriate include
You are upgrading from a NetWare 4.2 server with Support Pack 9.
An upgrade fails at some point after the Health Check Summary step completes. After the failure, the upgrade cannot be restarted.
As with any other server upgrade operations, you should make a full backup of your server data before attempting a Down Server upgrade.
Warning
The Down Server Upgrade has been tested only with NetWare 4.2 Support Pack 9. Its use in any other NetWare version is discouraged except for the emergency situation described earlier.
To perform a Down Server upgrade, complete the following steps:
1. If the server is running, enter DOWN and then EXIT at the server console.
2. Insert NetWare 6.5 SP3 CD 1 (Operating System) in the server’s CD drive.
3. Restart the server.
4. When prompted, press any key to interrupt the installation process.
5. Press P to specify installation parameters.
6. Type [inst: upgrade] and press Enter.
7. Press I to continue the installation.
From this point, the Down Server upgrade mimics in most ways the installation of a new OES NetWare server, as described previously in the section “Install Startup Files and Create SYS Volume,” starting with step 6 and continuing through the section “NetWare Installation Wizard.” The only variations occur when new installation steps are unnecessary due to the fact that they have already been defined on the existing server—for example, configuring the SYS: volume, defining protocols, etc.
With the changes in server hardware over the last years, lots of RAM, and huge drive arrays and Network-attached storage (NAS) options, the Server Consolidation Utility (SCU) enables you to consolidate data from redundant servers into a smaller number of more easily managed OES NetWare servers.
SCU enables you to copy entire volumes and/or specific directories from NetWare 4, 5, 6, or Windows NT source servers to NetWare 5.1 or later destination servers. The accompanying rights, trustees, ownership, namespace information, and even printers and printer agents can be copied along with the files to the destination server. For many consolidation operations, the servers can even be in different eDirectory trees.
SCU requires a Windows workstation with the following characteristics:
The SCU workstation should be a Windows NT 4, Windows 2000 (support pack 2 or later), or Windows XP Professional workstation with at least 50MB available disk space.
Install the Novell client that ships with OES NetWare or run a minimum of Novell client for Windows NT/2000 version 4.83 or later. You will need supervisor rights to both the source and destination servers.
Make sure Microsoft Data Access Components (MDAC) 2.7 or later is installed on the workstation. For information on MDAC and to install the latest version of MDAC, see http://msdn.microsoft.com/library/default.asp?url=/downloads/list/dataaccess.asp.
If the source server is running NetWare 4.x, configure the Novell client for IPX or IPX and the IP protocols.
For best performance, the source server, destination server, and client workstation should be located on a common network segment.
After the workstation prerequisites have been met, you can complete the SCU installation. SCU files are located on the NetWare 6.5 SP3 CD 1 (Operating System), in the PRODUCTSSERVCONS directory. To complete the installation, follow these steps:
1. Launch the SCU installation by executing NWSC.EXE.
2. Specify the language for the utility installation and click OK.
3. At the Introduction screen, click Next.
4. At the License Agreement screen, select the I accept the terms of the License Agreement radio button and then click Next.
5. At the Choose Destination Location screen, specify the path into which you want to install SCU. The default location is C:Program FilesNovell Server Consolidation Utility.
6. At the Installation Summary, click Install.
7. At the ReadMe screen, click Next.
At the Install Complete screen, click Done.
With the SCU installed you can now perform server consolidations in your network. This is described in the following section.
Before starting the actual consolidation process, make sure your servers are prepared for the consolidation by reviewing the following checklist:
The destination server must be running NetWare 5.1 or later.
The source server must be running NetWare 4.1 or later, or Windows NT.
Make sure that the latest support packs are installed on both the source and destination servers.
(Conditional) If you are migrating data from NetWare 4, make sure the source server’s volumes are running long namespace support on all volumes to be copied. To add long namespace 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.
Have a current backup of eDirectory files from both source and destination eDirectory trees, if applicable.
Both source and destination server must be using the same code page to avoid data corruption. If the code pages do not match, Novell only recommends converting an English code page server to a non-English code page. Converting from non-English to English, or from non-English to another non-English, can cause file corruption. For information on converting an English server to a non-English code page, see the OES online documentation.
(Conditional) If there are compressed files on the source server, set Convert Compressed to Uncompressed=0. This prevents the files from decompressing because of the consolidation process.
Make sure that the latest SMDR.NLM and TSA.NLM files are loaded on the source and destination server.
(Conditional) If you are consolidating from a NetWare 4 source server, make sure the source and destination servers can communicate via IPX. To do this, use the IPXPING utility from the console of both source and destination server to ping the internal IPX number of the other server.
There are also some general consolidation issues that you should consider as you plan your server consolidation:
Open files cannot be copied. However, if you are copying from an NSS volume you can enable File Copy on Write, which permits an open file to be accessed in the same state that it was in when it was last closed by all processes. You can set this volume attribute from ConsoleOne or from the server console by typing NSS/filecopyonwritesnapshot=<volume name>.
If a failover occurs on a NetWare cluster involved in a server consolidation, SCU will stop. The server consolidation will have to be repeated.
NDPS printer agents can be moved as part of a server consolidation, but only within the same eDirectory tree. Print queues cannot be moved. Printer agents that are moved still use the same print broker.
Print Services Managers must be operational during the server consolidation. After moving the printer agents, unload the Print Services Manager on the source server so the migrated printer agents can establish a connection to the destination Print Services Manager.
After these preconditions are met, use the SCU to perform a server consolidation. You can consolidate from NDS/eDirectory, or from a Windows NT domain. The following describes the process for consolidating a NetWare server to OES NetWare. For other consolidation options, see the OES online documentation.
An SCU project file records your consolidation plan. The details of the consolidation are recorded, enabling you to run them immediately or save them to run at a later time.
To create an SCU project, complete the following steps:
1. Launch SCU. Once installed, it is available in Windows by selecting Start, Program Files, Novell Server Consolidation Utility. The executable file is FC.EXE. You can also launch SCU from Deployment Manager by selecting Consolidate Servers in the left pane and then selecting Install/Run the Server Consolidation Utility from the right pane.
2. Click OK at the opening splash screen. At the Startup screen, choose Create a New Project and click OK.
3. At the Project Type screen, make your selection and click OK. For a consolidation from a NetWare server, choose NetWare NDS/eDir Tree; for a Windows NT consolidation, choose Microsoft Windows Domain.
4. At the Setup Tasks screen, click Next.
5. Choose a name and location for the project file and click Next.
6. Choose the source and destination tree for the consolidation and click Next. You must be logged into a tree to see it in the drop-down list. If necessary you can authenticate to the trees you want by selecting the Login button.
7. Click Create to finish creating the project file.
After the new project file is created, you will be taken to the project window (see Figure 2.3). From this window you model the consolidation as you want it to take place. You select the volumes, directories, and printer objects to move, and drag them to the location you want in the new tree. The source tree is shown in the left pane, and the destination tree is shown in the right pane. Drag objects from the left pane to the right pane.
8. Click Do the Consolidation after you have modeled the consolidation in the project window. There are several conventions you should be aware of as you model the server consolidation in the project window. At any time you can save your project, in progress, by selecting File, Save As.
When moving Volume objects, a Volume Drop Options dialog box will ask you to migrate the volume contents into the directory or volume that you selected or to create a new directory with the name of the volume that is being moved. Select the option you want and click OK.
After you have dropped a volume or directory to a location in the destination tree, you cannot drag it to a new location. Rather, highlight the volume or directory and click Back Out on the button bar. This removes the volume or directory from the destination tree and enables you to reinsert it into the correct location.
To create a new container or folder in the destination tree as part of your consolidation process, highlight the parent container or folder in the right pane and click New Folder on the button bar.
To rename a newly created container or folder, highlight the parent container or folder in the right pane and select Edit, Rename.
To determine the new location of an object from the source tree, highlight the object in the left pane and choose Edit, Where Did It Go. The location of the object in the destination tree will be highlighted in the right pane.
To determine the original location of an object in the destination tree, highlight the object in the right pane and choose Edit, Where Did It Come From. The location of the object in the source tree will be highlighted in the left pane.
To see all objects currently dropped into the destination tree, choose a container in the left pane and choose Edit, Show Dropped Folders. Choose Show Dropped Printers to see printer objects that have been dropped into the destination tree.
This completes the creation of the SCU project. Following project creation you will go through a project verification process, which is discussed in the next section.
After the SCU project is created, SCU launches the Verification Wizard:
1. Click Next to begin the verification process.
2. At the Dropped Folders screen, review the source and destination paths and click Next. If any of the listed information is incorrect, cancel the verification and return to the project window to make the necessary changes.
3. (Conditional) At the Create Folders screen, review the new folders you have created as part of your consolidation project and click Next. If any of the listed information is incorrect, cancel the verification and return to the project window to make the necessary changes.
4. At the Duplicate File Resolution screen, make your selections and click Next. If the name of a source file is identical to an existing file in the destination volume or directory, you have three options to resolve the conflict:
a. Don’t copy over existing files—The source file will not be copied, there by keeping the existing destination file.
b. Copy the source file if it is newer—The source file will be copied over the destination file only if it is newer than the existing destination file.
c. Always copy the source file—The source file will always be copied over the destination file.
5. At the Synchronize Files and Folders screen, make your selections and click Next. Select Yes if you want to delete all files and folders on the destination server that do not exist on the source server. The default option is No.
6. At the Compare Files and Folders screen, make your selection and click Next. Select Yes if you want files to be compared post-consolidation to make sure everything copied correctly.
7. At the File Date Filters screen, make your selections and click Next (see Figure 2.4). Choose No to disable any file filter based on file date. If you want to filter the file copy based on file date, choose Yes and provide the following information:
a. Attribute—You can filter files based on the Accessed, Modified, and Created file attributes.
b. Attribute Dates—For each attribute, specify the appropriate dates to define how filtering will be done. The On or After date specifies that only files with an attribute date equal to, or later than, the date specified will be copied. The On or Before date specified that only files with an attribute date equal, or prior, to the date specified will be copied. Setting both dates will define a date range, and only files with attribute dates between the two dates will be copied.
Figure 2.4. File Date Filters in the Server Consolidation Utility.
Note
To make the date range work, the On or After date must be set to a date prior to the On or Before date.
8. At the Wildcard Selection screen, make your selection and click Next. Here you can specify any files to exclude from the consolidation. You can use the asterisk (*) as a wildcard to specify types of files or portions of filenames in your exclusion list.
9. At the Check for Trustees and Ownerships screen, make your selections and click Next. If the source and destination servers are in different trees, browse to the container you want to search. Check Search All Subordinate Containers to include all containers below the container selected. This process will review trustee rights and file ownership information for the objects that have been dropped into the destination tree, and update them as necessary based on their new location in the destination tree.
10. At the Password Verification screen, enter the passwords for the source and destination trees and click Next.
11. Click Next to begin the verification process. Before beginning to consolidate your data, you have the option of verifying that the destination server has enough disk space to accommodate the data from the source server. To do this, click Check for Sufficient Disk Space. This process can take some time if there is a lot of data being transferred from the source server.
Note
Click Yes to any messages notifying you that an updated SMDR.NLM or TSA.NLM must be copied for the consolidation to work. Selecting No will stop the consolidation.
12. (Conditional) At the Tree-to-Tree Object Match Up screen, reconcile how SCU should insert the source tree objects into the destination tree and click Next. To complete this process, do the following:
a. Select the type of objects to display from the drop-down list provided.
b. Highlight the object(s) you want to match from source tree to destination tree. Use the Ctrl and Shift keys to select multiple objects from the list. If you selected more than one user, right-click the users and then choose Create All Selected Users.
c. Select the Yes radio button to create new user objects for all selected users. You can browse to the container in the destination tree in which you want to create the selected users.
d. Click OK to continue.
13. (Conditional) At the Destination Object drop-down, select one of the four following options for placing the new objects from the source tree into the destination tree:
a. Same Name—Select this option to replace the object in the source tree with the object in the destination tree that has the same name.
b. Don’t match—Select this option if no matching object exists in the destination tree.
c. Browse—Select this option to locate and select a matching object from the destination tree.
d. Create—Select this option to specify a container in the destination tree in which a matching user, with a different name from that of the source tree user, will be created. You will be asked to specify the new name.
14. (Conditional) At the Unmatched Objects screen, click Yes to proceed without matching objects or No to go back and finish the object-matching process.
15. At the Error Resolution screen, click Next to continue the consolidation. If there are any errors during the verification process, they will be listed in the Error Resolution window, along with a possible resolution to the problem. Errors might include name conflicts, insufficient rights, files that need to be updated, required namespaces not loaded, or insufficient disk space. Verification errors fall into two categories:
Errors must be resolved before files can be copied. You need to take some action to resolve the problem before continuing with the consolidation.
Errors should be resolved but might not affect the copy process.
The project is now completely defined and you are ready to perform the actual server consolidation, which is described in the next section.
After the consolidation project is configured, you can either execute it immediately or schedule it for a delayed start some time down the road.
At the Start Novell Server Consolidation Utility screen, click Proceed to perform the consolidation immediately. During the consolidation, folders and objects are created, files are copied, and printer agents are moved to their destination as specified by the project plan you have just created. When the copy process is complete, the Process Finished screen enables you to view the error log, view the success log, and close the consolidation process.
Note
If you interrupt the copy process before it completes, all changes made to the destination tree will remain. Removing the new objects will require you to delete them manually.
Alternatively, you can use the Windows Scheduled Tasks feature to delay the consolidation to a time that is appropriate. This enables you to plan and test a consolidation project during the day and then schedule it to run during off hours to limit the impact on your production network.
To schedule a project to run at a later time, take note of the project name and location, and then complete the following steps:
1. Launch the Task Scheduler in Windows by selecting Start, Settings, Control Panel.
2. Select Scheduled Tasks and then select Add Scheduled Task to launch the scheduler.
3. At the Scheduled Task Wizard screen, click Next.
4. From the list of programs provided, select Novell Server Consolidation Utility and click Next.
5. Specify a name for the scheduled task, select One Time Only as the task frequency, and then click Next.
6. Specify start time and date for the scheduled task and click Next.
7. Specify Windows username and password of the Admin user who will perform the task and click Next.
8. Verify that scheduled task settings, and check Open Advanced Properties for This Task When I Click Finish, and then click Finish.
9. From the Advanced Properties screen, select the Task tab.
10. Add the following four parameters to the end of the path name in the Run field and click OK. Separate each parameter from another by a single space:
a. Location and name of project file—Specify the complete path to the SCU project file you have just created.
b. Y—Indicate that the specified SCU project should be run automatically.
c. Password for Source server—Enter the Admin password for the source server.
d. Password for Destination server—Enter the Admin password for the destination server.
The completed Run field should resemble this:
c:program files
ovellserver consolidation utilityfc.exe
"c:my documentsPrv_to_Wal.mdb" y novell novell
11. Enter the Windows username and password of the Admin running the project once again and click OK.
The scheduled task is now ready to run at the time and date you have specified.
OES NetWare continues to use the User Access License (UAL) model introduced with NetWare 6.0. In this model, users gain access to network services by connecting to the network instead of a specific server. The eDirectory user object for each user on the network receives a license unit, reserved for their user object, which provides them access to network services at any time and from any network workstation, regardless of location.
The UAL model replaces the Server Connection License model used with NetWare 5 and previous versions of NetWare. The UAL model is much easier to manage since you no longer have to track connections on individual servers, just connections to the network as a whole.
When you install or upgrade to OES NetWare, NLS is automatically installed. Actual license certificates may be installed either during the installation or post-installation. OES NetWare uses iManager to install and manage license certificates. License certificates enable users to access network resources, including NetWare servers and NLS-enabled applications and services. For more information on iManager, see Chapter 4.
With the UAL model, users gain access to network services by connecting to the network instead of a specific server. The eDirectory user object for each user on the network receives a license unit, reserved for their user object, which provides them access to network services at any time and from any network workstation, regardless of location.
The UAL model is much easier to manage than previous NetWare licensing models because you no longer have to track connections on individual servers, just connections to the network as a whole.
There are three main components to NLS:
License Service Provider (LSP)—This is the licensing software that runs on OES NetWare servers. When you install OES NetWare and its license certificates, the LSP software is copied to the server and an LSP object is created in the eDirectory tree. An LSP provides the actual licensing service. It handles requests from NLS clients and maintains the license certificates, which are stored in eDirectory.
Tip
Any eDirectory partition that will contain License Certificate objects should have at least one of its replicas stored on a server operating as an LSP.
NLS client—This is software that requests licensing services from an LSP. The NLS client will locate and communicate with LSPs as needed to request license information on behalf of NLS-enabled applications. NLS clients are used on both client workstations and NetWare servers. Nothing needs to be done to load an NLS client. The necessary components are installed with the Novell client for workstations and as part of the NetWare installation for servers.
NLS eDirectory objects—There are two main licensing objects used by NLS, in addition to the LSP object:
License Certificate object—When an NLS license is installed, a License Certificate object is created that corresponds to the printed license statement that is typically included in the packaging for software products. The name of the License Certificate object typically corresponds to a serial number or name specified by the software vendor.
License Container object—The License Container object is a special container object in eDirectory that is used to store License Certificate objects. When you install a license certificate, NLS creates a new License Container object unless a license container already exists. Each license container holds one or more license certificates. License Container objects are named using publisher, product, and version.
NLS requests are handled through the following process:
1. An application, either from a server or a workstation, issues a request to the NLS client.
2. The NLS client library packages the request from the application and submits it to an LSP.
3. The LSP 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.
4. If the requested resource is available, the LSP fills the request. If the LSP cannot fill the request, it searches for a resource. The LSP will start searching in its current container and then work its way upward in the tree.
5. When the search is complete, the LSP returns a license status (such as available/not available) to the client library. The library subsequently returns status to the application.
6. The application determines action based upon the status of license units.
When you install or upgrade to OES NetWare, NLS is automatically installed. Actual license certificates can be installed either during the installation or post-installation. OES NetWare uses iManager to install and manage license certificates. License certificates enable users to access network resources, including NetWare servers and NLS-enabled applications and services. For more information on iManager, see Chapter 4.
NLS is installed automatically with OES NetWare. To verify that NLS was installed and is running properly, check the following:
At the server console GUI, choose Novell, Install, and then look for a Novell Licensing Services entry.
Check that NLSLSP.NLM is running on the server. To do this you can type MODULES NLS* at the server console or through RConsoleJ.
Check to see whether there is an LSP object installed in the container where the server is installed. It will have the name NLS_LSP_servername.
Novell typically distributes licenses in an envelope, which is a file with the extension .NLF (Novell License File). The envelope contains one or more license certificates. Envelopes enable you to install more than one license certificate at a time into License Container objects. For example, if you have purchased three products in a suite, you can use an envelope to install license certificates simultaneously for all three products. In some cases you will also see individual license certificates. They are files with an extension of .NLS.
When adding license certificates to the eDirectory tree, you should know where in the tree you want to install the license certificate. This location or context determines who can use the license units associated with that license certificate. For more information on installing and configuring iManager, see Chapter 4.
To install license certificates through iManager, complete the following steps:
1. Open iManager and select Roles and Tasks.
2. In the Task frame, select Licenses and then Install a License.
3. Browse to and select the license file and click Next. OES NetWare licenses are normally found on a disk in the folder A:LICENSE. Some NLS-enabled applications also link their license certificates to a separate activation key. This key is stored in a file with a .KEY extension or can be entered manually to unlock the license certificate.
4. Choose the license(s) you want to install and click Next. OES NetWare, for example, includes both a server license unit and a group of user license units in each .NLF file.
5. Specify the context where you want the license certificates installed and click Install. If no License Container object exists in the context that you specify, one will be created. If a server license is being installed you will also need to specify the server to which this license should be applied.
6. Click Done to exit the license installation routine.
You can also use this process to allow only designated servers to grant requests for license units. This is known as a server assignment. Some products require that a license certificate have a server assignment before the certificate can be used. The following guidelines apply to server assignments:
Only one server assignment can be made for each license certificate.
No other server can allow use of units from that license certificate.
A server with a server assignment can have multiple license certificates assigned to it.
Note
If you participate in one of Novell’s Master software licensing programs, such as the Master License Agreement (MLA) or the Corporate License Agreement (CLA), you will receive special licenses that support an unlimited number of users. Such licenses should be installed in the top of the tree in the Organization container and no further license installations should be necessary.
To delete license certificates through iManager, complete the following steps:
1. Open iManager and select Roles and Tasks.
2. In the Task frame, select Licenses and then Delete a License.
3. Browse to the appropriate license and click OK. Remember to browse in the license container to choose a specific license object. You can also select an entire license container.