Novell Small Business Suite 6.6 Readme

June 21, 2005
1.0 Introduction
2.0 What's New in This Release
3.0 Known Issues
3.1 NetWare Installation
3.1.1 Selecting the Primary IP Address for Hostname during Installation
3.1.2 Connecting Workstation to Configure Small Business
3.1.3 Applying Support Packs before an In-Place Upgrade to OES NetWare 6.5
3.1.4 In-Place Upgrade Leaves Server in a Different State Than New Installation
3.1.5 NWUCINIT Error during Installation
3.1.6 System ABEND When CPQASM.NLM Loads During Boot
3.1.7 PSM Errors from Stop Processors and Start Processors Commands
3.2 Small Business Setup
3.2.1 Connecting Workstations after Configuring DHCP
3.2.2 Configuring GroupWise Using iManager Setup Task
3.2.3 Binding Multiple Network Cards to the Same IP Address
3.3 Accessing Web Services with the Browser Language Set to Polish
3.4 Novell Client Issues
3.5 GroupWise Issues
3.5.1 Upgrading GroupWise
3.5.2 Configuring GroupWise
3.5.3 Managing GroupWise
3.6 BorderManager Issues
3.6.1 Upgrading BorderManager
3.6.2 Installing BorderManager
3.6.3 BorderManager Proxy Caching Requires Traditional Volumes
3.7 ZENworks Desktops Management Issues
3.8 Other Product Readme Files
4.0 Interoperability Issues
4.1 OES NetWare 6.5
4.2 GroupWise 6.5
4.3 BorderManager 3.8
4.4 ZENworks 6.5 Desktop Management
5.0 Documentation Conventions
6.0 Legal Notices


1.0 Introduction

This document provides a brief overview of new features, general known issues, and interoperability issues for Novell® Small Business Suite 6.6.

To get a complete overview and installation instructions for this release, see the Novell Small Business Suite 6.6 Overview and Installation Guide.

For information about additional issues discovered after the initial release, refer to TID 10094148 in the Novell KnowledgeBase.


2.0 What's New in This Release

The Novell products included in the suite have been updated to the following:


3.0 Known Issues


3.1 NetWare Installation


3.1.1 Selecting the Primary IP Address for Hostname during Installation

If you bound two or more network boards to different IP addresses during the server installation, we recommend that you select the IP address for the public or external interface (rather than the internal interface) as the primary IP address when specifying the hostname for the primary IP address. The primary address is used for generating server certificates. You can avoid hostname warnings when accessing Web services from the Internet when the certificates match the external address of the server.


3.1.2 Connecting Workstation to Configure Small Business

When you install NetWare, it creates a DHCP server that is configured to the private or internal interface so workstations can connect to the server through a browser and complete additional configuration steps. You can connect using the DNS name you specified or through the IP address. You do not need to configure a static IP address in the workstation that you want to use to connect to the server.


3.1.3 Applying Support Packs before an In-Place Upgrade to OES NetWare 6.5

Novell Small Business Suite 6.6 contains several Novell products such as OES NetWare 6.5, GroupWise 6.5, BorderManager 3.8, and ZENworks 6.5 Desktop Management. Before you perform an in-place upgrade on an existing server to upgrade the server operating system to OES NetWare 6.5, make sure you apply the latest Support Pack for all the bundled Novell products installed on the server to be upgraded. This is especially critical for servers running earlier versions of BorderManager or ZENworks.

For example, if you have BorderManager 3.7 running on your server, first apply the latest Support Packs for 3.7, then perform the in-place upgrade to OES NetWare 6.5, and then install BorderManager 3.8.


3.1.4 In-Place Upgrade Leaves Server in a Different State Than New Installation

The script that the installation uses does not complete when performing an upgrade from previous versions of Novell Small Business Suite. This is not necessarily undesirable; however, we wanted you to be aware of the following differences.

  • Consoleone.ncf is not modified.

    This file enters some environmental variables for running ConsoleOne® from the server console. In some rare circumstances, the GroupWise snap-ins might get installed without the ConsoleOne classpath being modified.

    If you get a Class Not Found error on the logger screen when attempting to run ConsoleOne from the server console, edit the sys:\public\mgmt\consoleone\1.2\consoleone.ncf file by adding the following lines before the line that loads java (jjava -mp0 -ss512k -noverify -classpath $c1path;$CLASSPATH com.novell.application.console.shell.Console):

    #GroupWise 
    envset c1path=$c1path;sys:\public\mgmt\ConsoleOne\1.2\ConsoleOneExt\GroupWiseRes.jar
    envset c1path=$c1path;sys:\public\mgmt\ConsoleOne\1.2\ConsoleOneExt\GWAdminDirectory.jar
    envset c1path=$c1path;sys:\public\mgmt\ConsoleOne\1.2\ConsoleOneExt\GWAdminUtil.jar
    envset c1path=$c1path;sys:\public\mgmt\ConsoleOne\1.2\ConsoleOneExt\njweb.jar
  • If you have multiple Ethernet cards, not all interfaces are automatically set up for remote access outside the firewall by Novell Remote Manager, the Welcome Page, or other Web services.

    If you want to manage your server remotely outside your firewall, you must enable Novell Remote Manager to the external interface using the httpbind command.

    For example:

    httpbind 172.16.2.17:8009 /ssl /keyfile:"ssl certificateip"

    Then you can enable the other TCP/IP services such as the Web Administration page using the IP Address Management page in Novell Remote Manager.

  • Client file caching is not turned off by default.

    You probably already have this setting enabled the way you need; if so, no changes are necessary.

  • Virtual Office is not set as the End User Welcome portal for port 80.

    This action happens only when you choose to install Virtual Office from one of the preconfigured server pattern options or if you choose to install all the products that the pattern installs in a custom installation.

    This action would not be desirable if your Web services were already set up and working.


3.1.5 NWUCINIT Error during Installation

During the installation, you might see the following errors on the System Console screen console or in the console.log file:

UCMGR-403: File change mode error, file = sys:system\nwucutil.nlm
(errno=1).
UCINIT-100: Abnormal completion, status = 7009.

To resolve this problem:

  1. Copy nwucutil.nlm to sys:system.

  2. At the System Console prompt, enter nwucinit -patch.


3.1.6 System ABEND When CPQASM.NLM Loads During Boot

During the boot the system may ABEND when loading CPQASM.NLM. This issue appears when using NetWare 6.5 SP3 and later software. The issue is not specific to hardware platform.

To resolve this problem, download and apply the SERVER.EXE patch following instructions in TID 2971567 on support.novell.com.


3.1.7 PSM Errors from Stop Processors and Start Processors Commands

Issuing a stop processors command followed by a start processors command can result in PSM errors or hang the server on newer HP server platforms..

To resolve this problem, download and apply the SERVER.EXE patch following instructions in TID 2971567 on support.novell.com.


3.2 Small Business Setup


3.2.1 Connecting Workstations after Configuring DHCP

After you configure DHCP on the server, make sure to release and refresh the IP address configurations on any workstations that have been attached previously to a NetWare server. In some cases, you must reboot the workstation.

For example, the commands for release and renew from the Windows 2000 command line are

ipconfig /release

ipconfig /renew


3.2.2 Configuring GroupWise Using iManager Setup Task

Sometimes when you run the iManager task Set Up GroupWise and Messenger and then click Finish, the task indicates that it is configuring the GroupWise system but then does not complete the configuration. The configuration eventuality times out and returns a message stating that it has detected that one of the components did not complete in a reasonable amount of time and asks whether you want to continue waiting. Accept the prompt to continue waiting.

If you get the Continue Waiting message repeatedly for an excessive amount of time, then note the following:

  • This condition is usually due to stale connections to the server from the workstation. To resolve this issue, cancel the task, remove all connections to the server, and then try running the setup task again.
  • To clear the connections, you can reboot the workstation or clear the connection without rebooting the workstation. To clear the connection without rebooting, right-click the red N on the taskbar, click NetWare Connections, and then select the applicable tree and server. Click Detach, then click Refresh to be certain the connection has been deleted.


3.2.3 Binding Multiple Network Cards to the Same IP Address

The Set Up Internet Connectivity task in iManager has a problem recognizing multiple network cards with the same address. If you need to bind multiple network cards to the same IP address, we recommend configuring the second (third, fourth, etc.) card in inetcfg.nlm after using the Set Up Internet Connectivity task in iManager.

For inetcfg.nlm procedures, see "Setting Up" in the Novell NetWare TCP/IP Administration Guide for OES.


3.3 Accessing Web Services with the Browser Language Set to Polish

Virtual Office and some of the plug-ins to iManager are incomplete for Polish; therefore, when using iManager for setting up or monitoring items, some of the icons might be missing and some of the dialogs might display in English.


3.4 Novell Client Issues

With the version of the Novell ClientTM software released with Novell Small Business Suite 6.6 (version 4.90 SP1a on Windows NT*/2000/XP and version 3.4 on Windows 95/98), some incompatibilities exist with some third-party applications and client file caching. So we have disabled file caching by default in the installation process by inserting the following lines in the autoexec.ncf file:

# Change the following line to "on" to improve client performance: 
set client file caching enabled = off

With client file caching turned off, client performance will not be as great as with it turned on.

Before enabling file caching, we recommend that you first test applications with this switch set to On to be sure there are no incompatibilities before enabling it for production use.


3.5 GroupWise Issues


3.5.1 Upgrading GroupWise

When updating GroupWise, use the software and process outlined in the GroupWise documentation. Do not use the file copy or installation patterns provided in Novell Small Business Suite for new installations of GroupWise or the Set Up GroupWise and Messenger task in iManager.

For procedures, see "Updating GroupWise" in the GroupWise 6.5 Installation Guide.


3.5.2 Configuring GroupWise


Context Already Exists Error

When configuring GroupWise using the setup task in iManager, make sure you unload all instances of any utilities that access the domain database (such as ConsoleOne and NetWare Administrator).

If you do not unload them, the GroupWise installation fails and displays the following message:

An error occurred while trying to set up your basic GroupWise system. You must install GroupWise from the GroupWise CD. Error: The context already exists. {System Record


Domain Is Not Found Error

If you are configuring GroupWise from the setup task in iManager and you have previously managed GroupWise using ConsoleOne from the same workstation, you might get an error stating that the domain is not found.

To resolve this issue:

  1. Delete the snapinprefs.ser file on the workstation.

    This file is usually located in the c:\documents and settings\administrator\.consoleone directory.

  2. Try configuring GroupWise again.


3.5.3 Managing GroupWise

When using ConsoleOne to manage GroupWise, we recommend running ConsoleOne remotely through a mapped drive connection to the server rather than running it locally from the workstation so that you have access to all the snap-ins that you need. If you prefer to install and run ConsoleOne from the workstation, make sure you copy all the snap-ins required for the product that you are running. For more information, see the ConsoleOne online documentation.


3.6 BorderManager Issues


3.6.1 Upgrading BorderManager

Novell Small Business Suite 6.6 includes Novell BorderManager 3.8. To run BorderManager on Novell Small Business Suite 6.6, you must use BorderManager 3.8 or later. Earlier versions of BorderManager will not run on Novell Small Business Suite 6.6.

If you want to upgrade from a previously installed version, you must first upgrade to BorderManager 3.6.2 or later before upgrading the server to Novell Small Business Suite 6.6.

If you are upgrading from BorderManager 3.6, you must apply BorderManager Support Pack 2 or later to the server before upgrading the server to Novell Small Business Suite 6.6.

If you upgrade the server before upgrading BorderManager, you cannot use the upgrade process but must uninstall the current version of BorderManager and then install a new version of BorderManager 3.8.

IMPORTANT:  If you are upgrading BorderManager from an earlier version of the product, stop all running BorderManager services before installing Novell BorderManager 3.8.


3.6.2 Installing BorderManager

The online documentation for BorderManager 3.8 and the documentation on the Novell BorderManager 3.8 CD references a Web download to obtain the product. However, all the files you need for the BorderManager installation are provided on the Novell BorderManager 3.8 CD in this suite. You do not need the BorderManager Companion CD.

If you didn't choose to install the TCP/IP modules during the installation, you will see an error display when you reach the Minimum Requirement Check dialog. The error mentions that you need to run tintall.pl from the Companion CD after the installation and restart the server. But you need these files only if you are going to install the VPN client.

We have made these files available on the Novell Small Business Suite 6.6 NetWare 6.5 CD 2 Products with SP3 CD. You can easily install them by doing the following:

  1. Insert the Novell Small Business Suite 6 6 NetWare 6.5 CD 2 Products with SP3 CD into the server's CD-ROM drive.

  2. At the X-Server graphical console, click Install > Add.

  3. Browse to and select the postinst.ni file on the Novell Small Business Suite 6.6 NetWare 6.5 CD 2 Products with SP3 CD (nw65prod).

  4. Select the TCP/IP Files for Enabling Novell BorderManager 3.8 VPN component, then click Next > Copy Files.

  5. Restart the server.

For details about installing BorderManager, review "Installing BorderManager 3.8" in the Novell Small Business Suite 6.6 Overview and Installation Guide.


3.6.3 BorderManager Proxy Caching Requires Traditional Volumes

BorderManager requires a minimum 2 GB Traditional cache volume when you are installing proxy caching.

By default, the Novell Small Business Suite installation installs an NSS Data volume whether you choose a Default or Manual installation type. You cannot change the type of volume that is created during the installation. To delete the Data volume and set up a Traditional volume as a cache volume for BorderManager, use the Partition Disks link in Novell Remote Manager. For procedures, see "Managing Disk Partitions" in the Novell Remote Manager for NetWare Administration Guide for OES.


3.7 ZENworks Desktops Management Issues

Review the issues in the ZENworks 6.5 Desktop Management Readmes located in the ZENwork 6.5 online documentation.


3.8 Other Product Readme Files

Because Novell Small Business Suite includes several products, we recommend also reading the following Readme files if you are going to install the applicable product:


4.0 Interoperability Issues


4.1 OES NetWare 6.5

See the OES Coexistence and Migration Guide.


4.2 GroupWise 6.5

No issues are currently identified in this release.


4.3 BorderManager 3.8

No issues are currently identified in this release.


4.4 ZENworks 6.5 Desktop Management

No issues are currently identified in this release.


5.0 Documentation Conventions

In this documentation, a greater-than symbol (>) is used to separate actions within a step and items in a cross-reference path.

A trademark symbol (®, TM, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.


6.0 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. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classification to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in the U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical biological weaponry end uses. Please refer to www.novell.com/info/exports/ for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2003-2005 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher.

Novell, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.novell.com/company/legal/patents/ and one or more additional patents or pending patent applications in the U.S. and in other countries.

BorderManager is a registered trademark of Novell, Inc. in the United States and other countries.

ConsoleOne is a registered trademark of Novell, Inc. in the United States and other countries.

DirXML is a registered trademark of Novell, Inc. in the United States and other countries.

eDirectory is a trademark of Novell, Inc.

GroupWise is a registered trademark of Novell, Inc. in the United States and other countries.

NetWare is a registered trademark of Novell, Inc. in the United States and other countries.

Novell is a registered trademark of Novell, Inc. in the United States and other countries.

Novell Client is a trademark of Novell, Inc.

ZENworks is a registered trademark of Novell, Inc. in the United States and other countries.

All third-party trademarks are the property of their respective owners