July 15, 2009
The following sources provide information about Novell® Open Workgroup Suite Small Business Edition 2.5 (NOWS SBE 2.5):
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.
If you install NOWS SBE 2.5 with YaST*, the Web-based tools are no longer supported.
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.
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.
To set up software RAID in RAID1 (mirrored), follow these steps:
Change the booting option to point to boot from md0 “/”
Go to the Installation Settings screen >> to boot.
Select /dev/md0for the first item and change the root device to
After you have performed the installation, but before you begin to configure, remove the CD/DVD and reboot.
All user creation and user management for components is performed at thepage.
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.
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
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.
Install the NSS component.
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.
In thecolumn, select .
In thewindow, select the uninitialized or logical disk to be used and click .
A warning message appears. Read the message. If you choose to proceed, click. This returns you to the iManager Administration page.
In thecolumn, select .
Awindow appears. Name your pool, then click .
Anotherwindow appears. Select your device and assign its space, then click . This returns you to the iManager Administration page.
In thecolumn, select . Confirm that your new pool is in the column.
You now need to create a new volume in iManager. In thecolumn, select . A window appears.
Clickto create a new volume.
Awindow appears, prompting you to enter your new volume name. Name your name volume, then click .
Anotherwindow appears, prompting you to select a pool and volume quota. Fill in the appropriate information, then click .
A finalwindow appears, prompting you to fill in attribute information. Fill in the appropriate information, then click .
You have successfully created a new disk, pool, and volume. NSS is now operational.
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.
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.
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.
Locate the GroupWise configuration file on the server. This file is located opt/novell/groupwise/agents/share/gwia.cfg.
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.
Restart the GroupWise internet agent by entering the command /etc/initd/grpwise restart gwia.gwdom
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.
Launch ConsoleOne and click on the [ROOT] of your tree.
From the menu bar go to Tools > GroupWise System Operations > Internet Addressing
Click on the Create button and add your domain address (yourdomain.com) and click Ok.
Restart GroupWise by entering the command /etc/init.d/grpwise restart
The following commands need to be run once the installation of ClamAV has been completed successfully.
At the server you will need to run the following commands
Start ClamAV by entering the following command: /etc/init.d/clamd start
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.
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.
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
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 the Novell International Trade Services Web page for more information on exporting Novell software. Novell assumes no responsibility for your failure to obtain any necessary export approvals.
Copyright © 2009 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 on the Novell Legal Patents Web page and one or more additional patents or pending patent applications in the U.S. and in other countries.
For Novell trademarks, see the Novell Trademark and Service Mark list.
All third-party trademarks are the property of their respective owners.