Novell Open Workgroup Suite Small Business Edition 2.5 Issues Readme

July 15, 2009

1.0 Documentation

The following sources provide information about Novell® Open Workgroup Suite Small Business Edition 2.5 (NOWS SBE 2.5):

2.0 Known Issues

To check the version of the server, run rpm -q simba. The version number is helpful information to include when posting bugs or service requests.

The server log is located in /var/log/simba/server.log. Be sure to include information from the log when posting bugs or any service requests.

2.1 Installing NOWS SBE 2.5

If you install NOWS SBE 2.5 with YaST*, the Web-based tools are no longer supported.

2.2 Migrating to NOWS SBE 2.5

The NOWS SBE 2.5 server allows you to create NCP volumes on Linux* file systems.

For more information about migrating data from a traditional NetWare® server to a NOWS SBE 2.5 Linux server, see TID 3219860.

2.3 Partitioning NOWS SBE 2.5

The pre-configured partitions selected by the install are currently the only supported partitions available. Although you can change file system types to increase swap partition size, new partitions are not supported.

2.4 Configuring Software RAID

To set up software RAID in RAID1 (mirrored), follow these steps:

  1. Change the booting option to point to boot from md0 “/”

  2. Go to the Installation Settings screen > Auto YaST Settings > Expert to boot.

  3. Select Edit for the first item and change the root device to /dev/md0

  4. After you have performed the installation, but before you begin to configure, remove the CD/DVD and reboot.

For more information, see TID 7000012 and TID 3099959

2.5 Creating and Managing Users

All user creation and user management for components is performed at the User Administration page.

2.6 Using Novell Clients

Use the versions of clients that ship with NOWS SBE 2.5 and are available in Desktop Downloads. These clients have been tested and verified to work properly with the server components on the system.

2.7 Using Simba Commands

The NOWS SBE 2.5 interface is built by using Simba*, which is an application server similar to Tomcat or JBoss*. However, Simba is designed specifically for system installation and administrative tasks.

  • Simba files are located in the /var/lib/simba folder.

  • To stop Simba, use the following command: /etc/init.d/simba stop

  • To restart Simba, use the following command: /etc/init.d/simba start

  • The Simba server troubleshooting log is located at /var/log/simba/server.log

2.8 Installing Novell Storage Services

This section describes how to manually install NSS.

IMPORTANT:Before installing NSS, use the NOWS SBE 2.5 administrative GUI to install eDirectory, then install iManager and Samba.

  1. Install the NSS component.

  2. Log into iManager.

    IMPORTANT:You must have an uninitialized or logical disk available. It can contain no other mounted partitions. This configuration cannot be performed on the disk that contains either root (/) or swap.

  3. In the Roles and Tasks column, select Storage > Devices.

  4. In the Devices window, select the uninitialized or logical disk to be used and click Initialize Disk.

  5. A warning message appears. Read the message. If you choose to proceed, click OK. This returns you to the iManager Administration page.

  6. In the Roles and Tasks column, select Storage > Pools.

  7. A New Pool window appears. Name your pool, then click Next.

  8. Another New Pool window appears. Select your device and assign its space, then click Finish. This returns you to the iManager Administration page.

  9. In the Roles and Tasks column, select Storage > Pools. Confirm that your new pool is in the Pools column.

  10. You now need to create a new volume in iManager. In the Roles and Tasks column, select Storage > Volumes. A Volumes window appears.

  11. Click New to create a new volume.

  12. A New Volume window appears, prompting you to enter your new volume name. Name your name volume, then click Next.

  13. Another New Volume window appears, prompting you to select a pool and volume quota. Fill in the appropriate information, then click Next.

  14. A final New Volume window appears, prompting you to fill in attribute information. Fill in the appropriate information, then click Finish.

You have successfully created a new disk, pool, and volume. NSS is now operational.

2.9 Upgrading with an Existing Help Desk Instance

When upgrading a NOWS SBE server with Help Desk installed, you will need to reinstall Help Desk once the upgrade has been completed. This will not affect your existing Help Desk database.

2.10 Uninstalling eDirectory

If you need to uninstall eDirectory then first you must uninstall iManager first, otherwise your iManager instance will no longer function. Once you uninstall eDirectory, iManager can be installed if still required.

2.11 Mailscanner and GroupWise Configuration

When installing GroupWise and Mailscanner on the same server GroupWise should be installed first. In the event that Mailscanner is installed first you will need to update the SMTP port for GroupWise to ensure the proper flow of outgoing email.

  1. Locate the GroupWise configuration file on the server. This file is located opt/novell/groupwise/agents/share/gwia.cfg.

  2. Within the file update smtpport entry with port number 26 and remove the comment out to ensure the change is read on restart of the agent.

  3. Restart the GroupWise internet agent by entering the command /etc/initd/grpwise restart gwia.gwdom

2.12 Help Desk Notifications with GroupWise

During the installation of GroupWise there is not an Internet domain address defined within the GroupWise domain. Without this configuration your Help Desk instance will not be able to send out email notifications.

  1. Launch ConsoleOne and click on the [ROOT] of your tree.

  2. From the menu bar go to Tools > GroupWise System Operations > Internet Addressing

  3. Click on the Create button and add your domain address (yourdomain.com) and click Ok.

  4. Restart GroupWise by entering the command /etc/init.d/grpwise restart

2.13 ClamAV Post Installation Tasks

The following commands need to be run once the installation of ClamAV has been completed successfully.

  1. At the server you will need to run the following commands

    • dos2unix /etc/freshclam.conf

    • dos2unix /etc/clamd.conf

    • freshclam

  2. Start ClamAV by entering the following command: /etc/init.d/clamd start

2.14 Upgrading with TightVNC Installed

When upgrading a NOWS SBE server with TightVNC installed, you will need to reinstall TightVNC once the upgrade has been completed. This will not affect your existing TightVNC configuration.

3.0 Open Source Code

Novell, hereby, offers to give any third party a complete machine-readadable copy of the source code of Amanda, Clam, DLU, HylaFAX, Mailscanner*, OpenVPN*, and TightVNC, which are delivered as part of Novell Open Workgroup Suite Small Business Edition, under the terms of Sections 1 and 2 of version 2 of the GNU General Public License as publisTo enhed by the Free Software Foundation, on a medium customarily used for software interchange.

4.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