3.5 Starting an Upgrade

The following sections explain how to start in-place and remote upgrades.

3.5.1 In-Place Upgrades

When you perform an in-place upgrade to OES NetWare, both the operating system and eDirectory are upgraded. In addition, only the NetWare products or components that are currently installed are upgraded. Other Novell products that you might have purchased or installed separately (for example, GroupWise® or ZENworks) are not upgraded.

Additionally, the Enterprise server is migrated to the Apache 2 Web server when you upgrade to OES NetWare. During the upgrade, the existence of the Enterprise server is verified, and if it exists, information in the Enterprise server's config files is migrated to the Apache 2 server's config files. After the Apache 2 Web server is installed, the Enterprise server is automatically removed.

IMPORTANT:When upgrading a NetWare 5.1 or 6.0 server with the Novonyx Web Server to OES NetWare, the document root for the Novonyx Web Server is preserved and not updated to the Apache 2 Web Server document root. Some NetWare 6.5 Web services might not work correctly. To resolve this, review and edit the Apache configuration file, sys:\apache2\conf\httpd.conf.

If you are performing an upgrade, several components are already selected. These are the components currently installed on the server. Leaving the installed components checked reinstalls the products. Unchecking an installed component does not uninstall the product.

HINT:If you attempt to install a new server into your tree at the same time you upgrade another server in the tree to OES NetWare, you might have difficulty logging in to the server being upgraded until the other server’s installation is complete.

To begin an upgrade to OES NetWare:

  1. Insert the NetWare 6.5 SP6 CD 1 (Operating System) and if it does not auto-mount as a NetWare volume, do one of the following:

    • On a NetWare 6.5 server, enter LOAD CDDVD.NSS at the system console.
    • On a NetWare 6.0 server, enter LOAD CD9660.NSS at the system console.
    • On a NetWare 5 server, enter LOAD CDROM.NLM at the system console.

    If the CD still does not mount, reboot the server.

  2. From the server GUI console, click Novell and select Install.

  3. In the Installed Products page, select Add.

  4. When the Source Path page appears, browse to the location of your OES NetWare software.

  5. Select the product.ni file and click OK.

  6. Verify that the Source Path window has the correct path filled in and click OK.

Proceed to Accepting the License Agreements.

3.5.2 Remote Upgrades

One of the features in NetWare is the ability to remotely upgrade any servers in your network. The process is a simple one that can be accomplished in two different ways:

  • Remote Upgrade from iManager
  • Remote Upgrade from the Novell Deployment Manager

HINT:When you run a remote upgrade, if the source files are located on a remote server, that server must contain a DS replica in order for the server-to-server file copy to run efficiently. If a replica does not exist on the source server, the file copy might revert to a workstation copy, which can be significantly slower over a WAN link.

Remote Upgrade from iManager

Novell iManager 2.6 must be installed and configured in order for remote upgrades to successfully complete using this utility. For information on installation and configuration of iManage, see the Novell iManager 2.5 Administration Guide. After iManager is installed and configured, complete the following tasks:

  1. Click the Install and Upgrade link that displays on the left side of the iManager main page.

  2. Click the Upgrade to NetWare 6.5 link.

  3. From the page on the right, click the Upgrade a Server Remotely link.

  4. Click Browse and browse to the root of NetWare 6.5 SP6 CD 1 (Operating System) or the OES NetWare installation files that have been copied to a network server.

    NOTE:Performing the remote upgrade from a staging server that contains the OES NetWare installation files is significantly faster than launching from the NetWare 6.5 CD located on the workstation.

    The path selected should include nw65os. The OES NetWare Install program expects a mapped drive and does not support UNC paths.

    If you are not prompted for your source media, it is because you have run an upgrade from Deployment Manager in the past and it will launch the upgrade from that same source. If you do not want to use this previous location, delete the file \program files\common files\novell\ni\data\browserlaunch.rsp.

  5. Click OK.

  6. Follow the on-screen instructions to complete the remote upgrade.

    See Accepting the License Agreements.

After the initial reboot during a remote upgrade, a login screen might display requiring you to log in to the server being upgraded. If this occurs, provide the login information, click Details, type the IP address of the server being upgraded, then click OK.

If Installation/Upgrade tasks fail to run from iManager, you might need to change your security settings.

  1. In Internet Explorer, click Tools > Internet Options.

  2. Click Security > Custom Level.

  3. Under Initialize and Script ActiveX Controls Not Marked as Safe, select Enable.

  4. Click OK.

Remote Upgrade from Novell Deployment Manager

  1. On a Windows 2000 or Windows XP Professional Edition workstation that has the latest Novell Client installed on it, log in to your existing network as a user with the Supervisor right.

    If you are prompted to log in again while running Deployment Manager, you can specify the IP address of the server by clicking Details.

  2. Insert NetWare 6.5 SP6 CD 1 (Operating System) or map a drive to a server containing the OES NetWare installation files.

    NOTE:Performing the remote upgrade from a staging server that contains the OES NetWare Operating System files is significantly faster than launching from the NetWare 6.5 CD located on the workstation.

  3. Start the Deployment Manager utility (nwdeploy.exe or nwdeploynobrowser.exe) located at the root of the CD or NetWare installation files.

  4. Select Upgrade to NetWare 6.5 in the left navigation bar of Deployment Manager.

  5. In the right frame of the browser window, click the Upgrade a Server Remotely link.

  6. Follow the on-screen instructions to complete the remote upgrade. See Accepting the License Agreements.

3.5.3 Accepting the License Agreements

Accepting both license agreements means that you have read and agreed to the terms and conditions contained in the license agreements.

  1. For an upgrade, click I Accept for both license agreements.

3.5.4 Health Check Summary

NetWare performs a health check on your server to determine if an upgrade can proceed without problems. A summary of the checks that were run is displayed including a Success, Warning, or Failure state for each check that was run.

If the health check completes without any Warning or Failure states, the health check summary page does not display. If that is the case, proceed to Back Up Server Files.

A Success or Warning state allows the upgrade to continue. A Failure state stops the upgrade until the problem is resolved.

  1. To view the detailed health check log, click View Log.

  2. Click Next.

3.5.5 Back Up Server Files

This page allows you to specify whether to back up your server files. It also lets you select whether to automatically reboot the server after the file copy is complete and gives you the option of a Default or Manual installation.

  1. Select Yes or No depending on whether you want to back up the server files.

  2. If you selected Yes, specify the location for the backup files.

    IMPORTANT:Make sure that the drive you specify as the location for the backup is a valid drive on the server.

  3. If you want the server to automatically reboot after the file copy, click Yes. Otherwise, click No.

  4. Select either a Default or Manual upgrade by clicking the radio button next to the desired choice.

    The Default upgrade automatically detects drivers and upgrades the server to NetWare 6.5 with default settings.

    The Manual upgrade lets you manually configure your drivers and the default settings used in the Default upgrade.

  5. Click Next.

3.5.6 Installing Additional Components

After the file copy is complete, the Components page displays and you can choose which additional NetWare components to install. To see a description of a component, place the cursor over the component name.

NOTE:Because you are performing an upgrade, several components are already selected. These are the components currently installed on the server. Leaving the installed components checked reinstalls the products. Unchecking an installed component does not uninstall the product.

To select additional components to install:

  1. Select the components you want to install, then click Next. (Default selections can be deselected if desired.)

    After selecting the components that you want to install from the Components page, a Summary screen appears displaying the names of the selected products and the disk space (in MB) required to install them.

    If you want to change your product selection, click Back and make the necessary changes. After verifying the product names and space requirements, click Copy Files.

    (Conditional, if installing from CD) When prompted, remove NetWare 6.5 SP6 CD 1 (Operating System), insert NetWare 6.5 SP6 CD 2 (Products), then click OK.

    IMPORTANT:The iManager installation might take up to 15 minutes to complete. During this installation, the page will not change.

  2. If you see a message stating that there is a file conflict, select the file overwrite option that you prefer and click OK.

The system proceeds to copy files for a few minutes, and then reboots.

If you selected Manual during Step 4, then your device drivers are detected and you are presented with a screen or screens where you can modify these settings.

If you do not want to modify the settings:

  1. Select Continue.

  2. Press Enter.

If you want to modify the settings:

  1. Select Modify and press Enter.

  2. Make any desired changes.

  3. Select Continue and press Enter.

If you selected Default during Step 4, the system continues to copy files after the reboot.

IMPORTANT:If you are performing a remote upgrade and you are unable to reconnect to the server after it reboots, you can complete the upgrade locally by entering FINISHUP.NCF at the server console.

When this post-reboot file copy completes, a GUI screen appears and you are prompted to log in to eDirectory.

  1. Type your name and password in the fields provided.

  2. Click OK.

3.5.7 eDirectory Summary

The eDirectory Summary page is now displayed.

  1. Verify that the information on the eDirectory Summary page is accurate.

  2. Record the Admin password and any other relevant information before proceeding.

  3. Click Next.

3.5.8 Selecting the Login Method

NMAS™ server components are installed automatically when you run the NetWare 6.5 installation program. You need to select the login methods you want to install.

Select the login methods that you want to install into eDirectory by selecting the appropriate methods on the Novell Modular Authentication Service page. When you select a login method, a description of the component appears in the Description box. For more information on login methods, see Managing Login and Post-Login Methods and Sequences in the Novell Modular Authentication Services (NMAS) 2.3 Administration Guide.

The NDS login and Challenge-Response methods are installed by default.

  1. On the Novell Modular Authentication Service page, select the login methods you want to use from the options provided.

    Select Select All if you want to install all the login methods into eDirectory. Select Clear All if you want to clear all selections (except the two default methods).

  2. Click Next.

IMPORTANT:The NMAS client software must be installed on each client workstation where you want to use the NMAS login methods. The NMAS client software is included with the Novell Client software.