Novell Open Workgroup Suite Small Business Edition 1.0 SP1 Readme

January 31, 2008

1.0 Documentation

The following sources provide information about Novell® Open Workgroup Suite Small Business Edition:

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 Installation

2.1.1 Planning for Existing Data

IMPORTANT:If you install NOWS SBE on hardware that has an existing data partition, all data on the drive will be removed, and all partitions will be overwritten. Verify that there is no data on the disk prior to installing the NOWS SBE server.

For suggestions on how to manage installation with existing data, see TID 3733516.

2.1.2 Installation Devices

Most SATA drives are supported by this software. However, if your SATA drive does not work, you can use an external drive to install NOWS SBE.

If your server does not have a DVD drive, or if it has a DVD drive that is not supported by Open Enterprise Server (OES) 1 drivers (such as a SATA drive), it is possible to install from an external DVD drive connected to the USB port if the BIOS supports booting from a USB device. Simply connect the external DVD drive to the USB port and set the boot order and priority in the BIOS to the USB drive.

2.1.3 Install Username

After your installation is complete, a username and password screen appear. Do not change the automatically provided username, which is sbsadmin. The password, however, is user specific.

2.1.4 Installing Without a DHCP Server

It is much simpler to install the NOWS SBE server if a DHCP server is available. However, if a DHCP server is not available to provide an IP address to the NOWS SBE server during install, you can use YaST to manually configure a static IP address.

  1. After the NOWS SBE server installation is complete, you receive an error message indicating that no IP address was found. Press Enter to acknowledge the error.

  2. Log in to the server console as root. There is no password at this point.

  3. Right-click the console screen and select Open Terminal.

  4. Enter yast to launch the YaST configuration utility.

  5. Select Network Devices> Network Card.

  6. Click Change >Edit, then specify a static IP address and the subnet mask.

  7. Select Host Name and Name Server and specify the hostname, domain name, and name server (DNS) addresses.

  8. Select Routing and specify a default gateway.

  9. Click OK > Finish > Quit to exit YaST.

  10. Enter init 6 to reboot the server.

  11. Upon reboot, the console screen specifies the address to begin the Web configuration. On the Network Settings page of the Web configuration, specify all of this information again.

2.1.5 Configuration

The DNS and DHCP components do not provide a tool for making configuration changes. You can uninstall DNS or DHCP and then reinstall to change the configuration, or you can simply make the changes manually.


  • Edit the Zone files under /var/lib/named/master

  • To start or stop, use /etc/init.d/named start/stop

  • For additional information, use man named


  • Edit /etc/dhcpd.conf

  • To start or stop, use /etc/init.d/dhcpd start/stop

  • For additional help, use man dhcpd, man dhcpd.conf, or man dhcpd-options

2.2 Migration

The NOWS SBE server allows you to create NCP™ volumes on Linux* file systems (NSS volumes are not available). For more information about migrating data from a traditional NetWare® server to a NOWS SBE Linux server, see TID 3219860.

2.3 File Systems

  • NSS File System configuration is not supported with NOWS SBE.

  • For additional information about Samba, see the OES Planning and Implementation Guide, Overview of File Services.

2.4 VPN Access

NOWS SBE does not provide a configuration tool for site-to-site VPN access, but you can set up this access manually.

For additional information about VPN setup, see TID 3165776.

2.5 Novell Clients

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

2.6 Helpdesk E-Mail Address

After Helpdesk installation is completed, you must create an e-mail account to be used to notify Helpdesk users of the status of their incidents. The e-mail account can be set up in GroupWise® or an alternative e-mail server. The e-mail address forwards e-mails submitted to Helpdesk to employees when employee Type == helpdesk.

NOTE:The helpdesk username is helpdeskadmin.

2.7 Simba Commands

The NOWS SBE 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 and restart Simba, use the following commands: /etc/init.d/simba stop, then /etc/init.d/simba start

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

2.8 OpenOffice

The OpenOffice 2.1 application for Windows does not install automatically. The installation program runs WinZip. Clicking Unzip extracts the install files. It does not auto-launch Setup.exe. The default location of the file extraction is <Drive>:\Documents and Settings\<user name>\Local Settings\Temp\Setup.exe.

Execute Setup.exe to install OpenOffice for Windows.

2.9 Creating an iFolder User

If you create a user after installing the Novell iFolder® component, iFolder might require up to 24 hours to recognize the user. To update the iFolder more quickly, go to the iFolder Administration page and click System and LDAP. Under the LDAP tab, click Update and Synchronize Now. This forces iFolder to enable new users.

2.10 QuickBooks Portable Backups

Restoring QuickBooks Portable Backups does not work on NOWS SBE. These backups need to be restored on a local workstation, then moved to the NOWS SBE share.

2.11 No Support for Clustering

This release of the product does not support clustering.

2.12 Password Characters

Passwords can no longer contain the following characters: \ ' ` " * ! &.

2.13 License Key Failure

If your license key fails, make sure that Rug is activated.To do so, log in to the console on the command line, using /etc/init.d/rcd restart

3.0 Open Source Code

Novell, hereby, offers to give any third party a complete machine-readable copy of the source code of Amanda, Clam, DLU, HylaFAX*, Mailscanner, OpenVNC, 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 published 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 (® , ™, etc.) denotes a Novell trademark; an asterisk (*) denotes a third-party trademark.